Avaya Home Security System 03-300430 User manual

Maintenance Alarms for
Avaya Communication Manager 3.0,
Media Gateways and Servers
03-300430
Issue 1
June 2005
Copyright 2005, Avaya Inc.
All Rights Reserved
Notice
Every effort was made to ensure that the information in this document
was complete and accurate at the time of printing. However, information
is subject to change.
Warranty
Avaya Inc. provides a limited warranty on this product. Refer to your
sales agreement to establish the terms of the limited warranty. In
addition, Avaya’s standard warranty language as well as information
regarding support for this product, while under warranty, is available
through the following Web site: http://www.avaya.com/support.
Preventing Toll Fraud
"Toll fraud" is the unauthorized use of your telecommunications system
by an unauthorized party (for example, a person who is not a corporate
employee, agent, subcontractor, or is not working on your company's
behalf). Be aware that there may be a risk of toll fraud associated with
your system and that, if toll fraud occurs, it can result in substantial
additional charges for your telecommunications services.
Avaya Fraud Intervention
If you suspect that you are being victimized by toll fraud and you need
technical assistance or support, in the United States and Canada, call the
Technical Service Center's Toll Fraud Intervention Hotline at
1-800-643-2353.
Disclaimer
Avaya is not responsible for any modifications, additions or deletions to
the original published version of this documentation unless such
modifications, additions or deletions were performed by Avaya. Customer
and/or End User agree to indemnify and hold harmless Avaya, Avaya's
agents, servants and employees against all claims, lawsuits, demands
and judgments arising out of, or in connection with, subsequent
modifications, additions or deletions to this documentation to the extent
made by the Customer or End User.
How to Get Help
For additional support telephone numbers, go to the Avaya support Web
site: http://www.avaya.com/support. If you are:
•
Within the United States, click the Escalation Management
link. Then click the appropriate link for the type of support you
need.
•
Outside the United States, click the Escalation Management
link. Then click the International Services link that includes
telephone numbers for the international Centers of
Excellence.
Providing Telecommunications Security
Telecommunications security (of voice, data, and/or video
communications) is the prevention of any type of intrusion to (that is,
either unauthorized or malicious access to or use of) your company's
telecommunications equipment by some party.
Your company's "telecommunications equipment" includes both this
Avaya product and any other voice/data/video equipment that could be
accessed via this Avaya product (that is, "networked equipment").
An "outside party" is anyone who is not a corporate employee, agent,
subcontractor, or is not working on your company's behalf. Whereas, a
"malicious party" is anyone (including someone who may be otherwise
authorized) who accesses your telecommunications equipment with
either malicious or mischievous intent.
Such intrusions may be either to/through synchronous (time-multiplexed
and/or circuit-based), or asynchronous (character-, message-, or
packet-based) equipment, or interfaces for reasons of:
•
Utilization (of capabilities special to the accessed equipment)
•
Theft (such as, of intellectual property, financial assets, or toll
facility access)
•
Eavesdropping (privacy invasions to humans)
•
Mischief (troubling, but apparently innocuous, tampering)
•
Harm (such as harmful tampering, data loss or alteration,
regardless of motive or intent)
Be aware that there may be a risk of unauthorized intrusions associated
with your system and/or its networked equipment. Also realize that, if
such an intrusion should occur, it could result in a variety of losses to your
company (including but not limited to, human/data privacy, intellectual
property, material assets, financial resources, labor costs, and/or legal
costs).
Responsibility for Your Company’s Telecommunications Security
The final responsibility for securing both this system and its networked
equipment rests with you - Avaya’s customer system administrator, your
telecommunications peers, and your managers. Base the fulfillment of
your responsibility on acquired knowledge and resources from a variety
of sources including but not limited to:
•
Installation documents
•
System administration documents
•
Security documents
•
Hardware-/software-based security tools
•
Shared information between you and your peers
•
Telecommunications security experts
To prevent intrusions to your telecommunications equipment, you and
your peers should carefully program and configure:
•
Your Avaya-provided telecommunications systems and their
interfaces
•
Your Avaya-provided software applications, as well as their
underlying hardware/software platforms and interfaces
•
Any other equipment networked to your Avaya products
TCP/IP Facilities
Customers may experience differences in product performance, reliability
and security depending upon network configurations/design and
topologies, even when the product performs as warranted.
Standards Compliance
Avaya Inc. is not responsible for any radio or television interference
caused by unauthorized modifications of this equipment or the
substitution or attachment of connecting cables and equipment other
than those specified by Avaya Inc. The correction of interference caused
by such unauthorized modifications, substitution or attachment will be the
responsibility of the user. Pursuant to Part 15 of the Federal
Communications Commission (FCC) Rules, the user is cautioned that
changes or modifications not expressly approved by Avaya Inc. could
void the user’s authority to operate this equipment.
Product Safety Standards
This product complies with and conforms to the following international
Product Safety standards as applicable:
Safety of Information Technology Equipment, IEC 60950, 3rd Edition, or
IEC 60950-1, 1st Edition, including all relevant national deviations as
listed in Compliance with IEC for Electrical Equipment (IECEE) CB-96A.
Safety of Information Technology Equipment, CAN/CSA-C22.2
No. 60950-00 / UL 60950, 3rd Edition, or CAN/CSA-C22.2 No.
60950-1-03 / UL 60950-1.
Safety Requirements for Customer Equipment, ACA Technical Standard
(TS) 001 - 1997.
One or more of the following Mexican national standards, as applicable:
NOM 001 SCFI 1993, NOM SCFI 016 1993, NOM 019 SCFI 1998.
The equipment described in this document may contain Class 1 LASER
Device(s). These devices comply with the following standards:
•
EN 60825-1, Edition 1.1, 1998-01
•
21 CFR 1040.10 and CFR 1040.11.
The LASER devices used in Avaya equipment typically operate within the
following parameters:
Typical Center Wavelength
Maximum Output Power
830 nm - 860 nm
-1.5 dBm
1270 nm - 1360 nm
-3.0 dBm
1540 nm - 1570 nm
5.0 dBm
Luokan 1 Laserlaite
Klass 1 Laser Apparat
Use of controls or adjustments or performance of procedures other than
those specified herein may result in hazardous radiation exposures.
Contact your Avaya representative for more laser product information.
Electromagnetic Compatibility (EMC) Standards
This product complies with and conforms to the following international
EMC standards and all relevant national deviations:
Limits and Methods of Measurement of Radio Interference of Information
Technology Equipment, CISPR 22:1997 and EN55022:1998.
Information Technology Equipment - Immunity Characteristics - Limits
and Methods of Measurement, CISPR 24:1997 and EN55024:1998,
including:
•
Electrostatic Discharge (ESD) IEC 61000-4-2
•
Radiated Immunity IEC 61000-4-3
•
Electrical Fast Transient IEC 61000-4-4
•
Lightning Effects IEC 61000-4-5
•
Conducted Immunity IEC 61000-4-6
•
Mains Frequency Magnetic Field IEC 61000-4-8
•
Voltage Dips and Variations IEC 61000-4-11
Power Line Emissions, IEC 61000-3-2: Electromagnetic compatibility
(EMC) - Part 3-2: Limits - Limits for harmonic current emissions.
Power Line Emissions, IEC 61000-3-3: Electromagnetic compatibility
(EMC) - Part 3-3: Limits - Limitation of voltage changes, voltage
fluctuations and flicker in public low-voltage supply systems.
Federal Communications Commission Statement
Part 15:
Note: This equipment has been tested and found to comply with
the limits for a Class A digital device, pursuant to Part 15 of the
FCC Rules. These limits are designed to provide reasonable
protection against harmful interference when the equipment is
operated in a commercial environment. This equipment
generates, uses, and can radiate radio frequency energy and, if
not installed and used in accordance with the instruction
manual, may cause harmful interference to radio
communications. Operation of this equipment in a residential
area is likely to cause harmful interference in which case the
user will be required to correct the interference at his own
expense.
Part 68: Answer-Supervision Signaling
Allowing this equipment to be operated in a manner that does not provide
proper answer-supervision signaling is in violation of Part 68 rules. This
equipment returns answer-supervision signals to the public switched
network when:
•
answered by the called station,
•
answered by the attendant, or
•
routed to a recorded announcement that can be administered
by the customer premises equipment (CPE) user.
This equipment returns answer-supervision signals on all direct inward
dialed (DID) calls forwarded back to the public switched telephone
network. Permissible exceptions are:
•
A call is unanswered.
•
A busy tone is received.
•
A reorder tone is received.
Avaya attests that this registered equipment is capable of providing users
access to interstate providers of operator services through the use of
access codes. Modification of this equipment by call aggregators to block
access dialing codes is a violation of the Telephone Operator Consumers
Act of 1990.
Means of Connection
Connection of this equipment to the telephone network is shown in the
following tables.
For MCC1, SCC1, CMC1, G600, and G650 Media Gateways:
Manufacturer’s Port
Identifier
FIC Code
SOC/
REN/
A.S. Code
Network
Jacks
Off premises station
OL13C
9.0F
RJ2GX,
RJ21X,
RJ11C
DID trunk
02RV2-T
0.0B
RJ2GX,
RJ21X
CO trunk
02GS2
0.3A
RJ21X
02LS2
0.3A
RJ21X
Tie trunk
TL31M
9.0F
RJ2GX
Basic Rate Interface
02IS5
6.0F, 6.0Y
RJ49C
1.544 digital interface
04DU9-BN
6.0F
RJ48C,
RJ48M
04DU9-IKN
6.0F
RJ48C,
RJ48M
04DU9-ISN
6.0F
RJ48C,
RJ48M
04DU9-DN
6.0Y
RJ48C
120A4 channel service
unit
For G350 and G700 Media Gateways:
Manufacturer’s Port
Identifier
FIC Code
SOC/
REN/
A.S. Code
Network
Jacks
Ground Start CO trunk
02GS2
1.0A
RJ11C
DID trunk
02RV2-T
AS.0
RJ11C
Loop Start CO trunk
02LS2
0.5A
RJ11C
1.544 digital interface
04DU9-BN
6.0Y
RJ48C
04DU9-DN
6.0Y
RJ48C
04DU9-IKN
6.0Y
RJ48C
04DU9-ISN
6.0Y
RJ48C
02IS5
6.0F
RJ49C
Basic Rate Interface
REN Number
For MCC1, SCC1, CMC1, G600, and G650 Media Gateways:
This equipment complies with Part 68 of the FCC rules. On either the
rear or inside the front cover of this equipment is a label that contains,
among other information, the FCC registration number, and ringer
equivalence number (REN) for this equipment. If requested, this
information must be provided to the telephone company.
For G350 and G700 Media Gateways:
This equipment complies with Part 68 of the FCC rules and the
requirements adopted by the ACTA. On the rear of this equipment is a
label that contains, among other information, a product identifier in the
format US:AAAEQ##TXXXX. The digits represented by ## are the ringer
equivalence number (REN) without a decimal point (for example, 03 is a
REN of 0.3). If requested, this number must be provided to the telephone
company.
For all media gateways:
The REN is used to determine the quantity of devices that may be
connected to the telephone line. Excessive RENs on the telephone line
may result in devices not ringing in response to an incoming call. In most,
but not all areas, the sum of RENs should not exceed 5.0. To be certain
of the number of devices that may be connected to a line, as determined
by the total RENs, contact the local telephone company.
REN is not required for some types of analog or digital facilities.
For all media gateways:
If the terminal equipment (for example, the media server or media
gateway) causes harm to the telephone network, the telephone company
will notify you in advance that temporary discontinuance of service may
be required. But if advance notice is not practical, the telephone
company will notify the customer as soon as possible. Also, you will be
advised of your right to file a complaint with the FCC if you believe it is
necessary.
The telephone company may make changes in its facilities, equipment,
operations or procedures that could affect the operation of the
equipment. If this happens, the telephone company will provide advance
notice in order for you to make necessary modifications to maintain
uninterrupted service.
If trouble is experienced with this equipment, for repair or warranty
information, please contact the Technical Service Center at
1-800-242- 2121 or contact your local Avaya representative. If the
equipment is causing harm to the telephone network, the telephone
company may request that you disconnect the equipment until the
problem is resolved.
A plug and jack used to connect this equipment to the premises wiring
and telephone network must comply with the applicable FCC Part 68
rules and requirements adopted by the ACTA. A compliant telephone
cord and modular plug is provided with this product. It is designed to be
connected to a compatible modular jack that is also compliant. It is
recommended that repairs be performed by Avaya certified technicians.
The equipment cannot be used on public coin phone service provided by
the telephone company. Connection to party line service is subject to
state tariffs. Contact the state public utility commission, public service
commission or corporation commission for information.
This equipment, if it uses a telephone receiver, is hearing aid compatible.
Canadian Department of Communications (DOC) Interference
Information
This Class A digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe A est conforme à la norme
NMB-003 du Canada.
This equipment meets the applicable Industry Canada Terminal
Equipment Technical Specifications. This is confirmed by the registration
number. The abbreviation, IC, before the registration number signifies
that registration was performed based on a Declaration of Conformity
indicating that Industry Canada technical specifications were met. It does
not imply that Industry Canada approved the equipment.
Installation and Repairs
Before installing this equipment, users should ensure that it is
permissible to be connected to the facilities of the local
telecommunications company. The equipment must also be installed
using an acceptable method of connection. The customer should be
aware that compliance with the above conditions may not prevent
degradation of service in some situations.
Repairs to certified equipment should be coordinated by a representative
designated by the supplier. Any repairs or alterations made by the user to
this equipment, or equipment malfunctions, may give the
telecommunications company cause to request the user to disconnect
the equipment.
Declarations of Conformity
United States FCC Part 68 Supplier’s Declaration of Conformity (SDoC)
Avaya Inc. in the United States of America hereby certifies that the
equipment described in this document and bearing a TIA TSB-168 label
identification number complies with the FCC’s Rules and Regulations 47
CFR Part 68, and the Administrative Council on Terminal Attachments
(ACTA) adopted technical criteria.
Avaya further asserts that Avaya handset-equipped terminal equipment
described in this document complies with Paragraph 68.316 of the FCC
Rules and Regulations defining Hearing Aid Compatibility and is deemed
compatible with hearing aids.
Copies of SDoCs signed by the Responsible Party in the U. S. can be
obtained by contacting your local sales representative and are available
on the following Web site: http://www.avaya.com/support.
All Avaya media servers and media gateways are compliant with FCC
Part 68, but many have been registered with the FCC before the SDoC
process was available. A list of all Avaya registered products may be
found at: http://www.part68.org by conducting a search using "Avaya" as
manufacturer.
European Union Declarations of Conformity
Avaya Inc. declares that the equipment specified in this document
bearing the "CE" (Conformité Europeénne) mark conforms to the
European Union Radio and Telecommunications Terminal Equipment
Directive (1999/5/EC), including the Electromagnetic Compatibility
Directive (89/336/EEC) and Low Voltage Directive (73/23/EEC).
Copies of these Declarations of Conformity (DoCs) can be obtained by
contacting your local sales representative and are available on the
following Web site: http://www.avaya.com/support.
Japan
This is a Class A product based on the standard of the Voluntary Control
Council for Interference by Information Technology Equipment (VCCI). If
this equipment is used in a domestic environment, radio disturbance may
occur, in which case, the user may be required to take corrective actions.
To order copies of this and other documents:
Call:
Avaya Publications Center
Voice 1.800.457.1235 or 1.207.866.6701
FAX 1.800.457.1764 or 1.207.626.7269
Write: Globalware Solutions
200 Ward Hill Avenue
Haverhill, MA 01835 USA
Attention: Avaya Account Management
E-mail: [email protected]
For the most current versions of documentation, go to the Avaya support
Web site: http://www.avaya.com/support.
Contents
About this book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
Structure of book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
Audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
Downloading this book and updates from the Web . . . . . . . . . . . . . . . . . . . . . . . .
17
Safety labels and security alert labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18
Safety precautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18
Related resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
19
Technical assistance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
Sending us comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22
How to use this Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
22
Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23
Conventions used in this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
24
Useful terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26
Chapter 1: Server Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27
Background Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
29
Alarm-Related LEDs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30
Alarm Content . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
30
QOS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
Alarm Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
Alarms in Linux Media Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32
S8710 Alarms
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2: Denial Events
Event Type number ranges
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
121
125
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
126
Event Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
127
Denial Event Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
177
Chapter 3: LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
255
Alarm levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
255
Terminal alarm notification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
256
Attendant console LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
257
Circuit pack LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
257
Avaya Ethernet Switch LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
268
Issue 1 June 2005
5
Contents
UPS LEDs
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
269
IPSI LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
270
650A Power supply LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
273
655A Power Supply LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
273
Duplication memory card LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
274
S8710 Media Server LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
276
S8700 Media Server LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
279
S8500 Media Server LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
282
S8300 Media Server LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
283
G700 and Media Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
288
Chapter 4: G700 Media Gateway Traps. . . . . . . . . . . . . . . . . . . . . . . . . .
301
SNMP Alarming on the G700 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
301
G700 Alarm Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
304
G700 Traps and Resolutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
305
Chapter 5: Communication Manager Maintenance-Object Repair
Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
325
Subsystems Maintained by Communication Manager . . . . . . . . . . . . . . . . . . . . . .
326
Viewing Communication Manager Alarms. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
329
Command Syntax
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
329
Abort Code 1412 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
331
Escalation Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
331
ABRI-PORT (ASAI ISDN-BRI Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
332
AC-POWER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
333
ADM-CONN (Administered Connection) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
341
ADX8D-BD (AUDIX Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
344
ADX8D-PT (AUDIX Digital Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
345
ADX16D-B (16-Port AUDIX Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
353
ADX16A-BD (AUDIX Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
354
ADX16D-P (16-Port AUDIX Digital Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
355
ADX16A-PT (AUDIX Analog Line/Control Link) . . . . . . . . . . . . . . . . . . . . . . . . . .
363
AESV-LNK (AE Services Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
371
AESV-SESS (AE Services Session). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
375
ALARM-PT (Alarm Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
378
ANL-16-L (16-Port Analog Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
384
ANL-BD (Analog Line Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
403
6 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Contents
ANL-LINE (8-Port Analog Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
404
ANL-NE-L (8-Port Analog Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
425
AN-LN-PT (Analog Line Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
426
ANN-BD (Announcement circuit pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
447
ANN-PT (announcement port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
465
ANNOUNCE (announce) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
477
ASAI-ADJ (ASAI Adjunct) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
481
ASAI-BD (Multi-Application Platform Board) . . . . . . . . . . . . . . . . . . . . . . . . . . .
482
ASAI-EPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
484
ASAI-PT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
494
ASAI-RES (TN800 reserve slot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
506
ATM-BCH (ATM B-Channel Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
507
ATM-DCH (ATM D-Channel Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
522
ATM-EI (Expansion Interface Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
525
ATM-INTF (TN2305/6) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
573
ATM-NTWK (ATM Network Error) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
576
ATM PNC-DUP (ATM PNC Duplication). . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
587
ATM-SGRP (ATM Signaling Group) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
598
ATM-SYNC (ATM Synchronization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
610
ATM-TRK (Circuit Emulation Service
Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
617
ATM-WSP (ATM WAN Spare Processor) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
649
ATT-ADJ (AvayaAdjunct) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
654
ATTE-AJ (Ethernet Avaya Adjunct) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
655
AUDIX-BD (AUDIX Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
656
AUDIX-PT (AUDIX Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
657
AUX-BD (Auxiliary Trunk Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
658
AUX-TRK (Auxiliary Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
659
AXA12-BD (AUDIX Circuit Packs). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
670
ADX8D-BD (Audix Circuit Packs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
672
AXD12-BD (Audix Circuit Packs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
673
AXA12-RS (AUDIX Reserve Slots) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
674
ADX8D-RS (AUDIX Reserve Slots) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
675
AXD12-RS (AUDIX Reserve Slots) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
676
BRI-BD (ISDN-BRI Line Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
677
BRI-DAT (ISDN-BRI Data Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
684
Issue 1 June 2005
7
Contents
BRI-PORT (ISDN-BRI Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
685
BRI-SET, Various Adjuncts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
708
BRI-DAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
736
CAB-CALM (Customer alarm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
737
CAB-EXFR (emergency transfer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
739
CAB-MTCE (Media Gateway Maintenance). . . . . . . . . . . . . . . . . . . . . . . . . . . .
744
CAB-PFL (Power Fan Lead). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
749
CAB-TEMP (Cabinet Temperature) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
753
CABINET (Cabinet Sensors) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
758
CARR-POW (Carrier Power Supply) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
770
CDR-LNK (Call Detail Recording Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
788
CLAN-BD (Control LAN Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
789
CLSFY-BD (Call Classifier Circuit Pack). . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
810
CLSFY-PT (Call Classifier Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
811
CO-BD (Central Office Trunk Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . .
816
CO-DS1 (DS1 CO Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
817
CO-TRK (Analog CO Trunk). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
835
CONFIG (System Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
862
CUST-ALM (Customer-Provided Alarming Device) . . . . . . . . . . . . . . . . . . . . . . . .
869
DAT-LINE (Data Line Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
870
DC-POWER (Single-Carrier Cabinet Environment) . . . . . . . . . . . . . . . . . . . . . . . .
880
DETR-BD (Tone Detector Circuit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
884
DID-BD (Direct Inward Dial Trunk Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . .
885
DID-DS1 (Direct Inward Dial Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
886
DID-TRK (Direct Inward Dial Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
898
DIG-BD (Digital Line Circuit Pack). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
915
DIG-IP-STN (Digital IP Station) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
916
DIG-LINE (Digital Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
924
DIOD-BD (DIOD Trunk Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
951
DIOD-DS1 (DS1 DIOD Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
952
DIOD-TRK (DIOD Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
964
DLY-MTCE (MO-DAILY) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
975
DS1-BD (DS1 Interface Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
978
DS1-FAC (DS1 Facility) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053
DS1C-BD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1077
DT-LN-BD (Data Line Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1114
8 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Contents
DTMR-PT (Dual-Tone Multifrequency Receiver Port) . . . . . . . . . . . . . . . . . . . . . . . 1115
E-DIG-BD (Multi Application Platform Board)
. . . . . . . . . . . . . . . . . . . . . . . . . . 1121
E-DIG-RES (TN800 reserve slot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1123
E-DIG-STA (Emulated Digital Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124
EMG-XFER (Emergency Transfer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1134
EPN-SNTY (PN Sanity Audit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1143
ERR-LOG (Error Log) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1145
ESS (Enterprise Survivable Server)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1146
ETH-PT (Control LAN Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1153
ETR-PT (Enhanced Tone Receiver Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1167
EXP-INTF (Expansion Interface Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1176
EXP-PN (Expansion Port Network) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235
EXT-DEV (External device alarm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1240
EXT-DEV ADMIN? N (External Device Alarm) . . . . . . . . . . . . . . . . . . . . . . . . . . 1243
EXT-DEV ADMIN? Y (External Device Alarm) . . . . . . . . . . . . . . . . . . . . . . . . . . 1246
FIBER-LK (Fiber Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1250
FW-DWNLD (Firmware Download) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1298
GPTD-PT (General-Purpose Tone Detector Port) . . . . . . . . . . . . . . . . . . . . . . . . . 1308
H323-BCH (H.323 B Channel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1313
H323-SGRP (H.323 Signaling Group). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1315
H323-STN (H.323 IP Station) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1323
HYB-BD (Hybrid Line Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1328
HYB-LINE (Hybrid Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1329
INADS (INADS Link). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1351
IPMEDPRO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1355
IPMEDPRO (TN2302 IP Media Processor) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1356
IPMEDPRO (TN2602AP IP Media Resource 320) . . . . . . . . . . . . . . . . . . . . . . . . 1380
IPSV-CTL (Ipserver Interface Control). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1405
IP-SVR (IP Server Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1415
ISDN-PLK (ISDN-PRI Signaling Link Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1423
ISDN-SGR (ISDN-PRI Signaling Group) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1429
ISDN-TRK (DS1 ISDN Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1446
JNL-PRNT (Journal Printer Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1475
LGATE-AJ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1476
LGATE-BD (ISDN-BRI Line Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1477
LGATE-PT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1478
Issue 1 June 2005
9
Contents
LIC-ERR (License-Error Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1479
LOG-SVN (Login Security Violation) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1487
MAINT (PN’s Maintenance Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1490
MAPD-BD (MAPD Interface Circuit Pack TN802) . . . . . . . . . . . . . . . . . . . . . . . . . 1508
MEDPRO (Media Processor MAPD Circuit Pack). . . . . . . . . . . . . . . . . . . . . . . . . 1539
MEDPRO-C (Media-Processor Control). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1551
MEDPROPT (TN802/TN2302/TN2602 MED PRO DSP PORT) . . . . . . . . . . . . . . . . . 1553
MET-BD (MET Line Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1560
MET-LINE (MET Line) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1561
MED-GTWY (MEDIA GATEWAY) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1581
MG-ANA (ANALOG MM711) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1583
MG-ANN (Voice Announcements) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1585
MG-BRI (BRI Trunk Media Module MM720). . . . . . . . . . . . . . . . . . . . . . . . . . . . 1586
MG-DCP (Digital Line Media Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1593
MG-DS1 (DS1 Interface Media Module). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1594
MG-IAMM (Integrated Analog Media Module). . . . . . . . . . . . . . . . . . . . . . . . . . . 1643
MG-ICC (Internal Call Controller) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1650
MG-VOIP (MM760 MED PRO DSP PORT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1651
MIS (Management Information System). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1654
MMI-BD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1655
MMI-LEV (Multimedia Interface Resource Level) . . . . . . . . . . . . . . . . . . . . . . . . . 1666
MMI-PT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1669
MMI-SYNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1675
MODEM-BD (Modem Pool Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1677
MODEM-PT (Modem Pool Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1678
M/T-ANL (Maintenance/Test Analog Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1696
M/T-BD (Maintenance/Test Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1705
M/T-DIG (Maintenance/Test Digital Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1709
M/T-PKT (Maintenance/Test Packet Bus Port) . . . . . . . . . . . . . . . . . . . . . . . . . . 1722
NO-LIC (No License) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1727
NR-CONN (Network-Region Connect) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1731
OPS-LINE (DS1 Off-Premises Station Line). . . . . . . . . . . . . . . . . . . . . . . . . . . . 1736
PDMODULE (Processor Data Module) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1751
PE-BCHL (PRI Endpoint Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1773
PKT-BUS (Packet Bus) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1790
PKT-INT (Packet Interface) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1799
10 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Contents
PLAT-ALM (Platform Alarms) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1838
PMS-LINK (Property Management System Link) . . . . . . . . . . . . . . . . . . . . . . . . . 1839
PMS-PRNT/JNL-PRNT (PMS Printer Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1846
PNC-DUP (PNC Duplication) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1851
POWER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1869
POW-SUP (power supply) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1881
PPP-PT (Control LAN Packet/Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1893
PRI-CDR (Call Detail Recording Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1905
PROC-SAN (Process Sanity Audits) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1911
PS-RGEN (Power supply ring generator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1912
RANL-STA (Remote Analog Line (Station) Port) . . . . . . . . . . . . . . . . . . . . . . . . . 1918
RDIG-STA (Remote Digital Station) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1926
REM-OFF (Remote Office) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1940
RING-GEN (Analog Ring Generator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1942
RMB (Remote Maintenance Board)
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1949
RMB-REPORT (Remote Maintenance Board - Report)
. . . . . . . . . . . . . . . . . . . . . 1950
RMC-ENV (Power/Fan Sensors) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1951
SEC-CDR (Call Detail Recording Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1956
SER-BUS (Serial communication bus) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1957
SIP-BCH (SIP B Channel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1968
SIP-SGRP (SIP Signaling Group) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1970
S-SYN-BD (Speech Synthesis Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . 1978
S-SYN-PT (Speech Synthesis Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1979
SN-CONF (Switch Node Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1992
SNC-BD (Switch Node Clock Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2000
SNC-LINK (Switch Node Clock Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2039
SNC-REF (Switch Node Clock Reference) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2043
SNI-BD (SNI Circuit Pack). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2046
SNI-PEER (SNI Peer Link) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2113
SRP-EPN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2117
STA-FWDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2118
STRAT-3 (Stratum-3 Clock) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2128
SVC-SLOT (Service Slot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2141
SYNC (Port-Network Synchronization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2143
SYS-LINK (System Links) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2175
SYS-PRNT (System Printer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2181
Issue 1 June 2005
11
Contents
SYSTEM (System) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2186
TBRI-BD
(TN2185 ISDN Trunk-Side BRI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2192
TBRI-PT (ISDN Trunk-Side BRI Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2200
TBRI-TRK (Trunk-Side ISDN BRI Channel) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2224
TDM-BUS (TDM Bus) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2237
TDM-CLK (TDM Bus Clock) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2252
TDMODULE (Trunk Data Module). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2268
TIE-BD (Tie Trunk Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2269
TIE-DS1 (DS1 Tie Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2270
TBRI-PT (ISDN Trunk-Side BRI Port) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2291
TIE-TRK (Analog Tie Trunk) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2302
TIME-DAY (Time of Day) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2326
TONE-BD (Tone-Clock Circuit) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2327
TONE-PT (Tone Generator) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2353
TR-LN-BD (Trunk Line Board) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2363
TSC-ADM (Administered Temporary
Signaling Connections) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2364
TTR-LEV (TTR Level) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2370
UDS1-BD (UDS1 Interface Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2374
VAL-BD (Voice Announcements
over LAN Circuit Pack) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2477
VAL-PT (Voice Announcements over LAN Packet/Port). . . . . . . . . . . . . . . . . . . . . . 2503
VC-BD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2509
VC-DSPPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2513
VC-LEV (Voice Conditioner DSP Port Level) . . . . . . . . . . . . . . . . . . . . . . . . . . . 2522
VC-SUMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2525
WAE-PORT (Wideband Access Endpoint Port) . . . . . . . . . . . . . . . . . . . . . . . . . . 2531
XXX-BD (Common Port Circuit Pack/Media Module) . . . . . . . . . . . . . . . . . . . . . . . 2539
Index
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2557
12 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
About this book
Overview
This document provides procedures to monitor, test, and maintain an Avaya Media Server or
Gateway system. It covers many of the faults and troubles that can occur and provides simple
procedures to correct them. Simple, traditional troubleshooting methods are sometimes
sufficient to locate and clear faults. The traditional methods include substitution, visual
inspections, continuity checks, and clarification of operating procedures with end users.
Using this documentation, the Avaya technicians and the technicians of their business partners
and customers should be able to follow detailed procedures for:
●
Monitoring, testing, and maintaining an Avaya Media Server, Media Gateway, and many
other system components.
●
Using troubleshooting methods to clear faults.
●
Required replacements, visual inspections, continuity checks, and clarifying operating
procedures with end users.
Document set
Although this maintenance book is published separately, it is part of a set:
●
03-300190 Maintenance Alarms Reference (formerly 555-245-102)
●
03-300191 Maintenance Commands Reference (formerly 555-245-101)
●
03-300192 Maintenance Procedures Reference (formerly 555-245-103)
Equipment/platforms
This book contains information about the following equipment/platforms
●
Avaya S8700/S8710 Media Servers
●
Avaya S8500 Media Servers
●
Avaya S8300 Media Servers
●
Avaya G700/G650/G600/MCC/SCC Media Gateways
Issue 1 June 2005
13
About this book
It does not contain information about
●
DEFINITY G3R (see 555-233-117: Maintenance for DEFINITY R Servers or 555-233-142:
Maintenance for Avaya S8700 Media Servers with G600 Media Gateway)
●
DEFINITY SI (see 555-233-119: Maintenance for DEFINITY SI Servers or 555-233-143:
Avaya S8700 Media Servers with MCC1/SCC1)
●
Avaya S8100 Media Server (see 555-233-123: Maintenance for DEFINITY CSI Servers)
●
IBM eServer BladeCenter HS20 Type 8832
●
G150/G250/G350 Media Gateways
Structure of book
The following document contains combined Maintenance Alarms information for:
●
S8300, S8500, and S8700 media servers
●
MCC1, SCC1, and CMC1 media gateways
●
G600, G650, and G700 media gateways
The document includes new information developed for Communication Manager Release 2.0,
and preexisting or modified information brought together from Release 1.3 maintenance
documentation.
This document is the first of three reference documents:
●
Maintenance Alarms Reference (555-245-102)
●
Maintenance Commands Reference (03-300191)
●
Maintenance Procedures (03-300192)
The basis for these reference documents was the Release 1.3 S8700 media server with the
MCC1 and SCC1 media gateways maintenance document. To this document were added
Release 1.3 maintenance information for the S8300 media server, the G700, G600 and CMC1
media gateways, as well as new material developed for the S8500 media server and G650
media gateway.
In order to present maintenance information from all these sources side-by-side, when it was
not clear from a chapter or section title, marking conventions were adopted to delineate material
specific to a particular source. The markers act on three levels:
●
Chapters or Maintenance Objects (MOs)
●
Major and minor sections
●
Paragraphs or in-line comments
14 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Structure of book
Chapters or Maintenance Objects (MOs)
At the Chapter or MO level, bold names of the server(s) or gateway(s) that are represented
within the sections to follow are inserted immediately after the Chapter title or MO title. For
example, the heading for the SER-BUS (Serial communication bus) MO looks like:
SER-BUS (Serial communication bus)
G650
The G650 after the title indicates that the material in this MO relates to the G650 media gateway.
Major and minor sections
At the Major and minor sections level, a similar bold name along with a ruled line delineates the
beginning of a section of material specific to the media server or gateway identified. At the
conclusion of the section, another ruled line marks the end of the specific material and a return
to common text. For example, a section of material specific to the S8700 or S8500 media server
looks like:
S8700 | 8710 / S8500
1. If only 1 analog circuit pack in the system has this problem, replace the circuit pack.
2. If only analog circuit packs on a particular carrier have this error, the ringing generator
may not be connected to this carrier.
3. If analog circuit packs on many carriers have this error, it is probably a problem with the
ringing generator.
Such sections can occasionally extend for several pages.
Issue 1 June 2005
15
About this book
Paragraphs or in-line comments
At the paragraph level and for comments in-line, the specific media server or gateway is
indicated by its bold name, and the parenthetical information follows immediately afterward. For
example, a paragraph insert for the S8700 and S8500 media servers might looks like:
1. If the Tone-Clock circuit is a slave clock, then the EI to which it is listening is providing a bad
timing source. Follow the diagnostic procedures specified for TDM-CLK Error Code 2305.
2. S8700 | 8710 / S8500: If no problem can be found with the incoming synchronization signal,
replace the IPSI or Tone-Clock circuit pack. See Replacing the IPSI or Tone-Clock Circuit
Pack on page 2337.
In such cases, it is not necessary to delineate the beginning and end of the material.
An example of an in-line comment might look like:
3. Error Type 1: There is a serial number mismatch between the hardware serial number and
installed license file (S8700 | 8710 / S8500: there is a serial-number mismatch of the reference
IPSI and a subsequent License Error failure. S8300: there is a serial-number mismatch of the
G700 motherboard on which the serial number resides and a subsequent License Error
failure). This error is caused by the:
●
●
S8700 | 8710 / S8500: Reference IPSI not responding
S8300: G700 motherboard not responding
Expiration of the 10-day timer
The system enters No-License mode.
It is hoped that, by these techniques, material specific to several different sources can be
combined and viewed side-by-side without confusion.
Audience
The information in this book is intended for use by:
Avaya technicians, provisioning specialists, business partners, and customers, specifically:
●
Trained Avaya technicians
●
A maintenance technician dispatched to a customer site in response to a trouble alarm or
a user trouble report
●
A maintenance technician located at a remote maintenance facility
●
The customer’s assigned maintenance technician
The technician is expected to have a knowledge of telecommunications fundamentals and
of the particular Avaya Media Server and/or Media Gateway to the extent that the
procedures in this book can be performed, in most cases, without assistance.
16 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Downloading this book and updates from the Web
This book is not intended to solve all levels of troubles. It is limited to troubles that can be solved
using:
●
The Alarm Log
●
The Error Log
●
Trouble-clearing procedures
●
Maintenance tests
●
Traditional troubleshooting methods
If the trouble still has not been 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.
Downloading this book and updates from the Web
You can download the latest version of this book from the Avaya Web site. You must have
access to the Internet, and a copy of Acrobat Reader must be installed on your personal
computer.
Avaya makes every effort to ensure that the information in this book is complete and accurate.
However, information can change after we publish this book. Therefore, the Avaya Web site
might also contain new product information and updates to the information in this book. You can
also download these updates from the Avaya Web site.
Downloading this book
To download the latest version of this book:
1. Access the Avaya web site at http://support.avaya.com.
2. At the top center of the page, click Product Documentation.
The system displays the Welcome to Product Documentation page.
3. In the upper-left corner type the 9-digit book number in the Search Support field, and then
click Go.
The system displays the Product Documentation Search Results page.
4. Scroll down to find the latest issue number, and then click the book title that is to the right of
the latest issue number.
5. On the next page, scroll down and click one of the following options:
●
PDF Format to download the book in regular PDF format
●
ZIP Format to download the book in zipped PDF format
Issue 1 June 2005
17
About this book
Safety labels and security alert labels
Observe all caution, warning, and danger statements to help prevent loss of service, equipment
damage, personal injury, and security problems. This book uses the following safety labels and
security alert labels:
! CAUTION:
A caution statement calls attention to a situation that can result in harm to
software, loss of data, or an interruption in service.
CAUTION:
!
WARNING:
A warning statement calls attention to a situation that can result in harm to
hardware or equipment.
!
DANGER:
A danger statement calls attention to a situation that can result in harm to
personnel.
!
SECURITY ALERT:
A security alert calls attention to a situation that can increase the potential for
unauthorized use of a telecommunications system.
WARNING:
DANGER:
SECURITY ALERT:
Safety precautions
When performing maintenance or translation procedures on the system, users must observe
certain precautions. Observe all caution, warning, and danger admonishments to prevent loss
of service, possible equipment damage, and possible personal injury. In addition, the following
precautions regarding electromagnetic interference (EMI) and static electricity must be
observed:
Electromagnetic interference
This equipment generates, uses, and can radiate radio frequency energy. Electromagnetic
fields radiating from the switch may cause noise in the customer’s equipment. If the equipment
is not installed and used in accordance with the instruction book, radio interference may result.
!
WARNING:
WARNING:
To maintain the EMI integrity of the system, maintenance personnel must ensure
that all cabinet panels, covers, and so forth, are firmly secured before leaving the
customer’s premises.
18 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Related resources
Related resources
Table 1: Additional document resources on page 19 lists additional documentation that is
available for you, and which has been referenced within this document.
Table 1: Additional document resources
Document
Number
Avaya Enterprise Survivable Servers (ESS) User Guide, 03-300428
03-300428
Hardware Guide for Avaya Communication Manager, 555-245-207
555-245-207
Overview for Avaya Communication Manager, 03-300468
03-300468
Administrator Guide for Avaya Communication Manager, 03-300509
03-300509
Installation and Upgrades for the Avaya G700 Media Gateway Controlled by
an Avaya S8300 Media Server or an Avaya S8700 Media Server,
555-234-100
555-234-100
Maintenance Commands Reference (03-300191)
03-300431
Maintenance Procedures (03-300192)
03-300432
Maintenance for Avaya DEFINITY® Server R, 555-233-117
555-233-117
Avaya P333T User’s Guide
N/A
Avaya S8300 and Avaya S8700 Media Server Library, 555-233-825
555-233-825
EMBEDDED AUDIX System Maintenance, 585-300-110
585-300-110
DEFINITY AUDIX System Release 3.2.4 Maintenance, 585-300-110
585-300-110
AT&T Network and Data Connectivity, 555-025-201
555-025-201
Digital PBX Standards, RS4648
RS4648
User Manual Z3A Asynchronous Data Unit, 555-401-701
555-401-701
DEFINITY® Communications System Generic 1, Generic 2 and Generic 3
V1 and 2 – Integrated Channel Service Unit (CSU) Module Installation and
Operation, 555-230-193
555-230-193
DEFINITY® Communications System Generic 2.2 and Generic 3 V2 DS1/
CEPT1/ISDN-PRI Reference, 555-025-107
555-025-107
DEFINITY® Communications System Generic 1 and Generic 3i Wiring,
555-204-111
555-204-111
1 of 3
Issue 1 June 2005
19
About this book
Table 1: Additional document resources (continued)
Document
Number
Site Preparation, Installation, and Operator’s Manual, 167-405-035
167-405-035
Maintenance for the Avaya S8700 Media Server with an Avaya SCC1 Media
Gateway or an Avaya MCC1 Media Gateway, 555-233-143
555-233-143
Avaya MultiVantage Solutions Installation and Maintenance for Survivable
Remote EPN, 555-233-121
555-233-121
Installing the Avaya S8700 Media Server with the Avaya G600 Media
Gateway, the Avaya MCC1 Media Gateway, or the Avaya SCC1 Media
Gateway (Library CD)
Library CD
ATM Installation, Upgrades, and Administration using Avaya Communication
Manager, 555-233-124
555-233-124
Administration for Network Connectivity for Avaya Communication Manager,
555-233-504
555-233-504
Quick Start for Hardware Installation: Avaya S8700 Series Media Server,
555-245-703
555-245-703
Installing the Avaya S8700 Media Server with an Avaya G650 Media
Gateway, 555-245-109
555-245-109
Installing the S8500 Media Server with the G650 Media Gateway,
555-245-107
555-245-107
4606 IP Telephone User’s Guide, 555-233-775
555-233-775
4624 IP Telephone User’s Guide, 555-233-776
555-233-776
4612 IP Telephone User’s Guide, 555-233-777
555-233-777
Job Aid: Replacing the Avaya S8710 Media Server, 03-300146
03-300146
Job Aid: Replacing the Hard Drive in an Avaya S8710 Media Server,
03-300147
03-300147
Job Aids for Field Replacements for the Avaya S8700 Series Media Servers,
03-300530
03-300530
Job Aid: Replacing the Hard Drive in the S8700 Media Server (Pre-R2.0),
555-245-768
555-245-768
Job Aid: Replacing the Hard Drive in the S8700 Media Server (R2.x),
555-245-769
555-245-769
Job Aid: Replacing the S8500 Hard Drive, 555-245-761
555-245-761
Job Aid: Replacing the S8500 Remote Service Adapter, 555-245-759
555-245-759
2 of 3
20 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Technical assistance
Table 1: Additional document resources (continued)
Document
Number
Job Aid: Repacking the S8500 Dual Network Interface, 555-245-760
555-245-760
Job Aid: Replacing the G700 Media Gateway, 555-245-752
555-245-752
3 of 3
Technical assistance
Avaya provides the following resources for technical assistance.
Within the United States
For help with:
●
Feature Administration and system applications, call Avaya Technical Consulting Support
at 1-800-225-7585
●
Maintenance and repair, call the Avaya National Customer Care Support Line at
1-800-242-2121
●
Toll fraud, call Avaya Toll Fraud Intervention at 1-800-643-2353
International
For all international resources, contact your local Avaya authorized dealer for additional help.
Trademarks
All trademarks identified by the ® or ™ are registered trademarks or trademarks, respectively,
of Avaya Inc. All other trademarks are the property of their respective owners.
Issue 1 June 2005
21
About this book
Sending us comments
Avaya welcomes your comments about this book. To reach us by:
●
Mail, send your comments to:
Avaya Inc.
Product Documentation Group
Room B3-H13
1300 W. 120th Avenue
Westminster, CO 80234 USA
●
E-mail, send your comments to:
[email protected]
●
Fax, send your comments to:
1-303-538-1741
Ensure that you mention the name and number of this book.
How to use this Document
Most maintenance sessions involve analyzing the Alarm and Error Logs to diagnose a trouble
source and replacing a component such as a circuit pack or media module. The information in
Chapter 5: Communication Manager Maintenance-Object Repair Procedures of this reference
will generally suffice to address these needs. Certain complex elements of the system require a
more comprehensive approach. Special procedures for these elements appear in Chapter
4: General troubleshooting of Maintenance Procedures (03-300192).
Note:
Note:
This document is designed to be read online and in paper format. Because of the
large volume of information, additional cross-references have been added to
make it easier to locate information when using the manual online.
22 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Organization
Organization
Chapter 1: Server Alarms, contains information on alarms generated on various platforms,
including the S8300, S8500, and S8700 media server. These alarms cover such categories as
process watchdog, environmental, login, translation monitoring, and power supply alarms.
Alarm identifications, levels, and resolutions are given.
Chapter 2: Denial Events, contains information about denial events that are generated by Avaya
Communication Manager. Denial events are displayed via the Events Report (display
events screen) of Avaya Communication Manager.
Chapter 3: LEDs, contains information on the definition and interpretation of LED indicators to
be found on various system components, including servers, gateways, circuit packs, and media
modules.
Chapter 4: G700 Media Gateway Traps, contains information on traps that can occur on media
gateways. Trap identifications, alarm levels, trap descriptions, and recommended resolutions
are given.
Chapter 5: Communication Manager Maintenance-Object Repair Procedures, contains specific
troubleshooting and repair instructions for every component in the system. The maintenance
objects are listed alphabetically by name as they appear in the Alarm and Error Logs. Under
each maintenance object appears a description of the object’s function, tables for interpreting
alarm and error logs, and instructions on how to use tests, commands, and replacements to
resolve associated problems.
Issue 1 June 2005
23
About this book
Conventions used in this document
Table 2: Typography used in this book on page 24 lists the typographic conventions in this
document.
Table 2: Typography used in this book
To represent . . .
This typeface and syntax
are shown as . . .
●
Bold for literals
●
Bold italic for variables
●
Square brackets [ ]
around optional
parameters
●
“|” between exclusive
choices
SAT screen input
and output
●
Bold for input
●
Constant width for
output (screen
displays and
messages)
Linux commands
●
Constant-width bold for
literals
●
Constant-width bold
italics for variables
●
Square brackets []
around optional
arguments
●
“Or” sign | between
exclusive choices
SAT commands
Linux output
Constant width
For example, . . .
refresh ip-route [all | location]
Set the Save Translation
field to daily.
The message Command
successfully completed
should appear.
testmodem [-s] | [-t
arg]
Linux returns the message
almdisplay 4: Unable to
connect to MultiVantage.
1 of 2
24 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Conventions used in this document
Table 2: Typography used in this book (continued)
To represent . . .
Web interface
Keys
This typeface and syntax
are shown as . . .
●
Bold for menu
selections, tabs,
buttons, and field
names
●
Right arrow > to
separate a sequence
of menu selections
Special font for keyboard
keys and SAT screen
clickable buttons
For example, . . .
Select Alarms and
Notification, the appropriate
alarm, and then click Clear.
Select Diagnostics > View
System Logs, then click
Watchdog Logs.
Press Tab.
Click Next Page.
2 of 2
Other conventions used in this book:
●
Physical dimensions are in English [Foot Pound Second (FPS)] units, followed by metric
[Centimeter Gram Second) (CGS)] units in parentheses.
Wire-gauge measurements are in AWG, followed by the diameter in millimeters in
parentheses.
●
Circuit-pack codes (such as TN790B or TN2182B) are shown with the minimum
acceptable alphabetic suffix (like the “B” in the code TN2182B).
Generally, an alphabetic suffix higher than that shown is also acceptable. However, not
every vintage of either the minimum suffix or a higher suffix code is necessarily acceptable.
Issue 1 June 2005
25
About this book
Useful terms
Table 3: Terminology summary on page 26 summarizes some of the terms used in this book
and relates them to former terminology.
Table 3: Terminology summary
Present Terminology
Former Terminology
Communication Manager
MultiVantage
Avaya Call Processing
S8300 Media Server
ICC, Internal Call Controller
S8700 Media Server (or
non-co-resident S8300)
ECC, External Call Controller
MGP, Media Gateway Processor
860T Processor
Layer 2 Switching Processor
P330 Stack Processor
Cajun Stack Processor
i960 Processor
26 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Chapter 1: Server Alarms
S8700 | 8710 / S8500 / S8300
This chapter provides background information on server alarming. For detailed information on
G700 Media Gateway Traps, refer to Chapter 4: G700 Media Gateway Traps.
Introduction
During normal operations, software or firmware may detect error conditions pertaining to
specific Maintenance Objects (MOs) or other subsystems. The system automatically attempts
either to fix or circumvent these problems. Errors are detected in two ways:
●
Firmware on the component during ongoing operations
●
A “periodic test” or a “scheduled test” started by software
The technician can run tests on demand that are generally more comprehensive (and
potentially disruptive) than are the "scheduled tests".
When an error is detected, the maintenance software puts the error in the Error Log and
increments the error counter for that error. When an error counter is “active” (greater than 0),
there is a maintenance record for the MO. If a hardware component incurs too many errors, an
alarm is raised.
Alarms on the Linux media servers can occur in several areas:
●
Media Modules, Media 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, such as the G700, detect faults and alert the Media Server; the Media
Server then raises an alarm, and sends the alarm to an appropriate network management
site.
●
Communication Manager alarms reflect health status of network elements such as media
gateways, circuit packs, media modules, and their associated links, ports, and trunks.
●
Messaging alarms provide health status of embedded or external messaging systems.
Alarms may be viewed using the following:
●
Maintenance Web Interface
Provides alarms information related to Communication Manager, the media server, and
messaging.
Issue 1 June 2005
27
Server Alarms
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.
Note:
●
Media Server bash shell
Provides alarms information related to Communication Manager, the media server, and
messaging.
●
Media Server SAT CLI
Provides alarms information related to Communication Manager.
●
MGP CLI (on the G700 Media Gateway)
Provides alarms and traps information related to the G700 platform and its subsystems.
●
Layer 2 Switching Processor CLI (on the G700 Media gateway)
Provides information related to the media gateway stack.
Information related to Communication Manager, the media server, and messaging alarms can
be displayed using either the Maintenance Web Interface or the media server bash shell;
however, this document (Maintenance Alarms Reference (555-245-102)) provides maintenance
information only for Communication Manager (Chapter 5: Communication Manager
Maintenance-Object Repair Procedures)and media server alarms (Chapter 1: Server Alarms).
For messaging alarms and repair procedures, refer to the appropriate documentation for your
messaging system.
Alarm Classifications
Alarms are classified depending on their effect on system operation:
●
MAJOR alarms identify failures that cause a critical degradation of service. These alarms
require immediate attention.
●
MINOR alarms identify failures that cause some service degradation but that do not render
a crucial portion of the system inoperable. Minor alarms require attention. However,
typically a minor alarm affects only a few trunks, 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.
●
OFF-BOARD problems originate in a process or component that is external to the Media
Module.
28 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Background Terms
Background Terms
Table 4: Alarming Background Terms on page 29 gives a useful explanation of terms.
Table 4: Alarming Background Terms
Term
Explanation
TRAP
A trap is an event notification that is sent to the SNMP trap manager and
received from the Media Gateway Processor, Layer 2 Switching Processor,
or RTCP Monitor (Avaya VisAbility).
ALARM
Some traps are determined to be an alarm. If determined to be an alarm they
are sent to an appropriate alarm management site, such as INADS.
INADS
Initialization and Administration System, a software tool used by Avaya
services personnel to initialize, administer, and troubleshoot customer
communications systems remotely.
SNMP
Simple Network Management Protocol, the industry standard protocol
governing network management and the monitoring of network devices and
their functions.
RTCP
Real Time Control Protocol, contained in IETF RFC 1889.
ISM
Intelligent Site Manager, a VPN gateway on the customer’s LAN that
provides a means for services personnel to access the customer’s LAN in a
secure manner via the Internet.
VPN
Virtual Private Network, a private data network that makes use of the public
telecommunication infrastructure, maintaining privacy through the use of a
tunneling protocol and security procedures.
Issue 1 June 2005
29
Server Alarms
Alarm-Related LEDs
Table 5: Alarm-Related LEDs on page 30 shows alarm-related LEDs on the faceplate of the
G700 or on an attendant console, and shows how certain LEDs reflect specific alarm situations.
Table 5: Alarm-Related LEDs
LED
Location
Alarm-Related Cause
ALARM LED
Attendant Console
The system alarm causes the attendant console ALARM
LED to light.
ACK LED
Attendant Console
The ACK LED on the attendant console reflects the state
of acknowledgement of the alarm report from INADS.
However, this is only possible for S8700-based Media
Servers.
RED ALM or
ALARM LED
LED Panel of G700
Media Gateway
The RED ALM or ALARM LED indicates the "health" of
the G700 by lighting when there are impaired functions
of the Media Gateway Processor, Layer 2 Switching
Processor, or VOIP engine. It lights, for example, when
the power supply voltage is out of bounds, if the G700
cannot locate a Media Servers, or when the unit is
overheating. It also indicates when the system is in
Power-up mode, or when a Media Module is resetting.
Alarm Content
Alarms logged by Communication Manager are stored in an alarm log. All alarms include a date
and time stamp that reflects the date and time of the sending device. The alarm contains:
●
Device type
●
Component type
●
Device name
●
Current ip address
●
Additional information necessary for identification of alarm origination
●
Severity level to indicate the priority of the alarm
Alarms originating in a specific media server, such as an S8300, have a prefix denoting that of
an S8300.
30 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
QOS Alarms
QOS Alarms
An RTCP monitor using the local SNMP agent generates traps to a pre-administered trap
collector. The following QoS alarms are generated:
●
The voip-callqos alarm is generated if a single session exceeds configured QOS levels. It
can generate a warning or an SNMP trap. Warnings are used for less severe problems.
They can be accumulated internally within Avaya VoIP Monitoring Manager for use by the
alarms defined below.
●
The voip-systemqos alarm is generated if the number of voip-callqos warnings from all
terminals exceeds a configured count over a given period (e.g. 100 alarms over 24 hours).
The alarm causes a SNMP trap to be sent.
●
The voip-terminalqos alarm is like the voip-systemqos alarm except it applies to a single
terminal. If any one terminal generates a number of voip-callqos warnings that exceed a
threshold then the alarm is generated.
Alarm Management
This section describes methods to determine the source of alarms that are generated when an
error occurs. The alarm log is viewable and follows that defined in Maintenance for Avaya
DEFINITY® Server R, 555-233-117. Technicians can view alarms via the Web Interface, CLI,
and SAT command-line interface.
SNMP management is a function of the Avaya MultiService Network Manager application. For
additional information, including information on event logs and trap logs, please refer to the
Avaya P333T User’s Guide.
Alarm management follows the S8700 Media Server Alarming Architecture Design; see
Maintenance for the Avaya S8700 Media Server with an Avaya SCC1 Media Gateway or an
Avaya MCC1 Media Gateway, 555-233-143.
Connection Strategies to a Services Organization
A services organization, such as INADS, receives alarms from the Media Server and connects
to the media server for troubleshooting. There are currently two product-connect strategies:
dialup modem access and Virtual Private Network (VPN) access over the Internet.
For dialup modem access:
1. Connect a USB modem, connected to a telephone line, to the USB port on the faceplate of
the media server.
Issue 1 June 2005
31
Server Alarms
2. Enable the modem from the media server Web Interface. In addition, use the Setup Modem
Interface under the Configure Server pages.
3. With this modem, a client PC uses the Point-to-Point Protocol (PPP) to access the media
server and connect via telnet to a Linux shell.
4. Once logged into the media server, you can telnet out to media gateways, such as the
G700, and other devices on the network.
Note:
Additionally, this modem can be used to allow the media server to call out to the
INADS or other alarm receiving system to report alarms. When performing
remote diagnostic tests, Services personnel should disable alarm call-outs to
INADS to avoid generating unnecessary alarms. Alarm suppression is released
after 30 minutes. If you are remotely logged in through the modem you prevent
alarms from being sent because you are using the modem, but you do not
prevent an alarm noting the absence of alarm reporting service being logged at
the alarm receiving site.
Note:
The VPN alternative is achieved by the use of the Intelligent Site Manager (ISM) application.
The ISM is a VPN gateway that resides on the customer’s LAN and provides a means for
services personnel to gain access to the customer’s LAN in a secure manner over the Internet.
Telnet is then used to access the media server and/or media gateways and other IP network
equipment.
Alarms in Linux Media Servers
S8700 | 8710 / S8500 / S8300
A Linux-based media server can be configured so that it serves as the trap collector and
provides external alarm notification.
A process called the Global Maintenance Manager (GMM) runs on the media server and
collects events that are logged to the Linux syslog_d process. These events consist primarily of
failure notification events logged by Communication Manager and INTUITY maintenance
subsystems, or of traps sent by media gateways (G700). For events that require external
notification, one option is to call the Avaya technical service center’s INADS (Initialization and
Administration System). However, other possible options include sending an e-mail to specified
destinations, or sending an SNMP trap to a specified network management address.
The media server has an SNMP trap manager that collects traps from:
●
Uploads and downloads to media modules
●
VoIP Media Modules
●
VoIP engines on G700 motherboards
●
G700-associated UPS systems
32 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Media server alarms perform a similar role to Communication Manager alarms in a traditional
telephony context. Media Server alarms:
●
Comprise related sets of alarms, known as MOs
●
Create an internal record of actual or potential problems
●
Notify maintenance personnel of a problem
●
Help isolate the problem’s source
●
Point to and facilitate local and remote resolution of a problem
Note:
If a user is logged into a server by an analog modem that is also the server’s only
alarm-reporting interface, enter almsuppress to suppress alarm reporting.
Otherwise, the other server logs an occurrence of SME Event ID #1 (see SME
Alarm in Media Server on page 78).
Note:
Clearing Media Server Alarms
A media server is an open standards-based CPU in the data- communications context. Unlike a
Communication Manager alarm, which cannot be cleared unless it is also resolved, a server
alarm:
●
Can be manually cleared from its log, with the almclear Linux command
●
Should not be considered resolved until it is actually repaired
Displaying Media Server Alarms
In following sections, each server alarm is described, and its resolution procedure is provided.
Like traditional Communication Manager MOs, the 3-column table for each server MO shows an
alarm’s:
1. Event ID
2. Severity
3. Definition, probable cause, and troubleshooting procedure
To help isolate a server problem, the 3rd column of these tables begins with quoted text for each
event (unlike traditional Communication Manager MOs). The text consists of the verbose (-v)
output of the almdisplay -v Linux command. For example, “interchange hand off failed” is
the quoted text for Arbiter’s Event ID #3.
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.
Issue 1 June 2005
33
Server Alarms
S8300
Alarming on the S8300 Functioning as a Local Survivable Processor
The S8300 functioning as a Local Survivable Processor (LSP) logs an alarm when it becomes
active. It also logs an alarm for every G700 Media Gateway that registers with it. It does NOT
log alarms when IP phones register with it; rather, it logs a warning.
Communication Manager Hardware Traps
Table 6: Communication Manager Hardware Traps on page 34 illustrates hardware traps that
apply to Communication Manager.
Table 6: Communication Manager Hardware Traps
Note:
Trap
Description
Media Server HW trap
Hardware faults are analyzed by maintenance software and
correlate fault conditions to determine the appropriate action. If
appropriate action requires attention, a trap of critical severity is
sent.
Media Server HW clear
trap
Hardware faults that have created traps send a clear trap upon
clearing.
Media Server with
administered MG that’s
not registered
If a Media Server has an administered G700 but it has not
registered after an appropriate amount of time, send an alarm of
major severity indicating such.
Note:
The Avaya S8300 Media Server on a G700 Media Gateway platform has several
watchdog timers. If any one of them is not verified regularly, a trap of major
severity is sent. The timer associated with the S8300 is the S8300 Software
watchdog, which resets the S8300 processor if its connection is not verified
regularly.
34 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Backup and Restore Traps
The S8300 uses the LAN to backup a copy of its translation data. Table 7: Backup and Restore
Traps on page 35 illustrates the backup and restore traps.
Table 7: Backup and Restore Traps
Trap
Description
Successfully stored
backup
A trap of informational severity is sent when backup is successful.
(REPLY_ACK) The trap reads “Successful backup of S8300
translation data,” and names the backup location stored in the
string “BACKUP_LOCATION.”
This information also goes to the local maintenance screen, since
it is very possible that a backup is being requested as a result of an
on-site attempt to replace the S8300.
No backup data stored
A trap of major severity is sent as soon as a REPLY_ERROR
message is returned. The trap states “Translation Data backup not
available,” and names the backup location stored in the string
“BACKUP_LOCATION.”
Linux Media Server MOs and Alarms
Hardware MOs
The server’s hardware MOs are described in the following sections:
●
DAJ1/DAL1 (Duplication Memory Board) on page 49
●
RALM-SVC (Remote Alarm Service) on page 76
●
USB1 (Modem Testing) Alarms on page 95
●
UPS (Uninterruptible Power Supply) on page 89
●
Remote Maintenance Board (RMB) Alarms on page 116
Issue 1 June 2005
35
Server Alarms
Server-related alarms
Server-related alarms and their troubleshooting procedures are described in the following
tables:
●
ARB (Arbiter) on page 37
●
DAJ1/DAL1 Alarms in S8700 Media Server on page 54
●
DUP (Duplication Manager) on page 56
●
ENV (Environment) on page 60
●
FSY (File Synchronization) on page 67
●
HDD (Hard Disk Drive) on page 69
●
KRN (Kernel) on page 73
●
Login Alarms on page 74
●
NIC (Network Interface Card) on page 75
●
RALM-SVC (Remote Alarm Service) on page 76
●
SME Alarm in S8700 Media Server on page 78
●
SVC_MON (Service Monitor) on page 79
●
_TM (Translation Manager) on page 88
●
UPS Alarms to the Media Server on page 92
●
USB1 (Modem Testing) Alarms on page 95
●
_WD (Watchdog) Alarms on page 99
●
Login Alarms - S8300 on page 115
●
Virtual Alarms on page 116
●
Remote Maintenance Board (RMB) Alarms on page 116
●
S8500B Augmentix Server Availability Management Processor™ (A+SAMP) Alarms on
page 120
●
S8710 environmental alarms on page 121
●
S8710 server BIOS error messages on page 123
36 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
ARB (Arbiter)
S8700 | 8710 only
The Arbiter process runs on S8700 Media Servers to:
●
Decide which server is healthier and more able to be active
●
Coordinate data shadowing between servers, under the Duplication Manager’s control
At the physical and data-link layers, an Ethernet-based duplication link provides an inter-arbiter
UDP communication path to:
●
Enable this arbitration between the active and standby servers
●
Provide the necessary status signaling for memory refreshes
Issue 1 June 2005
37
Server Alarms
Table 8: ARB Alarms in Media Server on page 38 describes the Arbiter’s alarms and their
troubleshooting procedures. See DUP (Duplication Manager) on page 56 for more information.
Table 8: ARB Alarms in Media Server
Event
ID
3
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“Interchange hand off failed” — Standby server could not process active
server’s interchange request.
The interchange does not occur, and the active side remains active.
1. See if the standby side is RESET, either from the:
- Web interface’s Server section, by selecting View Summary
Status
- Linux command line, by entering server
2. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
3. If the problem persists, troubleshoot the standby server.
a. See if the standby side is RESET, either from the:
- Web interface’s Server section, by selecting View Summary
Status
- Linux command line, by entering server
b. Check for application problems, either from the:
- Web interface, by selecting View Process Status
- Linux command line, by entering statapp,
and restore any applications with problems.
c. Check for problems with an Ethernet interface, either from the:
- Web interface, by selecting the Execute Pingall diagnostic
- Linux command line, by entering 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,
escalate the problem.
1 of 12
38 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 8: ARB Alarms in Media Server (continued)
Event
ID
7
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Arbiter in invalid/unknown state” — Memory corruption or bad code/build
1. Verify that the server’s state is “Corrupt!”, either from the:
- Web interface’s Server section, by selecting View Summary
Status
- Linux command line, by entering server
2. Compare the suspected arbiter with the one in /root2 — using
the Linux commands:
/opt/ecs/sbin/acpfindvers /opt/ws/arbiter
(This command shows the arbiter’s version string.)
/sbin/cksum /opt/ws/arbiter
[This command runs a cyclical redundancy check (CRC) against
the arbiter, and then shows both the CRC’s output value and the
number of bytes in the arbiter file.]
3. If the two arbiter files differ:
a. Get a fresh copy of arbiter from the CD.
b. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
4. If the arbiter file is OK or the problem persists, escalate the
problem.
2 of 12
Issue 1 June 2005
39
Server Alarms
Table 8: ARB Alarms in Media Server (continued)
Event
ID
8
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“Both servers thought they were active”
1. To verify this condition, either from the:
- Web interface’s Server section, select View Summary Status
- Linux command line, enter server
2. To distinguish the cause, examine the trace logs for Interarbiter
messages with timestamps shortly before to shortly after the loss of
heartbeat, either from the:
- Web interface, by:
a. Selecting the View System Logs diagnostic and Logmanager
Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the Interarb pattern
- Linux command line, by entering logv -t ts
Depending on the cause, continue with either Step 3 or Step 4.
3 of 12
40 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 8: ARB Alarms in Media Server (continued)
Event
ID
8
Alarm
Level
MIN
(cont’d)
Alarm Text, Cause/Description, Recommendation
3. A high-priority process caused the active Arbiter to hang for at least
4.5 seconds (causing an interchange). Then, the hang lifted, and
each Arbiter realized that the other had assumed the active role.
An automatic resolution process should leave the newly active server
active, while the other server backs down to the standby role.
a. If so, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
b. If the problem recurs, escalate the problem.
4. Every Interarbiter link is down or mis-configured.
a. Check for problems with an Ethernet interface, either from the:
- Web interface, by selecting the Execute Pingall diagnostic
- Linux command line, by entering pingall -a
Check both sides of each failed link, and make any necessary
repairs.
b. If the links are OK but the problem persists, escalate the problem.
9
WRN
<SOH (state-of-health) string> — Before an interchange, the standby
server is significantly healthier than the active server requesting the
interchange. (The active server is probably unable to sustain call
processing.)
Understanding ARB Event #9’s String Pairs
ARB Event #9 generates pairs of SOH strings, where in each string pair,
the:
●
1st string represents the active
●
2nd string represents the standby
server’s SOH just before an interchange. Since – (unless prevented by
external circumstances) – Event 9 triggers a server interchange, the 1st
string normally represents the less healthy server – which became the
standby. So, the 1st string’s data is usually more pertinent.
4 of 12
Issue 1 June 2005
41
Server Alarms
Table 8: ARB Alarms in Media Server (continued)
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
9
WRN
The following is a sample string pair generated by ARB Event #9. Within
this sample, four pairs of digits in each string have special meaning, and
are labeled “aa” through “dd.”
(cont’d)
aa
bb cc
dd
↓↓
ØØ ØØ
ØØ
gmm 0700, pcd 00/00, dup 270, wd 81, actv 004
gmm 0700, pcd 06/06, dup 370, wd 01, actv 014
●
For “aa,” any value other than “00” indicates a hardware problem.
(For example, the value “20” is common for a power failure.)
In the previous sample, neither server had hardware trouble.
●
For “bb” and “cc,” different values within the same string indicate a
problem connecting to one or more IPSI connected PNs.
A PN reset can cause both server’s strings to reflect equally degraded
health, but that event (in itself) should not trigger a server interchange.
In the previous sample, both servers’ connectivity to IPSI connected
PNs is OK. (The 1st and 2nd strings have like “00” and “06” values,
respectively.)
●
For “dd,” any value other than “01” indicates a failed software
process. (More precisely, a certain value indicates a problem with a
discrete portion of the platform’s process set, including:
- “21” for a Linux daemon (for example, “atd”, “httpd”, “inetd”, or
“xntpd”)
- “41” for a platform service (for example, “dbgserv”, “prune”, or
“syslog”)
- “81” for reloaded Communication Manager software, as in the
previous sample
5 of 12
42 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 8: ARB Alarms in Media Server (continued)
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
9
WRN
Troubleshooting ARB Event #9
(cont’d)
1. compare the health of both servers, either from the:
- Web interface’s Server section, by selecting View Summary
Status
- Linux command line, by entering server
2. Using the output from Step 1, check the health of each server’s
individual processes.
3. Check the health of the active server’s individual processes, either
from the:
- Web interface, by selecting View Process Status
- Linux command line, by entering statapp
and restore any applications with problems.
4. See if the standby side is RESET, either from the:
- Web interface’s Server section, by selecting View Summary
Status
- Linux command line, by entering server
5. Check the health of the standby server’s individual processes, either
from the:
- Web interface, by selecting View Process Status
- Linux command line, by entering statapp,
and restore any applications with problems.
6. Check for problems with an Ethernet interface, either from the:
- Web interface, by selecting the Execute Pingall diagnostic
- Linux command line, by entering pingall -a
Check both sides of each failed link, and make any necessary repairs.
7. If the standby’s applications and interfaces are OK but the problem
persists, escalate the problem.
6 of 12
Issue 1 June 2005
43
Server Alarms
Table 8: ARB Alarms in Media Server (continued)
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
After the interchange, the newly active server’s health should be
significantly better (lower SOH value) than the standby server’s. If so,
troubleshoot the standby server:
If not:
1. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
2. If the problem recurs, escalate the problem.
11
WRN
“Cannot create receive socket;” “cannot create transmit socket;” “cannot
bind receive socket;” “cannot bind send socket”
Since the Arbiter continuously attempts to create or bind the socket, the
problem may resolve itself. Once resolved, the Arbiter can send and
receive across every Interarbiter link (no subsequent error messages in
the trace log).
1. Examine the alarm log to distinguish between a:
Bind or create problem
Send or receive socket problem
by accessing either the:
- Web interface, by:
a. Selecting Alarms and Notification and the appropriate alarm
b. Selecting the View System Logs diagnostic
c. Selecting the Logmanager Debug trace
d. Specifying the Event Range for the appropriate time frame
e. Matching the “cannot create” pattern
- Linux command line, by entering almdisplay -v
7 of 12
44 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 8: ARB Alarms in Media Server (continued)
Event
ID
Alarm
Level
11
WRN
(cont’d)
Alarm Text, Cause/Description, Recommendation
2. Check for both the completeness and consistency of the servers’
hosts and servers.conf files (containing IP addresses of the
system’s configured components), either from the:
- Web interface, by selecting Configure Server
- Linux command line, by entering:
more /etc/hosts
more /etc/opt/ecs/servers.conf
3. If the files are OK, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
4. If this problem affects call processing or if the problem persists,
continue with Step 5 now.
If not, continue only at the customer’s convenience.
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 not, enter server -if to force a server interchange.
c. Busy out the standby server from the Linux command line, by
entering server -b.
d. Reboot the server (as the standby), either from the:
- Web interface, by selecting Shutdown This Server
- Linux command line, by entering /sbin/shutdown -r
now
6. If rebooting the standby does not help or if the problem recurs,
escalate the problem to the next higher tier.
8 of 12
Issue 1 June 2005
45
Server Alarms
Table 8: ARB Alarms in Media Server (continued)
Event
ID
12
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“Interchange without doing prep” — Since the Arbiter could not create a
thread to request a file synchronization, some files did not get shadowed.
1. Examine the trace logs for the entry, Can't create
interchange-prep thread, either from the:
- Web interface by:
a. Selecting the View System Logs diagnostic and Logmanager
Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the “interchange-prep” pattern
- Linux command line, by entering logv -t ts
2. Resubmit any translation changes entered during the last 15-minute
file-synchronization interval.
3. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
9 of 12
46 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 8: ARB Alarms in Media Server (continued)
Event
ID
13
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“Heartbeat timeout from ACTIVE” — When the timeout occurs, this alarm
is only logged on the standby side. After logging the alarm, the servers
should have interchanged, so that the:
●
Alarm normally resides on the newly active (healthier) server
●
Previously active server has backed down to the standby role
As potential causes, either the:
Alternate side is in normal shutdown (irregular, but possibly innocuous).
1. On the standby server, look for occurrences of the stop command,
either from the:
- Web interface, by:
a. Selecting View System Logs
b. Selecting Platform command history log
c. Specifying the Event Range for the appropriate time frame
d. Matching the “Stop” pattern
- Linux command line, by entering listhistory
Note: From the system’s perspective, this is normal behavior.
However, in terms of potential service outage due to human error, this
is quite irregular. Shutting down a server effectively downgrades a
duplex-, high-, or critical-reliability system to an unsupported
standard-reliability system.
10 of 12
Issue 1 June 2005
47
Server Alarms
Table 8: ARB Alarms in Media Server (continued)
Event
ID
13
(cont’d)
Alarm
Level
MIN
Alarm Text, Cause/Description, Recommendation
2. From the Linux command line, enter start -a to restart the standby
server.
3. Prevent any future misuse of the stop command.
4. Manually clear the alarm on the active server, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
Either the:
●
The alternate side is hung (ARB Event 8 is not being generated)
●
Two or more Interarbiter links are down (ARB Event 8 is also being
generated)
Therefore, if the servers interchanged (the previously active server
backed down to standby), use the following procedure:
5. Check for problems with an Ethernet interface, either from the:
- Web interface, by selecting the Execute Pingall diagnostic
- Linux command line, by entering pingall -a
Check both sides of each failed link, and make any necessary repairs.
a. If the Ethernet interfaces are OK, see if the standby server is
busied-out, either from the:
- Web interface, by selecting View Summary Status
- Linux command line, by entering server
b. If so, release the standby server, either from the:
- Web interface, by selecting Release Server
- Linux command line, by entering server -r
If not, check for related alarms to troubleshoot the standby.
6. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
7. If the problem persists, escalate the problem.
11 of 12
48 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 8: ARB Alarms in Media Server (continued)
Event
ID
13
(cont’d)
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
If the servers did not interchange, use the following procedure:
8. See if the standby server is busied-out, either from the:
- Web interface, by selecting View Summary Status
- Linux command line, by entering server
9. If so, release the standby server, either from the:
- Web interface, by selecting Release Server
- Linux command line, by entering server -r
If not, escalate this problem for explicit guidance with general
troubleshooting of both servers.
12 of 12
Back to:
Hardware MOs
Server-related alarms
DAJ1/DAL1 (Duplication Memory Board)
S8700 | 8710 only
This MO supports each S8700 media server’s Duplication Memory board (DAJ1) and the S8710
media server’s Duplication Memory board (DAL1). These Duplication Memory boards are a NIC
(network interface card) serving as the physical and data-link interface for an Ethernet-based
duplication link between the servers. This link provides a call-status data path for sending:
●
TCP-based communication between each server’s Process Manager
●
UDP-based communication between each server’s Arbiter to:
- Enable arbitration between the active and standby servers
- Provide status signaling for memory refreshes
Note:
Note:
Note:
The Duplication Memory cards are not interchangeable between media servers.
The DAJ1 will only work in S8700 media servers and the DAL1 will only work in
S8710 media servers.
Note:
This call-status data is separate from the translations and Linux files shadowed
between servers. (See FSY (File Synchronization) on page 67.)
Issue 1 June 2005
49
Server Alarms
(Table 13: DAJ1/DAL1 Alarms in Media Server on page 54 describes the Duplication Memory
board’s alarms and their troubleshooting procedures.) [See also, ARB (Arbiter) on page 37,
DUP (Duplication Manager) on page 56, and NIC (Network Interface Card) on page 75.]
Both periodic and on-demand testing is provided for this MO. The periodic test runs the Read
Error Register test at 15-minute intervals. On-demand testing includes the Read Error Register
and Local Loop tests.
MO’s Name (in
Alarm Log)
Alarm
Level
Initial Linux Command to Run
Full Name of MO
DAJ1 or DAL1
MAJ
testdupboard1
Server Dup Mem board
DAJ1 or DAL1
MIN
testdupboard
Server Dup Mem board
DAJ1 or DAL1
WRN
testdupboard
Server Dup Mem board
1. See Table 9
Table 9: Testdupboard command syntax and arguments
Argument
Description
Syntax: testdupboard [-s] | [-l] | [-t arg] | [-?]
no
argument
Performs “short” test.
-s
Short test, performs read_err_reg test, this is also the default option.
-l
Performs “short” tests, and localloop test
-t
arg Specific test to perform. Possible values for arg are:
●
●
-?
read_err_reg
localloop.
Usage (this).
50 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Alarm Log Entries
Table 10: DAJ1/DAL1 Alarm Log Entries
EVENT
ID#
Associated Test
Alarm
Level
On/Off
Board
Linux Test to
Clear Value
2 (a)
Read Error Register test (EDC single-bit
errors)
WRN
ON
testdupboard
3 (b)
Read Error Register test (SDRAM multibit
errors)
MAJ
ON
testdupboard
4 (c)
DAJ1/DAL1 Local Looparound test
MIN
ON
testdupboard
5 (d)
Read Error Register test (Link Receiver CRC
errors)
MIN
ON
testdupboard
6 (e)
Read Error Register test (Link Receiver CRC
errors)
MAJ
ON
testdupboard
Notes:
a. Event ID #2 Test failed — Error counter query for single-bit EDC (bad error register) on
the SDRAM is pegging. If the test detects 20 consecutive failures, the following Warning
alarm is logged:
#1,ACT,[DAJ1|DAL1],A,2,WRN,Single-bit EDC test (bad SB err count)
b. Event ID #3 SDRAM has multiple bit errors — The [DAJ1|DAL1] board can also
generate this event as an in-line error.
If this test detects a failure, the media server’s state of health is lowered to its most
critical level, and the following Major alarm is logged:
#1,ACT,[DAJ1|DAL1],A,3,MAJ, SDRAM multibit errors
c. Event ID #4 Looparound test failed — Either a mismatched address or a mismatched bit
pattern could have caused a failure.
If this test detects 3 failures, the following Minor alarm is logged:
#1,ACT,[DAJ1|DAL1],A,4,MIN,Local Looparound test failure
d. Event ID #5 Optical Line Receiver experiencing CRC errors — If this test detects 3
failures, the following Minor alarm is logged:
#1,ACT,[DAJ1|DAL1],A,5,MIN,Link Receiver CRC errors
e. Event ID #6 Inability to open a communications link with the Duplication Memory board.
The board is out of service if this failure occurs once, and a Major alarm is logged:
#1,ACT,[DAJ1|DAL1],A,6,MAJ,Failed to open [DAJ1|DAL1] card
Issue 1 June 2005
51
Server Alarms
System Technician-Demanded Tests:
Descriptions and Error Codes
Investigate tests in the order shown in. By clearing error codes associated with the first test, you
may clear errors generated from other tests in the sequence.
Order of Investigation
Short Test
Sequence
Long Test
Sequence
D/ND1
Read Error Register test
X
X
D
[DAJ1|DAL1] Board Local Loop test
X
X
D
1. D = Destructive; ND = Nondestructive
Read Error Register Test
The Read Error Register test queries three registers including the:
●
Optical line receiver’s CRC error register
CRC errors indicate problems with the optical interface between the active and standby
servers.
●
SDRAM’s single-bit error register
Although the Duplication Memory board can “self heal” single-bit errors in the SDRAM’s
error register, chronic problems can indicate a more serious problem.
●
SDRAM’s multiple-bit error register
An SDRAM multiple-bit error condition indicates a problem in the Duplication Memory
board’s memory, and cannot be recovered.
The following errors can be detected:
52 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 11: TEST Read Error Register Test
Error Code
Test
Result
Description / Recommendation
Open failed
to MDD
ABRT
The Memory Duplication Driver (MDD) is the system driver that
communicates with the [DAJ1|DAL1] board. If this driver cannot be
opened, then the [DAJ1|DAL1] board’s registers cannot be read.
1. This is a system type error, try again.
System Error
–
MDD failed
to
return data
ABRT
[DAJ1|DAL1]
err count
query,
code=?
?= 1 to 7
FAIL
The test ran, but, for some reason the MDD could not return data.
1. This is a system type error, try again.
Test failed “[DAJ1|DAL1] err count query, code=?” — where “?”
indicates which of the [DAJ1|DAL1] board’s error counters had
positive data. The failure code can be 1–7 and is determined by the
bit vector, “0xxx”. (Every “x” bit could be set, indicating that every
error register had errors.) Specifically, if bit:
1 is set (0xx1) – Single-bit errors occurred.
2 is set (0x1x) – CRC errors occurred.
3 is set (01xx) – Multibit errors occurred.
[DAJ1|DAL1] Local Loop Test
Note:
This is an on-demand test that only runs on the standby media server when it is
busied out.
Note:
This test runs a local loop-around test on the standby media server’s [DAJ1|DAL1] board. A
32-bit data number is written to an address and verified for correct transmission. The test
reads the contents of the:
●
Last data received registers
●
Last address received register
and then compares the data. If the data matches, the test passes. If not, the test fails.
The following errors can be detected:
Issue 1 June 2005
53
Server Alarms
Table 12: TEST DAJ1/DAL1 Local Loop Test
Error Code
Test Result
Description / Recommendation
Open failed
to MDD
ABRT
The MDD is the system driver that communicates with the
Duplication Memory board. If this driver cannot be opened, the
board’s registers cannot be read.
This is a system type error, try again.
System Error
MDD failed
to return
data
ABRT
The test ran, but for some reason the MDD could not return
data.
This is a system type error, try again.
Loop-around
test failed
FAIL
The last address received does not match the address that was
written, or the last data received does not match the data that
was written.
Back to:
Hardware MOs
Server-related alarms
DAJ1/DAL1 Alarms in S8700 Media Server
S8700 | 8710 only
Table 13: DAJ1/DAL1 Alarms in Media Server on page 54 describes the Duplication Memory
card MO’s alarms and their troubleshooting procedures.
Table 13: DAJ1/DAL1 Alarms in Media Server
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
2
WRN
“Single-bit EDC test (bad SB err cnt)” — Single-bit SDRAM error occurred
20 times.
Software automatically clears the single-bit error register. This is a
log-only indication of the error’s occurrence.
1. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
1 of 2
54 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 13: DAJ1/DAL1 Alarms in Media Server (continued)
Event
ID
3
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Multibit EDC Test (bad err register)” — Catastrophic multibit SDRAM
error occurred. (Usually due to a hardware problem.)
1. Enter testdupboard on the Linux command line.
2. If the test fails, escalate this problem for explicit guidance with Steps
3 through 5.
3. Power-cycle the server.
4. Enter testdupboard again.
5. If the test still fails, replace the server.
4
MIN
“Local-loop failure” — On-demand local-loop test failed 3 times. (Cannot
read from or write to DAJ1|DAL1 buffers.)
The Localloop test only runs on a busied-out standby server.
1. If the on-demand test is failing (but a running duplicated system has
no problems), do nothing.
If the running duplicated system has problems, continue with Step 2
2. Enter testdupboard on the Linux command line.
3. If the test fails, escalate this problem for explicit guidance with Steps
4 through 6.
4. Power-cycle the server.
5. Enter testdupboard again.
6. If the test still fails, replace the server.
5
MIN
“Optical link received CRC errors” — Received multiple CRC errors
across the fiber link.
1. Run testdupboard on both servers.
2. If CRC errors are occurring on both servers, it may be a:
●
Likely problem with the fiber link
●
Far less likely problem with both Duplication Memory cards
If not, the other server’s Duplication Memory card may be faulty.
3. If the running system has duplication-related problems, escalate this
problem to replace the server.
If not, ignore the alarm.
2 of 2
Back to:
Hardware MOs
Server-related alarms
Issue 1 June 2005
55
Server Alarms
DUP (Duplication Manager)
S8700 | 8710 only
The Duplication Manager process, via coordination of the Arbiter process, runs on each S8700
Media Server to control data shadowing between them.
At the physical and data-link layers, an Ethernet-based duplication link provides a TCP
communication path between each server’s Duplication Manager to enable their control of data
shadowing.
Table 14: DUP Alarms in Media Server on page 57 describes the Duplication Manager’s
alarms and their troubleshooting procedures.
See ARB (Arbiter) on page 37 and DAJ1/DAL1 (Duplication Memory Board) on page 49 for
more information.
56 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 14: DUP Alarms in Media Server
Event
ID
1
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Duplication card error” — Duplication Manager determined that the
duplication card is not functioning, but it cannot distinguish between a bad
card, an unplugged card, or a bad fiber link.
1. Check the physical fiber connectivity at each server.
2. Verify the alarm, by accessing the trace log, either from the:
●
Web interface, by:
a. Selecting the View System Logs diagnostic and Logmanager
Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the “dup” pattern
●
Linux command line, by entering logv -t ts
3. Examine the trace-log query’s output for one of these messages:
“glbi: couldn't open Dup Card, errno=<#>. ndm exiting”
“glbi: mmap failed, errno=<#>. ndm exiting”
“Haven't heard from active dupmgr. Dup fiber link down.”
“san_check_rsp() FAILED: Dup Fiber link down.”
4. See if the dup link is both “up” and “refreshed”, either from the:
●
Web interface’s Server section, by selecting View Summary
Status
●
Linux command line, by entering the server command
5. If so, manually clear the alarm, either from the:
●
Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
●
Linux command line, by entering almclear -n #id
1 of 3
Issue 1 June 2005
57
Server Alarms
Table 14: DUP Alarms in Media Server (continued)
Event
ID
1
Alarm
Level
MAJ
(cont’d)
Alarm Text, Cause/Description, Recommendation
If not and at the customer’s convenience:
Since the following commands cause a brief service outage, they should
only be executed at the customer’s convenience.
a. Force a server interchange to make the suspected server standby,
either from the Linux command line, by entering server -if.
b. Busy out the standby server from the Linux command line, by
entering server -b.
c. Reboot the standby server, either from the:
- Web interface, by selecting Release Server
- Linux command line, by entering server -r
6. If the problem persists, you can try:
a. Replacing the fiber between the two servers
b. Rebooting the standby server
7. If the problem continues to persist, escalate for a probable server
replacement.
2
MAJ
“Duplication link down” — One server’s Duplication Manager cannot
communicate with the other server’s Duplication Manager.
1. Access the trace log, either from the:
- Web interface, by:
a. Selecting the View System Logs diagnostic and Logmanager
Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the “dup” pattern
- Linux command line, by entering logv -t ts
2. Examine the trace-log query’s output for one of these 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.”
2 of 3
58 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 14: DUP Alarms in Media Server (continued)
Event
ID
2
(cont’d)
Alarm
Level
MAJ
Alarm Text, Cause/Description, Recommendation
3. See if the dup link is “up”, either from the:
- Web interface’s Server section, by selecting View Summary
Status
- Linux command line, by entering the server command
4. If so, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
If not, check the duplication interface’s Ethernet connectivity, either
from the:
- Web interface, by selecting the Execute Pingall diagnostic
- Linux command line, by entering pingall -d
5. If pingall passes, check the other server’s applications, either from
the:
- Web interface, by selecting View Process Status
- Linux command line, by entering statapp
3 of 3
Back to:
Hardware MOs
Server-related alarms
Issue 1 June 2005
59
Server Alarms
ENV (Environment)
S8700 | 8710 / S8300 / S8500B
The ENV MO monitors environmental variables within the server, including temperature,
voltages, and fans. Table 15: ENV Alarms in Media Server on page 60 describes the ENV
MO’s alarms and their troubleshooting procedures.
Table 15: ENV Alarms in Media Server
Event
ID
1
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Temperature reached critical low” — Motherboard's temperature reached
a critically low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
2
MIN
“Temperature reached warning low” — Motherboard's temperature
reached a warning low.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
1 of 8
60 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 15: ENV Alarms in Media Server (continued)
Event
ID
3
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“Temperature reached warning high” — Motherboard's temperature
reached a warning high.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
4
S8300
MAJ
“Temperature reached critical high” — Motherboard's temperature
reached a critically high level.
1. Look for any obstructions blocking the server’s fans.
2. Check for any fan alarms, and clear those alarms.
3. Shut down and restart the system.
4. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
5. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear.
- Linux command line, by entering almclear -n #id
2 of 8
Issue 1 June 2005
61
Server Alarms
Table 15: ENV Alarms in Media Server (continued)
Event
ID
6
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“+3.3 voltage reached critical low” — Motherboard's nominal +3.3 voltage
reached a critically low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
8
MAJ
“+3.3 voltage reached critical high” — Motherboard's nominal +3.3 voltage
reached a critically high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
10
MAJ
“+5 voltage reached critical low” — Motherboard's nominal +5 voltage
reached a critically low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
3 of 8
62 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 15: ENV Alarms in Media Server (continued)
Event
ID
12
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“+5 voltage reached critical high” — Motherboard's nominal +5 voltage
reached a critically high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
14
MAJ
“+12 voltage reached critical low” — Motherboard's nominal +12 voltage
reached a critically low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
16
MAJ
“+12 voltage reached critical high” — Motherboard's nominal +12 voltage
reached a critically high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
4 of 8
Issue 1 June 2005
63
Server Alarms
Table 15: ENV Alarms in Media Server (continued)
Event
ID
18
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“-12 voltage reached critical low” — Motherboard's nominal -12 voltage
reached a critically low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
20
MAJ
“-12 voltage reached critical high” — Motherboard's nominal -12 voltage
reached a critically high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
22
MAJ
“CPU core voltage reached critical low” — Motherboard's CPU core
voltage reached a critically low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
5 of 8
64 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 15: ENV Alarms in Media Server (continued)
Event
ID
24
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“CPU core voltage reached critical high” — Motherboard's CPU core
voltage reached a critically high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
26
MAJ
“CPU I/O voltage reached critical low” — Motherboard's CPU I/O voltage
reached a critically low level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
28
MAJ
“CPU I/O voltage reached critical high” — Motherboard's CPU I/O voltage
reached a critically high level.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
6 of 8
Issue 1 June 2005
65
Server Alarms
Table 15: ENV Alarms in Media Server (continued)
Event
ID
29
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“All fan failure” — Every fan is running at a critically low speed.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
31
MAJ
S8500B
+1.5V under voltage. S8500B media server environment.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
33
S8500B
MAJ
+1.5V over voltage. S8500B media server environment.\
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
7 of 8
66 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 15: ENV Alarms in Media Server (continued)
Event
ID
35
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
+2.5V under voltage. S8500B media server environment.
S8500B
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
37
S8500B
MAJ
+2.5V over voltage. S8500B media server environment.
1. See if the alarmed condition is still present, either from the:
- Web interface, by selecting the View Temperature/Voltage
diagnostic
- Linux command line, by entering environment
2. If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
8 of 8
Back to:
Hardware MOs
Server-related alarms
FSY (File Synchronization)
S8700 | 8710 / S8500
The File Synchronization (FSY) process uses TCP-based communication over 100Base-T
Ethernet links to provide synchronized duplication of critical data-shadowed files, including
translations and important Linux files.
Note:
Note:
This set of files is separate from the data shadowed between each server’s
DAJ1/DAL1 (Duplication Memory Board) on page 49.
Issue 1 June 2005
67
Server Alarms
Table 16: FSY Alarm in Media Server on page 68 describes the FSY MO’s alarms and their
troubleshooting procedures.
Table 16: FSY Alarm in Media Server
Event
ID
1
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“File sync failed” — File synchronization operation failed.
1. See if the filesyncd (file sync daemon) process is up, either from the:
- Web interface, by selecting View Process Status
- Linux command line, by entering statapp
2. Check the trace log for more granular information. (The file sync
daemon can report failures of synchronizing one or more files.)
Access the trace log, either from the:
- Web interface, by:
a. Selecting the View System Logs diagnostic and Logmanager
Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the “file sync failed” pattern
- Linux command line, by entering logv -t ts
3. (Except S8500) Verify that the dup link is both “up” and “refreshed”,
either from the:
●
Web interface’s Server section, by selecting View Summary Status
●
Linux command line, by entering the server command
(Neither side should be “off-line” nor “down”.)
4. (Except S8500) Make sure that the Ethernet duplication link is up, either
from the:
- Web interface, by selecting the Execute Pingall diagnostic
- Linux command line, by entering pingall -a
If not, check each side of this failed link, and make any necessary
repairs.
5. (Except S8500) Check the physical fiber connectivity at each server to
verify that this alarm is not a consequence of other duplication-related
problems.
6. If the problem persists, escalate the problem.
Back to:
Hardware MOs
Server-related alarms
68 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
HDD (Hard Disk Drive)
The HDD MO monitors the hard drive via the Self Monitoring, Analysis, and Reporting
Technology (S.M.A.R.T) capability that is built into the hard disk drive unit. The integrated
controller for the hard disk drive works with sensors incorporated in the hard drive to monitor the
drive’s performance. The SMART technology makes status information concerning the disk
drive available to monitoring software.
The basic concept with SMART is that some hard disk drive problems do not occur suddenly.
They are the result of a gradual degradation of disk components. For example, if the value for
Reallocated Event Count (count of remap operations, both successful and non-successful) for
Event ID 21 is going up it may indicate an impending disk failure. At the very least it should be
monitored closely.
Table 17: HDD Alarm in Media Server on page 69 describes the HDD Event IDs and their
troubleshooting procedures.
Table 17: HDD Alarm in Media Server
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
19
WRN
Device: device_name, Failed attribute: attr_number
This message indicates that the attribute value has exceeded its threshold
value.
1. If posted, user very likely has a drive problem and should definitely
consider replacing the drive.
20
WRN
smartd: Device: device_name, Read Smartd Values Failed
smartd: Device: device_name, Read Smartd Threshold Failed
This message indicates the SMART utility was unable to read the current
SMART values or thresholds for the drive. This may result in SMART not
executing and the values that are reported may be stale (or outdated). See
also Event ID 22.
21
WRN
smartd: Device: /dev/had, S.M.A.R.T. Attribute: attr_number Changed
chng_value.
The value for the specified attribute number (attr_number) has changed by
the specified value (chng_value). Posting of this alarm may/may not
indicate possible drive problems.
Definitions for the attributes are:
1 of 4
Issue 1 June 2005
69
Server Alarms
Table 17: HDD Alarm in Media Server (continued)
Event
ID
21
(cont’d)
Alarm
Level
Alarm Text, Cause/Description, Recommendation
Num
Name
Description
1
Raw Read Error
Indicates the rate of hardware read errors
that occur when reading data from the
disk surface. This error is critical. An
increasing error rate may indicate a
failing disk drive. (Samsung, Seagate,
IBM (Hitachi), Fujitsu, Maxtor, Western
Digital)
2
Throughput
Performance
Overall throughput performance of the
hard disk.
3
Spin Up Time
Raw value average of time to spin up
drive spindle. (Samsung, Seagate, IBM
(Hitachi), Fujitsu, Maxtor, Western Digital)
4
Start Stop Count
Count of hard disk spindle start/stop
cycles. (Samsung, Seagate, IBM
(Hitachi), Fujitsu, Maxtor, Western Digital)
5
Reallocated Sector
Count
Amount of remapped sectors.
6
Read Channel Margin
No explanation of attribute available
7
Seek Error Rate
Average rate of seek errors: if this value
continues to increase it indicates there
may be a problem with the disk surface or
a mechanical problem. (Samsung,
Seagate, IBM (Hitachi), Fujitsu, Maxtor,
Western Digital)
8
Seek Time Performance
Disk seek system performance.
(Samsung, Seagate, IBM (Hitachi),
Fujitsu, Maxtor, Western Digital)
9
Power_On_Hours
Number of hours of the power-on state of
the drive. This value indicates aging.
(Samsung, Seagate, IBM (Hitachi),
Fujitsu, Maxtor, Western Digital)
10
Spin_Retry_Count
Count of retry of drive spindle spine start
up attempts. (Samsung, Seagate, IBM
(Hitachi), Fujitsu, Maxtor, Western Digital)
2 of 4
70 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 17: HDD Alarm in Media Server (continued)
Event
ID
21
Alarm
Level
Alarm Text, Cause/Description, Recommendation
11
Recalibration Retries
Number of times recalibration was
requested after initial request. (Samsung,
Seagate, IBM (Hitachi), Fujitsu, Maxtor,
Western Digital)
12
Device Power Cycle
Count
Count of full hard disk power on/off
cycles. (Samsung, Seagate, IBM
(Hitachi), Fujitsu, Maxtor, Western Digital)
13
Soft Read Error Rate
Rate of program read errors when
reading data from disk. (Samsung,
Seagate, IBM (Hitachi), Fujitsu, Maxtor,
Western Digital)
193
Load/Unload Cycle
Count of load/unload cycles into landing
zone position. (Samsung, Seagate, IBM
(Hitachi), Fujitsu, Maxtor, Western Digital)
194
Temperature
Hard disk drive temperature. (Samsung,
Seagate, IBM (Hitachi), Fujitsu, Maxtor,
Western Digital - select models)
196
Reallocated Event
Count
Count of remap operations (transferring
of data from bad sector to reserved disk
area) successful and non-successful.
This error is critical. An increasing
count for this error may indicate a
failing disk drive. (Samsung, Seagate,
IBM (Hitachi), Fujitsu, Maxtor, Western
Digital - select models)
197
Current Pending Sector
Count
Current count of unstable sectors (waiting
for remap). This error is critical. An
increasing count for this error may
indicate a failing disk drive. (Samsung,
Seagate, IBM (Hitachi), Fujitsu, Maxtor,
Western Digital)
198
Uncorrectable Sector
Count
Count of uncorrectable errors when
reading/writing a sector. This error is
critical. An increasing count for this
error may indicate a failing disk drive.
(Samsung, Seagate, IBM (Hitachi),
Fujitsu, Maxtor, Western Digital)
(cont’d)
3 of 4
Issue 1 June 2005
71
Server Alarms
Table 17: HDD Alarm in Media Server (continued)
Event
ID
Alarm
Level
21
Alarm Text, Cause/Description, Recommendation
199
UltraDMA CRC Error
Count
Count of Cyclic Redundancy Check
(CRC) errors during UltraDMA mode
(Samsung, Seagate, IBM (Hitachi),
Fujitsu - select models, Maxtor, Western
Digital - select models)
200
Write Error Rate (Multi
Zone Error Rate
Total number of errors found when writing
a sector. (Samsung, Seagate, IBM
(Hitachi), Fujitsu, Maxtor, Western Digital)
220
Disk Shift
Indicates how much the disk has shifted
(unit of measure unknown). This error is
critical. An increasing value for this
error may indicate a failing disk drive.
(Seagate)
221
G-Sense Error Rate
Rate of errors occurring as a result of
impact loads such as dropping the drive,
wrong installation, etc. (Seagate, Hitachi)
222
Loaded Hours
Loading on magnetic heads actuator
caused by the general operating time.
223
Load/Unload Retry
Count
Loading on magnetic heads actuator
caused by numerous recurrences of
operations like: reading, recording,
positioning, etc.
224
Load Friction
Loading of magnetic heads actuator
caused by friction in mechanical part of
the store.
226
Load-in Time
Total time of loading on the magnetic
heads actuator.
227
Torque Amplification
Count
Count of efforts of the rotating moment of
a drive
228
Power-Off Retract
Count
Count of the number of times the drive
was powered off.
230
GMR Head Amplitude
Amplitude of the heads trembling in
running mode.
(cont’d)
22
WRN
Failed to read smart values/thresholds
This indicates that the smart utility was not able to read the smart values/
thresholds from the drive. The smart utility is unable to function due to drive
access problems.
4 of 4
72 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
KRN (Kernel)
S8700 | 8710
The KRN MO monitors the operating system Kernel. Table 18: KRN Alarm in Media Server on
page 73 describes the MO’s alarms and their troubleshooting procedures.
Table 18: KRN Alarm in Media Server
Event
ID
10
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
Failure in a Synchronous Dynamic Random Access Memory (SDRAM)
Dual Inline Memory Module (DIMM). Error Correcting Code (ECC) memory
detected a multi-bit error (MBE) but cannot correct it.
1. The SDRAM DIMM within the media server is not field replaceable.
Replace the media server.
Back to:
Hardware MOs
Server-related alarms
Issue 1 June 2005
73
Server Alarms
Login Alarms
The Login MO monitors access to the server and alarms suspicious activity. Table 19: Login
Alarms in Media Server on page 74 describes the Login MO’s alarms and their troubleshooting
procedures.
Table 19: Login Alarms in Media Server
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
2
WRN
“sat_Auth:Login for [inads] invalid password” — An SAT login to
Communication Manager failed.
1. Verify the alarm, either from the:
- Web interface, by selecting View Current Alarms
- Linux command line, by entering almdisplay -v
2. Since mis-typing a login sequence usually causes this alarm, enter
almclear -n #id to clear the alarm.
3. If this alarm is perceived as a security threat (often due to its
persistence or frequent recurrence), notify the customer.
4
WRN
“Login for [inads] – failed – password check” — A login to a server’s Linux
command line failed.
1. Verify the alarm, either from the:
- Web interface, by selecting View Current Alarms
- Linux command line, by entering almdisplay -v
2. Since mis-typing a login sequence usually causes this alarm, enter
almclear -n #id to clear the alarm.
3. If this alarm is perceived as a security threat (often due to its
persistence or frequent recurrence), notify the customer.
5
MAJ
“Probation interval for login [inads] ends – lockout interval begins” —
Multiple consecutive login failures.
1. If this alarm is perceived as a security threat, notify the customer.
74 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
NIC (Network Interface Card)
S8700 | 8710 / S8500
This MO supports the NICs in each S8700 media server providing the physical and data-link
interfaces for Ethernet-based links.
Table 20: NIC Alarms in Media Server on page 75 describes NIC’s alarms and their
troubleshooting procedures. See DAJ1/DAL1 (Duplication Memory Board) on page 49 for more
information.
Table 20: NIC Alarms in Media Server
Event
ID
1
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“eth0 NIC Link is Down” — Ethernet link on native NIC 0 is down.
1. Verify Ethernet connectivity, either from the:
- Web interface, by selecting the Execute Pingall diagnostic
- Linux command line, by entering pingall -a
Check both sides of each failed link, and make any necessary repairs.
2. If the ping test fails, check the physical connections of NIC 0’s Ethernet
cable.
If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
1 of 2
Issue 1 June 2005
75
Server Alarms
Table 20: NIC Alarms in Media Server (continued)
Event
ID
2
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“eth1 NIC Link is Down” — Ethernet link on native NIC 1 is down.
1. Verify Ethernet connectivity, either from the:
- Web interface, by selecting the Execute Pingall diagnostic
- Linux command line, by entering pingall -a
Check both sides of each failed link, and make any necessary repairs.
2. If the ping test fails, check the physical connections of NIC 0’s Ethernet
cable.
If not, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and “Clear”
- Linux command line, by entering almclear -n #id
2 of 2
Back to:
Hardware MOs
Server-related alarms
RALM-SVC (Remote Alarm Service)
S8700 | 8710 only
For the RALM-SVC MO, maintenance software performed special periodic testing every 60
seconds.
MOs Name
Alarm Level
Initial Command to Run
Full Name of MO
RALM-SVC
MAJOR
None
Remote Alarm Service
RALM-SVC
MAJOR
None
Remote Alarm Service
76 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Alarm Log Entries
These tests verify that the standby media server’s components are operating correctly.
Table 21: RALM-SVC Alarm Log Entries
EVENT
ID#
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Linux Test to
Clear Value
1 (1)
SME_ARB test
MAJOR
ON
testdupboard
2 (2)
Standby_PN Check test
MAJOR
ON
testdupboard
Notes:
1. Event ID #1 SME_ARB test failed — This test determines the other server’s alarm-generation
capability by querying the local server’s Arbiter to report on the other server’s Remote
Alarm Service functionality. Both media servers must have their own alarm-generation
utilities. If the test fails 3 consecutive times, the following Major alarm is logged:
#1,ACT,SME,A,1,MAJ,Far-end alarm service is down
2. Event ID #2 Standby_PN_Check test failed — This periodic test:
1. Queries the standby media server about its PNs’ state of health
2. Compares the acquired information to an administered value
A failure indicates that a mismatch occurred and that the standby media server is out of
sync. If this test fails 2 consecutive times, the following Major alarm is logged:
#1,ACT,SME,A,2,MAJ,Standby Port-Network check failed
System Technician-Demanded Tests: Descriptions
and Error Codes
This MO provides no on-demand tests for system technicians.
Back to:
Hardware MOs
Server-related alarms
Issue 1 June 2005
77
Server Alarms
SME Alarm in S8700 Media Server
Table 22: SME Alarm in Media Server on page 78 describes the SME alarm (for RALM-SVC
(Remote Alarm Service) and its troubleshooting procedures.
Table 22: SME Alarm in Media Server
Event Alarm
ID
Level
1
Back to:
MAJ
Alarm Text, Cause/Description, Recommendation
“Far-end alarm service is down” — No remote alarm service is available
since the other server is unable to report alarms — due to a failure of either
the GMM or administered reporting mechanisms (SNMP and/or modem).
1. Look for any GMM failures on the other server, either using the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by examining
/var/log/ecs/wdlog.
2. If a GMM failure was found:
a. See if the GMM application is up, either from the:
- Web interface, by selecting View Process Status
- Linux command line, by entering statapp
b. If so, continue with Step 3.
If not, try to restart this application by entering start -s GMM on the
Linux command line.
c. If the GMM application successfully restarts, continue with Step 4.
If not, escalate the problem to the next higher tier.
3. If a GMM failure was not found, see if alarm reporting failed by looking in
the trace log for a string that includes “snd2Inads”, either from the:
- Web interface, by:
a. Selecting the View System Logs diagnostic and Logmanager
Debug trace
b. Specifying the “Event Range” for the appropriate time frame
c. Matching the “snd2Inads” pattern
- Linux command line, by entering logv -t ts
4. Test the administered reporting mechanisms, by entering testinads
on the Linux command line.
5. Once the alarm is resolved, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the appropriate
alarm, and Clear
- Linux command line, by entering almclear -n #id
Hardware MOs
Server-related alarms
78 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
SVC_MON (Service Monitor)
S8700 | 8710 / S8500
SVC_MON is a media server process, started by Watchdog, to monitor Linux services and
daemons. It also starts up threads to communicate with a hardware-sanity device.
Table 23: SVC_MON Alarms in Media Server on page 80 describes the SVC_MON MO’s
alarms and their troubleshooting procedures.
For information about Watchdog, see _WD (Watchdog) Alarms on page 99.
Issue 1 June 2005
79
Server Alarms
Table 23: SVC_MON Alarms in Media Server
Event Alarm
ID
Level
1
MIN
Alarm Text, Cause/Description, Recommendation
“service atd could not be restarted” — The Linux at daemon is down.
Scheduled services such as session cleanup or daily filesync will not work.
1. From the /sbin directory type service atd restart to restart the at
daemon.
2. If the daemon restarts, manually clear the alarm, either from the:
● Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
● Linux command line, by entering almclear -n #id
If not, escalate this problem for explicit guidance with steps 2a through 3
a. Enter grep svc_mon /var/log/messages to investigate why the
daemon failed.
! CAUTION:
CAUTION:
Since the following commands cause a brief service outage,
they should only be executed at the customer’s convenience.
b. If the grep command’s output does not help:
● S8700 | 8710: enter server to verify that the suspected server is the
standby. If necessary and at the customer’s convenience, enter
server -if to force a server interchange.
● S8500: Proceed to Step d.
If necessary and at the customer’s convenience, enter server -if to
force a server interchange.
c. S8700 | 8710: Reboot the standby server, either from the:
● Web interface, by selecting Shutdown This Server
● Linux command line, entering /sbin/shutdown -r now
d. S8500: Reboot the server, either from the:
● Web interface, by selecting Shutdown This Server
● Linux command line, entering /sbin/shutdown -r now
3. If rebooting the standby does not help or if the problem recurs, escalate
the problem to the next higher tier.
1 of 8
80 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 23: SVC_MON Alarms in Media Server (continued)
Event Alarm
ID
Level
2
MIN
Alarm Text, Cause/Description, Recommendation
“service crond could not be restarted” — The Linux cron daemon is down.
Periodic services such as session cleanup or daily filesync will not work.
1. Enter /sbin/service cron restart to restart the cron daemon.
2. If the daemon restarts, manually clear the alarm, either from the:
●
Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
●
Linux command line, by entering almclear -n #id
If not, escalate this problem for explicit guidance with steps 2a through 3
a. Enter grep svc_mon /var/log/messages to investigate why the
daemon failed.
Since the following commands cause a brief service outage, they should only
be executed at the customer’s convenience.
b. If the grep command’s output does not help:
●
S8700 | 8710: enter server to verify that the suspected server is the
standby. If necessary and at the customer’s convenience, enter
server -if to force a server interchange.
●
S8500: Proceed to Step d.
If necessary and at the customer’s convenience, enter server -if to
force a server interchange.
c. S8700 | 8710: Reboot the standby server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
d. S8500: Reboot the server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
3. If rebooting the standby does not help or if the problem recurs, escalate
the problem to the next higher tier.
2 of 8
Issue 1 June 2005
81
Server Alarms
Table 23: SVC_MON Alarms in Media Server (continued)
Event Alarm
ID
Level
3
MIN
Alarm Text, Cause/Description, Recommendation
“service inet could not be restarted” — The Linux internet server daemon is
down. Networking services will not work.
1. Enter /sbin/service inet restart to restart the inet daemon.
2. If the daemon restarts, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the appropriate
alarm, and Clear
- Linux command line, by entering almclear -n #id
If not, escalate this problem for explicit guidance with steps 2a through
3.
a. Enter grep svc_mon /var/log/messages to investigate why the
daemon failed.
b. If this problem affects call processing, continue with the following
steps now.
If not, continue only at the customer’s convenience – since the
following commands cause a brief service outage.
The following commands cause a brief service outage.
c. If the grep command’s output does not help:
●
S8700 | 8710: enter server to verify that the suspected server is the
standby. If necessary and at the customer’s convenience, enter
server -if to force a server interchange.
●
S8500: Proceed to Step e.
If necessary and at the customer’s convenience, enter server -if to
force a server interchange.
d. S8700 | 8710: Reboot the standby server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
e. S8500: Reboot the server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
3. If rebooting the standby does not help or if the problem recurs, escalate
the problem to the next higher tier.
3 of 8
82 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 23: SVC_MON Alarms in Media Server (continued)
Event Alarm
ID
Level
4
MIN
Alarm Text, Cause/Description, Recommendation
“service syslog could not be restarted” — Linux “syslog” service is down.
Event logging to syslog and alarm generation will fail.
1. Enter /sbin/service syslog restart to restart the syslog service.
2. If the service restarts, manually clear the alarm, either from the:
●
Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
●
Linux command line, by entering almclear -n #id
If not, escalate this problem for explicit guidance with steps 2a through 3
a. Enter grep svc_mon /var/log/messages to investigate why the
daemon failed.
Since the following commands cause a brief service outage, they should only
be executed at the customer’s convenience.
b. If the grep command’s output does not help:
●
S8700 | 8710: enter server to verify that the suspected server is the
standby. If necessary and at the customer’s convenience, enter
server -if to force a server interchange.
●
S8500: Proceed to Step d.
If necessary and at the customer’s convenience, enter server -if to
force a server interchange.
c. S8700 | 8710: Reboot the standby server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
d. S8500: Reboot the server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
3. If rebooting the standby does not help or if the problem recurs, escalate
the problem to the next higher tier.
4 of 8
Issue 1 June 2005
83
Server Alarms
Table 23: SVC_MON Alarms in Media Server (continued)
Event Alarm
ID
Level
5
MIN
Alarm Text, Cause/Description, Recommendation
“service xntpd could not be restarted” — The Linux network time protocol
daemon is down. The server’s clock and recently logged time stamps may
be inaccurate.
1. Enter /sbin/service xntpd restart to restart the xntpd daemon.
2. If the daemon restarts, manually clear the alarm, either from the:
●
Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
●
Linux command line, by entering almclear -n #id
If not, escalate this problem for explicit guidance with steps 2a through 3
a. Enter grep svc_mon /var/log/messages to investigate why the
daemon failed.
b. If this problem affects call processing, continue with the following
steps now.
If not, continue only at the customer’s convenience – since the
following commands cause a brief service outage.
The following commands cause a brief service outage.
c. If the grep command’s output does not help:
●
S8700 | 8710: enter server to verify that the suspected server is the
standby. If necessary and at the customer’s convenience, enter
server -if to force a server interchange.
●
S8500: Proceed to Step e.
If necessary and at the customer’s convenience, enter server -if to
force a server interchange.
d. S8700 | 8710: Reboot the standby server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
e. S8500: Reboot the server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
3. If rebooting the standby does not help or if the problem recurs, escalate
the problem to the next higher tier.
5 of 8
84 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 23: SVC_MON Alarms in Media Server (continued)
Event Alarm
ID
Level
6
MIN
Alarm Text, Cause/Description, Recommendation
“service dbgserv could not be restarted” — Debug server is down, and
Gemini debugger may not work. Although losing this service does not affect
operations, the debugging of a running system is prevented.
1. Enter /sbin/service dbgserv restart to restart the dbgserv
service.
2. If the service restarts, manually clear the alarm, either from the:
●
Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
●
Linux command line, by entering almclear -n #id
If not, escalate this problem for explicit guidance with steps 2a through 3
a. Enter grep svc_mon /var/log/messages to investigate why the
daemon failed.
Since the following commands cause a brief service outage, they should only
be executed at the customer’s convenience.
b. If the grep command’s output does not help:
●
S8700 | 8710: enter server to verify that the suspected server is the
standby. If necessary and at the customer’s convenience, enter
server -if to force a server interchange.
●
S8500: Proceed to Step d.
If necessary and at the customer’s convenience, enter server -if to
force a server interchange.
c. S8700 | 8710: Reboot the standby server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
d. S8500: Reboot the server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
3. If rebooting the standby does not help or if the problem recurs, escalate
the problem to the next higher tier.
6 of 8
Issue 1 June 2005
85
Server Alarms
Table 23: SVC_MON Alarms in Media Server (continued)
Event Alarm
ID
Level
7
MIN
Alarm Text, Cause/Description, Recommendation
“service prune could not be restarted” — The prune service is not running.
The hard disk’s partition usage is not being monitored or cleaned.
1. Enter /sbin/service prune restart to restart the prune service.
2. If the service restarts, manually clear the alarm, either from the:
●
Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
●
Linux command line, by entering almclear -n #id
If not, escalate this problem for explicit guidance with steps 2a through 3
a. Enter grep svc_mon /var/log/messages to investigate why the
daemon failed.
b. If this problem affects call processing, continue with the following
steps now.
If not, continue only at the customer’s convenience – since the
following commands cause a brief service outage.
The following commands cause a brief service outage.
c. If the grep command’s output does not help:
●
S8700 | 8710: enter server to verify that the suspected server is the
standby. If necessary and at the customer’s convenience, enter
server -if to force a server interchange.
●
S8500: Proceed to Step e.
If necessary and at the customer’s convenience, enter server -if to
force a server interchange.
d. S8700 | 8710: Reboot the standby server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
e. S8500: Reboot the server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
3. If rebooting the standby does not help or if the problem recurs, escalate
the problem to the next higher tier.
7 of 8
86 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 23: SVC_MON Alarms in Media Server (continued)
Event Alarm
ID
Level
8
MIN
Alarm Text, Cause/Description, Recommendation
“service httpd could not be restarted” — The hypertext transfer protocol
daemon is down. The Web interface will not work.
1. Enter /sbin/service httpd restart to restart the http daemon.
2. If the daemon restarts, manually clear the alarm, either from the:
●
Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
●
Linux command line, by entering almclear -n #id
If not, escalate this problem for explicit guidance with steps 2a through 3
a. Enter grep svc_mon /var/log/messages to investigate why the
daemon failed.
Since the following commands cause a brief service outage, they should only
be executed at the customer’s convenience.
b. If the grep command’s output does not help:
●
S8700 | 8710: enter server to verify that the suspected server is the
standby. If necessary and at the customer’s convenience, enter
server -if to force a server interchange.
●
S8500: Proceed to Step d.
If necessary and at the customer’s convenience, enter server -if to
force a server interchange.
c. S8700 | 8710: Reboot the standby server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
d. S8500: Reboot the server, either from the:
●
Web interface, by selecting Shutdown This Server
●
Linux command line, entering /sbin/shutdown -r now
3. If rebooting the standby does not help or if the problem recurs, escalate
the problem to the next higher tier.
8 of 8
Back to:
Hardware MOs
Server-related alarms
Issue 1 June 2005
87
Server Alarms
_TM (Translation Manager)
S8700 | 8710 / S8500 / S8300
The _TM MO is an S8700 Media Server that monitors the server’s ability to read
Communication Manager translations. Table 24: TM Alarm in Media Server on page 88
describes the _TM MO’s alarm and its troubleshooting procedures.
Table 24: TM Alarm in Media Server
Event
ID
1
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Cannot read translations” — Server could not read translations. Usually,
indicates a failure loading translations, but can also infrequently occur on a
running system.
S8700 | 8710: The servers spontaneously interchange.
S8500: The server reboots.
1. Check the integrity of the translation files xln1 and xln2 in /etc/opt/defty,
and verify that they are of the same non-zero length.
2. From the /etc/opt/defty directory enter the Linux command cksum
xln1 xln2 to verify that the checksum of the files are identical.
3. S8700 | 8710: Copy the translation files from the backup or the other
server.
4. S8500: 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 comes up, this is probably a translation problem.
If not, escalate the problem.
7. Once resolved, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
Back to:
Hardware MOs
Server-related alarms
88 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
UPS (Uninterruptible Power Supply)
S8700 | 8710 / S8500 / S8300
The UPS MO supports the UPS device for each media server. This MO’s maintenance software
reacts to UPS-generated in-line errors via SNMP traps.
Note:
Note:
This MO provides no periodic or on-demand tests.
UPS Traps to Media Server
Table 25: Enterprise-Specific UPS Traps to Server on page 89 contains the various
UPS-generated SNMP traps to the media server.
Table 25: Enterprise-Specific UPS Traps to Server
SNMP Trap from UPS
Event
ID
Definition of Trap
Trap (1)
#6
(1–8)
Alarm string = #1, ACT, UPS, A, 6, MAJ, power failure:
Shutting down in 6 minutes.
If the Event ID is 6, the UPS battery’s power is in a
critically low condition, with an estimated 6 minutes of
remaining holdover.
●
A warning is written to every logged-in user of the
server.
●
When 6 minutes elapse, the server begins shutting
down.
(For troubleshooting procedures, see Events #1–8 on
page 92)
Trap (1)
#7
(1–8)
Alarm string = #1, ACT, UPS, A, 7, MAJ, power failure:
Shutting down in 7 minutes.
The UPS battery’s power is in a critically low condition,
with an estimated 7 minutes of remaining holdover.
●
A warning is written to every logged-in user of the
server.
●
When 7 minutes elapse, the server begins shutting
down.
(For troubleshooting procedures, see Events #1–8 on
page 92)
1 of 4
Issue 1 June 2005
89
Server Alarms
Table 25: Enterprise-Specific UPS Traps to Server (continued)
SNMP Trap from UPS
Event
ID
Definition of Trap
Trap (1)
#8
(1–8)
Alarm string = #1, ACT, UPS, A, 8, MAJ, power failure:
Shutting down in 8 minutes.
The UPS battery’s power is in a critically low condition,
with an estimated 8 minutes of remaining holdover.
●
A warning is written to every logged-in user of the
server.
●
When 8 minutes elapse, the server begins shutting
down.
(For troubleshooting procedures, see Events #1–8 on
page 92)
Trap (3)
upsAlarmShutdownPend
ing
#12
Alarm string = #1, ACT, UPS, A, 12, WRN, Miscellaneous
trap, e.g., bad battery.
(For troubleshooting procedures, see Event #12 on
page 92)
Trap (3)1
upsAlarmShutdownImmi
nent
#13
Alarm string = #1,ACT, UPS, A, 13, MAJ, Miscellaneous
trap, e.g., bad battery.
(For troubleshooting procedures, see Event #13 on
page 92)
Trap (3)1
upsAlarmDepletedBatter
y
#14
Alarm string = #1,ACT,UPS,A,14,MAJ,Miscellaneous
trap, e.g., bad battery.
(For troubleshooting procedures, see Event #14 on
page 93)
Trap (3)1
upsAlarmBatteryBad
#15
Alarm string = #1,ACT,UPS,A,15,MIN,Miscellaneous
trap, e.g., bad battery
(For troubleshooting procedures, see Event #15 on
page 93)
Trap (3)
upsAlarmInputBad
#16
Alarm string = #1,ACT,UPS,A,16,MIN,Miscellaneous
trap, e.g., bad battery
(For troubleshooting procedures, see Event #16 on
page 93)
Trap (3)
upsAlarmTempBad
#17
Alarm string = #1,ACT,UPS,A,17,WRN,Miscellaneous
trap, e.g., bad battery
(For troubleshooting procedures, see Event #17 on
page 93)
2 of 4
90 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 25: Enterprise-Specific UPS Traps to Server (continued)
SNMP Trap from UPS
Event
ID
Definition of Trap
Trap (3)
upsAlarmCommunicatio
nsLost
#18
Alarm string = #1,ACT,UPS,A,18,WRN,Miscellaneous
trap, e.g., bad battery
(For troubleshooting procedures, see Event #18 on
page 93)
Trap (3)
upsAlarmBypassBad
#19
Alarm string = #1,ACT,UPS,A,19,WRN,Miscellaneous
trap, e.g., bad battery
(For troubleshooting procedures, see Event #19 on
page 94)
Trap (3)
upsAlarmLowBattery
#20
Alarm string = #1,ACT,UPS,A,20,WRN,Miscellaneous
trap, e.g., bad battery
(For troubleshooting procedures, see Event #20 on
page 94)
Trap (3)
upsAlarmUpsOutputOff
#21
Alarm string = #1,ACT,UPS,A,21,WRN,Miscellaneous
trap, e.g., bad battery
(For troubleshooting procedures, see Event #21 on
page 94)
Trap (3)
upsAlarmOutputBad
#22
Alarm string = #1,ACT,UPS,A,22,WRN,Miscellaneous
trap, e.g., bad battery
(For troubleshooting procedures, see Event #22 on
page 94)
Trap (3)
upsAlarmOutputOverloa
d
#23
Alarm string = #1,ACT,UPS,A,23,WRN,Miscellaneous
trap, e.g., bad battery
(For troubleshooting procedures, see Event #23 on
page 94)
Trap (3)
upsAlarmChargerFailed
#24
Alarm string = #1,ACT,UPS,A,24,WRN,Miscellaneous
trap, e.g., bad battery
(For troubleshooting procedures, see Event #24 on
page 94)
Trap (3) –
upsAlarmFanFailure
#25
Alarm string = #1,ACT,UPS,A,25,WRN,Miscellaneous
trap, e.g., bad battery
(For troubleshooting procedures, see Event #25 on
page 94)
Trap (3) –
upsAlarmFuseFailure
#26
Alarm string = #1,ACT,UPS,A,26,WRN,Miscellaneous
trap, e.g., bad battery
(For troubleshooting procedures, see Event #26 on
page 95)
3 of 4
Issue 1 June 2005
91
Server Alarms
Table 25: Enterprise-Specific UPS Traps to Server (continued)
SNMP Trap from UPS
Event
ID
Definition of Trap
Trap (3) –
upsAlarmGeneralFault
#27
#1,ACT,UPS,A,27,WRN,Miscellaneous trap, e.g., bad
battery
(For troubleshooting procedures, see Event #27 on
page 95)
4 of 4
1. These events will degrade the server’s state of health.
System Technician-Demanded Tests:
Descriptions and Error Codes
This MO provides no on-demand tests for system technicians.
Back to:
Hardware MOs
Server-related alarms
UPS Alarms to the Media Server
S8700 | 8710 / S8500 / S8300
Table 26: UPS Alarms to the Media Server on page 92 describes the server’s UPS-related
alarms and their troubleshooting procedures.
Table 26: UPS Alarms to the Media Server
Event
ID
1–8
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“upsEstimatedMinutesRemaining” — UPS does not have an AC-power
source.
1. Restore AC power to the UPS.
12
MAJ
“upsAlarmShutdownPending” — A shutdown-after-delay countdown is
underway (i.e., the UPS has been commanded off).
1. Stop countdown timer. (Can be done via SNMP messages.)
13
MAJ
“upsAlarmShutdownImminent” — The UPS will turn off power to the load in
< 5 seconds.
1. Restore AC power to the UPS.
1 of 4
92 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 26: UPS Alarms to the Media Server (continued)
Event
ID
14
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“upsAlarmDepletedBattery” — If primary power is lost, the UPS could not
sustain the current load.
1. Charge or replace the batteries in the UPS, according to procedures in
its Site Preparation, Installation, and Operator’s Manual, 167-405-035.
15
MAJ
“upsAlarmBatteryBad” — One or more batteries needs to be replaced.
1. Replace any defective batteries in the UPS, according to procedures in
its Site Preparation, Installation, and Operator’s Manual, 167-405-035.
16
MIN
“upsAlarmInputBad” — An input condition is out of tolerance.
1. Provide appropriate AC power to the UPS.
17
MIN
“upsAlarmTempBad” — The internal temperature of a UPS is out of
tolerance. (On the UPS, the “over temperature” alarm indicator flashes,
and the UPS changes to Bypass mode for cooling. Either:
1. Look for and remove any obstructions to the UPS’s fans.
2. Wait at least 5 minutes, and restart the UPS.
3. Check for and resolve any fan alarms (Event ID 25) against the UPS.
4. Either:
18
MIN
●
Change (increase or decrease) the environment’s temperature.
●
Change the alarming thresholds.
“upsAlarmCommunicationsLost” — The SNMP agent and the UPS are
having communications problems. (A UPS diagnosis may be required.)
1. Behind the UPS in its upper left-hand corner, verify that an SNMP card
(with an RJ45 connector) resides in the UPS — instead of a serial card
with DB9 and DB25 connectors.
2. Verify that the server is physically connected to the UPS via the RJ45
connector.
3. Verify that the SNMP card is properly administered according to the
procedures in its users guide, provided by the vendor.
4. If necessary, replace the SNMP card in the UPS.
5. If the problem persists, replace the UPS, and diagnose it later.
2 of 4
Issue 1 June 2005
93
Server Alarms
Table 26: UPS Alarms to the Media Server (continued)
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
19
WRN
“upsAlarmBypassBad” — The “source” power to the UPS, which (during a
UPS overload or failure) also serves as “bypass” power to the load, is out of
tolerance — incorrect voltage by > ±12% or frequency > ±3%.
This on-line UPS normally regenerates its source power into clean AC
power for the load. However, the source power’s quality is currently
unacceptable as bypass power to the load).
1. Verify that the UPS expects the correct “nominal input voltage” from its
power source.
2. If so, restore acceptable AC power to the UPS.
If not, reconfigure the UPS to expect the correct voltage, according to
procedures in its Site Preparation, Installation, and Operator’s Manual,
167-405-035.
20
WRN
“upsAlarmLowBattery” — The battery’s remaining run time ≤ specified
threshold.
1. Restore AC power to the UPS.
21
WRN
“upsAlarmUpsOutputOff” — As requested, UPS has shut down output
power. The UPS is in Standby mode.
1. Turn on output power. (Can be done via SNMP messages.)
22
WRN
“upsAlarmOutputBad” — A receptacle’s output is out of tolerance. (A UPS
diagnosis is required.)
1. Replace the UPS, and diagnose it later.
23
WRN
“upsAlarmOutputOverload” — The load on the UPS exceeds its output
capacity. The UPS enters Bypass mode.
1. Reduce the load on the UPS.
2. Verify that the UPS returns to Normal mode.
24
WRN
“upsAlarmChargerFailed” — The UPS battery charger has failed. (A UPS
diagnosis is required.)
1. Replace the UPS, and diagnose it later.
25
WRN
“upsAlarmFanFailure” — One or more UPS fans have failed. Unless lightly
loaded, the UPS enters Bypass mode.
1. Replace the UPS, and diagnose it later.
3 of 4
94 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 26: UPS Alarms to the Media Server (continued)
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
26
WRN
“upsAlarmFuseFailure” — One or more UPS fuses have failed.
1. Replace the UPS, and diagnose it later.
27
WRN
“upsAlarmGeneralFault” — A general fault occurred in the UPS. (A UPS
diagnosis is required.)
1. Replace the UPS, and diagnose it later.
4 of 4
This MO provides periodic and on-demand testing. The periodic test runs the “handshake” test
every 15 minutes. The on-demand tests include the “handshake”, “off-hook”, and “reset_usb”
tests.
Hardware MOs
Server-related alarms
USB1 (Modem Testing) Alarms
S8700 | 8710 / S8500
This MO provides periodic and on-demand testing. The periodic test runs the “handshake” test
every 15 minutes. The on-demand tests include the “handshake”, “off-hook”, and “reset_usb”
tests.
MO’s Name
(in Alarm Log)
Alarm
Level
Initial Linux Command to Run
USB1
MAJ
testmodem
USB Port Modem Testing
USB1
MIN
testmodem
USB Port Modem Testing
USB1
WRN
testmodem
USB Port Modem Testing
Full Name of MO
Usage: testmodem [-s] | [-l] | [-t arg] | [-?]
no argument
Performs “short” test.
-s
Short test, performs handshake and off-hook tests this is also the default
option.
-l
Performs “long” tests.
Issue 1 June 2005
95
Server Alarms
-t arg
Specific test to perform.
Possible values for arg are: reset_usb | handshake | off-hook |
-?
Usage (this).
Alarm Log Entries
Table 27: USB1 Alarm Log Entries
EVENT
ID#
Aux
Data
Associated Test
Alarm
Level
On/
Off
Board
Linux Test to
Clear Value
1 (1)
Handshake test
MIN
ON
testdupboard
2 (2)
Modem Off-Hook test
MAJ
ON
testdupboard
Notes:
1. Event ID #1 Handshake Test failed — With 3 consecutive failures of either the periodic or
on-demand test, the following Minor alarm is logged:
#1,ACT,USB1,A,1,MIN,USB Modem handshake test failed
2. Event ID #2 Modem Off-Hook test failed — With 3 consecutive failures of this test, the
following Major alarm is logged:
#1,ACT,USB1,A,2,MAJ,USB Modem Off-Hook test failed
System Technician-Demanded Tests:
Descriptions and Error Codes
Always investigate tests in the order presented in the following table. For example, by clearing
error codes associated with the Handshake test, you may also clear errors generated by other
tests in the testing sequence.
Short Test
Sequence
Long Test
Sequence
D/ND1
Handshake test
X
X
D
Off-Hook test
X
X
D
Reset USB test
X
X
D
Order of Investigation
1. D = Destructive; ND = Nondestructive
96 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Handshake Test
This test is destructive.
This test verifies that modem’s hardware is attached and that the modem can “handshake” with
the USB port. The test:
1. Tries to open the device
2. Sends a handshake string (ATZ) to the modem
The modem should return an “OK” string.
The following errors can be detected:
Table 28: TEST Handshake Test
Error Code
Test
Result
Description / Recommendation
Modem in
use, try again
later
ABRT
Another application is currently using the modem. Try again later.
Could not
open USB
port
ABRT
System error: An attempt to open the USB device failed.
1. Retry the test in about 5 minutes.
2. If the test still fails, escalate the problem.
Read error,
could not run
test
ABRT
After the ATZ is sent, a read of the USB device is done. If the
read fails, a probable system error aborted the test.
1. Retry the test in about 5 minutes.
2. If the test still fails, escalate the problem.
Modem
Handshake
test failed
FAIL
The modem did not return an “OK” string within a 15-second
interval.
Off-Hook Test
This test is destructive.
Issue 1 June 2005
97
Server Alarms
This test runs an off-hook test for the modem attached to the USB port on the server. The test
sends an ATH1 string to check that a line is connected to the modem. The following errors can
be detected:
Table 29: TEST Off-Hook Test
Error Code
Test
Result
Description / Recommendation
Modem in
use, try again
later
ABRT
Some other application is currently using the modem. Try again
later.
Could not
open USB
port
ABRT
System error: An attempt to open the USB device failed. Try again
later
Read error,
could not run
test
ABRT
After the ATZ is sent, a read of the USB device is done. If the read
fails, a probable system error aborted the test. Try again.
Modem
Off-Hook test
failed
FAIL
Modem Off-Hook test failed: The modem did not return an “OK”
string within a 15-second interval. This indicates that dial tone was
not detected in the allotted time.
Reset USB Test
This test is destructive.
This test causes the modem to be reset, even if the modem is in use. Although no failures are
produced by this test, the following error can be detected:
Table 30: TEST Reset USB
Error
Code
Test
Result
Description / Recommendation
Could not
open USB port
ABRT
System error: An attempt to open the USB device failed. Try
again later.
Back to:
Hardware MOs
Server-related alarms
98 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
_WD (Watchdog) Alarms
S8700 | 8710 / S8500 / S8300
The Watchdog MO is a media server process that:
●
Creates other Communication Manager processes
●
Monitors their sanity
●
Can recover their failures
These applications come up and start heartbeats to the Watchdog. For more information about
Watchdog, see Table 31: _WD Alarms in Media Server on page 100 that describes the _WD
MO’s alarms and their troubleshooting procedures.
Watchdog also starts up a script to monitor Linux services and daemons, and threads to
communicate with a hardware-sanity device. For alarm-related information about these
services, daemons, and threads, see SVC_MON (Service Monitor) on page 79.
Issue 1 June 2005
99
Server Alarms
Table 31: _WD Alarms in Media Server
Event
ID
4
S8300
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Application <name> (pid) TOTALLY FAILED” — An application is present,
but not launching. The application could not start the maximum allowed
number of times. (This alarm usually occurs with Event ID #20.)
1. To verify the alarm, look for the application’s name or process ID
(PID),” either using the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
2. If the application is down, enter start -s application to start the
application.
3. If the application comes up, continue with Step 7.
If not, check the trace log to further investigate why the application
fails, either from the:
- Web interface by:
a. Selecting the View System Logs diagnostic and Logmanager
Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the application’s PID as the pattern
- Linux command line, by entering logv -t ts
Look for a related core-dump file in /var/crash, and escalate for an
analysis of this file.
4. Verify that the executable file named in the log exists and is
executable.
To locate the application’s executable file, enter the Linux command:
ls -l /opt/ecs/sbin/appl
If the executable is present, Linux returns a symbolic link to its
location.
1 of 15
100 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 31: _WD Alarms in Media Server (continued)
Event
ID
Alarm
Level
4
(cont’d)
MAJ
Alarm Text, Cause/Description, Recommendation
5. If so (less common):
a. Enter ls -l on the symbolic link’s address.
b. Verify that the executable has “execution” permissions.
c. If not, enter chmod +x to enable execution of the application.
If not — Linux has returned a “null link” (more common):
- Acquire the executable from the CD.
6. Enter start -s application to start the application.
7. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
8. If the problem recurs, escalate the problem.
2 of 15
Issue 1 June 2005
101
Server Alarms
Table 31: _WD Alarms in Media Server (continued)
Event
ID
5
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“WARNING: timeout waiting for reqsvr to initialize” — During each server’s
boot process, the server’s Watchd process waits up to 2 minutes for its
“reqsvr” (request server) thread to initialize. If the 2-minute waiting interval
elapses, this server logs this alarm, and its boot process hangs.
(Meanwhile, if the other server is already booted or subsequently boots, it
assumes the active role.)
In that (when this alarm occurs) a server hangs during its booting process,
this alarm’s external symptoms resemble those of two other _WD alarms,
#13 (Except S8500) and #14 (Except S8500). Therefore, carefully
discriminate between these three events.
1. To inspect the symptoms of this problem, verify that the:
a. Linux OS and the Web interface are up (including the commands:
telnet, statapp, server, logv, cat, grep, tail, vi, etc.)
b. Watchdog application is partially up, but no other Communication
Manager software is up
c. The almdisplay command displays no alarms. Instead, the
command returns the message:
“almdisplay: 4: Unable to connect to
MultiVantage”
Since the following commands cause a brief service outage, they should
only be executed at the customer’s convenience.
2. Escalate this problem for explicit guidance with the following steps.
3. Enter server to verify that the suspected server is the standby.
If necessary and at the customer’s convenience, enter server -if
to force a server interchange.
4. Reboot the standby server, either from the:
- Web interface, by selecting Shutdown This Server
- Linux command line, by entering /sbin/shutdown -r now
5. Once the standby server has booted, verify that Event ID #5 was
logged, either using the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
3 of 15
102 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 31: _WD Alarms in Media Server (continued)
Event
ID
Alarm
Level
5
(cont’d)
MIN
6
MAJ
S8300
Alarm Text, Cause/Description, Recommendation
6. If rebooting the server does not help or if the problem recurs, escalate
the problem to the next higher tier.
“Application <name> (pid) not started, config parm errors” — Watchdog
cannot read its configuration file, /etc/opt/ecs/watchd.conf.
1. To verify the alarm, look for the application’s name or process ID
(PID), either using the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
2. Get a fresh copy of watchd.conf from the CD.
3. Verify that every executable file listed in watchd.conf exists and is
executable.
4. Enter start -s application to start the application.
5. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
4 of 15
Issue 1 June 2005
103
Server Alarms
Table 31: _WD Alarms in Media Server (continued)
Event
ID
7
S8300
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Application <name> not started, parm file errors” — Since an
application’s specified location in watchd.conf is incorrect, Watchdog
cannot start the application.
1. To verify the alarm, look for the application’s or process ID (PID),
either using the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
2. Verify that the executable file named in the log exists and is
executable.
To locate the application’s executable file, enter the Linux command:
ls -l /opt/ecs/sbin/appl
If the executable is present, Linux returns a symbolic link to its
location.
3. If so (less common):
a. Enter ls -l on the symbolic link’s address.
b. Verify that the executable has “execution” permissions.
c. If not, enter chmod +x to enable execution of the application.
If not — Linux has returned a “null link” (more common):
- Acquire the executable from the CD.
4. Verify that the string in watchd.conf is correct.
5. Enter start -s application to start the application.
6. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
5 of 15
104 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 31: _WD Alarms in Media Server (continued)
Event
ID
13
(Except
S8500)
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“ERROR: could not dup socket fd in reqsvr.c, heartbeat thread not created,
errno=<x>” — As either a:
●
Booting application initiates
●
Restarting application re-initiates heart beating with Watchdog (see
Event ID #5), the “reqsvr” (request server) thread tries to create a
duplicate socket for the hearbeating thread. This alarm indicates that
reqsvr could not create the socket. (Meanwhile, if the other server is
already started or subsequently starts, it assumes the active role.)
In that (when this alarm occurs) a server hangs, this alarm’s external
symptoms resemble those of two other _WD alarms, #5 and #14
(Except S8500). Therefore, carefully discriminate between these three
events.
1. To inspect the symptoms of this problem, verify that the:
a. Linux OS and the Web interface are up (including the commands:
telnet, statapp, server, logv, cat, grep, tail, vi, etc.)
b. Watchdog application is partially up, and some other
Communication Manager processes may be up, either using the:
- Web interface, by selecting View Process Status
- Linux command line, by entering statapp
c. If the GMM process is up, the almdisplay -v command shows
Event #13’s message string.
If not, the Watchdog log shows the message string, either using
the:
- Web interface, by selecting Diagnostics > View System Logs
and Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
Since the following commands cause a brief service outage, they should
only be executed at the customer’s convenience.
2. Escalate this problem for explicit guidance with the following steps.
3. Enter server to verify that the suspected server is the standby.
If necessary and at the customer’s convenience, enter server -if
to force a server interchange.
6 of 15
Issue 1 June 2005
105
Server Alarms
Table 31: _WD Alarms in Media Server (continued)
Event
ID
13
(Except
S8500)
(cont’d)
Alarm
Level
MIN
Alarm Text, Cause/Description, Recommendation
4. Reboot the standby server, either from the:
- Web interface, by selecting Shutdown This Server
- Linux command line, by entering /sbin/shutdown -r now
5. If rebooting the server does not help or if the problem recurs, escalate
the problem to the next higher tier.
14
(Except
S8500)
MIN
“ERROR in req2svr.p trying to create heartbeat thread, errno=<x>” — After
the “reqsvr” (request server) creates a duplicate socket (see Event ID #13
(Except S8500)), it tries to create a heart beating thread. This alarm
indicates that reqsvr could not create the thread. (Meanwhile, if the other
server is already started or subsequently starts, it assumes the active role.)
In that (when this alarm occurs) a server hangs, this alarm’s external
symptoms resemble those of two other _WD alarms, #5 and #13 (Except
S8500). Therefore, carefully discriminate between these three events.
1. To inspect the symptoms of this problem, verify that the:
a. Linux OS and the Web interface are up (including the commands:
telnet, statapp, server, logv, cat, grep, tail, vi, etc.)
b. Watchdog application is partially up, but all other Communication
Manager processes are up, either using the:
- Web interface, by selecting View Process Status
- Linux command line, by entering statapp
c. The almdisplay -v command shows Event #14’s message
string
Since the following commands cause a brief service outage, they should
only be executed at the customer’s convenience.
2. Escalate this problem for explicit guidance with the following steps.
3. Enter server to verify that the suspected server is the standby.
If necessary and at the customer’s convenience, enter server -if
to force a server interchange.
4. Reboot the standby server, either from the:
- Web interface, by selecting Shutdown This Server
5. If rebooting the server does not help or if the problem recurs, escalate
the problem to the next higher tier.
7 of 15
106 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 31: _WD Alarms in Media Server (continued)
Event
ID
15
S8300
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Detected a rolling reboot” — Watchdog has detected “x” number of Linux
reboots within “y” minutes (where x and y are configurable in /etc/opt/
ecs/watchd.conf). Rolling reboots have a wide variety of possible
causes.
1. To verify the alarm, look for the message, “WARNING: Rolling reboot
detected!!,“either using the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
2. Escalate this problem for explicit guidance with the following steps.
3. Paying special attention to Communication Manager errors, continue
examining the Watchdog log (from Step 1), and try to determine which
application failed.
4. Verify that every executable file listed in watchd.conf exists and is
executable. Rolling reboots are often caused by executables in
unexpected locations.
5. If the files and their locations are OK, investigate the trace log to
isolate the cause, either from the:
- Web interface by:
a. Selecting the View System Logs diagnostic and Logmanager
Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the “rolling reboot” pattern
- Linux command line, by entering logv -t ts
8 of 15
Issue 1 June 2005
107
Server Alarms
Table 31: _WD Alarms in Media Server (continued)
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
18
WRN
“Application <name> restarted. Retry <retry count>, New Pid: <pid>” —
An application has failed, and Watchdog successfully restarted it.
S8300
1. To verify the alarm, look for the application’s name or process ID (pid),
either using the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
2. No resolution. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
9 of 15
108 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 31: _WD Alarms in Media Server (continued)
Event
ID
19
S8300
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
“Application failed unintentionally” — Watchdog is bringing the system
down because an application failed to start correctly. The application may
have failed to start either because:
●
The file did not exist (coincident with Event ID #7).
●
Required application parameters were missing or invalid in
watchd.conf.
1. To verify the alarm, look for the message, “Application num <#>
(<application path>) not started. Watchdog exiting NOW,” either using
the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
2. Verify that the file named in the log exists and is executable.
3. Verify that the string in watchd.conf is correct.
4. If Steps 2 and 3 are OK, investigate the trace log to see why the
application fails, either from the:
- Web interface by:
a. Selecting the View System Logs diagnostic and Logmanager
Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the application’s number as the pattern
- Linux command line, by entering logv -t ts
5. Once resolved, manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
10 of 15
Issue 1 June 2005
109
Server Alarms
Table 31: _WD Alarms in Media Server (continued)
Event
ID
20
S8300
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Application <name> (pid) TOTALLY FAILED” — Application failed the
maximum allowed number of times. (This alarm usually occurs with Event
ID #4.)
1. To verify the alarm, look for the application’s name or process ID
(PID), either using the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
- See if the application is up, either from the:
- Web interface, by selecting View Process Status
- Linux command line, by entering statapp
2. If the application is down, enter start -s application to start the
application.
3. If the application comes up, continue with Step 7.
If not, check the trace log to further investigate why the application
fails, either from the:
- Web interface by:
a. Selecting the View System Logs diagnostic and Logmanager
Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the application’s PID as the pattern
- Linux command line, by entering logv -t ts
4. To locate the application’s executable file, enter the Linux command:
ls -l /opt/ecs/sbin/appl
If the executable is present, Linux returns a symbolic link to its
location.
11 of 15
110 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 31: _WD Alarms in Media Server (continued)
Event
ID
20
(cont’d)
Alarm
Level
MAJ
Alarm Text, Cause/Description, Recommendation
5. If so (less common):
a. Enter ls -l on the symbolic link’s address.
b. Verify that the executable has “execution” permissions.
c. If not, enter chmod +x to enable execution of the application.
If not — Linux has returned a “null link” (more common):
- Acquire the executable from the CD
6. Enter start -s application to start the application.
7. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
8. If the problem recurs, escalate the problem.
12 of 15
Issue 1 June 2005
111
Server Alarms
Table 31: _WD Alarms in Media Server (continued)
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
22
WRN
“Application <name> (<pid>) terminated” — Watchdog successfully shut
down the named application, and (if appropriate) watchdog will try to
restart it.
S8300
1. To verify the alarm, look for the application’s name or process ID
(PID), either using the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w
2. On the standby server, look for occurrences of the stop command,
either from the:
- Web interface, by:
a. Selecting View System Logs
b. Selecting Platform command history log
c. Specifying the Event Range for the appropriate time frame
d. Matching the “Stop” pattern
- Linux command line, by entering 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 quite 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, then Watchdog
responded to abnormal internal processes by shutting down the
application.
Check the trace log for information about this application, either from
the:
- Web interface, by:
a. Selecting the View System Logs diagnostic and Logmanager
Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the application’s PID as the pattern
- Linux command line, by entering logv -t ts
13 of 15
112 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 31: _WD Alarms in Media Server (continued)
Event
ID
Alarm
Level
22
WRN
S8300
Alarm Text, Cause/Description, Recommendation
5. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
(cont’d)
- Linux command line, by entering almclear -n #id
6. Watch to see if the alarm recurs. If so, escalate the problem.
23
S8300
MAJ
“Watchd high-monitor thread is rebooting the system” — The:
1. Lo-monitor thread is missing heartbeats (can't get CPU time).
2. Hi-monitor thread has tried 3 times to recover the system by killing any
infinitely looping processes.
If after 3 CPU-occupancy profiles and recoveries, the lo-monitor thread is
still not heartbeating, then Watchd reboots the server.
3. To verify the alarm, look for messages:
Containing the CPU profiling results and attempted recoveries
Stating that Watchd is rebooting the server
using either the:
- Web interface, by selecting Diagnostics > View System Logs and
Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
A resolution is probably unnecessary. The server has usually rebooted
by the time a technician can analyze the system. (A reboot clears the
alarm and normally fixes problems with unresponsive software.)
4. Watch to see if the alarm recurs. If so, escalate the problem.
14 of 15
Issue 1 June 2005
113
Server Alarms
Table 31: _WD Alarms in Media Server (continued)
Event
ID
24
S8300
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
“Watchd’s high-monitor thread is stopping tickling of hw” — Event ID #23’s
call to reboot the server was unsuccessfully invoked. (A Linux kernel’s
semaphore is possibly stuck.) After this happens, Watchd stops tickling
the HW sanity timer so that the HW sanity watchdog executes a hard
reboot of the processor.
1. To verify that the alarm occurred, look for messages about:
Stopping the tickling of the HW sanity timer
CPU occupancy profiling
using either the:
- Web interface, by selecting Diagnostics > View System Logs
and Watchdog Logs
- Linux command line, by entering logv -w or, directly, by
examining /var/log/ecs/wdlog.
- If the HW sanity watchdog successfully executed a hard reboot,
the alarm was cleared. (This reboot normally fixes problems due
to unresponsive software.)
If not, power cycle the server to release it from this condition and to
clear the alarm.
2. Watch to see if the alarm recurs. If so, escalate the problem.
15 of 15
Back to:
Hardware MOs
Server-related alarms
114 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Login Alarms - S8300
S8300
Table 32: Login Alarms in Media Server on page 115 describes media server login alarms and
their troubleshooting procedures.
Table 32: Login Alarms in Media Server
Event
ID
Alarm
Level
1
WRN
Alarm Text, Cause/Description, Recommendation
1. On the Web Interface, choose View Current Alarms.
2. Notify Customer.
2
WRN
1. On the Web Interface, choose View Current Alarms.
2. Notify Customer.
3
MIN
Security violation.
1. On the Web Interface, choose View Current Alarms.
2. Notify Customer.
4
MIN
Security violation.
1. On the Web Interface, choose View Current Alarms.
2. Notify Customer.
5
MAJ
Security violation.
1. On the Web Interface, choose View Current Alarms.
2. Notify Customer.
Back to:
Hardware MOs
Server-related alarms
Issue 1 June 2005
115
Server Alarms
Virtual Alarms
S8300 only
The Virtual Announcement Media Module faults are managed as server alarms. In the S8300
Media Server, the Virtual Analog Angel (VAA) represents a messaging board. The VAA is a
virtual board on the G700. When the G700 reboots, the VAA senses that it has lost connectivity
with the G700, and triggers its "removal and re-insertion". The removal of the VAA causes the
AUDIX ports to go out-of-service and to return back in service when the re-insertion is complete.
An alarm of MAJOR severity is generated, indicating loss of connectivity with the G700, which
must be cleared manually. Table 33: Virtual Alarm in S8300 Media Server on page 116
summarizes this server alarm.
Table 33: Virtual Alarm in S8300 Media Server
Event
ID
1
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
Virtual Analog Angel (VAA) loss of connectivity with a G700, resulting in
temporary Out of Service (OOS) of AUDIX ports. A G700 reboot caused VAA
to "remove and re-insert" virtual board. Must be cleared manually.
1. Manually clear the alarm, either from the:
- Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
- Linux command line, by entering almclear -n #id
2. Execute list configuration all on SAT.
Verify that V8 MG MSG BOARD does not show no board against it.
(no board means AUDIX ports OOS.)
Back to:
Hardware MOs
Server-related alarms
Remote Maintenance Board (RMB) Alarms
S8500
The Remote Supervisor Adapter (RSA) board is installed in PCI-X slot 1 of the S8500 Media
Server. It monitors and reports alarms on S8500 components and software and provides control
to power on and power off the server.
116 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Note:
The S8500 has a set of alarms for the RSA card, which is also called the Remote
Maintenance Board (RMB). The MO name is RMB. Alarms reported, by the
S8500 media server, via the MO name RMB will include a Product ID beginning
with one (1) followed by nine digits.
The A+SAMP board in a S8500B media server may also report alarms via the
MO name RMB. See S8500B Augmentix Server Availability Management
Processor™ (A+SAMP) Alarms on page 120. When the A+SAMP board reports
alarms via the MO name RMB the Product ID begins with a five (5) followed by
nine digits.
Note:
Table 34: RMB Alarms in the S8500 Media Server
Event
ID
1
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MIN
"RMB driver missing - handshake Failed" - The driver for communicating
with the RSA card cannot be found. Several failures can generate this fault:
●
the Linux bash command /sbin/lsmod is missing
●
the results from running /sbin/lsmod could not be read
●
/sbin/lsmod returned nothing
●
the RSA device driver was not loaded
●
the RSA device driver does not exist
The recommendations are:
1. Be sure /sbin/ibmod exists and is executable.
2. Be sure /tmp exists as a directory and can be written.
3. Be sure /lib/modules/ibmasm/ibmasm.o exists and has read
permission.
4. Run the bash command "service ibmasm start".
2
MIN
"RMB cli is not loaded on the server." - The program that talks to the RSA
card could not be found. Several failures generate this fault:
●
the Linux bash command /bin/ls is missing or not working properly
●
the bash command /opt/ecs/rmb/rsa/rsacli is missing or is not
executable
The recommendations are:
1. Be sure all the above files and directories exist and have read and
execute permissions.
2. Reload any missing files from the distribution.
1 of 3
Issue 1 June 2005
117
Server Alarms
Table 34: RMB Alarms in the S8500 Media Server (continued)
Event
ID
3
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
"RMB reset command failed" - The RSA card did not respond to a reset
command. Several failures generate this fault:
●
the bash command opt/IBMmpcli/bin/mpcli is missing or is not
executable
●
the directory /usr/java/latest is missing or not symbolically linked to
the Java runtime environment (JRE)
●
the file /opt/ecs/rmb/rsareset does not exist or cannot be read
●
no response from the RSA card
●
the RSA card did not execute the request
The recommendations are:
1. Be sure all the above files and directories exist and have read and
execute permissions.
2. Reload any missing files from the distribution.
3. Be sure the RSA card is installed by looking at the back and checking
that the green power LED on the RSA card is on, and that the amber
error LED is off.
4. Verify that the RSA card is working by dialing into it or logging on to it
over the service’s port of the RSA card.
5. Restart the RSA card from the RSA modem or service’s port and check
the LEDs on the back of the card.
6. Verify that the RSA card is plugged into the PCI-X slot of the server.
7. Verify that the flat ribbon cable from the RSA card to the server
motherboard has been installed and is firmly seated in the connectors
at both ends.
8. Replace the RSA card.
2 of 3
118 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Alarms in Linux Media Servers
Table 34: RMB Alarms in the S8500 Media Server (continued)
Event
ID
4
Alarm
Level
Alarm Text, Cause/Description, Recommendation
MAJ
"RMB failed handshake test" - The RSA card did not respond to commands
from the server. Several failures generate this fault:
●
the bash command /opt/IBMmpcli/bin/mpcli is missing or is not
executable
●
the directory /usr/java/latest is missing or not symbolically linked to
the Java runtime environment (JRE)
●
the file /opt/ecs/rmb/rsagetip1 does not exist or cannot be read
●
no response from the RSA card
●
the RSA card did not execute the request
The recommendations are:
1. Be sure all the above files and directories exist and have read and
execute permissions.
2. Reload any missing files from the distribution.
3. Be sure the RSA card is installed by looking at the back and checking
that the green power LED on the RSA card is on, and that the amber
error LED is off.
4. Verify that the RSA card is working by dialing into it or logging on to it
over the service’s port of the RSA card.
5. Restart the RSA card from the RSA modem or service’s port and check
the LEDs on the back of the card.
6. Verify that the RSA card is plugged into the PCI-X slot of the server.
7. Verify that the flat ribbon cable from the RSA card to the server
motherboard has been installed and is firmly seated in the connectors
at both ends.
8. Replace the RSA card.
3 of 3
Back to:
Hardware MOs
Server-related alarms
Issue 1 June 2005
119
Server Alarms
S8500B Augmentix Server Availability Management Processor™
(A+SAMP) Alarms
S8500B Only
The Augmentix Server Availability Management Processor (A+SAMP) board is installed in the
S8500B media server. It monitors and reports alarms on S8500B components and software and
provides control to power on and power off the server.
The A+SAMP will report alarms when it detects certain failure conditions. See A+SAMP Alarms
in the S8500B Media Server on page 120. These alarms will be reported under the
Maintenance Object (MO) name RMB. These alarms will be reported with a Product ID
beginning with a five (5) and followed by nine digits.
The S8500 media server may also report failure conditions via the MO name RMB but these
alarms will have a Product ID that begins with a one (1) followed by nine digits. See Remote
Maintenance Board (RMB) Alarms on page 116.
Table 35: A+SAMP Alarms in the S8500B Media Server
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
0
MIN
Test Alarm. Hardware Platform Interface (HPI) User Event
1
MIN
Loss of power to host. Hardware Platform Interface (HPI) Sensor Event.
2
MAJ
Host boot timeout. Hardware Platform Interface (HPI) OEM Event
3
MAJ
Host Alarm. Hardware Platform Interface (HPI) User Event
4
MIN
Loss of External Power to SAMP. Hardware Platform Interface (HPI)
Sensor Event
5
MAJ
Host failure timeout. Hardware Platform Interface (HPI) Watchdog Event
120 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
S8710 Alarms
S8710 Alarms
S8710 environmental alarms
The Environmental maintenance object (ENV-MO) monitors environmental variables within the
server, including temperature and fans. However, you can check these variables from the
Maintenance Web Pages also.
To check the S8710 server temperature and voltage readings:
1. At the Maintenance Web Pages, select Diagnostics > Temperature/Voltage.
2. The Temperature/Voltage page displays.
Issue 1 June 2005
121
Server Alarms
3. Use the descriptions in Table 36 to interpret the report.
Table 36: S8710 Temperature and voltage report
Field
Description
ID
An identification number automatically generated by the system.
Type
Power supply:
●
Intelligent—power regulating
●
Standard—other
Fan: speeds include
●
Var Speed—variable speed
●
Basic Fan—fixed speed
●
Auto. Speed—automatic speed fan
●
Pwr Supply—power supply
●
Unknown
Temperature: Basic Sensor—generic; ADM1022; Internal PS; Unknown
Type
Location
The device location in the media server.
Status
For power supplies and fans:
●
Normal—operating normally
●
Alarm—having a problem
Redundant
For all types: Yes, No, or NA
Fan Speed
Fans: percentage of full speed.
Current
●
Unknown
●
Automatic—For Auto. Speed Fans, no speed state
●
Low—< 30%
●
Medium—30%–70%
●
High—> 70%, reporting state: High state
●
Normal—reporting state: Normal state
●
Off
Temperature: current temperature of the device, in degrees Fahrenheit and
Celsius.
1 of 2
122 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
S8710 Alarms
Table 36: S8710 Temperature and voltage report (continued)
Field
Description
Threshold
Temperature: above for which an alarm is generated, in degrees Fahrenheit
and Celsius.
2 of 2
S8710 server BIOS error messages
The S8710 server BIOS error messages are listed and interpreted in Table 37.
Table 37: S8710 BIOS error messages
Error
Code
Description
Audible
Beeps
Possible Problem
Possible Action
207
Memory configuration
warning; DIMM in DIMM
Socket X is not 4 bytes
wide (32 bits) and only
supports standard ECC.
None
Installed DIMMs are
8 bytes wide (64
bits).
Escalate; replace
the media server
209
Online spare memory
configuration; spare bank
is invalid. Mixing of DIMMs
with 4 and 8 byte widths is
not allowed in this mode.
One
long and
one
short
Installed DIMMs for
online spare bank
are of a different
primary width than
the DIMMs in other
banks.
Escalate; replace
the media server
NA
A mixture of 533-MHz and
400-MHz front side bus
speed processors
detected. All processors
must have the same front
side bus speed. System
halted.
One
long and
one
short
Wrong processors;
Processors have
different front side
bus speeds.
Escalate; replace
the media server
NA
Media server only supports
400-MHz front side bus
speed processors. One or
more 533-MHz front side
bus speed processors
have been initialized at 400
MHz.
One
long and
one
short
Wrong processors;
Media server does
not support a front
side bus speed of
533 MHz.
Escalate; replace
the media server
Issue 1 June 2005
123
Server Alarms
124 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Chapter 2: Denial Events
The tables in this chapter define and explain the information listed on the Events Report
(display events screen). The Event Type tables are grouped by denial event category,
denial event number, and Communication Manager release number. The Event Tables list:
●
The number that identifies the Event Type. See Table 38: Denial Event types and
ranges on page 126. If the Event Type number defines different denial events in different
Communication Manager releases, that information is also listed.
●
Event Description text, as it appears on the Events Report (display events type
denial).
●
An explanation of why the event was generated.
●
Type of data in Event Data 1 and Event Data 2 fields, for each applicable Event Type,
where this information is available. See Event Data on page 127.
To view denial events, use:
●
display events type denial (to see historical denial event logs)
●
list trace station
●
list trace TAC
Use list trace to see any available Calling Party Number and Calling Party Name
associated with call setup.
Issue 1 June 2005
125
Denial Events
Event Type number ranges
Event Type number ranges help define the type and source of the denial event, as listed in
Table 38: Denial Event types and ranges. Some numbers are placeholders and have no
assigned denial event.
Table 38: Denial Event types and ranges
Number range
Type/source of denial event
Reference
0 - 999
Vector process
Avaya Communication Manager Call Center Software Call
Vectoring and Expert Agent Selection (EAS) Guide,
07-300186.
Hunt/Trunk Group Vector
process
Avaya Communication Manager Call Center Software Call
Vectoring and Expert Agent Selection (EAS) Guide,
07-300186.
Call Process
Table 48, Call Process denial events (1001 - 1172), on
page 177.
● 1000 - 1299
Call Process, reorder
Table 48, Call Process denial events (1001 - 1172), on
page 177 and Table 50, Call Process denial events (1225 1899), on page 193.
● 1164, 1167,
Call Process, ISDN, IP, SIP
Table 49, ISDN, IP, and SIP-generated denial events (1173
- 1224), on page 189.
● 1300 - 1899
Call Process, intercept
Table 50, Call Process denial events (1225 - 1899), on
page 193.
● 1900 - 1906
User Manager process
Table 51: User Manager denial events (1900 - 1906) on
page 226.
● 1907 - 2079
IP
Table 52: IP Denial Events (1907 - 2020) on page 226.
● 2021-2299
Call Process
Table 53, Call Process denial events (2021 - 2299), on page
238.
2300 - 2399
Connection Manager process
Table 54: Connection Manager denial events (2300 2399) on page 247.
2400 - 2499
Dial Plan Manager process
Table 55: Dial Plan Manager denial events (2400 - 2406) on
page 249.
3000 - 3100
Data Manager process
Table 56: Data Manager generated Denial Events (3001 3003) on page 249.
3101 - 3200
Dial Access Plan process
Table 57: Dial Access Plan denial events (3101 - 3200) on
page 250.
● 500 - 999
1000 - 2299
1173 - 1224
3201 - 3299
3300 - 3399
Meetme Conference
process
LSP process
Table 58: Meet Me Conference denial events (3201 3299) on page 250.
Table 59: LSP denial events (3300 - 3399).
1 of 2
126 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
Table 38: Denial Event types and ranges (continued)
Number range
Type/source of denial event
Reference
3400 - 3499
Data Error (corruption) process
Table 60: Data Error denial events (3400 - 3499) on
page 252.
3500 - 3599
Contact Closure process
Table 61: Contact Closure denial events (3500 - 3503) on
page 253.
3600 - 3604
ESS process
Table 62: ESS denial events (3600 - 3604) on page 254.
2 of 2
Event Data
Use Event Data information to isolate mis-translation and/or mis-matched provisioning.
Event Data might contain the information for:
●
Internal User ID (UID) of a component involved in the call (station, IP User, gatekeeper)
●
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. See Cause Values and their meanings/interpretations on page 128.
Issue 1 June 2005
127
Denial Events
Cause Values and their meanings/interpretations
See Table 49: ISDN, IP, and SIP-generated denial events (1173 - 1224) on page 189 for the
Denial Events that show Cause Value information (Cause Value, Location Code, and Diagnostic
Code) in Event Data 2 fields.
Event Data 2 sometimes contains data that represents the Cause Value (CV) (required), Cause
Value Diagnostic (DIAG) (optional), Location Code (LC) (optional) from the denial event. This
information (DIAG/LOC/CV) is coded as a 32 bit hexadecimal number, divided into 8-bit fields.
●
The least significant (right most) two digits are the Cause Value in hexadecimal.
●
The next two digits to the left are the Location Code (optional) in hexadecimal. See
Table 42: Location Code definitions on page 130.
●
The next two digits to the left are the Diagnostic Code (optional) in hexadecimal.
●
The most significant (left most) two digits are not used.
See Table 39: Event Data 2 layout on page 128.
Table 39: Event Data 2 layout
8 bits
8 bits
8 bits
8 bits
NOT USED
Diagnostic Code
(DIAG) (optional)
Zero + Location Code in lower 4 bits
(LOC) (optional)
Cause Value
(CV) (required)
Interpreting Event Data 2 Cause Value information
In our example, we will use Denial Event 1178 with Event Data 1 and Event Data 2.
display events denial
Page
1
of
EVENTS REPORT
Event Event
Type Description
Event
Data 1
Event
Data 2
1178
0x64
0x429
Normal Call Clearing
First
Occur
Last
Occur
Evnt
Cnt
01/09/09:53 01/09/09:53
1. Note the information under the Event Data 2 column: 0x429.
●
0x29 is the Cause Value.
●
0x4 is the Location Code.
●
0x00 is the Diagnostic Code (not provided for this denial event).
128 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
1
1
Event Data
2. Convert the hexadecimal number provided in Event Data 2 to three binary numbers: put a
one in the appropriate binary number positions that add up to the value of the number.
Each binary number consists of eight bits. See Table 40: Event Data 2 conversion
example on page 129 for an example of the hexadecimal number 0x429, and
Table 41: Hexadecimal, decimal, and binary equivalents on page 130 for the binary
equivalents for individual digits.
3. Add up the decimal weights that have a one for each of the eight bit segments.
●
Convert Cause Value 0x29 to decimal and find the sum.
Cause Value (Bits 1 - 8): 1 +8 + 32 = 41. This is Cause Value 41.
●
Convert Location Code 0x4 to decimal and find the sum.
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.
4. Use the information in this chapter to find an explanation of the Data Event 2 information.
●
Cause Value 41 = Temporary Failure. See Cause Values on page 134.
●
Location Code 4 = Remote Network/Public Network Serving Remote User (the Local
Exchange Carrier at the far end of the call). See Table 42: Location Code definitions on
page 130.
Table 40: 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
8
4
2
1
8
4
2
1
8
4
2
1
8
4
2
1
Decimal weight of each digit position
8
4
2
1
8
4
2
1
Decimal weight of the binary positions for each eight-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
21
20
19
18
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
Bit position
24
23
22
Issue 1 June 2005
129
Denial Events
.
Table 41: 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
Location Codes
See Table 49: ISDN, IP, and SIP-generated denial events (1173 - 1224) on page 189 for the
Denial Events that show Cause Value information (Cause Value, Location Code, and Diagnostic
Code) in Event Data 2 fields.
Use the location information of Event Data 2 to identify where in the network the called number
failed to be recognized, and from where the Cause Value originated. See Table 42: Location
Code definitions on page 130.
Table 42: Location Code definitions
Location
Code
Definition
0
User
1
Private Network Serving Local User.
The Local PBX or phone system on the Called Party premise
2
Public Network serving the Local User (the CO to which the PBX is directly
connected).
3
Transit network. For example, the long distance network to which the call was
passed by the LEC.
4
Public Network Serving Remote User [the Local Exchange Carrier (LEC) at the far
end of the call].
1 of 2
130 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
Table 42: Location Code definitions (continued)
Location
Code
Definition
5
Private Network Serving Remote User (the remote PBX or phone system on the
Called Party premises).
7
International.
A
Network beyond inter-networking point.
2 of 2
Transmission Protocols
See Table 49: ISDN, IP, and SIP-generated denial events (1173 - 1224) on page 189 for the
Denial Events that show Cause Value information (Cause Value, Location Code, and Diagnostic
Code) in Event Data 2 fields.
The meaning of the Denial Event Data information differs depending on the type of protocol
used for the call. The transmission protocol for your system is defined on the DS1 screen (add/
change/display ds1 location command) by:
●
The numeric country code value in the Protocol field - sets the country protocol.
●
The letter value for the protocol version in the Protocol Version field.
See Table 43, Country Codes and Transmission Protocols, on page 131.
Table 43: Country Codes and Transmission Protocols
Country
Protocol Supported
B-channel
Maint.
Message
Inter-working
Message
1-a
US-Canada
AT&T TR 41449 / 41459
SERVICE
PROGRESS
1-b
US
Bellcore TR1268;
NIUF.302;
ANSI T1.607
RESTART
PROGRESS
1-c
US-Canada
Nortel A211
AT&T TR 4449/41459
(with Layer 3 timers
adjusted)
SERVICE
PROGRESS
1-d
US
Bellcore TR3268
SERVICE
PROGRESS
2
Australia
AUSTEL TS014.1;
Telcom Australia TPH 1856
RESTART
PROGRESS
Country Code –
Protocol Version
1 of 3
Issue 1 June 2005
131
Denial Events
Table 43: Country Codes and Transmission Protocols (continued)
Country
Protocol Supported
B-channel
Maint.
Message
Inter-working
Message
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
DASS II/DPNSS through
external converter)
RESTART
PROGRESS
10-b
UK
ETS 300 102 (Mercury)
British Telcom ISDN 30
NONE
ALERTING
11
Spain
Telefonica ISDN Spec
RESTART
PROGRESS
12-a
France
VN4 (French National PRI)
NONE
ALERTING
12-b
France
Modified ETS 300 102
according to P10-20
(Euronumeris)
NONE
ALERTING
13-a
Germany
FTZ 1 TR 6
(German National PRI)
NONE
ALERTING
13-b
Germany
ETS 300 102
RESTART
ALERTING
14
Czech Republic
/ Slovakia
ETS 300 102
RESTART
PROGRESS
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
Country Code –
Protocol Version
2 of 3
132 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
Table 43: Country Codes and Transmission Protocols (continued)
Country
Protocol Supported
B-channel
Maint.
Message
Inter-working
Message
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
ETS 300 102
NONE
PROGRESS
ETS 300 102
RESTART
PROGRESS
Country Code –
Protocol Version
ETSI-b
QSIG
Private network
3 of 3
Cause Values
The Data Event 2 field on the display events screen sometimes contains Cause Value
information (DIAG/LOC/CV). Use this information to identify the Cause Value for each denial
event. The following information lists classes of Cause Values, their meaning and
interpretations, and associated translations.
See Table 49: ISDN, IP, and SIP-generated denial events (1173 - 1224) on page 189 for the
Denial Events that show Cause Value information (Cause Value, Location Code, and Diagnostic
Code) in Event Data 2 fields.
Cause Value Classes
Table 44: Cause Value Classes and Ranges
Number range
Cause Value Class
empty to 33
Normal Class Cause Values on page 134
●
12, 14, 15, 24
34 to 47
●
36, 48
49 to 63
●
55, 60, 64
unassigned
Resource Unavailable Class Cause Values on page 147
unassigned
Service or Option not Available Class Cause Values on page 151
unassigned
1 of 2
Issue 1 June 2005
133
Denial Events
Table 44: Cause Value Classes and Ranges (continued)
Number range
Cause Value Class
65 to 79
Service or Option not Implemented Class Cause Values on page 158
●
67, 68, 71-78, 80
81 to 95
●
92-94
96 to127
●
104-109, 116-126
unassigned
Invalid Message Class Cause Values on page 161
unassigned
Protocol Error Class Cause Values on page 165
unassigned
2 of 2
Cause Values
Normal Class Cause Values
Cause Value (empty)
[]Normal call clearing (1TR6: AT&T ISDN Protocol)
The call was disconnected normally by either end hanging up.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Cause Value 00
[0x0/0x80] Normal disconnect
The call was disconnected normally by either end hanging up. Most equipment uses Cause
Value 16 to report normal disconnect.
Cause Value 01
[0x1/0x81] Unassigned (Unallocated number)/
Invalid Call Reference Value (CRV) (1TR6: AT&T ISDN Protocol)
The call could not be completed because the number requested in the SETUP message is not
assigned/allocated by the ISDN network.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
134 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
See also Cause Value 22 on page 143 and Cause Value 56 on page 154.
Troubleshooting
●
Check the numbers sent to see if any prefixes or service values that were needed to
access the network were not sent.
●
Check the Cause Value Information Element (LOC). See Location Codes on page 130.
●
Check Communication Manager administration.
- Dial-plan/Location: The home NPA is administered incorrectly, causing incorrect code
conversion.
- IXC: The IXC matching pattern is administered incorrectly or not at all on the dial-plan,
causing incorrect IXC manipulation.
- 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.
- 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.
- ARS toll analysis: Toll/no toll classification is incorrect, causing incorrect code conversion
at the route pattern.
- 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 interexchange carrier.
- Trunk Group: The incorrect service or feature is specified for the call being made on a
CBC trunk group preference. The number format is being changed to a format incorrect
for the call type.
Cause Value 02
[0x2/0x82] No route to specified transit network/
Calling party off hold (5ESS: 5 Electronic Switching System)
The ISDN service provider’s equipment cannot route the call through the specified network. The
network either does not exist or is not compatible with the ISDN service provider’s equipment.
This Cause Value has local significance only. 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.
Because this Cause Value has only local significance, on tandem calls Communication
Manager might map it to Cause Value 31 instead of passing it back through the network.
Issue 1 June 2005
135
Denial Events
Troubleshooting
●
Check the diagnostic information (DIAG) for the transit network identity of the unreachable
network. See Cause Values and their meanings/interpretations on page 128.
●
Check the numbers sent for any missing prefixes or service values that were needed to
access the network.
●
Check that the call type (data, voice, fax) can be routed between the ISDN networks
serving both ends of the call.
●
Check that the bearer capabilities of the call are acceptable to the ISDN network serving
both ends of the call.
●
Check the Cause Value Information Element (LOC). See Location Codes on page 130.
●
Check Communication Manager administration.
- 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.
- Route pattern: Incorrect digits or IXC were inserted. Incorrect number of digits were
deleted. An incorrect ITC and/or BCIE were specified, affecting the SETUP message
bearer capability encoding. An incorrect service or feature was specified for the
preference. The number format specified is wrong for the call type.
- The ITC administered on the originating endpoint might be incorrect for this call.
- 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.
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)
The ISDN service provider cannot route the call to the indicated destination. Communication
Manager does not originate Cause Value 03.
Troubleshooting
●
Check the numbers sent for any missing prefixes or service values that were needed to
access the network.
●
Check the Cause Value Information Element (LOC). See Location Codes on page 130.
●
Check Communication Manager administration.
- Dial-plan/Location: The home NPA is administered incorrectly, causing incorrect code
conversion.
136 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
- IXC: The IXC matching pattern is administered incorrectly or not at all on the dial-plan,
causing incorrect IXC manipulation.
- 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.
- 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.
- ARS toll analysis: Toll/no toll classification is incorrect, causing incorrect code conversion
at the route pattern.
- 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 interexchange 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.
Cause Value 04
[0x4/0x84] Send special information tone/
Vacant Code (NI-2: National ISDN 2)
Cause Value 04 indicates the remote number that was dialed could not be reached.
Cause Value 04 (NI-2) indicates that the destination requested by the calling party cannot be
reached because the Numbering Plan Area (NPA) or Central Office (CO) code is vacant
(unassigned).
Troubleshooting
●
Check the numbers sent for any missing prefixes or service values that were needed to
access the network.
●
Check the Cause Value Information Element (LOC). See Location Codes on page 130.
●
Check Communication Manager administration.
- Dial-plan/Location: The home NPA is administered incorrectly, causing incorrect code
conversion.
- IXC: The IXC matching pattern is administered incorrectly or not at all on the dial-plan,
causing incorrect IXC manipulation.
- 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.
Issue 1 June 2005
137
Denial Events
- 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. An incorrect service
or feature is specified for the call being made on a CBC trunk group preference.
Changing the Number format to a format incorrect for the call type.
- ARS toll analysis: Toll/no toll classification is incorrect, causing incorrect code conversion
at the route pattern.
- 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 interexchange carrier.
Cause Value 05
[0x5/0x85] Misdialed trunk prefix
The remote number that was dialed could not be reached.
Troubleshooting
●
Check the numbers sent for any missing prefixes or service values that were needed to
access the network.
●
Check the Cause Value Information Element (LOC). See Location Codes on page 130.
●
Check Communication Manager administration.
- Dial-plan/Location: The home NPA is administered incorrectly, causing incorrect code
conversion.
- IXC: The IXC matching pattern is administered incorrectly or not at all on the dial-plan,
causing incorrect IXC manipulation.
- 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.
- 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.
- ARS toll analysis: Toll/no toll classification is incorrect, causing incorrect code conversion
at the route pattern.
- 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 interexchange carrier.
138 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
- 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. An incorrect service or feature is specified for the call being
made on a CBC trunk group preference. Changing the Number format to a format
incorrect for the call type.
Cause Value 06
[0x6/0x86] Channel Unacceptable
The call attempt failed because the requested channel is not acceptable to the ISDN service
provider.
Troubleshooting
●
Check Communication Manager administration.
- B-channels might be assigned off a T1/E1 into 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.
Cause Value 07
[0x7/0x87] Call awarded and being delivered in an established channel/
Call identity does not exist (1TR6: AT&T ISDN Protocol)
Cause Value 07 indicates that a new incoming call is being established and is being connected
on a channel that has previously been connected to the same user for similar type calls (for
example, packet mode X.25 virtual channels being established on the d-channel).
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 Value 08 For Autovon switching networks, the call attempt was blocked by a call with a
higher priority.
Cause Value 08 (NI-2) indicates that the network does not want to receive the prefix digit 0 as
part of the digit string in the CALLED PARTY NUMBER.
Cause Value 08 (1TR6) indicates that the call identity that sent in the call resume request is
already in use by the network.
Issue 1 June 2005
139
Denial Events
Troubleshooting
Wait and try the call again later.
Cause Value 09
[0x9/0x89] Preemption, circuit reserved for reuse/
Prefix 1 dialed in error (NI-2: National ISDN 2)
Cause Value 09 For Autovon switching networks, the call attempt was blocked by a call with a
higher priority reserving the requested channel for reuse.
Cause Value 09 (NI-2) indicates that the network does not want to receive the prefix digit 1 as
part of the digit string in the CALLED PARTY NUMBER.
Troubleshooting
Wait and try the call again later.
Cause Value 10
[0xA/0x8A] Prefix 1 not dialed (NI-2: National ISDN 2)/
No channel available (1TR6: AT&T ISDN Protocol)
Cause Value 10 (N1-2) indicates that he user must send the prefix digit 1 as part of the
CALLED PARTY NUMBER.
Cause Value 10 (1TR6) indicates that the call cannot be completed because there is no
appropriate circuit/channel presently available to handle the call request, or that congestion
exists within the ISDN network.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Cause Value 11
[0xB/0x8B] Excessive digits received call proceeding (NI-2: National ISDN 2)
The equipment received more address digits in the CALLED PARTY NUMBER IE than
expected during call origination procedures, and the received address information has been
truncated.
Cause Value 13
[0xD/0x8D] Service Denied (NI-1: National ISDN 1)
140 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
Cause Value 16
[0x10/0x90] Normal call clearing/
Requested facility not implemented (1TR6: AT&T ISDN Protocol)
Cause Value 16 indicates that the call was disconnected normally by either end hanging up.
Cause Value 16 (1TR6) indicates that the call could not be completed because the equipment
sending this Cause Value does not support the requested service, feature, or supplementary
service in the SETUP message.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Troubleshooting
●
Check the diagnostic information (DIAG) for the facility identifier of the not implemented
service. See Cause Values and their meanings/interpretations on page 128.
●
If the remote device terminated the connection unexpectedly, contact the person
responsible for the remote end to determine if there is a problem with the remote endpoint.
●
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 might have failed due to:
- Option settings with the endpoint devices
- Bandwidth constriction issues on the b-channel used by the two devices to make the call
Cause Value 17
[0x11/0x91] User busy/
Requested facility not subscribed (1TR6: AT&T ISDN Protocol)
Cause Value 17 indicates that the endpoint called is unable to accept another call.
Cause Value 17 (1TR6) 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.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
See also Cause Value 16 on page 141 and Cause Value 31 on page 146.
Troubleshooting
●
Wait and try the call again later.
●
If the user is supposed to have access to the service, feature, or supplementary service,
complete the ordering process with the ISDN service provider.
Issue 1 June 2005
141
Denial Events
●
Check the Cause Value Information Element (LOC).
- If the location information of the Cause Value is 4, “public network serving the remote
user”, the trunk group to the remote endpoint location might be experiencing an “all
trunks busy” condition or not enough channels allocated into a virtual group for the
particular NSF of the call.
- If the location information of the Cause Value is 0, “user”, the endpoint might be busy.
●
If Communication Manager is generating this Cause Value, and the endpoint is not busy,
check the following Communication Manager administration.
- 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.
- VDNs and Call vectoring: Analyze the vector processing and the call flow to determine
where the failure is occurring. VDN vector administration might incorrectly send the call
to a “busy” vector step. The call might go 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) might receive an inappropriate ISDN response while
checking other sites for available agents and return busy feedback to the caller. The LAI/
BSR attempt might interact with the public network features Egress on busy – overflow to
POTS, Alternate Destination Routing (ADR), or Alternate Destination Call Redirection
(ADCR).
- Trunk and/or station Class of Restriction (COR) might prevent the call from terminating at
the endpoint.
- The endpoint might be call forwarded, and this is the second call within the 30-second
time limit on a station call-forwarding a call.
Cause Value 18
[0x12/0x92] No user responding/
No response from the remote device
The remote device/endpoint/PBX 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 ISDN network or noisy conditions
on the T1/E1 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 request.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
142 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
Cause Value 19
[0x13/0x93] User alerting no answer
The remote device returned an alerting [ringing] indication but did not provide a connect
indication within the period of time prescribed by timer T301.
Communication Manager never originates this Cause Value.
Troubleshooting
Wait and retry the call later.
Cause Value 20
[0x14/0x94] Subscriber absent [wireless networks]
The mobile remote device/endpoint is not available.
Troubleshooting
Wait and try the call again later.
Cause Value 21
[0x15/0x95] Call rejected
The remote endpoint did not accept this call, even though the equipment is neither busy nor
incompatible and it could have accepted the call.
Check the diagnostic information (DIAG) for the user-supplied condition for why the call was
rejected. See Cause Values and their meanings/interpretations on page 128.
Cause Value 22
[0x16/0x96] Number changed
The called party number was changed to a new number.
Cause Value 01 appears if the ISDN network does not support Cause Value 22.
A BRI or Adjunct Switch Application Interface (ASAI) application might generate Cause Value
22. Communication Manager does not originate Cause Value 22 for PRI.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Check the diagnostic information (DIAG) for the new number. See Cause Values and their
meanings/interpretations on page 128.
Issue 1 June 2005
143
Denial Events
Cause Value 23
[0x17/0x97] Redirection to new destination
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
The call cannot be routed to the remote party.
Cause Value 26
[0x1A/0x9A] Non-selected user clearing
The call was cleared before the called endpoint was awarded the incoming call.
Cause Value 27
[0x1B/0x9B] Destination out of order
The call cannot be delivered to the remote endpoint because the interface to the endpoint is not
functioning correctly. A signaling message could not 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 turned off).
Communication Manager does not originate Cause Value 27.
Cause Value 28
[0x1C/0x9C] Invalid number format (address incomplete)
Special intercept announcement (NI-1: National ISDN 1)
The called endpoint could not be reached because the CALLED PARTY NUMBER information
is not in a valid format or is not complete.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
144 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
Troubleshooting
●
Check the Cause Value Information Element (LOC). See Location Codes on page 130.
●
Check Communication Manager administration (network generated the Cause Value).
- Dial-plan/Location: The home NPA is administered incorrectly, causing incorrect code
conversion.
- IXC: The IXC matching pattern is administered incorrectly or not at all on the dial-plan,
causing incorrect IXC manipulation.
- 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.
- 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.
- ARS toll analysis: Toll/no toll classification is incorrect, causing incorrect code conversion
at the route pattern.
- Route pattern: Incorrect NPA is causing incorrect code conversion. If the Prefix mark
field has the wrong value, incorrect code conversion takes place. Toll list in combination
with prefix mark is causing incorrect code conversion to take place. The wrong number of
digits are deleted, or failed to strip IXC digits or international code digits. Inserted the
wrong digits IXC forcing the call to the wrong inter-exchange carrier, or stripped out a
user dialed IXC code. The incorrect service or feature is specified for the call being made
on a CBC trunk group preference. The Number format was changed to a format incorrect
for the call type.
●
Check administration (Communication Manager generated the Cause Value).
- Trunk group: Incoming call handling table might cause 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)
The call could not be completed because the ISDN network does not support or is not
subscribed to the network service or feature requested for use by this call.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Issue 1 June 2005
145
Denial Events
Troubleshooting
●
Check the diagnostic information (DIAG) for the facility identifier of the service that was
rejected. See Cause Values and their meanings/interpretations on page 128.
●
Check Communication Manager administration (network generated the Cause Value).
- Route pattern: The service or feature field contains an incorrect value for this route
preference. The ITC/BCIE fields might not indicate the correct information for a data call.
●
Check administration (Communication Manager generated the Cause Value).
- Trunk group form: the Service type field might indicate a static service type when the
network is sending 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 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 every
maintenance cycle that elicits this response from the remote end.
This Cause Value has local significance only. 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
Cause Value 31
[0x1F/0x9F] Normal unspecified/
Special intercept announcement call blocked due to group restriction (NI-1: National
ISDN 1)
Cause Value 31 reports a normal event when no other cause in the normal class applies.
The ISDN network might substitute 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 135.
Cause Value 31 can also be used as a return code on BSR polling attempts instead of Cause
Value 16 or Cause Value 17 depending on which Cause Value has less impact/interaction on
the intervening ISDN network.
146 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
Cause Value 32
[0x20/0xA0] Outgoing calls barred (1TR6: AT&T ISDN Protocol)
The call could not be completed because the calling user does not have permission to make an
outgoing call.
This Cause Value has local significance only. 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
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 Value 34 indicates that he call cannot be completed because there is no appropriate
circuit/channel available to handle the call request, or congestion exists within the ISDN
network.
Communication Manager generates this Cause Value when a call is tandeming through
Communication Manager and the trunk group to be used for the outgoing leg is:
●
In “all trunks busy” condition
●
Otherwise 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 was rejected because the user is
not a member of the remote end’s Closed User Group (CUG), 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.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Issue 1 June 2005
147
Denial Events
Troubleshooting
●
Check Communication Manager administration (network generated the Cause Value).
- B-channels might be assigned off a T1/E1 into 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.
●
Check administration that might cause Communication Manager to generate this Cause
Value.
- 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 up, 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)
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.
Communication Manager does not support packet mode sessions on D-channels, therefore this
is not applicable to Communication Manager.
Cause Value 37
[0x25/0xA5] Semi-permanent connection not permitted (1TR6: AT&T ISDN Protocol)
Cause Value 38
[0x26/0xA6] Network out of order
The call was not completed because the ISDN network is not functioning correctly, and the
condition is likely to last a relatively long period of time. Immediately reattempting the call will
probably be unsuccessful.
Cause Value 39
[0x27/0xA7] Permanent frame mode connection out of service
This appears to be a Q.933 frame relay Cause Value. Equipment failure might have caused
termination of a frame relay PVC.
Not applicable to a Communication Manager system.
148 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
Cause Value 40
[0x28/0xA8] Permanent frame mode connection is operational
This appears to be 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
The call was not completed because the ISDN network is not functioning correctly. The
condition is not likely to last a long period of time. If the user attempts the call again it will
probably complete.
Cause Value 41 might also indicate:
●
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 being cleared as a result of one or more protocol errors at the remote network
interface.
See also Cause Value 63 on page 157 and Cause Value 79 on page 160.
Cause Value 42
[0x2A/0xAA] Switching equipment congestion
The call could not be completed because the switching equipment generating this Cause Value
is experiencing a period of high traffic.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Troubleshooting
Wait and try the call again later.
Cause Value 43
[0x2B/0xAB] Access information discarded
The network could not 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 interworked from ISDN to non-ISDN facilities, or the remote end does not support
delivery of such information.
Issue 1 June 2005
149
Denial Events
This Cause Value is usually delivered in a STATUS message. Communication Manager
generates this Cause Value when:
●
A tandem call inter-works from ISDN to non-ISDN trunking.
●
Calling number and/or calling name information is sent in the SETUP message when it is
not needed.
●
Connected number information is sent when the network does not support it.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Check the diagnostic information (DIAG) for the Information Element identifier of the discarded
information. See Cause Values and their meanings/interpretations on page 128.
Cause Value 44
[0x2C/0xAC] Requested circuit/channel not available
The call was not completed because the circuit/channel requested for use in the SETUP
message was not available, and the call could not be negotiated to another channel either
because no other channel was available, or negotiation is not supported or was not wanted for
this call.
This Cause Value is generated when a glare condition is occurring and B-channel negotiation is
not supported.
Communication Manager generates this Cause Value when:
●
It is the NETWORK side of the interface and a glare condition is occurring on the
requested B-channel.
●
The B-channel requested in the incoming SETUP message is not in the correct
maintenance state to handle a call (for example, it is busied out or undergoing testing).
Troubleshooting
●
CO switch default settings turn off channel negotiation support. Make a specific request to
turn on channel negotiation support when ordering CO service.
●
Check Communication Manager administration (network generated the Cause Value).
- Trunk group form: When the Channel Negotiation field is set to exclusive,
Communication Manager requests B-channels for calls without support for negotiation so
if at the remote end the requested B-channel is unavailable for whatever reason 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.
150 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
Cause Value 45
[0x2D/0xAD] Pre-empted
The call could not be completed because the equipment sending this Cause Value does not
have the requested B-channel in a maintenance state that allows for call requests to be
processed.
Communication Manager does not support this Cause Value.
Cause Value 46
[0x2E/0xAE] Precedence call Blocked
For Autovon switching networks, the call could not complete because the remote endpoint is
busy with a call that has a higher priority.
Cause Value 47
[0x2F/0xAF] Resource unavailable, unspecified/
New destination (4ESS/5ESS: 4/5 Electronic Switching System)
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, it invokes call redirection.
Communication Manager does not originate Cause Value 47.
Service or Option not Available Class Cause Values
Cause Value 49
[0x31/0xB1] Quality of service unavailable
The call could not 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).
Issue 1 June 2005
151
Denial Events
Cause Value 50
[0x32/0xB2] Requested facility not subscribed
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, then complete the required ordering
process with the ISDN service provider.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Communication Manager does not originate this Cause Value for PRI. A BRI or Adjunct Switch
Application Interface (ASAI) application might generate 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
being 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 might be incorrect for this call.
- 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.
●
On tandem calls through Communication Manager from ISDN trunks to ISDN trunks, an
inappropriate NSF can be tandemed from one D-channel to the other D-channel.
●
The problem is that 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) as appropriate.
●
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)
The requested action could not be completed. The requested action is incompatible with the
bearer capability of the call (for example, trying to place a data call on hold).
152 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
Cause Value 52
[0x34/0xB4] Outgoing calls barred
The call could not be completed because the network screened the call, and the calling user is
not permitted to make an outgoing call.
This Cause Value has local significance only. 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
Cause Value 53
[0x35/0xB5] Service operation violated (NI-1: National ISDN 1)/
Destination not obtainable (1TR6: AT&T ISDN Protocol)
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 not functioning correctly. A signaling message could not
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 turned off).
Cause Value 54
[0x36/0xB6] Incoming calls barred
The call could not complete because the called user is not allowed to accept the call delivered in
the SETUP message.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Troubleshooting
●
Check Communication Manager administration (network generated the Cause Value).
- Trunk group: Direction: The Communication Manager field might be 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.
- On tandem calls through Communication Manager from ISDN trunks to ISDN trunks, an
NSF for a one-way service (for example, Megacom 800) is being tandemed from one
D-channel to the other D-channel. The problem is that 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) as
appropriate.
Issue 1 June 2005
153
Denial Events
Cause Value 56
[0x38/0xB8] Number changed (1TR6: AT&T ISDN Protocol)
The called party number indicated has been changed to a new number that might be sent in the
diagnostic information (DIAG) for this Cause Value. See Cause Values and their meanings/
interpretations on page 128. If this Cause Value is not supported by the ISDN network, Cause
Value 01 is used instead.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Communication Manager does not originate this Cause Value for PRI. A BRI or Adjunct Switch
Application Interface (ASAI) application might generate this Cause Value.
Cause Value 57
[0x39/0xB9] Bearer capability not authorized/
Out of order (1TR6: AT&T ISDN Protocol)
Cause Value 57 indicates that the call could not 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 user has not subscribed to it or in other ways is not authorized to use.
Cause Value 57 (1TR6) indicates that the call cannot be delivered to the remote endpoint
because the interface to the endpoint is not functioning correctly. A signaling message could not
be delivered to the remote device (for example, due to a physical or data link layer failure at the
remote device, or the remote device is turned off).
Troubleshooting
●
Check the diagnostic information (DIAG) for the unauthorized bearer capability attributes.
See Cause Values and their meanings/interpretations on page 128.
●
Check Communication Manager administration (network generated the Cause Value).
- Route pattern: An incorrect ITC and/or BCIE specified, these fields affect how the bearer
capability is encoded in the SETUP message.
- 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.
- 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.
- 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.
154 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
- 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 might
be set wrong.
Cause Value 58
[0x3A/0xBA] Bearer capability not presently available/
No user responding (1TR6: AT&T ISDN Protocol)
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Cause Value 58 indicates that the call could not 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 for which there are presently no resources available to be used to
complete the call.
Troubleshooting
Wait and try the call again later.
Cause Value 58 (1TR6) indicates that the remote device/endpoint/PBX did not respond with an
ALERTING/PROGRESS/CONNECT indication within the prescribed period of time allocated by
the expiry of the T303 or T310 timers in the Q.931 specification.
Troubleshooting
●
Check the diagnostic information (DIAG) for the bearer capability attributes that are not
available. See Cause Values and their meanings/interpretations on page 128.
●
Check Communication Manager administration (network generated the Cause Value).
- Route pattern: An incorrect ITC and/or BCIE specified, these fields affect how the bearer
capability is encoded in the SETUP message.
- 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.
- 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.
- 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.
- 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 might
be set wrong.
Issue 1 June 2005
155
Denial Events
Cause Value 59
[0x3B/0xBB] User busy (1TR6: AT&T ISDN Protocol)
The endpoint called has indicated an inability to accept another call.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Troubleshooting
●
Wait and try the call again later.
●
Check the Cause Value Information Element (LOC)
- If the Location Information of the Cause Value is 0 (User), the endpoint is probably busy.
- If the Location information of the Cause Value is 4 (Public Network Serving Remote
User), it is most likely that the trunk group to the remote endpoint location is experiencing
an “all trunks busy” condition or not enough channels allocated into a virtual group for the
particular NSF of the call.
●
If Communication Manager is generating this Cause Value and the endpoint is not busy,
the following translations and features could be affecting the call:
- Trunk and/or station Class of Restriction (COR) might be preventing the call from
terminating at the called endpoint.
- The endpoint might be call-forwarded and this is the second call within the 30-second
time limit on a station call forwarding a call.
- Trunk group form: CBC service type: Usage Allocation is y. The usage allocation plan
might not have allocated enough incoming channels for the NSF associated with this call.
- VDNs and Call Vectoring: The vector associated with the VDN might be incorrectly
programmed and the call is inappropriately sent to a busy vector step. The skill/
Automatic Call Distribution (ACD) group that the call is trying to queue to might have a
full queue and cannot accept any more calls. Look Ahead Interflow/Best Service Routing
(LAI/BSR) might have 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 might be 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 where the failure is occurring.
Cause Value 61
[0x3D/0xBD] Incoming calls barred (1TR6: AT&T ISDN Protocol)
The call could not complete because the called user is not allowed to accept the call delivered in
the SETUP message.
156 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Troubleshooting
●
Check Communication Manager administration (network generated the Cause Value).
- Trunk group: Direction: Communication Manager might be set to “two-way” on a trunk
group 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.
- On tandem calls through Communication Manager from ISDN trunks to ISDN trunks, an
NSF for a one-way service (for example, Megacom 800) is being tandemed from one
D-channel to the other D-channel. The problem is that 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) as
appropriate.
Cause Value 62
[0x3E/0xBE] Service not authorized (VN4: French National PRI)/
Call rejected (1TR6: AT&T ISDN Protocol)
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, then
complete the required ordering process with the ISDN service provider.
Cause Value 62 (1TR6) indicates that the remote endpoint does not wish to accept this call,
although it could have accepted the call because the equipment is neither busy nor
incompatible.
The diagnostic information (DIAG) might be populated with the user-supplied condition for why
the call was rejected. See Cause Values and their meanings/interpretations on page 128.
Cause Value 63
[0x3F/0xBF] Service or option not available, unspecified
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 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.
Issue 1 June 2005
157
Denial Events
Service or Option not Implemented Class Cause Values
Cause Value 65
[0x41/0xC1] Bearer capability not implemented
The call could not be completed because the equipment sending this Cause Value does not
support the bearer capability requested in the SETUP message.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Troubleshooting
The diagnostic information (DIAG) of the Cause Value should contain if implemented the bearer
capability attributes that are not implemented. See Cause Values and their meanings/
interpretations on page 128.
Cause Value 66
[0x42/0xC2] Channel type not implemented
The call could not be completed because the equipment sending this Cause Value does not
support the channel type requested in the SETUP message.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Troubleshooting
●
Check the diagnostic information (DIAG) for the unsupported channel type. See Cause
Values and their meanings/interpretations on page 128.
●
Check Communication Manager administration (network generated Cause Value):
- 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 be sure the attempted call has not inadvertently been routed to this
interface or was mis-classified as a wideband call.
●
Communication Manager administration that can affect sending of this Cause Value:
- 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
- Communication Manager does not have wideband support enabled on the Wideband
Support field on the appropriate trunk group
- The trunk group does not have the correct type(s) of wideband channels enabled
- Communication Manager does not have the right size wideband endpoint programmed.
158 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
Cause Value 69
[0x45/0xC5] Requested facility not implemented
The call could not be completed because the equipment sending this Cause Value does not
support the requested service, feature, or supplementary service in the SETUP message.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Communication Manager does not originate this Cause Value for PRI. A BRI or Adjunct Switch
Application Interface (ASAI) application might generate this Cause Value.
Troubleshooting
●
Check the diagnostic information (DIAG) for the facility identifier of the not-implemented
service. See Cause Values and their meanings/interpretations on page 128.
●
Check Communication Manager administration (network generated the Cause Value).
- Route Pattern: service or feature: An incorrect service or feature is specified for the call
being made on this CBC trunk group preference. An incorrect ITC and/or BCIE specified,
these fields affect how the bearer capability is encoded in the SETUP message.
- The ITC administered on the originating endpoint might be incorrect for this call.
- 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.
- On tandem calls through Communication Manager from ISDN trunks to ISDN trunks, an
inappropriate NSF can be tandemed from one D-channel to the other D-channel. The
problem is that 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) as appropriate.
- 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.
●
Communication Manager is attempting to send User-to-User information in a message
through the public network when not subscribed to a UUS service, for example Look
Ahead Interflow/Best Service Routing (LAI/BSR) information, Adjunct Switch Application
Interface (ASAI) information, etc.
Issue 1 June 2005
159
Denial Events
Cause Value 70
[0x46/0xC6] Only restricted digital information bearer capability is 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.
Troubleshooting
●
Check Communication Manager administration (network generated the Cause Value).
- Route pattern: An incorrect ITC and/or BCIE specified, these fields affect how the bearer
capability is encoded in the SETUP message.
- 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.
- 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.
- 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.
- 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 might
be set wrong.
Cause Value 79
[0x4F/0xCF] Service or option not implemented, 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.
160 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
Invalid Message Class Cause Values
Cause Value 81
[0x51/0xD1] Invalid call reference value
The equipment sending this Cause Value received 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 side of
the interface thinks that the call has been torn down but the other side sends messages to
complete clearing the call. The response to this new call clearing sequence becomes a
RELEASE_COMPLETE message with Cause Value 81.
This Cause Value has local significance only. 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
Cause Value 82
[0x52/0xD2] Identified channel does not exist
The equipment sending this Cause Value received a SETUP request to use a channel that is
not activated on 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 number 13 to 23, this Cause Value is generated.
This Cause Value has local significance only. 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
Troubleshooting
●
Check the diagnostic information (DIAG) for the channel number of the non-existent
channel. See Cause Values and their meanings/interpretations on page 128.
●
Check Communication Manager administration (network generated the Cause Value).
- Communication Manager might have B-channels assigned off a T1/E1 into 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.
Issue 1 June 2005
161
Denial Events
●
Communication Manager administration that can affect sending this Cause Value:
- Communication Manager might have missed assigning some B-channels into a trunk
group that the remote believes can be used for service and is attempting to request a call
on one. Check which channel is being requested and if possible assign it into the
appropriate trunk group. If the channel being requested is the 24th (T1) or 16th (E1)
channel, it might be 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
This Cause Value indicates that a call resume has been attempted for a call with an identity that
differs from any that are presently in a suspended state.
Cause Value 84
[0x54/0xD4] Call identity in use
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
This Cause Value indicates that a call resume has been attempted for a call, but the network
does not presently 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
The equipment sending this cause received a resume request for a call identity indicating a
suspended call that had been cleared while still in the suspended state, either by a network
timeout or by the remote user.
162 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
Cause Value 87
[0x57/0xD7] User not a member of the Closed User Group [CUG]
The packet mode call was rejected because the user is not a member of the remote end’s
Closed User Group (CUG), 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.
Cause Value 88
[0x58/0xD8] Incompatible destination
The call could not 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 should always be passed back through the
network to the user.
Troubleshooting
●
Check Communication Manager administration (network generated the Cause Value).
- Route pattern: An incorrect ITC and/or BCIE specified, these fields affect how the bearer
capability is encoded in the SETUP message.
- 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.
- 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.
- 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.
- 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 might
be set wrong.
●
Communication Manager administration that can affect sending this Cause Value:
- The extension number assigned in Communication Manager that was received in the
incoming SETUP message for this data call is assigned to an analog extension.
- The extension number assigned in Communication Manager that was received in the
incoming SETUP message for this voice call is assigned to a data extension.
Issue 1 June 2005
163
Denial Events
- A data call attempt tandeming through Communication Manager ISDN trunk group to
ISDN trunk group the outgoing route pattern has the Bearer Capability Class (BCC)
required for making this call set to “NO” and/or the ITC and BCIE are not compatible with
the incoming bearer capability.
- A TSC setup attempt that is tandeming through Communication Manager, the outgoing
route pattern does not have the TSC bearer capability activated.
Cause Value 89
[0x59/0xD9] Network Congestion (1TR6: AT&T ISDN Protocol)
The call could not be completed because the switching equipment generating this Cause Value
is experiencing a period of high traffic.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
Troubleshooting
Wait and try the call again later.
Cause Value 90
[0x5A/0xDA] Non-existent closed user group (CUG)/
Remote user initiated clearing (1TR6: AT&T ISDN Protocol)
The packet mode call was rejected because the equipment that sent the Cause Value did 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.
Communication Manager does not support packet mode sessions on D-channels, therefore this
is not applicable to Communication Manager.
Cause Value 91
[0x5B/0xDB] Invalid transit network selection
The call could not be completed because the equipment that sent this Cause Value received a
request to route a call to a transit network that it does not have a connection to, or the transit
network identification that was received is of an incorrect format as defined in Annex C of the
ITU Q.931 specification for either the TNS IE or the NSF IE.
Communication Manager does not originate Cause Value 91.
164 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
Troubleshooting
●
Check Communication Manager administration (network generated the Cause Value).
- Communication Manager sent the transit network identification in the NSF IE when the
network expected it to be in the TNS IE. The protocol version on the DS1 form does not
match the near-end ISDN network that is terminating the D-channel. Contact the ISDN
network service provider and try to line up the protocols being 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
This Cause Value indicates an invalid message event only when no other cause in the invalid
message class applies.
Communication Manager does not originate this Cause Value for PRI. A BRI or Adjunct Switch
Application Interface (ASAI) application might generate this Cause Value.
Troubleshooting
The diagnostic information (DIAG) of the Cause Value should contain, if implemented, the
message type identifier of the invalid message. See Cause Values and their meanings/
interpretations on page 128.
Protocol Error Class Cause Values
Cause Value 96
[0x60/0xE0] Mandatory information element is missing
The equipment that sent this Cause Value Call Reference Value (CRV) received a message that
did not contain a required Information Element for the message to be parsed and processed.
Depending on which message in the call establishment sequence is missing information, a
message returned with this Cause Value might or might not indicate a problem establishing a
call.
When the public network is screening for Calling Party Number (CPN), the fact that CPN is
missing causes the network to return this Cause Value, but depending on optioning in the CO
the call might still go through.
This Cause Value has local significance only. 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
Issue 1 June 2005
165
Denial Events
Troubleshooting
●
Check that 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 of the interface are running different
protocols, they might be running with different Information Element encoding.
●
Check the diagnostic information (DIAG) for the IE identifier of the missing information.
See Cause Values and their meanings/interpretations on page 128.
Communication Manager generates diagnostic information. See Table 45, Cause Value 96 &
100 Diagnostic Information, on page 166.
Table 45: 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
1 of 2
166 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
Table 45: Cause Value 96 & 100 Diagnostic Information (continued)
Missing IE Identifier
Information Element
20
NETWORK SPECIFIC FACILITIES
27
NOTIFICATION INDICATOR
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
2 of 2
Cause Value 97
[0x61/0xE1] Message type non-existent or not implemented
The equipment that sent this Cause Value received a message containing a message type it
does not recognize, either because the message type is not defined or it is defined but not
implemented by the equipment.
Issue 1 June 2005
167
Denial Events
This Cause Value has local significance only. 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
Troubleshooting
●
Check that 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 of the interface are running different
protocols, they might be running with different Information Element encoding.
●
Check the diagnostic information generated by Communication Manager for the message
type identifier of the unrecognized message.
Table 46: Cause Value 97, 98, 101 Diagnostic Information
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
1 of 2
168 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
Table 46: Cause Value 97, 98, 101 Diagnostic Information (continued)
Message Type Identifier
Message
72
FACILITY REJECT
75
STATUS ENQUIRY
79
CONGESTION CONTROL
Maintenance Message
0F
SERVICE
07
SERVICE ACKNOWLEDGE
2 of 2
Cause Value 98
[0x62/0xE2] Message type, not compatible with call state, or non-existent, or not implemented
The equipment that sent this Cause Value received a message, and the procedures in the
protocol specification indicate that this is not a permissible message to receive while in this call
state. A STATUS message was received indicating an incompatible call state.
This Cause Value has local significance only. 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
Troubleshooting
●
Check that 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 of the interface are running different
protocols, they might be running with different call state machines, or different message
type encoding.
●
Check the diagnostic information generated by Communication Manager for the message
type identifier of the message that violates protocol. See Table 46: Cause Value 97, 98,
101 Diagnostic Information on page 168.
●
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 other end of the interface, run the message sequence of
the call through the SDL flow charts of the appropriate side (user or network) and the
appropriate protocol (TR41449/41459, TR1268, A211 etc.). If the call state at the other end
of the interface does not agree with that reported in the STATUS message and both sides
are already running the same protocol, then a problem with the implementation of the state
machine exists on either side.
Issue 1 June 2005
169
Denial Events
Problems have been revealed 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 shown any
problems with its state machine implementations for the different protocols.
Change Communication Manager administration to change the message sequence of the
call scenario causing the error, and help solve state machine implementation problems. For
example:
- change the inter-working message on the DS1 form from PROGRESS to ALERTING
- 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
The equipment that sent this Cause Value received a message that includes Information
Elements that are not recognized because the Information Element identifier is not defined, or it
is defined but has not been implemented by the equipment sending the Cause Value. However,
the Information Element is not mandatory in the message, and the equipment that sent the
Cause Value does not need to parse the Information Element in order to process the message.
This Cause Value has local significance only. 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
Troubleshooting
●
Check that 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 of the interface are running different
protocols, they might be running with different Information Element encoding.
●
Check Communication Manager administration (network generated the Cause Value).
- 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
The equipment that sent this Cause Value received a message that includes an Information
Element that it does recognize and implements, however one or more of the fields contained in
the Information Element are coded in such a way that it has not been implemented by the
equipment that sent this Cause Value.
170 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
This Cause Value has local significance only. 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
Troubleshooting
●
Check that 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 of the interface are running different
protocols, they might be running with different Information Element encoding.
●
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
should not affect call completion. There is no way to modify how Communication Manager
generates this information.
See Table 45, Cause Value 96 & 100 Diagnostic Information, on page 166.
Cause Value 101
[0x65/0xE5] Message not compatible with call state/
Protocol threshold exceeded (NI-2: National ISDN 2)
Cause Value 101 indicates that the equipment that sent this Cause Value received a message
that it does recognize, and procedures in the protocol specification indicate that it is not
permissible to receive the message while in this call state.
This Cause Value has local significance only. 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
Cause Value 101 (NI-2) can also mean that an established call or an establishing call is being
cleared because the threshold for multiple signaling protocol errors occurring during an active
call has been exceeded.
Troubleshooting
●
Check that 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 of the interface are running different
protocols, they might be running different call state machines.
●
Check the Communication Manager diagnostic information for the message type identifier
that is in violation of the protocol. Table 46: Cause Value 97, 98, 101 Diagnostic
Information on page 168
Issue 1 June 2005
171
Denial Events
●
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 other end of the interface, run the message sequence of
the call through the SDL flow charts of the appropriate side (user or network) and the
appropriate protocol (TR41449/41459, TR1268, A211 etc.). If the call state at the other end
of the interface does not agree with that reported in the STATUS message and both sides
are already running the same protocol, then a problem with the implementation of the state
machine exists on either side.
Problems have been revealed 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 shown any
problems with its state machine implementations for the different protocols.
Change Communication Manager administration to change the message sequence of the
call scenario causing the error, and help solve state machine implementation problems. For
example:
- change the inter-working message on the DS1 form from PROGRESS to ALERTING
- 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
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.
This Cause Value has local significance only. 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
Communication Manager logs timer expiry errors that it generates to the hardware error log
against the signaling group of the D-channel where the error occurred. The signaling group
(ISDN-SER) 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.
172 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
Table 47: Cause Value 102, Signaling Group Error Type 1, Aux Data information
Aux
Data
Value
Timer
Name
Timer
Value
Description
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)
Troubleshooting
●
Check the diagnostic information for the timer number that has expired. See Cause Values
and their meanings/interpretations on page 128.
●
Check that 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 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:
Issue 1 June 2005
173
Denial Events
●
●
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.
●
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.
●
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.
To interpret the receipt of Cause Value 102 from the far end, look at a trace/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 2 events that should have stopped the timer, the cause might be:
- 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.
- the far end might be experiencing a high traffic condition and did not have the processing
time to parse the sent message before the timer expired.
- even though the message was seen to be generated in an internal Communication
Manager trace, the message was never actually transmitted 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 did not respond to the receipt of the last message from the far
end, then Communication Manager internal hardware and software becomes suspect, and
trouble shooting the problem must proceed from that point.
Communication Manager administration that can contribute to seeing timer expiry errors:
●
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).
●
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 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. Thus 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 Communication Manager’s protocol version to c to line up the timers.
174 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Event Data
Cause Value 103
[0x67/0xE7] Parameter not implemented
The equipment sending this Cause Value received a message that includes an Information
Element that it does recognize and implements, however one or more of the fields contained in
the Information Element are coded in such a way that it has not been implemented by the
equipment sending this Cause Value.
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 Cause Values
and their meanings/interpretations on page 128.
This Cause Value has local significance only. 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
Cause Value 110
[0x6E/0xEE] Message with unrecognized parameter
The equipment sending this Cause Value received a message that includes Information
Elements that are not recognized because the Information Element identifier is not defined, or it
is defined but has not been implemented by the equipment sending the Cause Value. However,
the Information Element is not mandatory in the message, and the equipment sending the
Cause Value does not need to parse the Information Element in order to process the message.
This Cause Value has local significance only. 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
Cause Value 111
[0x6F/0xEF] Protocol error unspecified
Cause Value 111 indicates that he equipment sending this Cause Value experienced a protocol
error event for which no other Cause Value in the Protocol Error class applies.
This Cause Value has local significance only. 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
Issue 1 June 2005
175
Denial Events
Cause Value 111 (NI-2) is used in packet mode to be able to map the X.25 Cause Value 17
“remote procedure error”.
Communication Manager does not originate this Cause Value for PRI. A BRI or Adjunct Switch
Application Interface (ASAI) application might generate this Cause Value.
Cause Value 112
[0x70/0xF0] Local procedure error (1TR6: AT&T ISDN Protocol)
This is a packet mode Cause Value.
Cause Value 113
[0x71/0xF1] Remote procedure error (1TR6: AT&T ISDN Protocol)
This is a packet mode Cause Value.
Cause Value 114
[0x72/0xF2] Remote user suspended (1TR6: AT&T ISDN Protocol)
This Cause Value indicates to the remote user that the call has been put on hold.
Cause Value 115
[0x73/0xF3] Remote user resumed (1TR6: AT&T ISDN Protocol)
This Cause Value indicates to 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)
This Cause Value indicates that in the equipment sending this Cause Value is the point in the
network where the call has inter-worked with a network that does not provide Cause Value
information for actions it takes. Thus when an event takes place this Cause Value is sent
because the precise cause for the event cannot be ascertained.
This Cause Value has end-to-end significance and should always be passed back through the
network to the user.
176 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Communication Manager generates this Cause Value for events on tandem calls that have
inter-worked from ISDN trunk groups to non-ISDN trunk groups.
Troubleshooting
●
Check the Cause Value Information Element (LOC). See Location Codes on page 130.
Denial Event Tables
Call processing Denial Events
Event Types 1000 - 2299 show denial events generated during call processing, as listed in
Table 48, Call Process denial events (1001 - 1172), on page 177, Table 50, Call Process denial
events (1225 - 1899), on page 193, and Table 53, Call Process denial events (2021 - 2299), on
page 238.
Use Event Types 1000 - 1899 to help isolate the cause of receiving reorder or intercept
treatment:
●
Event Types 1000 -1299 might explain events where reorder treatments are initiated, or to
events that eventually lead to reorder treatments.
●
Event Types 1300 - 1899 might explain events where intercept treatments are initiated, or
to events that eventually lead to intercept treatments.
Table 48: Call Process denial events (1001 - 1172)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1001
Resource not available
grp_m process returned GM_FAIL in response to
GM_MTM_DIG_DONE message.
1002
Call parked on user
A call might already be parked on user.
1003
Can't connect Tone Det
Cannot connect or reconnect tone detector during
outgoing wait supervision. Automatic Number
Identification (ANI) request is expected.
1004
Can't reserve Tone Det
Cannot reserve tone detector.
1005
Trunk sequence error
Outgoing MFE call received answer before
addressing was complete.
1006
TTR_unavail
GCOL_ERR usually means no Touch Tone
Receiver (TTR) available.
Event Data 2
1 of 13
Issue 1 June 2005
177
Denial Events
Table 48: Call Process denial events (1001 - 1172) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1007
CAS_remhold
The Centralized Attendant Service (CAS) Remote
Hold feature was accessed. No CAS attendant
exists.
1008
CAS_remhold
Centralized Attendant Service (CAS) Remote
Hold was accessed by a non-CAS attendant.
1009
CAS_remhold
Centralized Attendant Service (CAS) Remote
Hold was accessed by non-CAS attendant.
Analog Answer-Hold/Unhold invalid.
1010
TEG denied origination
Terminating Extension Group was denied an
origination.
1011
Dest_unavail
Facilities were exhausted during rerouting. Bearer
capability is VOICE, VOICE BAND DATA.
Received unexpected TCM not yet used in
routing. Reroute attempt using received TCM
finds principal is NULL or attendant extended call
to ARS. Queueing is not allowed.
1012
Dest_unavail
Facilities were exhausted during 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.
Queueing is not allowed.
1013
Dest_unavail
Facilities were exhausted during 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.
Queueing is not allowed.
1014
Dest_unavail
Inter-PBX attendant service termination attempt
failed. The trunk was busy.
1015
Dest_unavail
Attendant seizing trunk for thru-dialing failed. The
trunk was busy or not available.
1016
Remote Cvg loop denial
Outgoing remote coverage call, with digit
conversion to the principal's extension. Prevent
looping.
1017
ADX_unavail
Termination to AUDIX coverage point failed,
unable to terminate at an AUDIX hunt group.
1018
MM_denial
Multimedia call. Convert termination to a meetme
User ID instead of station User ID failed. Invalid
bearer cap received.
1019
MM_denial
Multimedia call. Convert termination to a meetme
User ID instead of station User ID failed. user_m
failed to get & return meetme User ID.
1020
MM_denial
Multimedia call. Convert termination to a meetme
User ID instead of station User ID failed. user_m
returned a meetme uid = 0.
1021
Call Term overflow
Call termination overflow to DDD of an Electronic
Tandem Network Listed Directory Number. Call
should be blocked.
Event
Data 1
Event Data 2
2 of 13
178 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 48: Call Process denial events (1001 - 1172) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1022
CDR_resource
Call Detail Recording (CDR) resource exhaustion.
Caller from tie trunk can receive reorder tone.
1023
CDR_resource
Call Detail Recording (CDR) resource exhaustion.
Give Trunk/Personal Central Office Line (TK/
PCOL) caller termination to announcement. User
ID not found for announcement.
1024
CDR_resource
Call Detail Recording (CDR) resource exhaustion.
Caller from non-Trunk/Personal Central Office
Line (TK/PCOL) (from line) can receive reorder
tone.
1025
Incompatable Bandwidth
Terminated to an endpoint or trunk group that
cannot support the requested bandwidth.
1026
ADX_unavail
Call from non-trunk. Unable to terminate at an
AUDIX hunt group.
1027
Attd control trk denial
Switch Classified Calls might not go to a trunk
controlled by an attendant.
1028
Trk_unavail
No trunks are available and there is no chance of
being queued.
1029
Mod_unavail
Modem unavailable from pool.
1030
Mod_unavail
Modem unavailable from pool.
1031
LWC failure
Leave Word Calling. Async message response
from msg_sv: give user LW_REORDER.
1032
MM_fail
Multimedia call. Creating a multimedia user. User
ID (UID) - failure. user_m returned a mtm_uid of
0.
1033
MM_fail
Multimedia call. Cannot create a multimedia user.
1034
MM_fail
Multimedia call. GM_MTM_DIGIT digit sending
message failed on second address of
multi-number call.
1035
MM_fail
Multimedia call. Trying to send more than the
maximum of two addresses in a multi-number call.
1036
Station sec code len qry
The query for the administered minimum
station-security-code length failed.
1037
Routing UID=0
The Routing User ID (UID) = 0 for a remote
Distributed Communication System (DCS) user
that has activated automatic callback toward a
station local to this switch.
1038
Acd_login
Traditional Automatic Call Distribution (ACD)
agent login failed. The maximum number of logins
already exist.
1039
Acd_login
GM/UM set up of the Automatic Call Distribution
(ACD) Logical Agent login info failed, before
password matching, if any.
Event Data 2
3 of 13
Issue 1 June 2005
179
Denial Events
Table 48: Call Process denial events (1001 - 1172) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1040
Acd_login
GM/UM set up of the Automatic Call Distribution
(ACD) Logical Agent login info failed after
password matching succeeded.
1041
DS0 loop around failed
Incoming ds0 test call failed to set up
non-inverting digital loop-around capability.
1042
TTR_unavail
Facility Access Test. Touch Tone Receiver (TTR)
is missing, did not get attached, might be in use
by some other call.
1043
Specified TTR unavailable
Facility Access Test. The specified Touch Tone
Receiver (TTR) needed to collect digits was in
use.
1044
reserve for FAT fat_compl
Facility Access Test. Reserved for silent reorder
on the chance that recoding is required.
1045
FAT tone test failed
Facility Access Test. The test to hear tone failed.
The Expansion Network Link might be down.
1046
Specified TSLOT busy
Facility Access Test. Specified timeslot was busy.
1047
Music port connect fail
Facility Access Test. Completing call to music port
failed. EPN Link might be down, or music port is
not administered.
1048
FAT trunk busy
Facility Access Test - completing call to trunk.
Trunk is busy.
1049
ISDN trunk busy
Facility Access Test - completing call to ISDN
trunk. Trunk is busy.
1050
Illegal Message Retrieval
Remote access users are not allowed access to
messages via voice coverage message retrieval.
1051
Speech Port unavailable
No voice synthesis speech port is available for
coverage message retrieval.
1052
Called announcement busy
Call to announcement, but announcement is busy.
1053
Chime tone connection
Connection of a chime tone to a service failed.
There might be an invalid service ID or software
error.
1054
TTR_unavail
Collection of password digits needs a Touch Tone
Receiver (TTR). No in-service TTRs are available.
1055
No call to cancel
Deactivate automatic callback (ACB) was denied
or outgoing trunk queueing (OTQ) was denied.
The Caller ID of the ACB/OTQ call to be cancelled
could not be found. There might be nothing to
deactivate.
1056
Adjct Rte calls can't Que
Adjunct Switch Application Interface (ASAI)
adjunct originated switch classified calls and
adjunct-routed calls are not allowed to queue.
1057
COS - Auto Callback
User's Class of Service does not permit activation
of automatic callback.
Event
Data 1
Event Data 2
4 of 13
180 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 48: Call Process denial events (1001 - 1172) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1058
Auto Callback User ID
User activating automatic callback has software
partyblock member misrepresented.
1059
Auto Callback double qued
User is activating automatic callback, but the call
has already been queued or has no principal
terminating User ID.
1060
Auto Callback terminator
Activating automatic callback is not allowed when
the terminating extension is a group attendant,
terminating extension group, Vector Directory
Number, or if vector processing is active.
1061
Auto Callback terminator
Activating automatic callback.
● 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 did not
happen for one of several reasons
identified in rc from gm_term
re_termination attempt in onhk_que.c
1062
Auto Callback activation
Activating automatic callback. Checks on queue
availability and/or Distributed Communication
System (DCS) termination pass OK, but activation
is denied.
1063
Auto Callback ineligible
Activating Automatic Callback (ACB). Response
to callback type query is queue ineligible, might be
ACB is in use or call is on hold, or GQRY_ERR
(might be no call ID behind call back button).
1064
Double queueing denied
Manual activation of queueing. Call has already
been queued (automatic).
1065
Manual queing terminator
Manual activation of queueing. There is no
principal terminator on which to queue.
1066
Manual queing - full que
Manual activation of queueing. The queue is full
or queue length is zero.
1067
Manaual queing denied
Manual activation of queueing. Checks on queue
availability pass OK, but activation is denied.
1068
queued call went away
Reactivation of automatic callback or outgoing
trunk queueing. The call disappeared from the
queue.
1069
PMS link/printer down
Property Management System (PMS) cannot log
housekeeping status. PMS link is not operational
and the printer is down.
1070
(also in
Table 49)
TTR_unavail
ISDN trunk initiation of in-band end-to-end digit
collection failed. Might be waiting for a Touch Tone
Receiver (TTR).
1071
Wireless - trunk failure
General Central Office (GCO) Wireless
Subscriber System (WSS) call origination denied iap_cid_qry failure. Route to GCO subscriber
trunk failed.
Event Data 2
5 of 13
Issue 1 June 2005
181
Denial Events
Table 48: Call Process denial events (1001 - 1172) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1072
TTR_TDM_VC
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in Audio add-on password
supervision.
1073
TTR_TDM_VC
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in authorization code supervision,
waiting for digit analysis of the authorization code.
1074
TTR_TDM_VC
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in Code Call paging seizure
supervision.
1075
TTR_TDM_VC
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in feature supervision waiting to see
which feature is being invoked.
1076
TTR_TDM_VC
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in idle supervision.
1077
TTR_TDM_VC
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in normal answer supervision.
1078
TTR_TDM_VC
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in outgoing trunk outpulsing
supervision.
1079
TTR_TDM_VC
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in outgoing trunk seizure supervision.
1080
TTR_TDM_VC
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in the supervisor for telecommuting
access waiting for certain Feature Access Codes
after the telecommuting extension has been
accessed.
1081
Change SSC denied
Change Station Security Code (SSC) REORDER. Possible causes:
● Too many admin users or save-trans in
progress
● Data already locked
● Translations being 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 busy
Doing “Remove Skill” on agent currently busy for
that skill (has DAC or is in ACW or on call).
Event
Data 1
Event Data 2
6 of 13
182 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 48: Call Process denial events (1001 - 1172) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1083
Add/Rmv skill denied
Add/Remove Agent Skills. Possible causes:
Event
Data 1
Event Data 2
● could not get station ID
● too many admin users or
save-translations in progress
● data already locked, maybe translations
are being saved or SAT user is changing
agent data
1084
DCS link down
Remote user activation of call forward Distributed Communication System (DCS) link not
up.
1085
PMS response timeout
Property Management System failed to respond
to maid status in the 4 seconds allowed.
1086
MFC no answer timeout
MultiFrequency Compelled (MFC) call circuit
congestion. No answer timeout from MFC call.
1087
MFC no answer timeout
MultiFrequency Compelled call circuit congestion.
No answer timeout. Might be bad trunk or no
Touch Tone Receiver (TTR) available at remote
end, for example.
1088
No answer timeout
MultiFrequency Compelled call circuit congestion.
No answer timeout. Might be bad trunk or no
Touch Tone Receiver (TTR) available at remote
end, for example.
1089
MFC no answer timeout
MultiFrequency Compelled call circuit congestion.
No answer timeout. Might be bad trunk or no
Touch Tone Receiver (TTR) available at remote
end, for example.
1090
T302 intercept timeout
T302 interdigit timer timeout.
1091
Max Paste users Pasting
The maximum allowable stations are currently
using PC Application Software Exchange
(PASTE). Wait and try again.
1092
Announcement unavailable
Might be announcement is busy, or
announcement is not present on board.
1093
Announcement memory exh
Announcement is dropped, announcement
memory is exhausted.
1094
Permanent Seizure
Direct Inward Dialing trunk origination. Digit
timeout with no digits dialed. Permanent incoming
seizure treatment is to give reorder.
1095
QSIG Call Offer timeout
QSIG Call Offer encountered timeout of 1 minute
path retention timer.
1096
Wakeup time unavailable
Collecting digits for “room wakeup by tones”
feature. Cannot do a wakeup for the specified
time.
1097
MFC No Answer timeout
MFC call circuit congestion. No answer timeout.
Might be bad trunk or no Touch Tone Receiver
(TTR) available at remote end, for example.
7 of 13
Issue 1 June 2005
183
Denial Events
Table 48: Call Process denial events (1001 - 1172) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1098
TTI merge/unmerge failed
Station server could not perform Terminal
Translation Initiation (TTI) merge/unmerge.
Certain resources are unavailable. The user can
try again and the resources might be available.
1099
LWC access code rejected
Voice synthesis Leave Word Calling access code
rejected by msg_sv.
1100
TTI - station active
In preparation for lock resources 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 finding a
modem for an incoming data call.
1102
MM - voice call failure
Processing a Multimedia compatible vector, there
is failure doing conversion to voice call.
1103
Tone Detector conn fail
Cannot connect tone detector for trunk terminated
call. Silent Reorder.
1104
Tone Detector conn fail
Cannot connect tone detector for voice station or
DEXT. Silent Reorder.
1105
Ringback limit met
The limit is met of 4 ringbacks in a row before far
end answers. Silent Reorder.
1106
Ringback limit met
The limit is met of 36 ringbacks in a row before far
end answers. Silent Reorder.
1107
Reorder tone received
Reorder tone received before far end answers.
Silent Reorder.
1108
LWC access code rejected
The message server rejected the Leave Word
Calling Access code that was dialed.
1109
DCS link/msg buffer
Remote busy verification encountered a
Distributed Communication System (DCS) link
down or an exhausted DCS message buffer.
1110
DCS link down
Distributed Communication System (DCS) remote
trunk group selection. Remote Direct Trunk Group
Selection (DTGS) button push by attendant, but
DCS link is down.
1111
CFWD activate/cancel
Send a callforward activation message to the
remote switch. Message buffers exhausted, call
not UDP & not Distributed Communication
System (DCS), DCS link is down.
1112
TTR_unavail
Russian Automatic Number Identification (ANI)
3rd party feature button. Touch Tone Receiver
(TTR) not available.
1113
ANI error limit
3rd party feature activation. Automatic Number
Identification (ANI) error on 2 tries.
1114
DCS trunk required
Remote busy verification. A Distributed
Communication System (DCS) trunk is required.
Event
Data 1
Event Data 2
8 of 13
184 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 48: Call Process denial events (1001 - 1172) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1115
LWC timeout
Leave Word Calling timeout occurred in the dap
for a non-call associated attempt.
1116
DCS confirm msg timeout
Remote busy verification. A Distributed
Communication System (DCS) confirmation
message was not back in 4 seconds.
1117
Outgoing trk seizure fail
Outgoing trunk seizure failure, busy verify hit
glare, digit timeout via ogt_sz_sup().
1118
Analog station ringer
Analog principal station has trouble ringing.
1119
Analog station ringer
Analog covering station has trouble ringing and
principal was station not rung successfully.
1120
Bsy Vfy termination fail
RP_M found busy verification terminator
available, but termination to it failed.
1121
Bsy Vfy termination fail
RP_M found busy verification trunk terminator
available, but USER_M found it maintenance
busy or otherwise unavailable.
1122
Bsy Vfy termination fail
GRP_M found busy verification terminator
available, but USER_M found it out-of-service.
1123
Bsy Vfy termination fail
GRP_M found busy verify terminator available,
but USER_M denied termination 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 fail
GRP_M found busy verify hunt group member
available, but USER_M found hunt group all busy
1125
Bsy Vfy call went away
Bridging a busy verification party to a call that no
longer exists.
1126
Bsy Vfy merge failed
Bridging a busy verification party to a call cannot
be merged. Merge checks include:
● not being busy verified by another user
● not a data call
● the call is in either talk or park state
- One exception to this is Converse calls
which are always in nrm_ans_sup()
● no tone connected or bv or conference
tone connected
● not exceed conference limit
● no aux trunk involved in the call
Event Data 2
9 of 13
Issue 1 June 2005
185
Denial Events
Table 48: Call Process denial events (1001 - 1172) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1127
Bsy Vfy warn tone conn
Busy verification warning tone connection (callr)
failed.
1128
Bsy Vfy warn tone conn
Busy verify warning tone connection to verified
call (callr2) failed.
1129
Bsy Vfy call went away
Bridging a busy-verification call with a
busy-verification call that no longer exists.
1130
Bsy Vfy merge failed
Bridging a busy verification party to a call cannot
be merged. Merge checks include:
● not being busy verified by another user
● not a data call
● the call is in either talk or park state
- One exception to this is Converse calls
which are always in nrm_ans_sup()
● no tone connected or bv or conference
tone connected
● not exceed conference limit
● no aux trunk involved in the call
1131
Bsy Vfy merge failed
Bridging a busy verification party to a call, the
merge operation failed.
1132
Auto Callback failure
Event
Data 1
Event Data 2
● Query for calling party’s callback type
failed
● Adding an automatic callback call to the
que 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 termination fail
Whisper paging termination to station, idle call
appearance failed.
1134
Whisp Pg to OS station
Whisper paging to Out of Service (OOS) station.
1135
Whisp Pg term denied
Whisper page to station denied.
STATION - admin busy
● user has blocked whisper pages or has
service observe pending
● (BRI) maintenance busy and the call is
already queued
● whisper page not allowed towards
analog line
● whisper page termination requires at
least 2 idle call appearances
● the current call is in the CA_DIAL state
1136
Whisp Pg hunt grp busy
Whisper paging - hunt group all made busy.
shouldn’t see this - hnt_qry does not respond to
qtype QWHISP_PG.
1137
Whisp Pg user blocked
User has whisper page blocked.
1138
Whisp Pg Svc Obsvd call
Whisper page - bridging to service-observed call.
10 of 13
186 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 48: Call Process denial events (1001 - 1172) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1139
Whisp Pg Attd call
Whisper page - bridging to call with an attendant
on it.
1140
Whisp Pg Man Exclsn call
Whisper page - bridging to call with manual
exclusion activated.
1141
Whisp Pg merge denied
Bridging a busy whisper paging party to a call
cannot be merged.
Merge checks include:
● not being busy verified by another user
● not a data call
● the call is in either talk or park state
- One exception to this is Converse calls
which are always in nrm_ans_sup()
● no tone connected or bv or conference
tone connected
● not exceed conference limit
● no aux trunk involved in the call
1142
Whisp Pg warn tone conn
Whisper page warning tone connection to callr
failed.
1143
Whisp Pg warn tone conn
Whisper page warning tone connection to callr2
failed.
1144
Whisp Pg merge failed
Merge page call with paged call - query for
originator’s portid failed.
1145
Whisp Pg merge failed
Merge page call with paged call - query for paged
party’s portid failed.
1146
Whisp Pg call went away
Merge page call with paged call - paged party’s
call no longer exists
1147
Whisp Pg blocked
Merge page call with paged call - paged party has
whisper page blocked.
1148
Whisp Pg Svc Obsvd call
Merge page call with paged call - paged party is
being service observed.
1149
Whisp Pg merge Attd call
Merge page call with paged call - paged party is
on a call with an attendant.
1150
Whisp Pg merge Man Exclsn
Merge page call with paged call - paged party has
manual exclusion activated.
1151
Whisp Pg merge denied
Bridging a busy whisper paging party to a call
cannot be merged.
Merge checks include:
● not being busy verified by another user
● not a data call
● the call is in either talk or park state
- One exception to this is Converse calls
which are always in nrm_ans_sup()
● no tone connected or bv or conference
tone connected
● not exceed conference limit
● no aux trunk involved in the call
1152
Whisp Pg merge failed
Merge page call with paged call - merge operation
failed.
Event Data 2
11 of 13
Issue 1 June 2005
187
Denial Events
Table 48: Call Process denial events (1001 - 1172) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1153
ARS man activation queing
Manual activation of queueing seen while in ARS
supervision - ARS DAC has been dialed.
1154
Outgoing trk seizure fail
Seize failed. Indicates either:
● 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 timeout
Digit timeout while in busy verification on
non-DCS call type and not bridge-on case.
1156
Connection resrce unavail
Connection resource not available. this is an
administered connection.
1157
TTR_unavail
Activate service observing feature. 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 could not get a Touch Tone Receiver
(TTR).
1158
Svc Obsv Ext table full
Validation of service observed extension. No room
in software table to store service observing User
IDs.
1159
Cancel wakeup failed
Collect digits for time used by the wakeup
features. Could not cancel wakeup.
1160
Activate wakeup failed
Collect digits for time used by the wakeup
features. Could not activate wakeup time.
Possible 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 parties
Whisper page - bridging to a call that has
maximum number of parties already connected.
1162
Max# connected parties
Whisper page - bridging to call that has maximum
number of parties already connected.
1163
TTR_TDM_VC
Time Division Multiplexed (TDM) Voice Condition
(VC) creation for Touch Tone Receiver (TTR)
failed while in whisper supervision.
1164
(also in
Table 49)
ISDN no cause value
Outgoing ISDN trunk rejected/ dropped by far end
1165
Attd ctrl of ARS pref (s)
Attendant control of trunk group access ARS
preference(s).
1166
(also in
Table 49)
Unassigned number
Unassigned number.
Event
Data 1
Event Data 2
DIAG/LOC/CV
12 of 13
188 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 48: Call Process denial events (1001 - 1172) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1167
Can’t term emergency call
No Attendants or redirection extension assigned
for termination of emergency call.
1168
Second call failed
Russia MultiFrequency (MF) Packet Signaling Second call attempt failed.
1169
Retry option not enabled
Russia MultiFrequency (MF) Packet Signaling.
Either T1 or T2 timer expired, or a B6 signal was
received, and the “Re-try?” option is no.
1170
Erroneous signal received
Russia MultiFrequency (MF) Packet Signaling Erroneous signal received.
1171
ATM Blockage:TDMSVC fail
TDM_SVC failed due to lack of resources, call
was dropped. The caller hears dead air.
1172
Path Rep ASAI to non-ASAI
Path Replace merged from Adjunct Switch
Application Interface (ASAI) callr to non-ASAI
callr.
Event Data 2
13 of 13
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 your 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 49: ISDN, IP, and SIP-generated denial events (1173 - 1224)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
Event Data 2
1070 (also
in Table 48)
TTR_unavail
ISDN trunk initiation of in-band end-to-end digit
collection failed. Might be waiting for a Touch
Tone Receiver (TTR).
1164
(also in
Table 48)
ISDN no cause value
Outgoing ISDN trunk rejected/ dropped by far
end.
1166
(also in
Table 48)
Unassigned number
Unassigned number.
1173
No route to transit ntwk
No route to specific transit network.
See Cause Value 02.
UID
DIAG/LOC/CV
1174
No route to dest
No route to destination.
See Cause Value 03 on page 136.
UID
DIAG/LOC/CV
DIAG/LOC/CV
1 of 4
Issue 1 June 2005
189
Denial Events
Table 49: ISDN, IP, and SIP-generated denial events (1173 - 1224) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
Event Data 2
1175
ISDN channel unacceptable
Channel unacceptable.
See Cause Value 06 on page 139.
UID
DIAG/LOC/CV
1176
ISDN MLPP circ not resrvd
MLPP preemption, circuit not reserved.
See Cause Value 08 on page 139.
UID
DIAG/LOC/CV
1177
ISDN MLPP circ resv reuse
MLPP preemption, circuit reserved for reuse.
See Cause Value 09 on page 140.
UID
DIAG/LOC/CV
1178
Normal call clearing
Normal call clearing.
See Cause Value 16 on page 141.
UID
DIAG/LOC/CV
1179
User busy
User busy.
See Cause Value 17 on page 141.
UID
DIAG/LOC/CV
1180
No user responding
No user responding.
See Cause Value 18 on page 142.
UID
DIAG/LOC/CV
1181
User alerting, no answer
User alerting, no answer.
See Cause Value 19 on page 143.
UID
DIAG/LOC/CV
1182
Subscriber absent
Subscriber absent.
See Cause Value 20 on page 143.
UID
DIAG/LOC/CV
1183
Call rejected
Call rejected.
See Cause Value 21 on page 143.
UID
DIAG/LOC/CV
1184
Number changed
Number changed.
See Cause Value 22 on page 143.
UID
DIAG/LOC/CV
1185
Dest out of order
Destination out of order.
See Cause Value 27 on page 144.
UID
DIAG/LOC/CV
1186
Invalid number format
Invalid number format.
See Cause Value 28 on page 144.
UID
DIAG/LOC/CV
1187
Facility rejected
Facility rejected.
See Cause Value 29 on page 145.
UID
DIAG/LOC/CV
1188
Response status enquiry
Response status enquiry.
See Cause Value 30 on page 146.
UID
DIAG/LOC/CV
1189
Normal, unspecified
Normal, unspecified.
See Cause Value 31 on page 146.
UID
DIAG/LOC/CV
1190
No circ/chan avail
No circuit or channel available.
See Cause Value 34 on page 147.
UID
DIAG/LOC/CV
1191
Network failure
Network failure.
See Cause Value 38 on page 148.
UID
DIAG/LOC/CV
1192
Temporary failure
Temporary failure.
See Cause Value 41 on page 149.
UID
DIAG/LOC/CV
1193
Equipment congestion
Switching equipment congestion.
See Cause Value 42 on page 149.
UID
DIAG/LOC/CV
1194
ISDN user info discarded
User info discarded.
See Cause Value 43 on page 149.
UID
DIAG/LOC/CV
2 of 4
190 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 49: ISDN, IP, and SIP-generated denial events (1173 - 1224) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
Event Data 2
1195
Circ/channel unavail
Requested circuit / channel not available.
See Cause Value 44 on page 150.
UID
DIAG/LOC/CV
1196
ISDN blocked precedence
Locked precedence level.
See Cause Value 46 on page 151.
UID
DIAG/LOC/CV
1197
Resources unavail/unspec
Resources unavailable, unspecified.
See Cause Value 47 on page 151.
UID
DIAG/LOC/CV
1198
ISDN req fac no subscribe
Requested facility no subscribed.
See Cause Value 50 on page 152.
UID
DIAG/LOC/CV
1199
ISDN outgoing call barred
Outgoing calls barred.
See Cause Value 52 on page 153.
UID
DIAG/LOC/CV
1200
ISDN incoming call barred
Incoming calls barred.
See Cause Value 54 on page 153.
UID
DIAG/LOC/CV
1201
Bearer cap not available
Bearer capability not presently available.
See Cause Value 58 on page 155.
UID
DIAG/LOC/CV
1202
Service unauth FranceVN4
Service not authorized / France VN4.
See Cause Value 62 on page 157.
UID
DIAG/LOC/CV
1203
Serv/option unavailable
Service/option not available, unspecified.
See Cause Value 63 on page 157.
UID
DIAG/LOC/CV
1204
Bearer cap not implem
Bearer capability not implemented.
See Cause Value 65 on page 158.
UID
DIAG/LOC/CV
1205
ISDN chan type not implem
Channel type not implemented.
See Cause Value 66 on page 158.
UID
DIAG/LOC/CV
1206
Req facility not implem
Requested facility not implemented.
See Cause Value 69 on page 159.
UID
DIAG/LOC/CV
1207
Only restr digital BC av
Only restricted digital BC available.
See Cause Value 70 on page 160.
UID
DIAG/LOC/CV
1208
Srv/opt not imp/unsp
Service/option not implemented, unspecified.
See Cause Value 79 on page 160.
UID
DIAG/LOC/CV
1209
Invalid call reference
Invalid call reference.
See Cause Value 81 on page 161.
UID
DIAG/LOC/CV
1210
Channel doesn't exist
Identified channel does not exist.
See Cause Value 82 on page 161.
UID
DIAG/LOC/CV
1211
Incompatible dest
Incompatible destination.
See Cause Value 88 on page 163.
UID
DIAG/LOC/CV
1212
ISDN trans ntwk not exist
Transit network does not exist.
See Cause Value 91 on page 164.
UID
DIAG/LOC/CV
1213
Invalid message
Invalid Message.
See Cause Value 95 on page 165.
UID
DIAG/LOC/CV
1214
Mandatory IE missing
Mandatory IE is missing.
See Cause Value 96 on page 165.
UID
DIAG/LOC/CV
3 of 4
Issue 1 June 2005
191
Denial Events
Table 49: ISDN, IP, and SIP-generated denial events (1173 - 1224) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
Event Data 2
1215
ISDN msg typ nonexist/imp
Message type nonexistent or not implemented.
See Cause Value 97 on page 167.
UID
DIAG/LOC/CV
1216
Msg not compat state
Message not compatible with call state.
See Cause Value 98 on page 169.
UID
DIAG/LOC/CV
1217
ISDN nonexistant IE
Nonexistent IE.
See Cause Value 99 on page 170.
UID
DIAG/LOC/CV
1218
Invalid IE contents
Invalid IE contents.
See Cause Value 100 on page 170.
UID
DIAG/LOC/CV
1219
ISDN msg not compat state
Message not compatible with call state.
See Cause Value 101 on page 171.
UID
DIAG/LOC/CV
1220
Recovery on timer expiry
Recovery on timer expiry.
See Cause Value 102 on page 172.
UID
DIAG/LOC/CV
1221
Protocol err unspecified
Protocol Error Unspecified.
See Cause Value 111 on page 175.
UID
DIAG/LOC/CV
1222
ISDN intr ana ntwk Fr VN4
Inter-worked to analog network France VN4
UID
DIAG/LOC/CV
1223
ISDN goto con mode Fr VN4
Go to conversation mode France VN4
UID
DIAG/LOC/CV
1224
Interwork/cause unknown
Inter-working or cause unknown.
See Cause Value 127 on page 176.
UID
DIAG/LOC/CV
1570 (also
in Table 53)
TTR insertion failed
Processing incoming digits for ISDN call.
Insertion of Touch Tone Receiver (TTR) to
collect in-band digits failed.
1573 (also
in Table 53)
Principal is not ISDN
Get called digits, calling number and name,
etc., and send ISDN SETUP message to the far
end. The principal is not ISDN.
4 of 4
192 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Call processing Denial Events
Event Types 1000 - 1899 show denial events generated during call processing, as listed in Call
Process denial events (1001 - 1172) on page 177 and Call Process denial events (1225 1899) on page 193.
Table 50: Call Process denial events (1225 - 1899)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1225
All SBS extensions in use
Separation of Bearer and Signaling (SBS)
Signaling call tried to allocate an SBS extension,
but all SBS extensions are in use.
1226
Cannot get SBS Sig CID
Separation of Bearer and Signaling (SBS) Bearer
call tried to retrieve SBS Signaling call Caller ID.
1227
Can't send SBS ID to orig
Separation of Bearer and Signaling (SBS)
Signaling call tried to send an INFO message
with unique ID, but the INFO could not be sent.
1228
Non-bearer trk to SBS ext
A non-trunk call terminated to an allocated
Separation of Bearer and Signaling (SBS)
extension waiting for the Bearer SBS call to
come.
1229
Unable to get ARS fac
Error occurred when getting the ARS Feature
Access Code in order to build the Separation of
Bearer and Signaling (SBS) complete callback
number.
1230
Unable to get contry code
Error occurred when getting the local country
code in order to build the Separation of Bearer
and Signaling (SBS) complete callback number.
1231
Unable to get intl accode
Error occurred when getting the international
access code in order to build the Separation of
Bearer and Signaling (SBS) complete callback
number.
1232
TTR err SBS ID dgt coll
Error occurred when trying to allocate Touch
Tone Receiver (TTR) to collect the Unique ID
in-band at the terminating node.
1233
Invalid SBS ID dgts/tmo
Invalid or partial Separation of Bearer and
Signaling (SBS) Unique ID collected, or interdigit
tmo while collecting Unique ID at SBS
terminating node.
1234
TTR err IGAR ID dgt coll
Error occurred when trying to allocate Touch
Tone Receiver (TTR) to collect the Unique ID
in-band at the originating node.
1235
Invalid IGAR ID dgts/tmo
Invalid or partial Inter-Gateway Alternate Routing
(IGAR) Index collected, or interdigit timeout while
collecting destination IGAR index at IGAR
originating node.
1236-1299
not assigned
Event Data 2
begin intercept type source of denials
1 of 33
Issue 1 June 2005
193
Denial Events
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1300
Digits prevent call route
MultiFrequency Compelled call not routed due to
invalid digit, not enough digits, etc.
1301
Need MFC or TT dial type
Outgoing dial type is not MultiFrequency
Compelled or Touch Tone (TT).
1302
Dgts needed or caller typ
Minimum digits not dialed before pressing feature
button, or calling party is not a station or
attendant.
1303
TTR queue type invalid
Touch Tone Receiver (TTR) queueing problem.
Invalid “ttrq_typ” found.
1304
Dgt absorbtion/insertion
Digit block requires preconditioning for digit
absorption or insertion. Error in treatment. A
Touch Tone Receiver (TTR) is available.
1305
Dgt collection software
Software error. Invalid return code
ttrq_type == ORIG_TTRQ?
y - valid rc: GCOL_AUTO, GCOL_OK
ttrq_type == NO_TTRQ?
y - valid rc: GCOL_AUTO, GCOL_OK
GCOL_ERR, GCOL_ATTD, GCOL_ATTD_NS,
GCOL_NS, GCOL_TTRQ, GCOL_TERM
1306
Satlt dropped TGU B4 ansr
Italian outgoing tie (TGU) call dropped by satellite
before answer.
1307
LoginID UID query failure
Query for User ID of logged-in Logical Agent’s
LoginID failed.
1308
PNT or TIE restriction
Enforce PNT-PNT Restrictions. PTT or TIE not
allowed to connect to this PTT trunk.
1309
Data/Voice BCC setup fail
Trouble setting up voice to data/data to voice
(change Bearer Capability Class) and/or outgoing
Bearer Capability Class (BCC) for ISDN voice
call.
1310
Incompatible term endpnt
Tried to terminate to incompatible endpoint.
1311
Routing software failure
Invalid return code from dpm_rerte. Software
error.
1312
Route PTRN trunk unavail
No available trunks in the routing pattern.
1313
Remote DTGS invalid digit
Remote Direct Trunk Group Selection (DTGS)
that was processing digits (after tie Trunk Access
Code) from the preprocessing digit buffer to the
digit buffer found invalid digit (digit = 0 or > 0xa).
1314
Dgt collection setup fail
Error during setup for end-to-end signaling digit
collection.
1315
Dgt collection setup fail
Error during setup for end-to-end signaling digit
collection prevented setting an indication in
ttrq_typ that the call was queued during
termination waiting for a Touch Tone Receiver
(TTR) (CODEC_TTR).
Event
Data 1
Event Data 2
2 of 33
194 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1316
No unrstrictd term point
No principal to terminate to, or it is termination
restricted, and there is no termination coverage
point.
1317
Coverage software failure
Software error call_p termination to coverage
point received invalid gm_term return code.
1318
Split UID query failure
Adjunct Switch Application Interface (ASAI)
Direct Agent Call termination fails in querying isg
for split User ID.
1319
Call record sftw failure
Incoming QSIG call completion ringout call.
Failure retrieving suspended Temporary
Signaling Connection (TSC) call record from
service dispatcher.
1320
Call record sftw failure
Incoming QSIG call completion ringout call. Call
completion ringout call record does not match
Temporary Signaling Connection (TSC) call
record retrieved from service dispatcher
suspension.
1321
Illegal term to rmt Audix
Adjunct Switch Application Interface (ASAI)
switch classified call. Illegal attempt to terminate
off-switch to a remote AUDIX.
1322
Data to station w/o H.320
ATA call to station type endpoint, but the station
does not have the H.320 conversion flag set.
1323
Dgt collection setup fail
Authorization code received, terminate to local
extension, origination from ISDN trunk or
endpoint, error during end-to-end signaling digit
collection setup.
1324
Data Ext code calling
Code calling by a data extension.
1325
ASAI SCC to UDP nite svc
ASAI Switch Classified Call (SCC) to hunt group
with UDP night service. This type of call is not
allowed to go off-switch.
1326
MM to Attd ctrld trunk
Multimedia user is not allowed to call a trunk
under attendant control, Attendant Control of
Trunk Group Active (ACTGA).
1327
Obtaining Attd UID fails
Call to trunk under attendant control (Attendant
Control of Trunk Group Active (ACTGA)). Failure
getting attendant User ID from dpm.
1328
Term to ACTGA Attd fails
Call to trunk under attendant control (Attendant
Control of Trunk Group Active (ACTGA)). Failure
terminating caller to controlling attendant.
1329
Term to inappropriate pt
Block termination to incoming-only type trunk or
user with voice bearer termination to a DEXT
group.
1330
Iterative term attd-retry
Call termination failure rerouting to attendant.
Retry of termination to attendant was blocked to
prevent an endless retry.
1331
Italian misoperation
Italian misoperation treatment.
Event Data 2
3 of 33
Issue 1 June 2005
195
Denial Events
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1332
Data mod options qry fail
Reserving a pooled modem. Query data module
for its options failed.
1333
Term to modem failure
Seizing (terminating on) a pooled modem failed.
1334
Term to modem failure
Analog endpoint termination to pooled modem
(after administrable time delay expires) failed.
1335
LWC blocked by msg_sv
Leave Word Calling. Async message response
from msg_sv says give user LW_INTRCPT.
1336
Tone detection timeout
Tone detector timeout without receiving a valid
tone.
1337
Intrcpt tone from far end
Intercept tone received before far end answers.
1338
Wait for answer timeout
Wait answer supervision was timedout on a call
from a station or tie trunk.
1339
Auth code required
Digit analysis and routing problem. Authorization
code required.
1340
Rmt cfwd invald local ext
The attendant activated call forwarding for a
remote extension to an invalid local extension.
1341
Non-voice call intercept
Non-voice call was routed to attendant or
announcement for intercept treatment. Switch to
intercept tone treatment.
1342
Dest BCC incompatible
The destination bearer capability code is
incompatible.
1343
Need higher FRL to route
A higher Facility Restriction Level is needed to
route the call.
1344
Hop count restricted
The outgoing call is hop count restricted.
1345
Multiparty caller paging
Accessing paging equipment with more than 1
party on the call is not allowed.
1346
Svc Obsrv from wireless
Service observing is not possible from wireless
stations because they don’t support “off-hook
idle” state.
1347
Svc Obsrv dpm query fail
Query of dpm to see if Feature Access Code
service observing is optioned failed.
1348
No Fac Svc Observing
Feature Access Code service observing is not
optioned.
1349
Term dial-up tst brdg app
Feature Access Code entered to do terminal
dial-up test, not allowed on bridged appearances.
1350
Term dial-up tst term typ
Terminal dial-up test is not allowed 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 expected
Appending number to end of digit buffer. All digits
have been processed for an Adjunct Switch
Application Interface (ASAI) originated call, but
more digits are expected to be collected.
Event
Data 1
Event Data 2
4 of 33
196 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1352
Port ntwk numbr too large
Facility access test specified a port network
number greater than the maximum allowed
(MAX_PPNS).
1353
Cabinet number too large
Malicious call trace specified a cabinet number
greater than the maximum allowed
(MAX_PPNS).
1354
SSC dialed ext's uid fail
Station Security Code (SSC) digit processing.
The dialed extension’s User ID has lost its
association with the extension number.
1355
Auth code reqired. (ASAI)
Call requires an authorization code. Call is an
Adjunct Switch Application Interface (ASAI)
phantom call. Not allowed.
1356
ASAI SCC VDN destination
The first leg of an Adjunct Switch Application
Interface (ASAI) Switch Classified Call (SCC) has
Vector Directory Number as destination.
1357
LAGT COR/COR restriction
There is a COR-to-COR (Class of Restriction)
between the originating logical agent and
terminating facility.
1358
ASAI SCC term loginID
Adjunct Switch Application Interface (ASAI)
Switch Classified Call (SCC) first leg attempting
to terminate to logical agent loginID. Not allowed.
1359
LoginID extensn qry fail
gm_query failure determining if the loginID
extension used for the Direct Agent call is
associated with a logged-in agent.
1360
ASAI SCC term loginID
Adjunct Switch Application Interface (ASAI)
Switch Classified Call (SCC) first leg attempting
to terminate to logical agent loginID. Not allowed.
1361
Page data call preindictd
Paging is denied if data call preindication was
activated.
1362
FAC follows priority FAC
Priority feature activation code shouldn’t be
followed by other feature activation codes. (auth)
1363
FAC follows priority FAC
Priority feature activation code shouldn’t be
followed by other feature activation codes. (route)
1364
FAC follows priority FAC
Priority feature activation code shouldn’t be
followed by other feature activation codes. (other)
1365
More digits needed to rte
Adjunct Switch Application Interface (ASAI) call.
DPM says it needs more digits to route on. There
are no digits left to use in the preprocessing
buffer, and no more digits are expected.
1366
BCC incompatibility
Being called from auth_code(). DPM says digit
analysis is done and we have Bearer Capability
Class (BCC) incompatibility.
1367
BCC incompatibility
Not being called from auth_code(). DPM says
digit analysis is done and we have Bearer
Capability Class (BCC) incompatibility.
Event Data 2
5 of 33
Issue 1 June 2005
197
Denial Events
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1368
MFC out dialing timeout
outgoing MultiFrequency Compelled call under
outpulse supervision. Interdigit or end-of-dialing
timeout without any expectation of user
completing dialing.
1369
Dgt tmout PCOL merge fail
Unexpected digit timeout. Drop of principal finds
that it is a Personal Central Office Line (PCOL)
group User ID. Merge of PCOL member(s) into
the call (pcol_merge()) for disposition via
stndseq() fails.
1370
Digit timeout - drop fail
Unexpected digit timeout. Drop of non-Personal
Central Office Line (PCOL)-type principal failure.
1371
Abbrv Dial DAC limit
Abbreviated Dialing was already dial accessed.
There is a limit of 3 times that the DAC can be
dialed to get digits to route on. This would seem
to have a purpose of preventing looping via
entries in the abbreviated dial lists.
1372
Abbrv Dial list/entry inv
Abbreviated Dialing. Invalid list and/or list entry.
1373
Abbrv Dial software fail
Abbreviated Dialing. Software error while getting
the digits stored in user’s abbreviated dial list.
1374
Agent skills enabled qry
Error while querying system parameters to see if
Expert Agent Selection (EAS) agent skills is
enabled.
1375
Dbl agent login to statn
Agent is logging into a physical station that
already has an agent logged in.
1376
Agent login illegl source
Trunk user or Remote Access user trying to do
Expert Agent Selection (EAS) agent login
operation. Not allowed.
1377
Last ACD call skill qry
Query of UM for last Automatic Call Distribution
(ACD) call’s skill fails. Query of attendant, hunt,
DEXT, paging or Personal Central Office Line
(PCOL) group or Non Call Associated-Temporary
Signaling Connection (NCA-TSC) user
1378
No hunt grp for split idx
Split group index from dialed digits is a
non-existent hunt group number.
1379
Agent logout fail (auto?)
Agent logout failure. Might be spl_chk.c. logging
out while auto-available.
1380
Agent login failure
Agent login failure getting number of digits in
logical agents password. Might be login-id User
ID was not found in dpm extension table Ext_e, or
an invalid logical agent login-id extension.
1381
Agent login failure
Agent logging into MCH split already logged in
logging into adjunct controlled split?
1382
agent login invalid/error
Login invalid or error condition.
Event
Data 1
Event Data 2
6 of 33
198 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1383
Agent login failure/error
Logical Agent (LAGT) failure getting 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'd
Maximum number of simultaneous logins
exceeded or ACPT_LOGIN failed.
1385
Agent passwd digits fail
Failure getting logical agent password digits from
DPM.
1386
Agent passwd mismatch
Agent entered password does not match
administered password.
1387
Agent login invalid/error
Login invalid or error condition.
1388
Login acceptance fails
Logical Agent login processing of ACPT_LOGIN
message to the la_spl_chk routine fails.
1389
Agent login max/error
Maximum number of simultaneous logins
exceeded, or this agent failed the login digits
check (for example, this agent is using someone
else’s login-id).
1390
Work mode change failed
Change of Agent Work Mode to after-call-work
failed.
1391
Work mode change failed
Change of Logical Agent Work Mode to aux-work
failed.
1392
Work mode change failed
Change of Agent Work Mode to man_in failed.
1393
Work mode change failed
Change of Agent Work Mode to auto-in failed.
1394
Agent feat act FAC error
Unrecognized Feature Access Code being
processed for Automatic Call Distribution (ACD)
agent feature activation.
1395
Agent sup assist rqst er
Agent requesting supervisor assist. Possible
causes:
● split group invalid
● agent not logged in
● split group has no supervisor
● administered
1396
Split invalid/agent login
Adjunct Switch Application Interface (ASAI)
requesting supervisor assist. Possible causes:
● split group invalid
● agent not logged in
1397
Direct agent call setup
Supervisor assisted call to Expert Agent
Selection (EAS) login ID. Error encountered in
setting up Direct Agent Call.
1398
Direct agent calling COR
Supervisor assisted call to Expert Agent
Selection (EAS) login ID. Direct agent calling
Class of Restriction (COR) check failure.
Event Data 2
7 of 33
Issue 1 June 2005
199
Denial Events
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1399
EAS not enabled
Activating Add/Remove Skill feature but Expert
Agent Selection (EAS) is not enabled.
1400
EAS not enabled
Activating Add/Remove Skill feature but Expert
Agent Selection (EAS) is not enabled.
1401
COR_AR_SKL query failure
Activating Add/Remove Skill feature
COR_AR_SKL dpm_query failed. User ID
structure not found.
1402
Skills COR restricted
Activating Add/Remove Skill feature. User has no
Class of Restriction (COR) permission to Add/
Remove Agent Skills.
1403
Console prmsn, EAS agent
Activating Add/Remove Skill feature. User has no
console permission and is not an Expert Agent
Selection (EAS) Agent. Activator is wrong type.
1404
LoginID prompt setup err
Activating Add/Remove Skill feature. Error in
setting up the prompt for agent’s loginID.
1405
Skills prompt setup err
Setting up prompting for skill number in the Add/
Remove Skills feature. Error in setting up prompt
for agent’s skills.
1406
LoginID tenant nbr fail
Add agent. Skills translations failed to get the
Tenant Number for the agent’s loginID.
1407
Skills tenant nbr fail
Add agent Skills translations. Failed to get the
Tenant Number for the agent’s skill.
1408
Tenant number mismatch
Add agent Skills translations. Tenant Number of
the Expert Agent Selection (EAS) agent’s loginID
does not match the Tenant Number of the skill
being added.
1409
Skill level out of range
Add agent Skills translations. Skill level out of
range.
1410
DAC skill nbr qry failed
Remove agent Skills translations. dpm_query for
Logical Agent’s (LAGT) DAC skill number failed.
1411
DAC skill not removable
Remove agent Skills translations. Logical agent’s
DAC skill is not removable.
1412
Skills ftr msg failure
Add/Remove agent Skills translations. Add/
Remove Skills feature message sending to
station server failed. (SS_AR_SKL)
1413
DAC agent dest/split
Adjunct Switch Application Interface (ASAI) third
party direct agent call. Process CP_DIR_AGENT
message from ISG. No DAC agent destination or
split specified in message.
1414
DAC agent dgts to uid
Adjunct Switch Application Interface (ASAI) third
party direct agent call. Process CP_DIR_AGENT
message from ISG. DAC agent digits conversion
to User ID. failure.
Event
Data 1
Event Data 2
8 of 33
200 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1415
DAC msg err/agent login
Adjunct Switch Application Interface (ASAI) third
party direct agent call. process CP_DIR_AGENT
message from ISG. 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 fail
Collecting authorization code digits as end-to-end
signaling failed.
1417
TTR queueing invalid
Collecting authorization code digits. “TTR
queueing occurred in remote access” is indicated
in Touch Tone Receiver (TTR) of callr - not valid
in this routine.
1418
Bsy vfy trk member
Error on query for busy status. Possible causes:
trunk member specified greater than maximum
trunks in group, or corrupted trunk index after a
tape read.
1419
COS restrctn Rus Intrsn
User’s Class of Service does not allow access to
Russian Power Trunk Intrusion feature.
1420
Bsy vfy call merge fail
Merging the busy-verifying call with the
busy-verified call. Failure to find an available
callr2 party slot.
1421
Bsy vfy termination fail
Terminating the busy-verifying call to a trunk.
Failure to find an available caller party slot.
1422
Bsy vfy termination fail
Terminating the busy-verifying call to a trunk.
Error getting the trunk’s index into the tmem_tbl
1423
Software invalid stim
Remote user activation/deactivation of a type of
attendant call forwarding - stimulus other than
CP_ACFON, CP_ACFBDAON or CP_ACFOFF
received.
1424
Cfwd dest dgts storage
Activation of call forwarding. Call forward
destination address digits did not all get stored.
1425
Cfwd actvt error/denial
Activation of call forwarding. Error or denial of
activation.
1426
Off prem extension size
Request remote switch to activate 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 extension nbr
Activating call forwarding. Feature button IDs
forwarded party extension number for which we
cannot find a user ID.
1428
Phys ext not cfwd avail
Logged-in Expert Agent Selection (EAS) agent’s
physical extension is unavailable for any “simple”
(on switch?) call- forwarding.
Event Data 2
9 of 33
Issue 1 June 2005
201
Denial Events
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1429
Rmte cfwd not allowed
Disallow remote call-forwarding of 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 activate
User’s Class of Service does not allow this call
forwarding activation.
1431
Cfwd deact not allowed
Expert Agent Selection (EAS) agents are not
permitted to deactivate call forwarding.
1432
Cfwd deact err/denial
Deactivation of call forwarding. Error or denial of
deactivation.
1433
Held xfr call missing
Converse Data Return requires that there be a
call held due to transfer while processing the
Converse Data return code (CONV_DAT_RET).
1434
Held call retrieval fail
Converse Data Return processing 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 typ/pty
Converse Data Return processing encountered
an invalid vector step type (not V_CONVERSE)
or the party is invalid.
1436
No COS for ctl rstrctn
User Class of Service does not allow activation/
deactivation of controlled restrictions.
1437
Sys parm - dir call pkup
Directed-call-pickup system parameter is not
enabled.
1438
Invalid usr dir call pkup
Directed call pickup attempt from invalid user (for
example, not a station or attendant).
1439
Dir call pkup COR rsrtrct
Directed call pickup attempt from user without
Class of Restriction (COR) permission.
1440
Dir call pkup non-station
Directed call pickup attempt on a call to an
endpoint other than a station.
1441
Dir call pkup COR rsrtrct
Directed call pickup attempt to a station that has
no Class of Restriction (COR) permission to
accept directed call pickup.
1442
Ring check query failure
Directed call pickup attempt. Failure of UM query
to see if called station is still ringing before
completing the pickup to it.
1443
COS deny dat pvcy ftr act
User’s Class of Service does not allow activation
of the data privacy feature.
1444
DS0 test call invalid
DS0 test call is valid only for incoming data trunk
calls.
1445
Rmt emrg accs to attd dny
Emergency access call to attendant is not
permitted from a remote user.
1446
Port ID/UID mapping fail
Facilities Access Test call. Trunk or Touch Tone
Receiver (TTR) port_id->User ID mapping failed.
Event
Data 1
Event Data 2
10 of 33
202 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1447
TTR port type query fail
Facilities Access Test call - Touch Tone Receiver
(TTR) test. CM query for TTR port type fails.
1448
Tested not trunk or TTR
Facilities Access Test call - user type being tested
is neither a trunk or Touch Tone Receiver (TTR),
but logic that got us here thought it was.
1449
Vis Imprd Svc incompatibl
Facilities Access Test call - this feature is not
compatible with Visually Impaired Service.
1450
FAT call error
Facilities Access Test call. Possible causes:
● CM 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 portid to User ID mapping
failed.
1451
Connection to music error
Facilities Access Test call to a music port. CM
error connecting to music.
1452
FAT non-ISDN COR rstrct
Facilities Access Test (FAT) call to a trunk. User
is Class of Restriction (COR) restricted from
making a FAT test of the non-ISDN trunk.
1453
FAT test RLT/DID illegal
Facilities Access Test (FAT) call to a trunk. FAT is
allowed for this trunk type, Release Link Trunk
(RLT) or Direct Inward Dialing (DID).
1454
Trk svc state change fail
Facilities Access Test call to a trunk. Failure
moving trunk from out-of-service state to
in-service. Might be a bad User ID.
1455
FarEnd TstLn nbr qry fail
Facilities Access Test call to a PRI trunk. GM
query for far end ISDN test line number failed
(QTC_NUM).
1456
FarEnd TstLn nbr invalid
Facilities Access Test call to a PRI trunk. Invalid
digit in far end test line number.
1457
FarEnd TstLn nbr invalid
Facilities Access Test call to a PRI trunk. Invalid
digit in far end test line number.
1458
Wrg Bch svc/usg/mnt state
Facilities Access Test (FAT) call 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. Might be a
bad User ID.
1460
Trk grp qry/get TAC
Facilities Access Test call to a trunk. um_query
failure getting trunk’s group User ID
(QTRKGRPUID)? dpm_dgtget() failure getting
trunk group’s “real” dial access code.
1461
User Cverage path missing
User activating Send All Calls does 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.
Event Data 2
11 of 33
Issue 1 June 2005
203
Denial Events
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1462
Split group digits wrong
User activating/deactivating Position Busy.
Wrong number of digits used to specify split
group.
1463
Agent denied in split group
Agent deactivating Position Busy, not allowed in
split group.
1464
Agent not in aux work
Agent not in AUX_WORK activating Position
Busy.
1465
SAC unavail to attd
Send All Calls (SAC) or Position Busy feature
activation/deactivation denied (for example,
attendant is not allowed to activate/deactivate
SAC).
1466
No call to xfr to AUDIX
Route transferred or call conferenced to AUDIX.
There is no held call that would be transferred/
conferenced in with AUDIX.
1467
No call to xfr to AUDIX
Route transferred or call conferenced to AUDIX,
but the calling party was disconnected.
1468
Inelgbl invoker xfr AUDIX
Route transferred or conferenced call to AUDIX.
Only the principal or covering user (or bridges of
them) are allowed to invoke this feature.
1469
Invld remote ADX mach-nbr
Route remote transfer to AUDIX. Failure getting
the remote principal’s AUDIX Machine number.
1470
No ADX mach-nbr/
node-name
Route remote transfer to AUDIX. The remote
principals AUDIX Machine number does not
translate into an adjunct index. (QAX_ADJ_IDX)
1471
Invalid AUDIX mach-nbr
Route remote transfer to AUDIX. The remote
principal’s AUDIX Machine number received is
“0”. dpm query for user’s serving AUDIX index
fails.
1472
Invalid AUDIX mach-nbr
Route remote transfer to AUDIX. The remote
principal’s AUDIX Machine number received is
“0”. dpm query for user’s serving AUDIX index
received “0”. Query of grp_m for the first AUDIX
whose DCS link is up fails.
1473
No local AUDIX mach-nbr
route local transfer to AUDIX. the local principals
AUDIX Machine number received is “0”. dpm
query for user’s serving AUDIX index fails.
1474
No primary AUDIX hnt grp
Route transfer to AUDIX. Query for an AUDIX.
Adjunct’s Primary Transfer into AX Hunt Group
failed.
1475
No ADX hnt grp-cvg path
Route local non-vector transfer to AUDIX. AUDIX
hunt group is not in the principal’s coverage path.
1476
Dat pvcy/rstrct ICOM call
User with data privacy or data restriction is trying
to originate an ICOM call. This is not allowed.
1477
Invalid ICOM grp/dial cod
ICOM call handling. Invalid ICOM group or ICOM
dial code of terminating station. (icm_route())
Event
Data 1
Event Data 2
12 of 33
204 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1478
Block iteratve Lst Nbr Dl
Last Number Dialed was accessed through an
Abbreviated Dialing list. Do not allow it again.
1479
LND digits - DPM fail
User’s Last Number Dialed (LND) digits were not
returned successfully by dial plan manager.
(DPM_LND)
1480
LND digits - DPM fail
User’s Last Number Dialed (LND) digits were not
returned successfully by dial plan manager.
(software error)
1481
MASI setup not incmg ISDN
Multimedia Application Server Interface (MASI)
path setup call - valid only for incoming ISDN
calls.
1482
MCT on DCS trk disallowed
User activating Malicious Call Trace for a DCS
trunk not allowed.
1483
MCT target type invalid
Malicious Call Trace target cannot be a group
User ID. Target PORT entered, must be a regular
TRUNK port or PRI.
1484
MCT target not in a call
Malicious Call Trace target must actually be
involved in a call.
1485
MCT call serv_d rtrv fail
Malicious Call Trace cannot retrieve callr from
serv-d for the call being traced.
1486
MCT trace resorce unavail
Malicious Call Trace activation by button could
not get trace resources from GRP_M.
1487
MCT start invld ctlr alrt
Malicious Call Trace start invalid controller
alerting return code from GRP_M (mct_start()).
1488
MCT deact dny by GRP_M/er
Malicious Call Trace deactivation (not via
busyout) denied by GRP_M or error. (mct_end())
1489
MCT activator grp uid/uid
Malicious Call Trace activation failure getting
individual User ID from activator group User ID.
1490
MCT activator COR rstrctd
Malicious Call Trace (MCT) activation. Activator’s
Class of Restriction (COR) does not allow MCT
feature access.
1491
Trk ext/int ID cnvsn fail
Malicious Call Trace request targeted to a trunk
port ID. Failure converting the external ID
(cabinet, carrier, slot, circuit) into an internal ID
(angel, circuit). (dig23dportid() - ATM,
dig2portid()).
1492
MCT act on trk pt ID fail
Malicious Call Trace request targeted to a trunk
port ID. failure activating MCT for given trunk pt
ID.
1493
AD prg from non station
Abbreviated dialing programming is messaging
the station server to enter a different mode and
prepare for digit collection. Only simple users
allowed. Wrong user type.
1494
Extension/passwd required
Coverage message retrieval. Remote access not
allowed unless the user supplies the extension
and password.
Event Data 2
13 of 33
Issue 1 June 2005
205
Denial Events
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1495
Local only/annc dest/uid
Announcement record/playback 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/conn fail
Begin integrated announcement session.
Integrated announcement not identified
(ann_sess()). cm_pt_conn failure or invalid Caller
ID root (au_sbegin()).
1497
Restricted by COS
User’s Class of Service does not 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 failure
MultiMedia Call Handling multimedia call
activation from voice station. Notification of
USER_M failed.
1499
MM failure getting BCC
MultiMedia Call Handling multimedia call
activation from voice station button. Failure
getting bearer capability from USER_M.
1500
Ext nbr or page typ invld
Failure getting Code Call paging ID
corresponding to dialed extension. Invalid
extension number or page type.
1501
Page call park failure
Drop paging equipment, start park timer, and park
call permanently. There is no record in callr of a
call having been parked during a page.
1502
Drop software failure
Paging zone seizure denied. gm_drop() problem
returned other than GDRP_OK, GDRP_ANS, or
GDRP_OUT.
1503
Answer back merge failure
Answer parked call, give confirmation tone to
parked party, merge 2 calls. Have no call record
of party originating answer back.
1504
Answer back merge failure
Answer parked call, give confirmation tone to
parked party, merge 2 calls. No call parked on
this extension.
1505
Answer back merge failure
Answer parked call, give confirmation tone to
parked party, merge 2 calls. Unknown return from
GRP_M retrieval of Caller ID of the parked call.
1506
Answer back merge failure
Answer parked call, give confirmation tone to
parked party, merge 2 calls. Unknown return from
GRP_M unpark of call if the last party drops.
1507
Answer back merge failure
Answer parked call, give confirmation tone to
parked party, merge 2 calls. Accessing the callr of
the parked call failed retrieval from serv-d.
Event
Data 1
Event Data 2
14 of 33
206 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1508
Unparking vec ctrld call
Answer parked call, give 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 dialed
Answer parked call, give confirmation tone to
parked party, merge 2 calls. User ID of station
dialed for answer back differs from park_uid in
call_r.
1510
COR/COR user restricted
Answer parked call, give confirmation tone to
parked party, merge 2 calls. COR-to-COR (Class
of Restriction) between user where call is parked
and users in answer back callr.
1511
Parked call already dropd
Answer parked call, give 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 to merge
Answer parked call, give confirmation tone to
parked party, merge 2 calls. The merge is not
possible because cannot find an empty slot in
callr2.
1513
Park call on station only
Trying to park a call on a non-station type user.
must park on a user with a SMPL group type.
1514
No call to park
There is no conference pending. The caller to be
parked must have dropped or been dropped.
1515
Park ftr serv_d failure
Failure encountered releasing the callr to serv_d.
1516
Park ftr serv_d failure
Failure encountered retrieving the callr from
serv_d.
1517
Park ftr serv_d failure
Failure encountered retrieving the callr from
serv_d.
1518
Too many park conferees
Too many conferees in the call to allow parking.
1519
Vector active cant park
Vectoring is active on the held call. Cannot allow
the held call to be parked.
1520
Park ftr serv_d failure
Failure encountered releasing the callr to serv_d.
1521
Park ftr serv_d failure
Failure encountered retrieving the callr from
serv_d.
1522
TAAS from guest room
Pickup for Call Pickup or Trunk 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 mbr
Pickup for Call Pickup or Trunk Answer Any
Station (TAAS). Pickup initiator is not a member
of a pickup group.
1524
Picked up call ID error
Pickup for Call Pickup or Trunk Answer Any
Station (TAAS). Error encountered getting call ID
of call to be picked up.
Event Data 2
fail code
(for example,
DPXFR_DENY
_9)
15 of 33
Issue 1 June 2005
207
Denial Events
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1525
Call pickup from adjnct
Pickup for Call Pickup or Trunk Answer Any
Station (TAAS). Pickup of call originated by an
adjunct is not allowed.
1526
Pickup of call wait call
Pickup for Call Pickup. Pickup of a call waiting
call is not allowed.
1527
Pickup of converse call
Pickup for Call Pickup or Trunk 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 call
Stations A and B are in same pickup 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 rstrct
Pickup for Call Pickup or Trunk Answer Any
Station (TAAS). COR-to-COR (Class of
Restriction) restriction between the initiator of
pickup and user(s) of the call being picked up.
1530
Priority call COS denied
Caller’s Class of Service does not allow initiation
of priority calling treatment of call.
1531
Priority call COS denied
Caller pushes the priority calling button after the
call has been dialed, but before it is answered.
Caller’s Class of Service does not allow initiation
of priority calling treatment of call.
1532
Passwd storage exhausted
Dual Tone MultiFrequency (DTMF) password
collection for audio add-on party in VSP-MCU
passworded conference. No room in opls_dig to
store conference password - should never
happen.
1533
Invalid TTR queueing type
Dual Tone MultiFrequency (DTMF) password
collection for audio add-on party in VSP-MCU
passworded conference. Touch Tone Receiver
(TTR) queing type in callr has invalid indication
whether or where TTR queing occurred.
1534
Software invalid stim
Performing the callback of a party after the call
has been queued. Invalid Call Processing (CP)
message being processed and passed from a
call supervisor.
1535
ACB held call dropped
Analog station flashooks and dials 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 error
GQSRV_ERR error returned from gm_qsrvc().
1537
Callback type sftw error
Invalid callback type returned by gm_query().
1538
Auto callback COS denied
User’s Class of Service does not allow activation
of Automatic Callback feature.
1539
Callback type qry failed
gm_query() for callback type failed.
Event
Data 1
Event Data 2
fail code
(for example,
DPXFR_DENY
_9)
16 of 33
208 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1540
Callback type qry failed
Invalid callback type returned by gm_query().
1541
Invalid call ID/conn fail
Switch has answered remote access call. Set up
end-to-end signaling digit collection. Invalid
Caller ID or Touch Tone Receiver (TTR)
connection failure. (tu_ecoll_dg(), bch_ecoll_dg()
-).
1542
TTR queueing error
Switch answered a remote access call. Set up
end-to-end signaling digit collection. Touch Tone
Receiver (TTR) queueing erroneously occurred
in auth_feat().
1543
Telcmt accss ext qry fail
Switch answered a remote access call and set up
end-to-end signaling digit collection. Failure
querying DPM for User ID of telecommuting
access extension.
1544
Barrier/auth cod qry fail
Switch answered a remote access call and set up
end-to-end signaling digit collection. Invalid
response from DPM on query for whether barrier
code and authorization code are needed.
(dpm_remqry())
1545
Acct code length qry fail
Query of DPM for SMDR account code length
failed.
1546
Held call serv_d failure
Handle T120 requests for a video conference.
Accessing the callr of the held call failed retrieval
from serv-d.
1547
Video conf deact flag er
T120 request for deactivation of video
conference, but the call has no indication that a
video conference exists. (mm_dataconf_on)
1548
Dat drop not frm dat orig
T120 request for deactivation of 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 failure
CM failure on T120 drop request from valid user
with T120 on.
1550
T120 activate CM failure
CM failure on Feature Access Code dialed
request for T120 activation.
1551
Invalid test tone specfd
Terminating trunk transmission test call. Invalid
test tone specified for connection to the call.
1552
Whisp pg elgblity qry err
Query of GRP_M for whisper page eligibility
encountered an error or the response was
invalid.
1553
Whisp pg too many parties
Activate whisper page answer ftr. callr party block
has no slot available for the page originator.
1554
Whisp pg ansr merge fail
Activate whisper page answer ftr. switch of the
Caller ID of the paging party from the original call
failed (um_wpswap())
1555
Whisp pg too many parties
Merging the paging call with the paged call. callr2
party block has no slot available for the merged
call.
Event Data 2
17 of 33
Issue 1 June 2005
209
Denial Events
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1556
Annc/music connect fail
Wakeup announcement verification. Failure of
the CM to connect a wakeup announcement or
music to the call.
1557
Wakeup annc vfy COS deny
Call originator does not have Class of Service
permission to verify wakeup announcements.
1558
Maid status PMS msg fail
Sending the PMA_MDSTATUS message to the
PMS failed.
1559
Maid status ext COS deny
Maid status Feature Access Code dialed from a
room station that does not have Class of Service
permission.
1560
Maid info digits qry fail
Query of DPM for number of maid info digits
failed.
1561
Maid status PMS msg fail
Send of a PMA_MDSTATUS message to the
PMS failed.
1562
Maid status ext COS deny
Maid status Feature Access Code dialed from a
designated station that does not have Class of
Service permission.
1563
Maid status ftr ID invld
Processes the dialed maid status code, but callr
feat_id is invalid for either maid status dialed from
a guest room or from a designated station.
1564
PMS rejects hskp status
Property Management System rejects
housekeeping status v.
1565
PMS hskp response invalid
Property Management System response to
housekeeping status is invalid. (CP_MDRES)
1566
Guest rm station COS deny
Routing call to Property 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 qry fail
Routing call to Property Management System to
log or obtain guest room status. Query of DPM for
number of maid information digits failed.
1568
Maid status PMS msg fail
Routing call to Property Management System
(PMS) to log or obtain guest room status. Send of
a PMA_MDSTATUS message to the PMS failed.
1569
Voice msg type call_r flg
Digit timeout waiting for entry of Do Not Disturb
turn-off time or entry of Automatic Wakeup time.
callr does not have this flagged as a Voice
message type call (vtype).
1570 (also
in Table 49)
TTR insertion failed
Processing incoming digits for ISDN call.
Insertion of Touch Tone Receiver (TTR) to collect
in-band digits failed.
1571
WSS no callng pty nbr IE
Processing incoming digits for ISDN call. A
General Central Office (GCO) Wireless
Subscriber System (WSS) call origination denied
- no calling party number IE was sent.
Event
Data 1
Event Data 2
18 of 33
210 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1572
Call hndlng/usg alloc err
Processing incoming digits for ISDN call.Eerror
during Incoming Call Handling Treatment or
Usage allocation Check (GM_ISDNDIG).
1573 (also
in Table 49)
Principal is not ISDN
Get called digits, calling number and name, etc.,
and send ISDN SETUP message to the far end.
The principal is not ISDN.
1574
SETUP msg IEs not created
Get called digits, calling number and name, etc.,
and send ISDN SETUP message to the far end.
IEs necessary for SETUP not created and stored
in the IAP.
1575
SETUP msg send failed
Get called digits, calling number and name, etc.,
and send ISDN SETUP message to the far end.
The “send” failed. (trk_setup(), um_setup())
1576
ISDN routing failure
Get called digits, calling number and name, etc.,
and send ISDN SETUP message to the far end.
Routing failure. (gm_routepat())
1577
ISDN SETUP msg failure
ISDN trunk group Trunk Access Code dialed or
simulated Q931_REC IEs set up and stored in
iap, and request send of SETUP msg. cp_setup()
returned a failure error.code. suser_m got a
failure indication from the gip in trying to send the
ISDN SETUP message?
1578
Inc tst call 2many partys
Incoming test call for talk/listen on same timeslot.
Failure to find an available callr party slot.
1579
Inc tst call wrg usr type
Incoming test call for talk/listen on same timeslot.
This type of test call is not permitted to access
the user type.
1580
Must be ISDN trunk group
Check for usage allocation restrictions on
incoming overlap receiving calls. Possible
causes:
● not ISDN trunk group
● insane index into the call by call data
table
● get_tmem() failure from GRP_M
usage_chk()
● Unexpected error from inc_cuap_sf()
1581
Passwd digits err/timeout
MCU audio add-on password 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/feat_id wron
Generating intercept via CP_REORDER with sup
= ACT_TTI_SUP (for Terminal Translation
Initiation digit collection) and feat_id !=
CHG_SEC (Change station security code).
Possible causes:
● wrong supervisory state
● wrong feat_id in callr
Event Data 2
19 of 33
Issue 1 June 2005
211
Denial Events
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1583
Spvsr state/feat_id wrong
Generating intercept via CP_CONFTONE with
sup = ACT_TTI_SUP (for Terminal Translation
Initiation digit collection) and feat_id !=
CHG_SEC (Change station security code).
Possible causes:
● wrong supervisory state
● wrong feat_id in callr
1584
Software invalid stim
Software error. Invalid Call Processing (CP)
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 digit
Invalid digit detected while processing
abbreviated dialing.
1586
Abbrev dial prg rejected
Rejection of abbreviated dialing programming
from station server.
1587
Agent extension invalid
Add/Remove Agent Skills. Feature 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 illegal
Add/Remove Agent Skills feature has been
invoked and the Skill number has been collected.
It does not represent a legal skill group number.
1589
Skill number invalid
Add/Remove Agent Skills feature has been
invoked and the Skill number is not valid.
1590
System or software error
Add/Remove Agent Skills feature has been
invoked. STN_SV encountered system or
software error.
1591
Digit collection error
Add/Remove Agent Skills feature has been
invoked. Error in digit collection.
1592
Routing not to a station
QSIG Call Completion ringout call from remote
originating party. Routing erroneously to a local
facility that is not an SMPL station.
1593
Digit tmo/invld rsn code
Interdigit timeout or invalid reason code entered
during Expert Agent Selection (EAS) aux work
and logout reason code digit collection is in
progress.
1594
Software invalid stim
Code Call paging seizure supervision received a
Call Processing (CP) stimulus from one of a big
list of incompatible feature CP stimulus.
1595
Cfwd tenant parttn rstrct
Attendant-activation of call forwarding, and
extended administration of call forwarding. Error
or access denial resulted from TENANT_CHECK
where originator’s partition is restricted from
accessing partition of extension being
administered for call forwarding.
Event
Data 1
Event Data 2
20 of 33
212 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1596
Attd must enter station
Attendant-activation of call forwarding, and
extended administration of call forwarding. The
extension being administered is not a simple
station user.
1597
Attd cant fwd attd calls
Attendant-activation of call forwarding, and
extended administration of call forwarding.
Attendant is not allowed to forward its own calls.
1598
Feature ID invalid
Attendant-activation of call forwarding, and
extended administration of call forwarding. The
feature ID in callr feat_id is wrong for the Call
Processing (CP) stimulus being processed by
this supervisor.
1599
Change cvg COR restricted
Attendant-activation of call forwarding, and
extended administration of call forwarding.
Change coverage Feature Access Code was
dialed. Class of Restriction (COR) of dialed
extension does not permit change coverage.
1600
Software error
Attendant-activation of call forwarding, and
extended administration of call forwarding.
CP_REJECT - partial perch write in station server
to administer the new active coverage option
failed.
1601
Software invalid stim
Attendant-activation of call forwarding, and
extended administration of call forwarding. Invalid
Call Processing (CP) stimulus type sent to this
supervisor.
1602
Cfwd act to paging grp NA
Call forwarding supervision. Activating call
forwarding to a paging group is not allowed.
1603
Cfwd offnet COS restrcted
Call forwarding supervision. Activating call
forwarding off-net is not allowed for this user.
check the Class of Service permissions.
1604
Cfwd offnet COS restrcted
Call forwarding supervision. Activating call
forwarding off-net via AAR/ARS is not allowed for
this user. Check the Class of Service
permissions.
1605
Cfwd to self denied
Call forwarding supervision. Call forwarding to
self is prevented.
1606
Software error
Call forwarding supervision. Invalid feedback
message type received with CP_FEEDBK type
stimulus to this supervisor from dap function.
1607
Software invalid stim
Call forwarding supervision. invalid Call
Processing (CP) stimulus type sent to this
supervisor.
1608
Routing not to data user
The “routed to” party is not a Data User.
1609
Local rtg must be to sta
QSIG Call Completion ringout call from the
remote originating party. Routing locally, but not
to a station. This is not allowed.
1610
Party count not = 1
Prepare to collect deluxe paging & park
extension. The callr pty_cnt is not = 1.
Event Data 2
21 of 33
Issue 1 June 2005
213
Denial Events
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1611
Not MM station/chnl busy
Sending down the MultiMedia Call Handling
Basic mode activation message to the User
Manager fails. Possible causes:
● station not part of Multi-media
● data user busy on at least one channel.
1612
Svc link creation failure
Sending down the MultiMedia Call Handling
Enhanced mode deactivation message to the
User Manager fails. Might be the creation of a
service link failed.
1613
BCC query failed
MultiMedia Call Handling multinumber type call.
Query of USER_M for bearer capability failed.
1614
Ctrl rstrct/DND fail
Controlled restriction activation/ deactivation, with
possible interaction with do-not-disturb. Failure
return from (dpm_crstrict() or awu_cancel()).
1615
Rstrct typ/featid/usr id
Initial processing supervision for controlled
restriction. Possible causes:
● originator’s User ID not found in
DP_MGR User ID data tables
● restriction digit does not identify with
outward, total, termination or
station-to-station type restriction
● featid is not one of:
- activate user control restriction
- deactivate user control restriction
- activate group control restriction
- deactivate group control restriction
1616
Ctrl rstrct featid bad
Initial processing supervision for controlled
restriction. Might be featid is not one of:
● activate user control restriction
● deactivate user control restriction
● activate group control restriction
● deactivate group control restriction
1617
Dialing tmo/invalid digit
Supervisor for Logical Agents is logging in by
dialing LoginID digits, dialing timeout occurs or
an invalid digit is dialed.
1618
Paging timeout
Loudspeaker paging seizure supervision. Might
be a paging timeout.
1619
LWC access cod dgt invld
Supervision for Leave Word Calling access code.
Processing invalid digit dialed.
1620
LWC access code rejected
Supervision for Leave Word Calling access code.
Processing msg_sv rejects code.
1621
Software invalid stim
Invalid Call Processing (CP) message stimulus’d
to Malicious Call Trace supervisor.
1622
BCC selection digit invld
Supervision for multimedia parameter selection.
Invalid digit dialed for selecting bearer capability
for call.
1623
MM parm select failure
Supervision for multimedia parameter selection.
error returned from gm_ftr_act().
Event
Data 1
Event Data 2
22 of 33
214 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1624
Backward tone absent tmo
Trunk outpulsing supervision. Outgoing backward
tone absent timeout on MultiFrequency
Compelled digit sending.
1625
7 min tmo - no tone rcvd
Trunk outpulsing supervision. 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.
1626
MFC trk seize failure
Trunk seizure supervision on outgoing trunks.
MultiFrequency Compelled trunk seizure failure.
1627
Out trk seize dgt invld
Trunk seizure supervision on outgoing trunks.
1628
7 min tmo - no tone rcvd
Trunk seizure supervision on 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 tone rcvd
Supervision when there is a tone 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 invld dg
Queued call or anticipated manually queued call
sees CP_INVDGT from somewhere.
1631
Rmt ACB ftr act timeout
Queued call or anticipated manually queued call
sees timeout waiting for remote drop by activator
of Automatic Call Back feature.
1632
PASTE enbl/rstrct/usrtyp
Possible causes:
● 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
● (su_ok4paste()) COR restricted for
PASTE
1633
Digit tmo/list nbr invld
Inter-digit timeout or invalid list number entered
during PC Application Software Exchange
(PASTE) display list number collection.
1634
Software invalid stim
Supervision after position busy (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 fail
Refresh Terminal Parameters supervision. The
query to get the extension type failed.
Event Data 2
23 of 33
Issue 1 June 2005
215
Denial Events
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1636
Not a downloadable set
Refresh Terminal Parameters 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.
1637
Wrt prot/maxd/annc bd
Supervision for announcement record/playback
session processing. Integrated announcement
session instruction message sent to GRP_M.
Possible causes:
● announcement is write/delete protected
● invalid feat_type or not the same Caller
ID that is in the session
● CM port connection failure
● invalid Caller ID root (au_sbegin())
● CM port disconnect failure
● CM port listen failure
● no announcement board
● maximum number of announcements
already recorded
1638
Record playback reject
Supervision for announcement record/playback
session processing. CP_REJECT stimulus
received from somewhere.
1639
Permanent seizure
Standard action stimulus processing. Non-Direct
Inward Dialing trunk origination. Digit timeout with
no digits dialed. The permanent incoming seizure
treatment is to give intercept.
1640
Permanent seizure
Standard action stimulus processing. Italian
external tie (TGU) call. Digit timeout with no digits
dialed. The permanent incoming seizure
treatment is to give intercept.
1641
Permanent seizure
Standard action stimulus processing. Trunk group
type other than: DID, IN_TIE, EX_TIE, TAN_TIE,
ACCESS, IN_APLT,EX_APLT, ISDN_PRI, or
DIOD. Digit timeout with no digits dialed. The
permanent incoming seizure treatment is to give
intercept.
1642
Ofhk alrt tmo intvl admin
Standard action stimulus processing. Station,
attendant or analog adjunct data extension
originator. Off-hook alert feature activation. No
off-hook alert timeout interval administered.
(OHK_ALERT)
1643
Off-hook dialing time out
Standard action stimulus 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 CP_DG_TMO for Line Intercept Tone timer.
1644
Orig block/invalid digits
Standard action stimulus processing. originator
group type not trunk, DEXT, SMPL(station), or
attendant? DEXT, SMPL, ATTD does not Class of
Service allow off-hook alert and NOT processing
a CP_DG_TMO for Line Intercept Tone timer.
1645
Talk state MFC trk fail
MultiFrequency Compelled trunk failure after the
call is the talking state. (CP_MFCINTRCPT)
Event
Data 1
Event Data 2
24 of 33
216 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1646
No act call_ap/sftw err
One-button transfer to data feature activation
failed. Possible causes:
● No active call appearance
● Call id passed from call_p to su_obt() is
not on the active call appearance
1647
Telcomtr diald illegl FAC
Supervisor for telecommuting access.
Telecommuting extension was accessed, then a
Feature Access Code was dialed that is not
allowed to telecommute.
1648
Ctrl rstrct VDN extension
Supervision for controlled restriction of user.
Control Restriction Activation/Deactivation for a
Vector Directory Number extension is not
allowed.
1649
Ctrl rstrct locl ext only
Supervision for controlled restriction of user.
Control Restriction Activation/ Deactivation must
be on an extension that is local to the switch.
1650
Rstrct typ/featid/COR/sta
Supervision for controlled restriction of user.
Possible causes:
● Originator’s User ID not found in
DP_MGR User ID data tables
● Restriction digit does not identify with
outward, total, termination or
station-to-station type restriction
● Featid 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 fail
Station server could not perform Terminal
Translation Initiation (TTI) merge/unmerge.
1652
LWC access cod dgt invld
Voice synthesis Leave Word Calling access code
digit processing saw an invalid digit or msg_sv,
rejected the request.
1653
TTI - attd not allowed
Terminal Translation Initiation (TTI) unmerge
operation is not allowed from attendants.
1654
TTI - attd not allowed
Personal Station Access (PSA) associate
operation cannot be originated by attendant.
1655
TTI - BRI not allowed
Personal Station Access (PSA) associate
operation cannot be originated by BRI station.
1656
Other calls active/COS
Personal Station Access (PSA) associate
operation. If not on a Terminal Translation
Initiation (TTI) port, check the Class of Service.
Deny if possible. Also check for other calls active
on the station.
1657
TTI - attd not allowed
Personal Station Access (PSA) disassociate
operation cannot be originated by attendant.
Event Data 2
25 of 33
Issue 1 June 2005
217
Denial Events
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1658
TTI - BRI not allowed
Cannot Personal Station Access (PSA)
disassociate a BRI station.
1659
TTI - COS restricted
Class of Service does not allow Personal Station
Access (PSA) disassociate operation.
1660
TTI - BRI not allowed
Cannot Personal Station Access (PSA) associate
a BRI station.
1661
TTI - COS restricted
Class of Service of the extension to be
associated does not have Personal Station
Access (PSA) capability.
1662
Crossing tenant partition
Personal Station Access (PSA) associate
operation cannot cross tenant partitions.
1663
Invalid user ID/sftw err
Personal Station Access (PSA) associate
operation. There is no extension associated with
user ID. Invalid User ID or software error.
1664
Getting user ID failed
Failure getting the User ID for the extension
dialed in an association/ dissociation step.
1665
Data mod usr id qry fail
Data Terminal Translation Initiation (TTI) call. The
query for the real User ID of data module in dext
group failed.
1666
Originator ext not dialed
Unmerge sequence initiated, and the extension
dialed must be the same as the originator’s.
1667
Non trunk intercept
Proper intercept treatment for non DID/TIE/ISDN
trunk groups, or non-trunk originators.
1668
Trk needs disc supervisn
Activate service observing feature. Service
observing cannot be activated by a trunk without
disconnect supervision.
1669
Svc obsrv from attd NA
Activate service observing feature. Service
observing cannot be activated by an attendant.
1670
Svc obsrv from brdg NA
Activate service observing feature.Service
observing cannot be activated from a bridged
appearance.
1671
Svc obsrvg svc obsrvd NA
Activate service observing feature.Service
observing cannot be activated by a user that is
already a service observer or is being service
observed.
1672
Svc obsrvr/obsrvd COR dny
Activate service observing feature. Activating
user’s Class of Restriction (COR) does not allow
it to be a service observer of intended observed.
1673
Svc obsrvr COR rstrct
Activate service observing feature. Activator’s
Class of Restriction (COR) check failed.
1674
Svc obsrvr/obsrvd COR dny
Activate service observing feature. Activating
user’s Class of Restriction (COR) does not allow
it to be a service observer of intended observed.
Event
Data 1
Event Data 2
1
26 of 33
218 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1675
Svc obsrvr vecstep/extdgt
Activate service observing feature. 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 ext/VDN
Validation of service observed extension. Service
observing is allowed only on a simple User ID or
a Vector Directory Number.
1677
Svc obsrv cust opt qry
Validation of service observed extension. Query
for service observing customer-options failed.
1678
Need VDN obsrvg option
Validation of service observed extension. Vector
Directory Number observing is not enabled.
1679
Svc obsrvee data rstrctd
Validation of service observed extension.
Observee is data restricted.
1680
Svc obsrvg svc obsrvd
Validation of service observed extension.
Non-Vector Directory Number observee is
already being observed, or is an observer.
1681
Svc obsrvee COR rstricted
Validation of service observed extension. Class
of Restriction (COR) of observee does not allow
being observed.
1682
Svc obsrvd COR chk fail
Validation of service observed extension. Class
of Restriction (COR) check failure.
1683
Svc obsrvr/obsrvd COR dny
Validation of service observed extension.
Observer/observee Class of Restrictions do not
allow observer to observe observee.
1684
Svc obsrvg/obsrvg race
Validation of service observed extension. The
observee is already in the process of activating
service observing for another party.
1685
Svc obsrv ftr act failure
Validation of service observed extension. Feature
activation of selected “listen only” or “listen/talk”
service observing failed.
1686
Svc obsrv VDN SO wait flg
Supervision after confirmation tone to a service
observer. DPM failure to set Vector Directory
Number (VDN) Service Observing wait flag in the
VDN’s VDN information block.
1687
Obsrvr conf_state unclear
Supervision after confirmation tone 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 race
Supervision after confirmation 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 fail
Supervision after confirmation tone to a service
observer. Failure activating service observing for
observee.
Event Data 2
27 of 33
Issue 1 June 2005
219
Denial Events
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1690
Software invalid stim
Supervision after confirmation tone to a service
observer. Invalid Call Processing (CP) stimulus
received by this supervisor.
1691
Term restriction chk fail
Processing incoming Call Forwarding. All
Distributed Communication System (DCS)
message. Other switch had problem processing
CF_ACT message. Termination restriction check
failed or could not convert designated extension
to a user ID.
1692
LWCpmsn/UDPext/dpst
admin
Leave Word Calling (LWC) operations generates
INT_DRP. Possible causes:
● attendant cannot leave DCS messages
because of eDIM, S85
● lw_nocall() activator of lwc store does
not have lwc permission
● activator is not a udp ext
● lwc_store() lw_rmstore()- DCS LWC - no
remote users involved
● lwc store operation remote to localVoice 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/sftw err
Italian Direct Inward Dial (DID) trunk group drop
treatment. Possible causes:
● DID origination on outgoing trunk
● Invalid return code from gm_orig()?
● Software error?
1694
Sta intrcpt tone fwd disc
Station Intercept Tone Forward Disconnect.
1695
Bsy vfy sta/trk/hnt grp
Cannot busy verify attendants.
1696
Bsy vfy trk grp no mbr
Busy verify of trunk failure. Possible causes:
● No trunk in the group
● Trunk group member not found
1697
Bsy vfy access endpt trk
Busy verification not supported for access
endpoint trunk type.
1698
Bsy vfy hnt grp no mbr
Busy verify of hunt group failure. Might be there is
no member in the hunt group.
1699
LWC msg stor fail (conf)
Leave Word Calling message cannot be stored
when there is a conference call.
1700
LWC msg - no destination
No destination determined for Leave Word
Calling message store.
1701
Whisp pg not to station
Whisper page allowed only to simple station
group type of user.
1702
Whisp pg query fail
Whisper paging - shouldn’t see this - sim_quer/
su_query don’t develop GQRY_INVALID
response to qtype QWHISP_PG
Event
Data 1
Event Data 2
28 of 33
220 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1703
Whisp pg query fail
Whisper paging - shouldn’t see this - sim_quer/
su_query don’t develop GQRY_AE response to
qtype QWHISP_PG
1704
Whisp pg usr not allowed
Whisper paging. User is not allowed to make
whisper pages.
1705
Whisp pg query fail
Whisper paging. QWHISP_PG type gm_query
failed.
1706
Wake up typ/voice actvat
VIP and DAILY type wakeup cannot be modified
or deleted via voice-activated process.
1707
No attd to rcv wakeup
Voice synthesizer is not available. Routing
automatic wakeup call to attendant, but no
attendant. (TN725).
1708
No attd to rcv wakeup
Voice synthesizer not available. Routing
automatic wakeup call to attendant, but no
attendant. (TN725).
1709
Bsy vfy term is PCOL
Busy verify is denied, the principal terminator is
Personal Central Office Line (PCOL).
1710
Bsy vfy is term rstrctd
Busy verify is termination restricted.
1711
Bsy vfy dgt invalid/tmo
While collecting digits for busy verification,
supervisor got an indication of invalid digit or digit
timeout.
1712
Ofhk alrt tmo intvl admin
Standard action stimulus 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 invalid/tmo
While collecting trunk member number digits for
busy verification, supervisor got an indication of
invalid digit or digit timeout.
1714
Whisp pg term is PCOL
Whisper page feature activated, principal
terminator is Personal Central Office Line
(PCOL).
1715
Whisp pg is term rstrctd
Whisper page feature activated, whisper page is
termination restricted.
1716
Software invalid stim
Whisper page feature activated, whisper page
supervisor saw an invalid Call Processing (CP)
stimulus while collecting station digits.
1717
Self Sta Display denial
Self Station Disp feature activated, either
activated from a bridged appearance or GRP_M
denial.
1718
Grp call pkup not enabled
Group Call pickup is not enabled.
1719
Invalid dgts collected
Invalid digits are collected in dgt_egpkup().
1720
QSIG VM-no simple uid
Could not obtain simple user User ID for an SS-B
ISDN trunk.
Event Data 2
29 of 33
Issue 1 June 2005
221
Denial Events
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
1721
QSIG VM-no remote user id
Received a Voicemail Number MSI but did not
receive an original diverting number.
1722
QSIG VM-prin not smpl uid
The local principal User ID is not a simple user
User ID.
1723
QSIG VM-no voicemail nbr
Do not know the number of the voicemail adjunct,
the call cannot transfer to the adjunct.
1724
Annc Record Session Fail
Announcement record session was denied by the
board.
1725
QSIG VM-hunt not in cvg p
Principal does not have a QSIG MWI (Message
Waiting Indicator) hunt group in its coverage
path.
1726
Cant get Smpl Attd-uid
Cannot get simple attendant User ID.
1727
cannot use PASTE
Station restriction is total, cannot use PC
Application Software Exchange (PASTE).
1728
Deny PE originated calls
PE already active on call.
1729
Direct Agent call failed
Direct Agent Call failed.
1730
Trk-grp uid retrieve fail
All failed to retrieve Release Link Trunk (RLT)
trunk group User ID for Centralized Attendant
Service (CAS).
1731
I/C call on O/G Trunk
Incoming call on outgoing trunk.
1732
Caller COR Restricted
Caller Class of Restriction (COR) restricted
access.
1733
Conference 2 Attendants
Cannot conference 2 attendants.
1734
Max Pub Net Trks on conf
Maximum number of Public Network Trunks on
conference.
1735
Max conf parties w/PNTrks
Maximum number of conference parties with
Public Network Trunks.
1736
Max conf parties wo/PNTrk
Maximum number of conference parties without
Public Network Trunks.
1737
Max conf/xfer parties
Maximum number of conference or transfer
parties.
1738
Conf/xfer unstable calls
Cannot conference or transfer unstable calls.
1739
Div Reroute/Path Replace
Cannot transfer Diversion Rerouting or Path
Replacement call.
1740
No Disconnect Supervision
Cannot transfer, no disconnect control party.
1741
Transfer trunk to trunk
Cannot transfer trunk to trunk.
1742
Conf/xfer Whisper Page
Cannot conference or transfer whisper page.
1743
cnf/xfr Emergency/Wakeup
Cannot conference or transfer emergency or
wakeup call.
Event
Data 1
Event Data 2
UID
board’s reason
for denial.
30 of 33
222 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1744
Conf/xfer a tone
Cannot conference or transfer tone.
1745
Conf/xfer Announcements
Cannot conference or transfer with multiple
announcements.
1746
Conf/xfer a Vector call
Cannot conference or transfer vector call.
1747
Cnf/xfr Service Observers
Cannot conference or transfer two service
observers.
1748
Conf/xfer a Page call
Cannot conference or transfer group or
loudspeaker page call.
1749
No Disconnect Supervision
Cannot route call, no disconnect control party.
1750
FRL too low to route call
Cannot route the call, Facility Restriction Level is
too low.
1751
No AAR/ARS route pat/pref
No route pattern or preference translated.
1752
Conf with no ISDN connect
Conference when ISDN connect message has
not been sent due to SA8434.
1753
Caller cvgpt COR restrict
Remote/caller cannot terminate to coverage point
due to Class of Restriction (COR) setting.
1754
Caller cvgpt COR restrict
Remote/caller cannot terminate to coverage point
due to Class of Restriction (COR) setting.
1755
Caller cvgpt COR restrict
Remote caller cannot terminate to coverage point
due to Class of Restriction (COR) setting.
1756
Caller fwdto COR restrict
Remote/caller cannot terminate forwarded to
party, Class of Restriction (COR) setting.
1757
Attd release COR restrict
Attendant cannot release call, Class of
Restriction (COR) setting.
1758
Attd release link failure
Attendant cannot release call, link restriction.
1759
Attd hold COR restrict
Attendant cannot release call, Class of
Restriction (COR) setting.
1760
Conference COR restrict
Controller cannot conference call, Class of
Restriction (COR) setting.
1761
Transfer COR restrict
Controller cannot transfer call, Class of
Restriction (COR) setting.
1762
Transfer no pooled modem
Controller cannot transfer call, no pooled modem.
1763
Cnf/xfr Intercept Anncmt
Attempt to transfer/conference an intercept
announcement.
1764
Btn Ring Control timeout
Button ring control activated via Feature Access
Code & time out has occurred. SA8428
1765
Invalid button pushed
Invalid button pushed in button ring control mode.
SA8428
1766
Remote Logout Agent fail
no info available
Event Data 2
fail code
31 of 33
Issue 1 June 2005
223
Denial Events
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
Event Data 2
1767
Rmt Logout COR restricted
no info available
1768
Rmt Logout COS restricted
no info available
1769
Rmt Logout invalid input
no info available
1770
Rmt Logout tenant number
no info available
1771
Rmt Logout cant do self
no info available
1772
PSA on Virt EXT disallow
Personal Station Access (PSA) associate/
disassociate not allowed for virtual extension.
1773
Cnf/xfr Atd Intcpt Ann
Attempt to transfer an intercept announcement at
the attendant.
1774
Stn Lock act/deact failed
Station lock activation or deactivation failed.
1775
No adm for SBS extensions
Separation of Bearer and Signaling (SBS) call
tried to allocate an SBS extension, but none was
administered.
1776
Can't send SBS # to orig
Separation of Bearer and Signaling (SBS) call
tried to send back an INFO message with the
SBS complete public number, but the INFO could
not be sent. Check proper administration of
isdn-pub-unk form.
1777
Calling Pty COR chk fail
Error occurred when retrieving Class of
Restriction (COR) of calling party.
1778
Orig COR/Auth COR dny
Calling party Class of Restriction (COR) not
allowed to use mapped COR from authorization
code entry.
1779
FIPN RO when call on hold
Fujitsu Intelligent Priva Network (FIPN -a Fujitsu
ISDN Protocol spec) route optimization denial.
There is call on hold. SA8506
1780
AAR/ARS fac not
administered
ARS/ARR Feature Access Code is not
administered.
1781
Note: Error codes 1781 through 1791 apply to Feature Access Code invocations that are designed to operate on
contact closure relays on a G350 Media Gateway. These error codes apply only to Linux-based servers.
17811
CC: Improper COS
ARS/ARR Feature Access Code is not
administered.
17821
CC: Invalid digits
Invalid digits (or a symbol for a digit, etc.) entered
for contact-closure related operation on a G350
Media Gateway.
17831
CC: MG# out of range
Media gateway number is out-of-range.
17841
CC: software error
Contact-closure related operation had internal
software error, should never happen. First byte of
the seconds data item gives info to ID where
error occurred out of many places that it can
happen.
17851
CC: Invalid closure#
Contact-closure related operation had bad
closure number.
32 of 33
224 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 50: Call Process denial events (1225 - 1899) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
17861
CC: MG not administered
Contact-closure related operation had
unadministered media gateway number.
17871
CC: MG not registered
An unregistered media gateway was selected for
a contact-relay related operation on a G350
Media Gateway.
17881
CC: MG in link recovery
The G350 Media Gateway selected for a
contact-relay related operation was in link
recovery mode.
17891
CC: No CC on this MG type
The media gateway selected for a contact-relay
related operation does not have a contact relay.
17891
CC: MG not a G350 gateway
The media gateway selected for a contact-relay
related operation is not a G350.
17901
CC: Invalid button push
An invalid feature button was pushed after
invoking contact closure feature.
17911
CC: Trunk usr not allowed
Trunk access is not allowed for contact closure
feature.
1792
MI Chg Fail: Agt Burnout
Deny change to manual-in mode because the
agent is in burnout state.
1793
AI Chg Fail: Agt Burnout
Deny change to auto-in mode because the agent
is in burnout state.
1794
No STNHNT for Remote cvg.
Deny station hunt after coverage if the last
coverage party is remote.
1795
Caller FEAC restricted access.
Communication
Manager Re-
Event
Data 1
Event Data 2
lease 2.2
Communication
Manager
Release
2.2
17961899
not assigned
33 of 33
1. Error codes 1781 through 1791 apply to Feature Access Code invocations that are designed to operate on
contact closure relays on a G350 Media Gateway. These error codes apply only to Linux-based servers.
Issue 1 June 2005
225
Denial Events
User Manager Events
Event Types 1900 - 1906 show User Manager-generated denial events, as listed in User
Manager denial events (1900 - 1906) on page 226.
Table 51: User Manager denial events (1900 - 1906)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
1900
Invalid CFWD destination
CF_DEST digits do not map to station User ID.
1901
Control Restrn Check fail
Control Restriction.
1902
Enhanced Abbr List Failur
Enhanced Abbreviated Dialing entry length failed.
1903
LWC Button xln Error
Ignore Leave Word Calling button push due to bad translation.
1904
Override for the PGN disa
User not allowed to activate override for this partition
1905
Auto selection of DID dis
Automatic selection of Direct Inward Dialing numbers is disabled.
1906
SA8428 Btn Ring Ctl disab
SA8428 Station User Button Ring Control has been disabled,
ignore button-ring button push.
Event
Data 2
IP Denial Events
Event Types 1907 - 2079 show IP denial events, as listed in IP Denial Events (1907 - 2020) on
page 226.
Table 52: IP Denial Events (1907 - 2020)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1907
IP RRJ-Invalid RAS addr
IP Registration Rejected because the
RAS address in the registration request
(RRQ) is invalid.
0
IP address of
the endpoint
1908
IP RRJ-Invld call SigAddr
IP Registration Rejection because the call
signaling address in the registration
request (RRQ) is invalid.
0
IP address of
the endpoint
1 of 13
226 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 52: IP Denial Events (1907 - 2020) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1909
IP RRJ-RemoteOfc
misadmin
Registration rejected because:
0
IP address of
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 not enabled on
the Signaling Group screen.
● Remote Office is enabled on the
Signaling Group screen, but the
Terminal Type in the RRQ is not
valid (the Terminal Type is not a
gateway).
1910
IP RRJ-H323 UserObj undef
IP Registration rejected because there is
no H323 User Object.
0
IP address of
the endpoint
1911
IP RRJ-Exceed max endpts
IP Registration rejected because the
capacity for either registered endpoints,
registered Remote Office endpoints, or
registered un-authenticating endpoints is
exceeded. Check maximum allowed in
the system on page 1 of the System
Parameters Customer Options screen.
0
Upper part:
number of
registered RO
endpoints.
Lower part:
number of
registered IP
endpoints.
1912
IP RRJ-Exceed ProdID/Ver
IP Registration rejected because the
maximum number of registered endpoints
of a specific product ID and version is
exceeded. Check the limit on the
System-Parameters Customer-Options
screen.
Truncated
Product ID from
the SystemParameters
CustomerOptions screen
Upper part:
registered limit.
Lower part:
actual count.
1913
IP RRJ-Invalid ProdID/Ver
IP Registration rejected because of an
invalid Product ID / Version. Registering
Application's product ID is not
administered on the System-Parameters
Customer-Options screen or no Product
ID in registration request (RRQ)
message.
Truncated
Product ID of the
registering
application
Major version
number of the
endpoint sent in
the RRQ
1914
IP RRJ-ProdID search fail
IP Registration rejected because the
search for the registering application's
Product ID failed.
Truncated
Product ID of the
registering
application
Major version
number of the
endpoint sent in
the RRQ
1915
IP RRJ-Invalid endpt/Ver
Registration rejected because the
endpoint version is not compatible with
the gatekeeper version.
IP address of
endpoint
Endpoint’s
major version
number in 2nd
byte, minor
version number
in low byte
2 of 13
Issue 1 June 2005
227
Denial Events
Table 52: IP Denial Events (1907 - 2020) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1916
IP RRJ-No H323
NonStdData
Registration rejected because
Non-standard Data (NSD) is missing in
the registration request (RRQ) from the
endpoint.
0
IP address of
the endpoint
1917
IP RRJ-Invld H323 ObjID
Registration rejected because the H323
Object ID in the registration request
(RRQ) is invalid.
Object ID in
RRQ
IP address of
the endpoint
1918
IP RRJ-Invld H225 NSData
Registration rejected because cannot
decode H225 Non-standard Data (NSD)
message.
0
IP address of
the endpoint
1919
IP RRJ-Bad H225
NSDchoice
Registration rejected because an
unexpected Non-standard Data (NSD)
message was received from the
registering application.
NSD choice in
RRQ
IP address of
the endpoint
1920
IP GRJ-RRJ: new LM fail
Registration rejected because of failure in
creating a new Login Manager. Possible
causes are:
UID
IP address of
the endpoint
● No available heap memory to
create LoginMgr
● Cannot start LoginMgr timer
● Clock not set
1921
IP RRJ-IP-TTI port fail
Registration rejected because of failure
when inserting the IP Terminal
Translation Initiation (TTI) port.
UID
IP address of
the endpoint
1922
IP RRJ-TTI inactive
Registration rejected for an IP set with
Terminal Translation Initiation (TTI)
service. Possible causes:
0
IP address
0
IP address
IP address of the
endpoint
TTI state where:
0=TTI off
2=TTI on for
voice
3=TTI on for
data
Communication
Manager
● TTI is not enabled on the
Release
2.1 and
earlier
System Parameters Customer
Options screen.
● Remote Office is not enabled on
the System Parameters Feature
Options screen.
1922
IP RRJ-TTI or RO inactive
Communication
Manager
Registration rejected for an IP set with
Terminal Translation Initiation (TTI)
service. Possible causes:
● TTI is not enabled on the
Release
2.2
System-Parameters
Customer-Options screen.
● Remote Office is not enabled on
the Feature Related
System-Parameters screen.
1922
Communication
Manager
Release
3.0
IP RRJ-TTI or RO inactive
Registration rejected for an IP set with
Terminal Translation Initiation (TTI)
service. Possible cause is TTI is not
enabled on the System-Parameters
Customer-Options screen.
3 of 13
228 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 52: IP Denial Events (1907 - 2020) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1923
IP RRJ-No E164 number
Registration rejected because there is no
valid E.164 number in the RRQ or the
extension is not administered.
UID
IP address of
the endpoint
1924
IP RRJ-No GRQ msg rcvd
Registration rejected because no
Gatekeeper Request message was
received or RRQ was received more than
15 seconds after GRQ
UID
IP address of
the endpoint
1925
IGAR trunk routing failed
Registration rejected, denied while
routing an outgoing Inter-Gateway
Alternate Routing (IGAR) trunk call,
because of failure creating a new Login
Manager. Possible cause:
UID
IP address
● No available heap memory to
create LoginMgr
● Cannot start LoginMgr timer
● Clock not set
1926
IP RRJ-Authenticatn fail
Registration rejected because of
password authentication/ 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.
UID
IP address of
the endpoint
1927
IP RRJ-Invld station type
Registration rejected because of:
UID
station type or
IP address of
the endpoint
UID
station type or
IP address of
the endpoint
Communication
Manager
● Invalid station type
● No Remote Office or IP
Release
2.2 and
earlier
Softphone administration on the
station screen
● IP Softphone tried to register
shared-control to the wrong
telephone endpoint type.
1927
Communication
Manager
Release
3.0
IP RRJ-Invld station type
Registration rejected because of:
● Invalid station type for the
endpoint application
● R1 IP telephone
● R1 or R2 IP softphone in
roadWarrior or Telecommuter
mode
● IP console and not console
station type
● IP softphone and softphone not
set to yes on station screen
● IP telephone application and not
IP telephone station type
● Softphone that cannot operate
with a station type that does not
have a BIS or the speaker is
turned off
4 of 13
Issue 1 June 2005
229
Denial Events
Table 52: IP Denial Events (1907 - 2020) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1928
IP RRJ-StnTyp/Protocl err
Registration rejected because station
type and call-signaling protocol are
inconsistent. An IP Softphone should be
assigned as one of the following:
UID
Endpoint type
(3rd and 2nd
nyble); call
signaling
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 MMCmplx
Registration rejected: user record for
dual-connected DCP set is missing the
index for the multimedia complex.
UID
IP address of
the endpoint
1930
IP RRJ-No voice path spec
Registration rejected because the
endpoint (the virtual phone) has neither
an associated multimedia extension nor a
specified voice path, so no audio path
exists. Either:
UID
IP address of
the endpoint
UID
IP address of
the endpoint
Communication
Manager
Release
2.2 and
earlier
● Add a Media Complex extension
on the station screen
or
● Add an extension on the
softphone (register as a
telecommuter)
1930
IP RRJ-No voice path spec
Communication
Manager
Release
3.0
Registration rejected because the
endpoint (the virtual phone) has neither a
specified voice path for telecommuter
mode or is itself audio capable, so no
audio path exists.
● Add an extension on the
softphone (register as a
telecommuter)
1931
IP RRJ-H323 ext is
MMCmpx
Registration rejected because this H.323
extension is administered as a Media
Complex extension on a non-H.323 (for
example, a DCP) set.
UID
IP address of
the endpoint
1932
IP RRJ-Ext has data modl
Registration rejected because the
extension has a data module.
UID
IP address of
the endpoint
1933
IP RRJ-IP addr mismatch
Registration rejected because the H.323
application is not at the same IP address
as the authenticating application.
UID
IP address of
registering
endpoint
1934
IP RRJ-Ext already reg
Registration rejected because the
extension is already registered.
UID
IP address of
the endpoint
1935
IP RRJ-Not Remote Ofc ext
Registration rejected because Remote
Office is not administered on the station
screen for this extension.
UID
IP address of
the endpoint
5 of 13
230 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 52: IP Denial Events (1907 - 2020) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1936
IP RRJ-RO stn mismatch
Registration rejected because of invalid
analog station type.
UID
IP address of
the endpoint
IP RRJ-RO stn mismatch
Registration of Remote Office endpoint
rejected because set type on Remote
Office differs from set type on station
screen.
UID
IP address of
the endpoint
1937
IP RRJ-RemOfc not admin
Registration rejected because the
Remote Office is not administered on the
remote-office form
UID
IP address of
the endpoint
1938
IP RRJ-Immediate re-reg
Immediate re-registration is rejected
when a registration or unregistration is in
progress for the extension.
UID
IP address of
the endpoint
1939
IP RRJ-Failure moving ext
Registration rejected because of failure
while trying to force the unregistration of
an extension in the process of moving it
to another port.
UID
IP address of
the endpoint
1940
IP RRJ-Duplicate ext
Registration rejected as a duplicate
extension.
UID
IP address of
the endpoint
1941
IP KA-from invld endpt ID
Keep Alive registration request rejected
because of invalid endpoint identifier in
RRQ.
UID
IP address of
the endpoint
1942
IP KA-from unreg user
Keep Alive registration request rejected
because it was received from an
unregistered extension.
UID
IP address of
the endpoint
1943
IP-KA-from unreg SigGrp
Keep Alive registration request rejected
because it was received from an
unregistered signaling group.
UID
IP address of
the far-end
1944
IP RRJ-PSA merge failure
Registration rejected because the
Personal Station Access (PSA) merge
failed (internal software error). Check for
corruption
UID
IP address of
the endpoint
1945
IP RRJ-New IP user fail
Registration rejected because of failure to
construct new H323 User object (internal
software error).
0
IP address of
the endpoint
1946
IP RRJ-PSA merge failure
Registration rejected because the
LoginManager Personal Station Access
(PSA) merge operation failed (internal
software error). Check for corruption.
0
IP address of
the endpoint
1947
IP RRJ-PSA unmerge fail
Registration rejected because the
LoginManager Personal Station Access
(PSA) unmerge operation failed (internal
software error). Check for corruption.
UID
IP address of
the endpoint
Communication
Manager
Release
2.2 and
earlier
1936
Communication
Manager
Release
3.0
6 of 13
Issue 1 June 2005
231
Denial Events
Table 52: IP Denial Events (1907 - 2020) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1948
IP RRJ-Complete pend reg
Registration rejected because of failure to
obtain a station user record (internal
software error – corrupt translation).
UID
IP address of
the endpoint
1949
IP RRJ-Build KARCF msg
Registration rejected because of failure to
build a KeepAlive Registration Confirm
(KARCF) message (internal software
error).
0
IP address of
the endpoint
1950
IP RRJ-Build RCF msg
Registration rejected because of failure to
build a Registration Confirm (RCF)
message (internal software error).
0 or UID
IP address of
the endpoint
1951
IP GRJ-Invld IP addr/port
Gatekeeper request rejected because of
invalid destination IP address and port in
the request (GRQ).
0
IP address
1952
IP GRJ-Invld gatekeeperID
Gatekeeper request rejected because the
message is not for this gatekeeper.
Gatekeeper ID
IP address
1953
IP GRJ-Invld auth capblty
Gatekeeper request rejected because the
gatekeeper supports a capability that the
registering endpoint does not.
0
IP address of
the endpoint
1954
IP GRJ-Invld auth algrthm
Gatekeeper request rejected because no
compatible authentication algorithm
exists between the endpoint and the
gatekeeper.
0
IP address of
the endpoint
1955
(not
used in
IP GRJ-Bld GCF:Gatewy/
MCU
Gatekeeper request rejected because of
failure to build a GateKeeper Confirm
(GCF) message for a GateWay/MCU
(internal software error).
0
IP address
IP GRJ-Bld GCF:TTI
Gatekeeper request rejected because of
failure to build a GateKeeper Confirm
(GCF) message for an un-named
endpoint registration (internal software
error).
0
IP address
IP GRJ-GK will not host
Gatekeeper request rejected because the
gatekeeper is unwilling to host endpoint
because:
TTI state
IP address of
the endpoint
Communication
Manager
Release
3.0)
1956
(not
used in
Communication
Manager
Release
3.0
1957
Communication
Manager
Release
2.2 and
earlier
● no alias address has been
provided
or
● Terminal Translation Initiation
(TTI) is in incorrect state (for
example, TTI is not enabled for
voice)
7 of 13
232 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 52: IP Denial Events (1907 - 2020) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1957
IP GRJ-GK will not host
Gatekeeper request rejected because the
gatekeeper is unwilling to host endpoint
because no alias address has been
provided.
Endpoint type
sent in GRQ
IP address of
the endpoint
1958
IP GRJ-Invalid extension
Gatekeeper request rejected because the
extension is not administered.
Either extension
number or 0
IP address of
the endpoint
1959
IP GRJ-No stn user record
Gatekeeper request rejected because no
station user record exists for registering
this user (internal software error).
UID
IP address of
the endpoint
1960
IP FURQ-Shared Ctrl Unreg
Forced Unregistration Request: The
Gatekeeper is unregistering the IP
Softphone because it is in shared control
with IP Telephone, and the Telephone is
unregistering.
UID
IP address of IP
Softphone
1961
IP GRJ-Build GCF msg
Gatekeeper request rejected because of
failure to build a GateKeeper Confirm
(GCF) message (internal software error).
UID
IP address of
the endpoint
1962
IP LRJ-No H323 sig group
Location Request rejected because no
H.323 signaling group is administered to
handle the call.
UID
IP address of
the far-end
1963
IP LRJ-Build LCF msg
Location Request rejected because of
failure to build a Location Request
Confirm (LCF) message (internal
software error).
UID
IP address
1964
IP DRJ-Null UserID
Disengage Request rejected because the
endpoint ID could not be converted to a
User ID (UID).
UID
IP address
1965
IP DRJ-Bld DCF:Gatewy/
MCU
Disengage Request rejected because of
failure to build Disengage Request
Confirm (DCF) message for a gateway or
MCU (internal software error).
UID
IP address
1966
IP DRJ-Endpt not reg
Disengage Request rejected because the
endpoint is not registered.
UID
IP address
1967
IP DRJ-Build DCF msg
Disengage Request rejected because of
failure to build a Disengage Request
Confirm (DCF) message for a
non-gateway or MCU user (internal
software error).
UID
IP address
1968
IP BRJ-Null UserID
Bandwidth Request rejected because an
invalid endpoint ID was received.
0
IP address
1969
IP BRJ-Bld BCF:Gatewy/
MCU
Bandwidth Request rejected because of
failure to build a Bandwidth Request
Confirm (BCF) message for a Gateway or
MCU (internal software error).
UID
IP address
1970
IP BRJ-Endpt not reg
Bandwidth Request rejected because the
endpoint is not registered.
UID
IP address
Communication
Manager
Release
3.0
8 of 13
Issue 1 June 2005
233
Denial Events
Table 52: IP Denial Events (1907 - 2020) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1971
IP BRJ-Build BCF msg
Bandwidth Request rejected because of
failure to build a Bandwidth Request
Confirm (BCF) message for a
non-Gateway or MCU user (internal
software error).
UID
IP address
1972
IP BRJ-No H323 user
Bandwidth Request rejected because the
H.323 user object does not exist (internal
software error).
UID
IP address
1973
IP BRJ-Call non-existent
Bandwidth Request rejected because the
request is made for a non-existing call.
UID
IP address
1974
IP BRJ-Bandwdth rqst fail
Bandwidth Request rejected because of
unexpected return code from bandwidth
request.
UID
IP address
1975
IP ARJ-Null UserID
Admission Request rejected: received
invalid endpoint ID.
NIL UID
IP address
1976
IP ARJ-Endpt not reg
Admission Request rejected: the endpoint
is not registered.
UID
IP address
1977
IP ARJ-No avail B-channel
Admission Request rejected: no
B channel is available for the call.
UID
IP address
1978
IP ARJ-Bld ACF:Gatewy/
MCU
Admission Request rejected: because of
failure to build an Admission Request
Confirm (ACF) message for a Gateway or
MCU (internal software error).
UID
IP address
1979
IP ARJ-Not an H323 user
Admission Request rejected: request was
received from a non-H.323 user.
UID
IP address
1980
IP ARJ-Stn not in service
Admission Request rejected: station is
not in service.
UID
IP address
1981
IP ARJ-Build ACF msg
Admission Request rejected: failure to
build an Admission Request Confirm
(ACF) message for a non-Gateway or
MCU user (internal software error).
UID
IP address
1982
IP ARJ-No H323 user
Admission Request rejected: H.323 user
object does not exist (internal software
error).
UID
IP address
1983
IP ARJ-CRV already in use
Admission Request rejected: Call
Reference Value (CRV) is already in use
by another call.
UID
IP address
1984
IP ARJ-CRV does not exist
Admission Request rejected: this call
reference value (CRV) does not exist.
UID
IP address
1985
IP ARJ-CRV already in use
Admission Request rejected: Call
Reference Value (CRV) is already in use
by another call. An ARQ has been
received while an earlier one is still
pending.
UID
IP address
1986
IP ARJ-Insuff bandwidth
Admission Request rejected: insufficient
bandwidth available to support this call.
UID
IP address
9 of 13
234 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 52: IP Denial Events (1907 - 2020) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
1987
IP ARJ-Admissn rqst fail
Admission Request rejected: unexpected
return code from Admission Request
(internal software error).
UID
IP address
1988
IP URJ-Null UserID
Unregistration Request rejected: received
invalid endpoint ID.
0
IP address of
the endpoint
1989
IP URJ-Endpt not reg
Unregistration Request rejected: endpoint
is not registered.
UID
IP address of
the endpoint
1990
IP URJ-No endpoint ID
Unregistration Request rejected: no
endpoint ID provided in URQ.
0
IP address of
the endpoint
1991
IP URJ-GW/MCU is not reg
Unregistration Request rejected: URQ
received from a Gateway or MCU that is
not registered.
UID
IP address of
the far-end
1992
IP URJ-No H323 sig group
Unregistration Request rejected because
there is no H.323 user for the signaling
group (internal software error).
UID
IP address of
the far-end
1993
IP URJ-No non-std data
Unregistration Request rejected because
there is no non-standard data in the URQ.
UID
IP address of
the endpoint
1994
IP URJ-NSD has invld OID
Unregistration Request rejected because
the Non-standard Data (NSD) from the
registered application has an invalid
object ID in the URQ.
UID
IP address of
the endpoint
1995
IP URJ-Can’t decode NSD
Unregistration Request rejected because
of failure to decode Non-standard Data
(NSD) in the URQ.
UID
IP address of
the endpoint
1996
IP URJ-Unexpected NSD
msg
Unregistration Request rejected because
of unexpected Non-standard Data (NSD)
in the URQ from the registered endpoint.
UID
IP address of
the endpoint
1997
IP URJ-User is on a call
Unregistration Request rejected because
the user is on a call.
UID
IP address of
the endpoint
1998
IP URJ-PSA unmerge failed
Unregistration Request rejected because
the Personal Station Access (PSA)
unmerge operation failed (internal
software error). Check for corruption.
UID
IP address of
the endpoint
1999
IP URJ-PSA merge failed
Unregistration Request rejected because
the Personal Station Access (PSA) merge
operation failed (internal software error).
Check for corruption
UID
IP address of
the endpoint
2000
IP URJ-No stn user record
Unregistration Request rejected because
no station user record exists for
unregistering user (internal software
error).
UID
IP address of
the endpoint
2001
IP URJ-TTI op failed
Unregistration Request rejected because
of an unexpected Terminal Translation
Initiation (TTI) return code.
UID
IP address of
the endpoint
10 of 13
Issue 1 June 2005
235
Denial Events
Table 52: IP Denial Events (1907 - 2020) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2002
IP URJ-Build UCF msg
Unregistration Request rejected because
of failure to build an unregistration
request confirm (UCF) message (internal
software error).
0
IP address of
the endpoint
2003
IP URJ-PSA unmerge failed
Unregistration Request rejected because
the Personal Station Access (PSA)
unmerge operation failed (internal
software error). Check for corruption.
UID
IP address of
the endpoint
2004
IP URJ-No stn user record
Unregistration Request rejected because
the no station user record exists for the
unregistering user (internal software
error).
UID
IP address of
the endpoint
2005
IP URJ-PSA unmerge failed
Unregistration Request rejected because
the Personal Station Access (PSA)
unmerge operation failed (internal
software error).
UID
IP address of
the endpoint
2006
(not
used in
IP FURQ-no H.323 ext reg
Force Unregistration Request. Received
a KeepAlive request (RRQ) from a
dual-connect endpoint without a
registered H.323 extension (cannot make
calls). Re-register the endpoint.
UID
IP address
2007
IP FURQ-User, no sig conn
Force Unregistration Request. Unregister
user because there is no signaling
connection. RAS is alive, but the
signaling connection has gone down
(user cannot make calls). Re-register the
endpoint.
UID
IP address of
the endpoint
2008
IP FURQ-H323, no sig conn
Force Unregistration Request. Unregister
associated H.323 user because there is
no signaling connection. Re-register the
endpoint.
UID
IP address of
the endpoint
2009
IP FURQ-Move user
Force Unregistration Request. Extension
is already registered, but received a
forced login registration request (RRQ).
Send a URQ to the existing extension.
UID
IP address of
the endpoint
2010
IP FURQ-Sig Conn closed
Forced Unregistration Request. The
Gatekeeper is unregistering the endpoint
because its call signaling connection has
closed.
UID
0
2011
IP FURQ-NoQ931 msg rcvd
Force Unregistration Request. After an
endpoint registers it 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, so unregister it.
H.323 UID
IP address of
the endpoint
2012
IP FURQ-Aged Endpt-no KA
Force Unregistration Request. Unregister
endpoint that has aged out. Endpoint's
time to live (TTL) expired without
receiving a keep-alive request (RRQ).
UID
IP address of
the endpoint
Communication
Manager
Release
3.0)
11 of 13
236 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 52: IP Denial Events (1907 - 2020) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2013
IP FURQ-SigGrp removed
Force Unregistration Request. An H.323
Gateway (administered as a signaling
group) is registered. Unregister the
Gateway before removing the
administered signaling group.
Gateway UID
IP address of
the far-end
2014
IP FURQ-Siggrp changed
Force Unregistration Request. Changes
have been made to a registered H.323
Gateway (administered as a signaling
group). Unregister the Gateway.
Signaling group
IP address of
the near-end
2015
IP FURQ-Ext removed
Forced Unregistration Request.
Unregister user because the extension
has been removed.
UID
0
2016
(not
used in
IP FURQ-IPusr is sftphone
Forced Unregistration Request.
IP User-UID
0
● A user has Personal Station
Accessed (PSA) an extension
that was registered as an IP
endpoint.
Communication
Manager
Release
3.0)
● An IP telephone extension in
shared-control was moved to
another IP port via registration.
Both shared-control IP
Telephone and IP softphone will
unregister if the rejected
registration attempt is forced.
2017
IP FURQ-Records
exhausted
Forced Unregistration Request.
Unregister the LAN port if there are no
station user-records remaining.
IP User-UID
0
IP FURQ-Records
exhausted
Forced Unregistration Request.
Unregister the endpoint if there are no
station user-records remaining.
IP User-UID
0
2018
IP FURQ-Mtc: H323/Vphone
Forced Unregistration Request. The
release command was run on the
extension or port.
UID
0
2019
IP FURQ-Mtc: Remote Max
Forced Unregistration Request. The
release command was run on the
Remote Office extension or port.
UID
0
Communication
Manager
Release
2.2 and
earlier
2017
Communication
Manager
Release
3.0
12 of 13
Issue 1 June 2005
237
Denial Events
Table 52: IP Denial Events (1907 - 2020) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2020
IP FURQ-Mtc:RemOfc TTI
Forced Unregistration Request. Terminal
Translation Initiation (TTI) background
maintenance task has requested the
removal of Remote Office LAN TTI ports.
UID
0
IP FURQ-Mtc:RemOfc TTI
Forced Unregistration Request. Terminal
Translation Initiation (TTI) was turned off.
UID
0
Communication
Manager
Release
2.2 and
earlier
2020
Communication
Manager
Release
3.0
13 of 13
Call Process Denial Events
Event Types 2021 - 2299 show Call Process denial events, as listed in Call Process denial
events (2021 - 2299) on page 238.
Table 53: Call Process denial events (2021 - 2299)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2021
Cust Sel of DIDs inactive
Custom Selection of VIP Direct
Inward Dialing numbers feature is
not active.
2022
Annc pres but not admin
Announcement present but not
administered.
2023
Annc pres none on board
Announcement present but no
announcements administered for
the board.
2024
Cannot create entry
Registration rejected because
unable to create an entry in the
MTM complex table.
UID
IP address of the endpoint
2025
Unadministered option
Registration rejected because the
option chosen by the endpoint in
the RRQ for the emergency call
does not match the option
administered on the station form.
UID
IP address of the endpoint
2026
Xmobile OOS: block orig
Xmobile offhook request rejected
because Xmobile station has been
taken out of service.
1 of 9
238 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 53: Call Process denial events (2021 - 2299) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2027
Annc not found on board
User attempted to play
MO_VAL_BD announcement and
file was not found on board.
2028
Annc file has bad format
User attempted to play
MO_VAL_BD announcement and
file had bad format.
2029
IP GRJ-NSD has invld
OID
Gatekeeper Request rejected
because the Non Standard Data
(NSD) from the registered
application has an invalid object ID.
UID
IP address of the endpoint
2030
IP GRJ-Can't decode
NSD
Gatekeeper Request rejected
because of failure to decode Non
Standard Data (NSD) element.
UID
IP address of the endpoint
2031
IP GRJ-Unexpected NSD
msg
Gatekeeper Request rejected
because of unexpected Non
Standard Data (NSD) message
from the registered application
endpoint.
UID
IP address of the endpoint
2032
Force Unregistration Req
Force Unregistration Request.
Instruct the RAS manager to
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
Unregister
Force Unregistration Request. The
command to force unregister
endpoints has been executed from
the SAT.
User ID
IP address
IP FURQ-Demand
Unregister
Force Unregistration Request.
Reset ip-stations was executed
from the SAT to force unregister
endpoints.
NULL
NULL
2034
Illegal TSC interaction
A QSIG Non Call
Associated-Temporary Signaling
Connection (NCA-TSC) tried to
route out an AT&T TSC, or vice
versa, and this interaction is not
supported. This might occur when a
bsr_poll call over an IP trunk tries to
use a QSIG TSC but is tandemed
out an AT&T TSC.
2035
NCA-TSC not available
Possible causes:
● The terminated
administered 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
Communication
Manager
Release
2.2 and
earlier
2033
Communication
Manager
Release
3.0
2 of 9
Issue 1 June 2005
239
Denial Events
Table 53: Call Process denial events (2021 - 2299) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2036
Incoming QSIG LWC
failed
Leave Word Calling on the
incoming side of a QSIG_LWC MSI
CS0FAC message failed.
2037
QSIG LWC fail find voice
Getting the voice callr on the
outgoing side of a QSIG_LWC MSI
SETUP message failed.
2038
QSIG LWC fail get cling
Getting the calling party number
from the incoming side of the call
failed.
2039
IP KA-No endpoint ID
Keep Alive Registration Request.
Registration rejected because no
endpoint identifier was provided.
0
IP address
2040
IP GRJ-No CLAN
available
Gatekeeper Request rejected
because no resources available for
signaling connection.
UID
IP address
2041
IP RRJ-No DSP Resource
Registration Request rejected
because no Digital Signal
Processor (DSP) resources are
available.
UID
IP address
20422046
not assigned
2047
Reject-Unauthorized MG
Registration rejected because it
was received from unauthorized
media gateway.
2048
Reject-MGC not ready
Registration rejected because it is
not ready for a media gateway
re-registration.
2049
No VOIP Resource
VOIP Resources unavailable.
2050
No MG Resource
No gateway resource available.
2051
IP GRJ-RemOfc No Sig
Grp
Remote Office invalid request
(GRQ) No Sig Group available.
2052
IP RRJ-RemOfc No Sig
Grp
Remote Office invalid registration
request (RRQ) No Sig group
available.
2053
MG heartbeat missed
MGKeepAlive: Wakeup() media
gateway heartbeat missed,
indicates lack of traffic from
specified gateway.
2054
Signaling CONN
Congestion
UMSocket: SockWrite() Congestion
on the Signaling Link due to PCD
buffer exhaustion.
2055
Reset MG - Pkt Send Err
Reset the media gateway Signaling
Link due to error in Sending
packets.
3 of 9
240 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 53: Call Process denial events (2021 - 2299) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2056
No null caps SBS orig
end
IncomingMsg. Null caps not
received on originating end of
Separation of Bearer and Signaling
(SBS) trunk.
2057
No null caps SBS term
end
IncomingMsg. Null caps not
received on terminating end of
Separation of Bearer and Signaling
(SBS) trunk.
2058
Null caps on H323 trunk
IncomingMsg. Null caps received
on terminating end of H323 trunk.
2059
SecCode change
disallowed
Change of security code through
Feature Access Code not
supported for IP.
2060
SA8508:Off
Emergency access call to the
attendant using the 2nd access
code is not permitted because the
SA8508 is not optioned.
2061
Invalid Post msg dgt/tmo
Post message digit timeout.
2062
Post msg too many msg
dgt
Post message too many digits.
2063
Post msg not stn user
Post message not station user.
2064
IP RRJ-NSD encode
failed
Registration rejected because of
failure to encode Non-standard
Data (NSD) message.
UID
IP address
2065
IP RRJ-Invalid vendor id
Registration rejected because LSP
requesting registration has not sent
a valid vendor ID.
NULL
IP address
2066
IP RRJ-LSP obj not init
Registration rejected because the
LSP object has not been initialized.
NULL
IP address
2067
IP RRJ-NSD improper
OID
Registration rejected because the
Non-standard Data (NSD) sent by
the LSP contains an invalid OID.
NULL
IP address
2068
IP RRJ-Cannot decode
NSD
Registration rejected because of
failure to decode Non-standard
Data (NSD) message sent by the
LSP.
NULL
IP address
2069
IP RRJ-Unxpctd NSD
Registration rejected because of
receipt of an unexpected
Non-standard Data (NSD) message
from LSP.
NULL
IP address
2070
MG must send full reg
msg
Media gateway attempted
registration with “warm start”
condition, but the controller needs
“cold start” data.
2071
Serial Number incorrect
Media gateway attempted to
register with a different serial
number.
4 of 9
Issue 1 June 2005
241
Denial Events
Table 53: Call Process denial events (2021 - 2299) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2072
Conf/Transfer 2 Meet-me
Conference or transfer 2 Meet-me
conference call.
2073
Permission denied (or)
Download permission
deny
User attempted to download
firmware to a station. User does not
have console permission.
2074
Rec fail: annc is playing
Attempt to record a VAL
announcement while that
announcement is playing on a VAL
board.
2075
Var-in-Vec COS restricted
User does not have console
permissions
2076
IP RRJ-Call Mismatch
IP Registration Rejection (RRJ)
because of no call present on the
switch side. But there is a call
present on the ept.
UID
IP address.
2077
IP FURQ-CallTimer
Expired
Force Unregistration Request.
Unregister endpoint whose call
preservation timer (H323 link loss
delay timer) expires.
UID
IP address.
2078
Extend Call Button Denial
OPTIM Extend Call via extend call
button press was denied.
station where
the button
was pushed
Reason the call was denied:
0 - denied because the 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 state
Registration rejected because 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 dialed TSA
IP Softphone in shared control
configuration with DCP is forced
unregistered because user dialed
TSA.
2081
IP FURQ-Invld sta state
IP Softphone in shared control
configuration with DCP is forced
unregistered because softphone
switched to invalid state.
2082
Exceeded TLS conn limit
A TLS socket was rejected because
of the constraint on the maximum
number of TLS peers.
2083
TLS: No cert returned
A peer cert was rejected by
common name checking.
5 of 9
242 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 53: Call Process denial events (2021 - 2299) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
2084
TLS: Handshake Failure
Handshake failed, for example due
to no common cipher suite.
2085
TLS: Certificate expired
An expired certificate was returned
and rejected.
2086
SBS bearer Auth not
supp
If authorization code is 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
OutofSrv
Used to inform softphone trying to
register in shared control with an
out-of-service DCP endpoint to try
registration with LSP.
2088
Bad Record Max. For example, an
attacker does not have the correct
private key, which can go
undetected until the MAC of the
exchange is checked.
2089
Bad Record Max. For example, an
attacker does not have the correct
private key, which can go
undetected until the MAC of the
exchange is checked.
2090
TLS shutdown received. Listen
socket could not be created.
2091
Conf/xfer Audix rec
AUDIX one-step rec while conf.
2092
Post msg invalid SSC
Post message invalid Station
Security Code (SSC).
2093
Can't start
announcement
Cannot start announcement.
2094
TCP/IP sig socket failure
Establish a socket on an IP trunk.
The far end might be
mis-administered.
2095
Rmt Div-fwding ext local
QSIG Remote Diversion activation
for local extension not allowed.
2096
Rmt Div-SSC too long
QSIG Remote Diversion Station
Security Code (SSC) contains too
many digits.
2097
Rmt Div-non QSIG trunk
QSIG Remote Diversion is not
allowed over a non-QSIG trunk.
2098
Rmt Div-act ext not stn
QSIG Remote Diversion activation
only allowed from station user.
2099
Rmt Div-act/deact failed
QSIG Remote Diversion activation/
deactivation failed.
Event Data 1
Event Data 2
UID
IP address
IP address of
the far end to
which the call
failed
Port number of the far end
6 of 9
Issue 1 June 2005
243
Denial Events
Table 53: Call Process denial events (2021 - 2299) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2100
Rmt Div-QSIG VALU
disable
QSIG Remote Diversion is not
allowed over a QSIG trunk with
QSIG VALU disabled.
2101
Feat. requires only dgts
A feature was activated via a
request URI. The part of the request
URI string that should contain all
digits contained characters other
than digits.
2102
SIP Estab Timer expiry
SIP call establishment timer expired
prior to 200 OK (incoming or
outgoing call). Timer length is
administered on SIP sig-group
forms.
2103
Cannot ring add-in party
Attempt to add a party to a call
failed at the termination stage.
UID of the
party that was
attempting to
terminate
Cause value/feedback
indicating the reason.
2104
Cannot add party to call
Attempt to add a party to a call
failed at or after answer.
UID of the
party that was
being added
in
reason code:
1: internal failure (look for
proc_err around same time)
2: internal failure (look 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
6: internal failure (look for
proc_err around same time)
7: internal failure (look for
proc_err around same time)
2105
SCCAN handover denied
Seamless Converged
Communications Across Networks
(SCCAN) attempt to handover
failed.
UID of the
station
involved in
handover
reason for failure:
0: No call found to handover
to
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
7 of 9
244 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 53: Call Process denial events (2021 - 2299) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2106
SCCAN announcement
denied
Seamless Converged
Communications Across Networks
(SCCAN) attempt to handover
failed.
UID of the
station
involved in
handover
reason for failure:
0: Announcement not
administered on sys-param
sccan form
1+ - Feedback type
OPTIM SCCAN termination
was denied
1: WLAN call limit exceeded
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
2107
SCCAN call out blocked
OPTIM Seamless Converged
Communications Across Networks
(SCCAN) termination was denied
UID of the
station
involved
reason for denial:
1: WLAN call limit exceeded
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
denied
There are problems with Seamless
Converged Communications
Across Networks (SCCAN) notify
retransmission response.
UID of the
station
involved
reason for denial:
1:Could not get Event header
from request
2: Could not 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
2109
IP RRJ-Unknown
unnamed
Registration rejected because an
unnamed endpoint did not have the
terminal present bit set, or because
it did not supply Lucent vendor
information.
2110
Release btn push ignored
Agent pushed IM_ACD_REL button
simultaneously with call
termination.
UID of agent
pushing
IM_ACD_RE
L button
NULL
2111
IP RRJ-TTI reg not in map
Deny Terminal Translation Initiation
(TTI) registration, IP endpoint not in
ip-network-map.
IP address
TTI state
2112
IP RRJ-TTI reg shared ctl
Deny Terminal Translation Initiation
(TTI) registration, IP endpoint
requesting shared control.
IP address
TTI state
8 of 9
Issue 1 June 2005
245
Denial Events
Table 53: Call Process denial events (2021 - 2299) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event Data 1
Event Data 2
2113
IP RRJ-TTI incapable
Deny Terminal Translation Initiation
(TTI) registration, IP endpoint not
TTI capable.
IP address
TTI state
2114
IP RRJ-TTI reg eConsole
Deny Terminal Translation Initiation
(TTI) registration, request from IP
eConsole.
NULL
IP address.
2115
IP RRJ-RO addr no admin
Deny Terminal Translation Initiation
(TTI) registration, Remote Office
address not administered.
IP address
TTI state
2116
460.1 Neg failed in GRQ
460.1 feature not supported.
2117
Agent accept login error
Non-EAS ACD split agent accept
login failed
Agent UID
Caller ID
2118
ACD agent tot exceeds
max
Max number of ACD agents already
logged-in
UID
Logged-in ACD agent count
2119
Memb per skill exceeds
mx
Max number of agents already
logged-in to skill
Agent UID
Skill number
2120
Advocate agents exceed
mx
Max number of Business Advocate
agents already logged-in
Agent UID
Logged-in Business Advocate
Agent count
2121
Oth agt using this logid
Some other agent already using
this loginID
Agent UID
Split number
2122
This agt using oth logid
This agent already using some
other loginID
Agent UID
Split number
2123
BCMS logid val failed
BCMS (Basic Call Management
System) Login ID validation failed.
Agent UID
Split number
2124
Agent tot exceeds sys
max
Agent total exceeds system limit
Agent UID
Agent total
2125
Over CMS agent login
cap
Maxed-out mis_ap CMS capacity
Agent UID
Skill number
2126
Over CMS agent login
cap
Maxed out mis_ap CMS capacity
Agent UID
Skill number
2127
Over BCMS agent login
cap
Maxed out mis_ap BCMS (Basic
Call Management System) capacity
Agent UID
BCMS agent total
2128
Missing far-end IGAR LDN
(Inter-Gateway Alternate Routing)
2129
No idle trunks in either network
region (IGAR request)
2130
Deny TTI registration - IP endpoint
not in ip-network-map
IP address
TTI state
2131
Deny TTI registration - IP endpoint
requesting shared control
IP address
TTI state
21322299
not assigned
9 of 9
246 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Connection Manager Denial Events
Event Types 2300 - 2399 show Connection Manager denial events, as listed in Connection
Manager denial events (2300 - 2399) on page 247.
Table 54: Connection Manager denial events (2300 - 2399)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
2300
Ept capabilities mismatch
Endpoint connects to Time Division Multiplexed (TDM) bus or
it hairpinned capabilities mismatch.
2301
Tran/rec codec mismatch
Transmitted or received codec mismatch.
2302
Ip_ept is in loopback
Ip_ept is in loopback.
2303
Silence suppress mismatch
Endpoint connects to Time Division Multiplexed (TDM) bus or
is hairpinned silence suppression mismatch.
2304
Tran/rec codec mismatch
Transmitted or received codec mismatch.
2305
Silence suppress mismatch
Ept1 directly connected to Ept2 silence suppression
mismatch.
2306
Reject outbound OLC
Reject outbound OLC.
2307
TDM resource blockage
Time Division Multiplexed (TDM) resource blockage.
2308
Selected codec mismatch
Codec no longer supported.
2309
Drop call codec mismatch
Drop call, codec mismatch.
2310
Invalid regions
Invalid region.
2311
Invalid codec region
Invalid codec region.
2312
No DSP resource
No Digital Signal Processor (DSP) resource.
2313
No free list channels
No channels on free list.
2314
No channel resources
No channel resources.
2315
Not enough capacity
23162328
not assigned
2329
No BW, prowler <--> IP ept
No bandwidth channel resources between processor and IP
endpoint.
2330
No BW, prowler <--> prowler
No bandwidth channel resources between processors.
2331
No VOIP channel, PN <--> PN
No Voice Over IPchannel resources between port networks.
2332
No BW, prowler <--> MG
No bandwidth channel resources between processor and
media gateway.
2333
No VOIP channel, PN <--> MG
No Voice Over IPchannel resources between port network
and media gateway.
Event
Data 2
1 of 2
Issue 1 June 2005
247
Denial Events
Table 54: Connection Manager denial events (2300 - 2399) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
2334
No channel resources
No channel resources.
2335
RejReqMode-no common
mode
Deny inbound RM, not compatible with modes received in
request.
2336
RejReqMode-no common
mode
Deny inbound RM, cannot arrive at common profile.
2337
RejReqMode-no modes rcvd
Deny inbound RM, no data modes were received in request.
2338
RejReqMode-not 2 connectd
Deny inbound RM, there are not two pt_conn parties on call.
2339
RejReqMode-no common
mode
Deny inbound RM dirip ept, no common profile.
2340
T38Fail-no voip resources
Insufficient voip resources.
2341
T38Fail-far end timeout
Far-end timeout.
2342
T38Fail-near end timeout
Near-end timeout.
2343
ReqMode reject received
Time Division Multiplexed (TDM)/HP connection.
2344
ReqMode reject received
DIRIP connection.
2345
ReqMode release received
Request release received, Time Division Multiplexed (TDM)/
HP connection.
2346
ReqMode release received
Request release received, DIRIP connection.
2347
Rej inc T38OLC, not seq'd
Not in sequence, dropping call.
2348
Rej inc T38OLC, no common
Incompatible mode, Time Division Multiplexed (TDM)/HP
connection. Dropping call.
2349
Rej inc T38OLC, no common
Incompatible mode, DIRIP connection. Dropping call.
2350
Rej inc T38OLC, idle state
Deny inbound T38 OLC - IDLE state. Dropping call.
2351
Failed Xoip Attempt
XOIP failed attempt, invalid call type.
2352
Failed Fax Relay Xoip
Fax Relay XOIP failed attempt.
2353
Failed Modem Relay Xoip
Modem Relay XOIP failed.
2354
T38Fail-no dsp resources
Insufficient Digital Signal Processor (DSP) resources.
2355
IGAR trunk limit exceeded
Attempt to exceed the number of trunks allowed for
Inter-Gateway Alternate Routing (IGAR) in this network
region.
2356
All IGAR managers in-use
All Inter-Gateway Alternate Routing (IGAR) manager are in
use.
2357
Failed Fax Prowler
Prowler reports chl could not go to FAX mode.
2358
Failed Fax Media Gateway
Media Gateway reports chl could not go to FAX mode.
23592399
not assigned
Event
Data 1
Event
Data 2
2 of 2
248 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Dial Plan Manager Denial Events
Event Types 2400 - 2406 show Dial Plan Manager denial events, as listed in Dial Plan Manager
denial events (2400 - 2406) on page 249.
Table 55: Dial Plan Manager denial events (2400 - 2406)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
2400
UDP: too many conversions
Digit conversion counter exceeded.
2401
UDP: node-rte pat blank
Node number route pattern is blank.
2402
UDP: ENP code blank
ENP numbering prefix is blank.
2403
Loc Digits Size incorrect
Location Prefix digits size is not n, where the UDP form’s
matching row, Insert digits field is Ln.
2404
Var-in-Vec No adm for VAC
Variable Access Code (VAC) in Variables in Vector Table not
administered.
2405
Var-in-Vec Invalid digit
Invalid digit entered, or Feature Access Code corrupted from
call_p to dp_mgr.
2406
Unadministered annc ext
Unadministered announcement extension for a location.
Event
Data 2
Data Manager Denial Events
Event Types 3001 - 3003 show Data Manager denial events, as listed in Table 56: Data Manager
generated Denial Events (3001 - 3003) on page 249.
Table 56: Data Manager generated Denial Events (3001 - 3003)
Event Type
Event Description, as it appears on the event log
Explanation
3001
Bridge in use
indicate 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 object is in use
Issue 1 June 2005
249
Denial Events
Dial Access Plan Denial Events
Event Types 3101 - 3200 show Dial Access Plan denial events, as listed in Dial Access Plan
denial events (3101 - 3200) on page 250.
Table 57: Dial Access Plan denial events (3101 - 3200)
Event
Type
Event Description, as it
appears on the event log
Explanation
3101
DCS invalid PBX/Mach/Node
Distributed Communication System (DCS) requires Trunk
Group pbx-id, Signal Group Mach-id, or AAR Analysis node
number.
3102
DCS no msg buffer avail
No Distributed Communication System (DCS) message buffers
are available.
3103
DCS Station LWC mis-admin
Distributed Communication System (DCS) station Leave Word
Calling is mis-administered.
3104
DCS Trunk Group mis-admin
Distributed Communication System (DCS) trunk-group is
mis-administered.
3105
DCS invalid PBX/Mach/Node
Distributed Communication System (DCS) requires Trunk
Group pbx-id, Signal Group Mach-id, or AAR Analysis node
number
31063200
not assigned
Event
Data 1
Event
Data 2
Meet Me Conference Denial Events
Event Types 3201 - 3299 show denial events generated by the Meet Me conference process, as
listed in Meet Me Conference denial events (3201 - 3299) on page 250.
Table 58: Meet Me Conference denial events (3201 - 3299)
Event
Type
Event Description, as it
appears on the event log
Explanation
3201
Meet-Me Access chg TMO
Meet-me security/access change time-out.
3202
Invld Num Digits MM Acc.
Meet-me security/access change received too many digits.
3203
MM Extention not valid
Meet-me security/access change not a valid extension.
3204
MM Access Chg Not a VDN
Meet-me security/access change not a Vector Directory Number
extension.
3205
MM Invalid Access Entered
Meet-me security/access change invalid security/access code.
Event
Data 1
Event
Data 2
1 of 2
250 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 58: Meet Me Conference denial events (3201 - 3299) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
3206
MM Access Obj/SAT Busy
SAT window with Meet-me security/access code or obj is busy
and cannot make changes via AC.
3207
Merge Meet-me Conf call
User tried to merge to a existing Meet-me conference call and
mmcon _val failed to validate the merge.
3208
Serv Observ Meet-me VDN
User tried to service-observe a Meet-me conference call and
the service observing route failed.
3209
Meet-me Conf call full
Meet-me conference total party number is over limit.
3210
Wrong MM Acc. code dialed
Party failed to dial correct Meet-me conference access.
3211
Chg Station no Cons/Perm
Meet-me security/access change the station extension does not
have console permissions.
3212
VDN not a meetme type
Vector Directory Number (VDN) is not a meetme type.
3213
MM Invalid Conf Ctrlr Sta
Station extension does not match controller extension.
3214
MM Inv Trk not Remote Acc
Trunk User ID not allowed as a controller extension.
3215
MM Invalid Station Type
Invalid station type of calling extension.
3216
Conf/Transfer 2 Meet-me
Conference/or transfer 2 Meet-me conference call.
3217
MM Abbrev Dial Invalid
Cannot use abbreviated dialing.
3218
Error in EMMC route dgt
Error retrieving Enhanced MeetMe Conferencing (EMMC)
routing digits.
3219
Empty EMMC route digits
Empty Enhanced MeetMe Conferencing (EMMC) routing digits.
3220
Exceed EMMC active conf
Exceeded Enhanced MeetMe Conferencing (EMMC) active
conference.
3221
Exceed EMMC license ports
Exceeded Enhanced MeetMe Conferencing (EMMC) license
ports.
3222
Exceed EMMC party limit
Exceeded Enhanced MeetMe Conferencing (EMMC) party limit.
3223
32243299
Event
Data 1
Event
Data 2
Enhanced MeetMe Conferencing (EMMC)-no new vector proc
not assigned
2 of 2
Issue 1 June 2005
251
Denial Events
LSP Denial Events
Event Types 3300 - 3399 show LSP-generated denial events, as listed in LSP denial events
(3300 - 3399) on page 252.
Table 59: LSP denial events (3300 - 3399)
Event
Type
Event Description
Explanation
Event
Data 1
Event
Data 2
3300
IP RRJ-LSP not active
Local Survivable Processor (LSP) is not yet active.
NULL
sending LSP’s
IP address
3301
IP RRJ-LSP not admin
Local Survivable Processor (LSP) has not been
administered.
NULL
sending LSP’s
IP address
3302
IP RRJ-Version mismatch
Local Survivable Processor has not been
administered.
NULL
sending LSP’s
IP address
3303
IP RRJ-GK reg with GK
Local Survivable Processor (LSP)/ESS is
attempting to register with another LSP/ESS.
3304
IP RRJ-LSP's MG not admin
Local Survivable Processor’s serial number does
not match any administered gateway.
NULL
sending LSP’s
IP address
33053399
not assigned
(keyword)
Data Error Events
Event Types 3400 - 3499 show data error-generated denial events, as listed in Data Error denial
events (3400 - 3499) on page 252.
Table 60: Data Error denial events (3400 - 3499)
Event
Type
Event Description, as it
appears on the event log
Explanation
3400
Error in vector data
Bad step type.
3401
Invalid vector step type
Bad step type.
3402
Companding mode mismatch
Companding mode mismatch.
3403
Bad date in MCT record
Bad Malicious Call Trace date.
3404
Bad date in MCT record
Bad Malicious Call Trace date.
3405
Unicode cus file not read
Unicode translation read error. Entire customer file not read.
3406
Error in Unicode cus file
Unicode translation read error. Error found in customer file.
Event
Data 1
Event
Data 2
1 of 2
252 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Denial Event Tables
Table 60: Data Error denial events (3400 - 3499) (continued)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
3407
Unicode ava file not read
Unicode translation read error. Entire Avaya file not read.
3408
Error in Unicode ava file
Unicode translation read error. Error found in Avaya file.
34093500
not assigned
Event
Data 2
2 of 2
Contact Closure Denial Events
Contact Closure Denial Event Types 3501 - 3503 show successful feature activations and are
kept as historical data, as listed in Contact Closure denial events (3500 - 3503) on page 253.
Table 61: Contact Closure denial events (3500 - 3503)
Event
Type
Event Description
Explanation
3500
not assigned
3501
Relay OPEN
Contact closure OPEN.
3502
Relay CLOSE
Contact closure CLOSE.
3503
Relay PULSE
Contact closure PULSE.
(keyword)
Event
Data 1
Event
Data 2
Issue 1 June 2005
253
Denial Events
ESS Denial Events
Event Types 3600 - 3604 are ESS-generated denial events, and listed in ESS denial events
(3600 - 3604) on page 254.
Table 62: ESS denial events (3600 - 3604)
Event
Type
Event Description, as it
appears on the event log
Explanation
Event
Data 1
Event Data 2
3600
IP RRJ-ESS not admin
ESS has not been administered.
NULL
sending ESS’s IP address
3601
IP RRJ-ESS obj not init
EssMgr_ptr has not been initialized.
NULL
sending ESS’s IP address
3602
IP RRJ-ESS bad SID sent
ESS sent a bad System ID.
SID
sending ESS’s IP address
ESS had a failure from ParseNsdLSPInfo
method.
NULL
sending ESS’s IP address
3603
3604-
not assigned
254 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Chapter 3: LEDs
This chapter describes the meanings of the LEDs on system components and the alarm levels
they indicate. The chapter includes the following topics:
●
Alarm levels on page 255
●
Terminal alarm notification on page 256
●
Attendant console LEDs on page 257
●
Circuit pack LEDs on page 257
●
Avaya Ethernet Switch LEDs on page 268
●
UPS LEDs on page 269
●
IPSI LEDs on page 270
●
650A Power supply LEDs on page 273
●
655A Power Supply LEDs on page 273
●
S8710 Media Server LEDs on page 276
●
S8700 Media Server LEDs on page 279
●
S8500 Media Server LEDs on page 282
●
S8300 Media Server LEDs on page 283
●
G700 and Media Module LEDs on page 288
Alarm levels
If a maintenance object in the system begins to fail some of the periodic tests, the system
automatically generates an alarm that indicates the system needs to be restored to a normal
condition. The system identifies three levels of alarms:
●
Major alarms — Failures that cause critical degradation of service and require immediate
attention.
●
Minor alarms — Failures that cause some degradation of service, but do not render a
crucial portion of the system inoperable. This condition requires action, but its
consequences are not immediate. Problems might be impairing service to a few trunks or
stations or interfering with one feature across the entire system.
●
Warning alarms — Failures that cause no significant degradation of service or failures in
equipment external to the system.
Issue 1 June 2005
255
LEDs
Alarms are communicated to the system users and technicians by entries in the alarm log and
the lighting of LEDs located on the attendant console, on all circuit packs, on the server, on the
Cajun Ethernet switch if there is one, and, optionally, on customer-designated voice terminals.
Warning alarms are not reported to the attendant console.
Terminal alarm notification
Terminal alarm notification is an optional feature which displays several types of alarms on
voice terminals with administered feature buttons or the attendant console. A maximum of 10
digital and/or hybrid voice terminals may be used.
When an alarm occurs, the green status LED associated with the assigned button will be in a
steady state. The LED may be turned off by pressing the button associated with the lighted
alarm LED. If the LED is turned off and the alarm has not been resolved by the time
maintenance reschedules testing, the green status LED will resume its steady state.
The following alarms are displayed:
ac-alarm
Administered Connection alarm: A locally administered connection
(ADM-CONN) has a major, minor, or warning alarm active.
pr-awu-alm
Auto Wakeup Journal Printer alarm: The automatic wakeup journal printer has
a major, minor, or warning alarm active.
off-bd-alarm
DS1 or ATM Facility alarm: An off-board major, minor, or warning alarm is
active on a DS1-BD, UDS1-BD, or ATM-TRK board.
trk-ac-alm
Facility Access alarm: The facility access trunk test feature is activated.
major-alrm
Major alarm: The system has logged a major alarm.
mj/mn-alrm
Major/Minor alarm: The system has logged a major or minor alarm.
pr-pms-alm
The Property Management System (PMS) printer has a major, minor, or
warning alarm active.
rs-alert
Reset-Alert: reset system 2 or 3 has been performed.
cdr1-alrm
Call Detail Recording alarm: The primary CDR link has a major, minor, or
warning alarm active.
cdr2-alrm
Call Detail Recording alarm: The secondary link has a major, minor, or warning
alarm active.
pr-sys-alm
System Printer alarm: The System Printer (SYS-PRNT) has a major, minor, or
warning alarm active.
pms-alarm
The Property Management System has a major, minor or warning alarm active.
256 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Attendant console LEDs
Attendant console LEDs
The console has two red LEDs, labeled “ALM” and “ACK.” The ALM LED lights steadily when
there is a major or minor alarm at the switch cabinet. The ACK LED lights steadily if the alarm
has been successfully reported. If the system is unable to report the alarm, the LED flashes; this
signals the attendant to call the Avaya alarm receiving system and report the alarm.
Circuit pack LEDs
Typically each circuit pack has three LEDs on the front panel visible at the front of the carrier.
There are some exceptions to this (for example, DS1CONV or IPSI circuit pack) that are
covered later in this section. On most circuit packs, the LEDs indicate the following when lit
(Table 63: LED indicators on page 257). Exceptions to these indications are explained in
subsequent sections.
Table 63: LED indicators
LED
Color
State
Interpretation
Red
Alarm
The system detected a fault in this circuit pack. The alarm log should contain
an on-board alarm for this circuit pack or one of the maintenance objects
associated with it. The red LED is also lit briefly when a circuit pack is
inserted or reset. If the circuit pack passes its initialization tests, the LED is
extinguished. If a fault is detected, it remains lit.
Green
Testing
The system is currently running tests on this circuit pack as part of
background maintenance or demand testing. This LED is also lit briefly
during initialization tests when a circuit pack is inserted or reset.
Yellow
Busy
The circuit pack is currently in use by the system.
This section includes LED interpretation on the following circuit packs:
●
LED alarms without Alarm Log entry or with Error Type 1 on page 258
●
Expansion Interface circuit pack LEDs on page 259
●
Maintenance circuit pack LEDs on page 260
●
DS1C (TN574/TN1654) circuit pack LEDs on page 261
●
Switch Node Interface LEDs on page 265
●
Tone-Clock circuit pack LEDs on page 266
●
IPSI LEDs on page 270
Issue 1 June 2005
257
LEDs
LED alarms without Alarm Log entry
or with Error Type 1
Whenever the system or a part of the system is reset, every affected circuit pack will briefly light
their red and green LEDs as they are initialized. Upon power up of a newly installed system,
several alarm indicators may remain lit until the circuit packs are administered. These alarms
should be ignored until administration is completed.
Boards with a “P” suffix have downloadable firmware. If such a board has both its green and
yellow LEDs lit simultaneously, a download may be in progress and the board will not appear to
be recognized. Use either the SAT command status firmware download or status
firmware download last to verify this condition.
G350: For G350 - WAN media modules, MM314, MM340, and MM342. If these media modules
are inserted in a slot administered for a voice media module the red LED will be lit.
After a circuit pack has been initialized, a red LED should be accompanied by an alarm in the
alarm log. A single fault can sometimes light alarm LEDs on several circuit packs, as in the
following examples.
●
A TDM bus problem may cause several port circuit packs to display red LEDs.
●
A Maintenance circuit pack can prevent an Expansion Interface (EI) circuit pack from
initializing.
●
Extensive interactions in the Center Stage Switch (CSS) can cause multiple alarms from
single faults in DS1C, SNI and SNC circuit packs and fiber links.
●
Tone-Clock problems may cause other circuit packs to report alarms.
●
Mis-connected optical fiber cables may cause several circuit packs to alarm.
●
Packet-bus faults can cause several port circuit packs to display red LEDs.
If a circuit pack has had at least five minutes to be initialized, and the red LED is lit without an
associated alarm in the alarm log, the circuit pack may not be in communication with the
system. This may also be the case when a circuit pack is properly administered and present in
its slot, but there is an error type 1 logged against it. To determine whether this is so, proceed as
follows:
1. Enter the list configuration board location command. If the system does not
detect the circuit pack, this command will return:
identifier not assigned or no board.
If the documentation for the associated maintenance object gives no special instructions for
this situation, go to the next step.
2. Check the hardware error log for TONE-BD or TDM-BUS errors. If the board has a “P” suffix
execute the reset board location command, otherwise execute the test tdm and
test tone-clock commands and use the appropriate maintenance procedures to
resolve any identified faults. If this does not resolve the problem, go to the next step.
258 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Circuit pack LEDs
3. Reseat the suspect circuit pack.
! CAUTION:
This procedure can cause a partial or total service outage. Consult thoroughly the
documentation for the associated maintenance object before proceeding.
Observe the precautions and procedures described above.
CAUTION:
4. Inspect the backplane connectors for bent pins.
5. If the system seems to be functioning correctly, but the circuit pack in question will not
communicate with the system, replace the circuit pack.
Expansion Interface circuit pack LEDs
The Expansion Interface (EI) TN570 circuit pack has the standard red, green and yellow LEDs.
The red and green LEDs have the traditional meaning, where red indicates an alarm condition,
and green indicates testing in progress.
The yellow LED displays various flashing patterns to provide status information useful in
isolating faults in the fiber link and other components connected to the fiber link.
Table 64: Expansion Interface yellow LED flashing codes on page 259 illustrates the EI yellow
LED states.
Table 64: Expansion Interface yellow LED flashing codes
LED
on
LED
off
Condition
0.1 sec
0.1 sec
Fiber Out-of-Frame. This state indicates a failure of test #989. This may
be caused by absence of the opposite end EI or Switch Node Interface
(SNI), a broken or missing fiber, or a missing lightwave transceiver on
either endpoint.
0.5 sec
0.5 sec
In Frame — No Neighbor. This state corresponds to a failure of test #
237, usually due to a failure of this EI or of the EI or SNI at the other end
of the fiber.
2 sec
0.2 sec
EI Active. This is the normal state of an active EI that is an archangel of
an EPN.
solid on
EI Active. This is the normal state for an active EI that is not an EPN
archangel. These include EPN EIs connected to other EPN EIs in direct
connect configurations, and EIs located in the processor port network.
solid off
EI Standby. This is the normal state for a standby EI in systems with a
duplication option.
Issue 1 June 2005
259
LEDs
Maintenance circuit pack LEDs
TN775D PN maintenance circuit packs have seven LEDs on their front panels. The top three
LEDs are the standard group of red, green and yellow, and indicate the status of the circuit
pack. The green LED on TN775Ds blinks faintly once per second, indicating continual
self-testing.
The second group of three LEDs, labeled “ALARMS”, reflects maintenance conditions
throughout the system and indicates alarms reported against other components, as shown in
Table 65: Maintenance circuit pack LED interpretation on page 260.
Table 65: Maintenance circuit pack LED interpretation
LED
color
State
Level/
Function
Interpretation
Red
flashing
MAJOR
Major alarm against a component in the same cabinet.
solid
MAJOR
Major alarm against a component in another cabinet.
solid
MINOR
Minor alarm against a component in another cabinet.
flashing
MINOR
Minor alarm against a component in the same cabinet.
flashing
WARNING
Warning alarm against a component in the same
cabinet.
solid
WARNING
Warning alarm against a component in another
cabinet.
Green
on
ACK
Acknowledged; alarm has been reported.
Red
on
EMERGENCY
TRANSFER
Emergency transfer has been invoked. This occurs
upon power-up as well as during disabling failures.
Yellow
These LEDS are illustrated Figure 1: TN775 circuit pack LEDs on faceplate on page 261.
260 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Circuit pack LEDs
Figure 1: TN775 circuit pack LEDs on faceplate
Figure notes:
1.
Alarm LED (Red)
4.
Latch pin
2.
Test LED (Green)
5.
Locking lever
3.
Busy LED (Yellow)
DS1C (TN574/TN1654) circuit pack LEDs
The TN574 and the TN1654 LEDs provide an indication of the state of the DS1 converter and
facilities.
Note:
Note:
DS1 converters are used exclusively with a CSS.
TN574 circuit pack LEDs
Seven LEDs provide an indication of the state of the DS1 converter (DS1C-BD) TN574 circuit
pack and the DS1 facilities. The top group has the standard red, green and yellow LEDs. The
red and green LEDs have the traditional meaning, where red indicates an alarm condition, and
green indicates testing in progress. The four green LEDs on the bottom indicate the status of
the DS1 facilities (see following section).
Issue 1 June 2005
261
LEDs
The yellow LED is used to indicate the state of the fiber interface, the fiber channel, and the
DS1 channel as listed in Table 66: DS1C yellow LED flashing states on page 262 in order of
priority.
Table 66: DS1C yellow LED flashing states
LED
on
LED
off
Condition
0.1 sec
0.1 sec
Fiber Out-of-Frame or Fiber Loss of Signal
0.5 sec
0.5 sec
In Frame, fiber channel down. The fiber channel communicating between
the DS1C and the other fiber endpoint (EI or SNI) is down.
1 sec
1 sec
In Frame, DS1 channel down. The channel between the two DS1Cs in the
DS1C complex is down.
solid on
DS1C active. This is the normal state for an active DS1C.
solid off
DS1C standby. This is the normal state for a standby DS1C in
critical-reliability systems (duplicated PNC).
DS1 Facility LEDs
Below the three standard LEDs on the DS1C circuit pack are four green LEDs that indicate
whether a receive signal is present for each of the four DS1 facilities. Figure 2: TN574 DS1
Converter circuit pack LEDs on page 263 shows which facility (A, B, C, or D) corresponds to
each LED. If a green LED is off, there is a Loss of Signal condition on the DS1 facility
associated with that LED. The presence of a signal does not guarantee that the signal is using
the correct framing format or line coding; an Alarm Indication Signal indicating that the opposite
end of the DS1C complex is out of service may be present.
262 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Circuit pack LEDs
Figure 2: TN574 DS1 Converter circuit pack LEDs
Figure notes:
1.
Alarm LED (Red)
4.
STATUS LEDs
2.
Test LED (Green)
5.
SPAN LEDs
3.
Busy LED (Yellow)
TN1654 circuit pack LEDs
The TN1654 DS1C-BD board has 11 LEDs on its faceplate. The top three system standard
LEDs indicate the state of the DS1C-BD board. These LEDs are under firmware control until the
board has established a link to the S8700 Media Server via the EI or SNI. Once the link is
established, software controls the three LEDs. If the link breaks, the LEDs are again under
firmware control.
The red and green LEDs have the traditional meaning, where red indicates an alarm condition,
and green indicates testing in progress. The red and green LEDs are also turned on during
circuit pack initialization by firmware. When the control link to the circuit pack is lost, firmware
controls the red LED to indicate an alarm condition.
Issue 1 June 2005
263
LEDs
The yellow LED under firmware control is used to indicate the state of the physical fiber
interface, the Fiber Channel (link to EI or SNI), the DS1 Control Channel (link to opposite
DS1CONV board), and the S8700 Media Server communications link in the following manner
and order of priority. (The yellow LED remains on for longer periods of time as the DS1CONV
complex becomes closer to being fully operational.)
1. If the fiber is Out of Frame or if a Fiber Loss of Signal condition exists, the yellow LED will
flicker at a 5 Hz rate (on for 100 mS, off for 100 mS).
2. If the fiber channel is down (DS1 Converter circuit pack/fiber endpoint communications), the
yellow LED will flash at a 1 Hz rate (on for 500 ms, off for 500 ms).
3. If the DS1 control channel is down between the two DS1CONVs in the DS1CONV complex,
the yellow LED will pulse at a 0.5 Hz rate (on for 1 second, off for 1 second).
4. If the S8700 Media Server communications link is down, the yellow LED will wink off every 2
seconds for 200ms (2 sec on, 200 msec off).
5. If all is well with the fiber interface and every communications channel, the yellow LED will
remain on continuously in a standard- or high-reliability system configuration. In
critical-reliability systems (duplicated PNC), an active DS1CONV circuit pack will have its
yellow LED on continuously, and a standby DS1CONV circuit pack will have its yellow LED
off. The LED will then be under software control.
The bottom four green LEDs on the TN574 DS1CONV board are under hardware control. The
four green LEDs indicate, for each DS1CONV facility, whether a receive signal is present for the
DS1 facility
The next four LEDs on the TN1654 DS1CONV board are labeled STATUS LEDs and are for
future use. These LEDs will not be lit.
The bottom four LEDs on the TN1654 board are labeled SPAN LEDs. These LEDs are under
firmware control. If the facility is not administered, then the LED is not lit. The LED is lit amber if
the facility is running alarm free. If the facility is detecting either a red alarm (loss-of-signal or
loss-of-frame), a yellow alarm (remote frame alarm) or a blue alarm (AIS signal) then the LED is
lit red. The SPAN SELECT switch on the TN1654 faceplate is for future use. Pushing the switch
will have no effect on the board. See Figure 3: TN1654 DS1CONV circuit pack on page 265 for
a view of the faceplate on the TN1654 DS1CONV circuit pack.
264 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Circuit pack LEDs
Figure 3: TN1654 DS1CONV circuit pack
.
INSET
0015_0 RBP 052396
Switch Node Interface LEDs
The Switch Node Interface (SNI) TN573 circuit pack has the standard red, green, and yellow
LEDs. The red and green LEDs have the traditional meaning, where red indicates an alarm
condition, and green indicates testing in progress.
The yellow LED displays various flashing patterns to provide status information useful in
isolating faults in the fiber link and other components connected to the fiber link.
Issue 1 June 2005
265
LEDs
Table 67: Switch Node Interface (SNI) yellow LED flashing states on page 266 illustrates the
SNI yellow LED states.
Table 67: Switch Node Interface (SNI) yellow LED flashing states
LED
on
LED
off
0.1 sec
0.1 sec
Fiber Out-of-Frame. This state indicates a failure of test #238, which may
be caused by absence of the opposite end EI or Switch Node Interface, a
broken or missing fiber, or a missing lightwave transceiver on either
endpoint.
0.5 sec
0.5 sec
In Frame — No Neighbor. This state corresponds to a failure of test #
237, usually due to a failure of this SNI, or the EI or SNI at the opposite of
the fiber. This condition may also be due to a faulty Switch Node Clock
(SNC).
solid
on
Condition
SNI Active. This is the normal state for an active SNI.
solid
off
SNI Standby. This is the normal state for a standby SNI in systems with a
duplication option.
Tone-Clock circuit pack LEDs
The Tone-Clock circuit packs found in non IPSI connected port networks have the standard red,
green and yellow LEDs. The red LED has the traditional meaning. The yellow and green LEDs
flash in specific patterns to indicate the status of the circuit pack. The standby status applies
only to systems with a duplication option.
Maintenance/Test circuit pack LEDs
The TN771D maintenance/test circuit pack has the standard red, green, and yellow LEDs. The
red and green LEDs have the traditional meaning, where red indicates an alarm condition, and
green indicates testing in progress.
The yellow LED can be off or on continuously or flashing, depending on the mode of operation
of the TN771D and whether or not it has detected errors. The yellow LED is on steady when the
TN771D’s analog test port or digital test ports are being used to test trunks or line circuits. The
yellow LED is also used to indicate packet-bus status. Table 68: TN771D Maintenance/Test
Yellow LED States on page 267 illustrates the maintenance/test yellow LED states as they
apply to packet-bus activity.
266 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Circuit pack LEDs
Table 68: TN771D Maintenance/Test Yellow LED States
LED State1
TN771D Mode
Condition
Solid off
Normal
The Maintenance/Test circuit pack detects no packet-bus
faults.
Solid on2
Normal
The Maintenance/Test packet-bus port has successfully
reconfigured the packet bus around a fault.
Flashing (1 Hz)
Normal
The Maintenance/Test packet-bus port is unable to
reconfigure the packet bus around a fault.
Solid off
Standalone3
The Maintenance/Test detects no packet-bus faults.
Solid on
Standalone
This condition cannot normally occur. The LED is always
either off or blinking in standalone mode.
Flashing (1 Hz)
Standalone
The Maintenance/Test packet-bus port detects a
packet-bus fault.
1. It takes 5 to 10 seconds for the yellow LED to respond to a change in the state of the packet bus.
2. Because the yellow LED on the Maintenance/Test circuit pack can also be on steady when the digital and
analog test ports on the circuit pack are in use, exact interpretation of the yellow LED may require that the
technician busy out the analog and digital test ports or examine the error and alarm logs for PKT-BUS
errors and alarms.
3. “Standalone” refers to the TN771D’s capability to operate autonomously as a troubleshooting aid.
Issue 1 June 2005
267
LEDs
Avaya Ethernet Switch LEDs
The Avaya Ethernet switch’s LEDs are shown in Figure 4: Avaya Ethernet switch LEDs on
page 268.
Figure 4: Avaya Ethernet switch LEDs
51 52 53 54
55 56 57 58
1
2
3
4
5
6
7
8
9
Cajun P333T Switch
10 11 12
EXPANSION
SLOT
59 60 61 62
63 64 65 66
FIV
13 14 15 16
LNK COL Tx
17 18 19 20
Rx FDX FC Hspd LAG
21 22 23 24
SYS OPR PWR
LAG
LAG
LAG
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
CONSOLE
51 52 53 54
55 56 57 58
59 60 61 62
63 64 65 66
1
2
3
4
5
6
7
8
9
10 11 12
EXPANSION
SLOT
1
FIV
13 14 15 16
LNK COL Tx
17 18 19 20
21 22 23 24
Rx FDX FC Hspd LAG
2
SYS OPR PWR
3
ledl333t KLC 030602
4
Figure notes:
1.
Ports in use
3.
Power
2.
CPU boot status
4.
Lights if this module is the Cajun
P33x stack master
The following three LEDs are the primary indicators:
●
SYS shows whether this module is the Cajun P330 stack master.
●
OPR shows CPU boot status.
●
PWR shows when power is on.
For all other LEDs, refer to the quick start guide and user guide that came with the Avaya
Ethernet switch.
268 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
UPS LEDs
UPS LEDs
All Ethernet hubs and UPSs have LEDs to indicate that they are powered on or off. LEDs “on”
imply the device is powered on. LED “off” implies the device is powered down.
The Powerware front panel has the LEDs shown in Figure 5: UPS LEDs on page 269.
Figure 5: UPS LEDs
ledlups KLC 030102
1
2
8
7
3
4
5
6
Figure notes:
1.
Normal mode indicator
5.
Off button
2.
Battery mode indicator
6.
On button
3.
Bypass mode indicator
7.
Bar graph indicators
4.
Test/Alarm reset button
8.
Alarm indicators
When the Normal mode LED is steady green, it has power. If the LED is flashing, the UPS is in
standby mode.
For information on the other LEDs, refer to the UPS user’s guide that came with the Powerware
UPS unit.
Issue 1 June 2005
269
LEDs
IPSI LEDs
There are four LEDs on the TN2312AP IPSI faceplate, and five LEDs on the TN2312BP IPSI
faceplate. The top three LEDs are the standard ones found on most TN circuit packs. The fourth
LED imitates the TN2182B Tone-Clock’s amber LED. The archangel flashes the yellow LED
when active, 2 seconds on and 200 msec off. In addition, the TN2312BP has a fifth LED that
shows the emergency transfer control status.
Figure 6: IPSI display showing connectivity status
2
3
4
5
ledlipsi KLC 030502
1
Table 69: IPSI connection status (figure notes)
Connectivity status
1
2
3
4
5
IPSI is connected to Avaya Ethernet switch
no
yes
yes
yes
yes
IPSI has an IP address
no
no
yes
yes
no
Laptop computer is connected to IPSI
services port
no
no
no
yes
yes
270 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
IPSI LEDs
Figure 7: S8700 IP-Connect IPSI display
1
2
CLK
S
E
R
V
I
C
E
ledlip1 KLC 030502
N
E
T
W
O
R
K
Figure notes:
1.
IPSI using DHCP
2.
IPSI has connectivity and an IP address
Issue 1 June 2005
271
LEDs
Figure 8: S8700 Multi-Connect IPSI Board Display
1
CLK
2
3
S
E
R
V
I
C
E
ledsa01 KLC 030502
N
E
T
W
O
R
K
Figure notes:
1.
Switch identifier
2.
Cabinet
3.
IPSI has connectivity and an IP address
272 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
650A Power supply LEDs
650A Power supply LEDs
Table 70: LED and alarm conditions on page 273 shows the LED and alarm conditions for the
650A Power Supply. Ring voltage and neon bus output do not activate alarm status.
Table 70: LED and alarm conditions
Condition
LED
status
Alarm
state
Fan alarm
Normal
Red off;
Yellow on
Open
Normal
No input power
Red off;
Yellow off
Closed
No input power
DC output not present (except Neon)
Red on;
Yellow off
Closed
DC output not present
(except Neon)
Fan alarm
Red on;
Yellow on
Closed
Fan alarm
655A Power Supply LEDs
The G650 media gateway normally has two 655A power supplies. Each has a set of five LEDs,
the function of which is indicated in Table 71: 655A Power Supply LEDs on page 273.
Table 71: 655A Power Supply LEDs
LED
Color
Function
1
Red
Failure of power supply or fan
2
Yellow
Status of power supply OK
3
Green
AC input voltage applied
4
Green
DC input voltage applied
5
Green
Power supply providing ring voltage
Normally the ring voltage LED (#5) on the left power supply is ON and the ring voltage LED on
the right power supply is OFF. This changes momentarily when the ringer interchange test is
run. The ring voltage LED will only remain lit on the right power supply when there is a power
supply failure of the left hand supply or the left hand supply is removed.
Issue 1 June 2005
273
LEDs
LED indicators of serial bus commands to the power supply
Operation of the 655A power supply LED indicators for visual indication of serial bus commands
to the power supply for power supply shutdown and ringing shutdown are described below.
Power supply shutdown
The 655A power supply can be commanded off for a period selectable from 1 to 255 seconds.
The intent is to allow a hard reset to the G650 chassis remotely. The yellow LED indicating
correct operation of the 655A power supply is on for normal power supply operation. When the
power supply is commanded off, the yellow LED blinks at a rate of 1 second on and 100ms off,
indicating that the power supply is operational but commanded off by the serial bus.
Ringing shutdown
The left hand power supply in the G650 cabinet is the master ringer. If the master ringer fails,
ringing is transferred to the redundant power supply, if present, and the red LED on the left hand
power supply turns on and the yellow LED turns off, indicating failure of the power supply.
The serial bus can command the ringer off for a period of 1 to 255 seconds. The purpose of this
command is to verify redundant ringer operation through the serial bus, remotely from the G650
chassis. The red LED blinks at a rate of 1 second on and 100ms off, indicating that the power
supply is operational but commanded off by the serial bus.
A second command relating to ringer operation is the to command the master ringer off, which
shuts down the master ringer and transfers control to the redundant power supply. This
command is used to permanently transfer ring voltage to the redundant power supply through
the serial bus, in order to resolve a problem with the master ringer. The red LED blinks at a rate
of 1 second on and 100ms off, indicating that the power supply is operational but commanded
off by the serial bus.
Duplication memory card LEDs
The Duplication memory card has LEDs that indicate active/standby, fiber link integrity/activity
states. The LED functions are:
●
Link Active -- Green when light signal is sensed on the fiber.
●
Link Sync -- Green when characters are received.
●
Trans Mode -- Green when transmission is enabled.
●
Receive Mode -- Green when reception is enabled.
274 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Duplication memory card LEDs
On the active server the Trans Mode LED will be green and the Receive Mode LED will be dark.
On the standby server the Receive Mode will be green and the Trans Mode LED will be dark.
Also see System shutdown LEDs on page 280.
Testing the Duplication Memory card LEDs
When you test the LEDs, the DAJ-1 or DAL-1 duplication memory card LED should blink
according to the following pattern:
1 second red, 1 second red off, 1 second green, 1 second green off
and so on for a total of one minute.
If the LED shows any of the following flashing patterns, an abnormal condition is indicated.
Table 72: Duplication memory card abnormal LED conditions on page 275 describes the
condition and suggests actions to take to resolve it.
!
WARNING:
WARNING:
The DAJ-1 and DAL-1 are not interchangeable. The DAJ-1 will not function in the
S8710 and the DAL-1 will not function in the S8700 media server.
Table 72: Duplication memory card abnormal LED conditions
LED
Color
Behavior
Indication
Resolution
Red
Flashes on 1 second,
off 3 seconds
in a repeating pattern
The green element
is burned out
Replace the server.
Green
Flashes on 1 second,
off 3 seconds,
in a repeating pattern
The red element is
burned out
Replace the server.
LED remains off
continuously
The DAJ-1 or
DAL-1 card is not
getting power, or
the server is hung
If the server is hung, it should
automatically reboot itself. If it does
not, power it down and reboot it.
Flashed continuously
The server is hung
If the server is hung, it should
automatically reboot itself. If it does
not, power it down and reboot it.
Green or
Red
Issue 1 June 2005
275
LEDs
S8710 Media Server LEDs
The S8710 Media Server has LEDs on both the front and back panels. Use the links in Table 73
for LED information and interpretation.
Table 73: S8710 LED information
S8710
location
Diagram
LED interpretation
Front panel
Figure 9
Table 74: S8710 front panel LED interpretation on page 277
Back panel
Figure 10
Figure notes: S8710 rear panel LED interpretation on
page 278
Figure 9: LEDs on front panel of S8710 Media Server
1
2
3
4
disc
2
1
2
6
0
0
Simplex
1
1
COMPACT
Duplex ch 1 ch 2
5
1
msdsled1 KLC 041304
276 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
S8710 Media Server LEDs
Table 74: S8710 front panel LED interpretation
Number
Description
Status
1
Internal health
GREEN: normal
AMBER: system degraded. See system board
LEDs to identify component in degraded state.
RED: system critical. See system board LEDs to
identify component in critical state.
2
Power supply
GREEN: normal
AMBER: power redundancy failure
RED: Critical power supply failure
3
NIC 1 (Eth0) link/activity
(GREEN)
STEADY ON: network link
FLASHING: network link and activity
Off: No link to network
4
NIC 2 (Eth1) link/activity
(GREEN)
STEADY ON: network link
FLASHING: network link and activity
OFF: No link to network
5
Active/Standby mode (BLUE)
STEADY ON: in active mode
FLASHING: in standby mode
OFF: deactivated
NOTE: If pressed, the LED is deactivated; wait 10
seconds and the LED comes back on.
6
Power on/
Standby button/
System power
GREEN: system on
AMBER: system shut down but power still applied
OFF: power supply failure
Issue 1 June 2005
277
LEDs
Figure 10: LEDs on back panel of S8710 Media Server
1
3
2
3
2
4
3
3
2
DAL1
DUP
MEMORY
LINC
ACTIVE
LINC
SYNC
TRANS
MODE
RECEIVE
MODE
100 MGz
2
100 MGz
iLO
2
1
1
133 MGz
VDCI
UID
5
6
8
7
msds871c KLC 040604
Figure notes:S8710 rear panel LED interpretation
Number
Description
Status
1
Not used
ON: expansion board failed.
OFF: normal
2
Not used
STEADY ON: slot has power
FLASHING: power is cycling
OFF: no power
3
Quad-NIC fault
(slot 2) (AMBER)
ON: expansion board failed.
OFF: normal
4
Quad-NIC power
(slot 2) (GREEN)
STEADY ON: slot has power
FLASHING: power is cycling
OFF: no power
5
RJ45 link (GREEN)
ON: linked to network
OFF: not linked to network
6
RJ45 link (GREEN)
STEADY ON: network activity
FLASHING: network activity
OFF: no network activity
7
Active/standby mode
(BLUE)
STEADY ON: in active mode
FLASHING: in standby mode
Off: deactivated
NOTE: If pressed, the LED is deactivated; wait 10 seconds
and the LED comes back on.
1 of 2
278 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
S8700 Media Server LEDs
Figure notes:S8710 rear panel LED interpretation (continued)
Number
Description
Status
8
Power supply
(GREEN)
ON: power is on and power supply is functioning properly
OFF: indicates one or more of the following conditions:
●
AC power is unavailable
●
Power supply failed
●
Power supply in standby mode
●
Power supply exceeded current limit
2 of 2
S8700 Media Server LEDs
The S8700 Media Server has an LED called Active/Standby that indicates whether the server is
the active server or the standby server. The Active/Standby LED in the “on” state implies active
and in the “flashing” state implies standby. It flashes at the rate of 400 ms “on” and 600 ms “off”
when in standby mode.
Issue 1 June 2005
279
LEDs
Figure 11: S8700 Media Server LEDs—Front and Back
1
2
ACTIVE
SERVICE
1
3
4
STANDBY
5
6
U2
7
8
5
4
3
2
9
RECEIVE
LINE
AVAYA
LINK
STAT
TRANS
DAI - 1
DUP
MEMORY
2
10
11
1
scdlled KLC 030502
Figure notes:
1.
Power
7.
U2 (not used)
2.
Configuration fault
8.
4 NIC ports (the numbers indicate their
assigned Ethernet ports)
3.
Disk activity
9.
LEDs for the NIC ports
4.
Network activity (not used)
1
0
.
LEDs for fiber optic duplication connectivity
5.
Service—configuration health (not used)
1.
Status LED (not used)
6.
Active or standby mode indicator
System shutdown LEDs
All server and Avaya duplication memory card LEDs are in the “off” state but still powered “on”
when the server is shut down.
Testing server LEDs
Using the media server Web interface, click Diagnostics > Test Server LEDs to make sure
that the Active/Standby LED on the server and the transmit LED on the DAJ-1 or DAL-1
duplication memory card are controllable and not burned out, and that the server is not hung.
During the test, the Active/Standby LED on the media server and the transmit LED on the
duplication memory card should blink slowly (1 second on, 1 second off) for 1 minute.
280 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
S8700 Media Server LEDs
To test the server LEDs:
1. On the main menu, under Diagnostics, click Test Server LEDs.
2. On the Test Server LEDs screen, click Test LEDs.
3. Observe the Active/Standby LED on your server and the transmit LED on your duplication
card to ensure they are blinking.
Interpreting the test results
An abnormal condition is indicated if an LED shows any of the following flashing patterns.
LED color / behavior
Indication
Flashes red
The green element is either burned out or not controlled.
Flashes green
The red element is either burned out or not controlled.
Flashes between red
and amber
The green element is stuck on.
Flashes between green
and amber
The red element is stuck on.
Stays amber continuously
Either the server is hung or the LED controller is stuck.
Stays off continuously
The server is hung or powered off, the controller is stuck, or the
server is using a new or different LED controller.
Also see Testing the Duplication Memory card LEDs on page 275.
Resolving problems
If the server is hung, you do not need to do anything. It should automatically reboot and fix itself.
If the server does not reboot itself, power it down and then reboot it.
If an LED is clearly stuck or has a burned out element, ignore the indicators until you can
conveniently replace the server.
Issue 1 June 2005
281
LEDs
S8500 Media Server LEDs
The S8500 Media Server has:
●
Five (5) LEDs on the front panel (Figure 12: S8500 front panel on page 282)
●
Four (4) LEDs on the back (Figure 13: S8500 rear panel on page 283)
Figure 12: S8500 front panel
1
2
3
4
5
disc
6
h3msfrnt LAO 070103
7
8
9
Figure notes:
1.
CD-ROM drive activity LED (green)
6.
System-error LED (amber)
2.
CD eject button
7.
Hard disk drive activity LED (green)
3.
Power-control button
8.
Reset button
4.
USB connector 1
9.
Power-on LED (green)
5.
USB connector 2
The four LEDs on the S8500 back panel are shown in Figure 13: S8500 rear panel on
page 283.
282 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
S8300 Media Server LEDs
Figure 13: S8500 rear panel
PCI
1
100-127 -, 3,0A, 50/60 Hz
200-240 -, 1,5A, 50/60 Hz
PCI 2
LINK TX/RX
133 MHz/64 Bit, 100 MHz/64 Bit
LINK TX/RX
2
1
h3msble2 KLC 082503
100-127 -, 3,0A,
200-240 -, 1,5A, 5
2
1
Figure notes:
1.
Activity
2.
Connection speed
●
LED is off: there is a 10 BASE-T active link.
●
LED is green: there is a 100 BASE-T active link.
●
LED is orange: there is a 1000 BASE-T active link.
S8300 Media Server LEDs
Figure 14: S8300 Media Server
The S8300 Media Server has a total of 6 LEDs on the faceplate (Figure 14: S8300 Media
Server on page 283). The three standard, red, green, and yellow LEDs. See S8300 LED
differences from Media Modules on page 284 for a detailed description of these LEDs.
The three additional LEDs:
●
A fourth LED labeled “OK-to-Remove”, which indicates when the S8300’s disk is properly
shut down.
●
Fifth and sixth LEDs, located on the lower left and right sides, respectively, of the
Services Port, which indicate whether or not data is being sent over the RJ45 jack, and
the data rate.
Issue 1 June 2005
283
LEDs
GREEN “OK-to-Remove” LED
The S8300 has a hard drive that must be shut down prior to removal of the S8300. Initiate a
shutdown process by first depressing the shutdown button located next to the fourth GREEN
“Ok-to-Remove” LED for 2-4 seconds (specific to the S8300). The GREEN LED will first blink;
then go steady. Once steady, the GREEN LED indicates that the disk drive has been shut down
properly and the S8300 is ready to be removed. Follow standard Media Module removal
procedures after the GREEN LED indicates that the disk drive has been properly parked.
There are three different ways that you can properly shut down the S8300 before it is removed:
●
Press the shutdown button on the faceplate for 2-4 seconds.
●
Initiate shutdown via the Web interface with a computer connected either:
●
Remotely, on the customer’s LAN
●
Locally, on the S8300 using the Services Port on the faceplate of the S8300
GREEN or YELLOW Services Port LEDs
One LED is located on the lower left side of the Services port. It indicates the data rate of the
connection:
●
When GREEN, this LED indicates a 10MB connection.
●
When YELLOW, this LED indicates a 100MB connection.
A second LED, located on the lower right side of the Services port, indicates whether or not data
is being sent over the RJ45 jack. This LED serves as a visual status of the Services' Ethernet
interface (TX/RX).
S8300 LED differences from Media Modules
Certain behaviors of the traditional S8300 LEDs differ from the Media Modules because the
S8300 is a Media Server running Communication Manager.
●
Situations like “insanity” and IP concepts of “registered” through H.248 do not necessarily
apply to other Media Modules.
●
The RED LED provides a major alarm indication. Software turns off the RED LED during
system startup. After startup, software turns on the RED LED whenever a major alarm is
present, and turns off the RED LED whenever a major alarm clears. Since the S8300
sees a major alarm whenever a G700 Media Gateway becomes unregistered, this
means the RED LED turns on. If the Media Gateway subsequently becomes registered,
the major alarm clears, and the RED LED turns off.
284 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
S8300 Media Server LEDs
Note:
Note:
For an S8300 configured as an LSP, the converse is true. If a G700 Media
Gateway registers with an LSP, a major alarm is generated, and the RED LED
turns on. When the Media Gateway unregisters, the RED LED turns off.
The RED LED can be turned on by software to report an application or other error. The
RED LED can also be turned on by a hardware watchdog that has not been cleared for at
least 10ms, when the processing complex has ceased to function.
●
The GREEN LED provides self-testing and maintenance indication. For an S8300, the
software turns on the Green LED when the Avaya Communication Manager application
is running. This is important to know when the S8300 is used in the Local Survivable
Processor (LSP) configuration and no gateways or IP endpoints are registered with it.
●
The YELLOW LED provides active “in use” indication. For an S8300, the software turns
on the YELLOW LED during system startup, and turns off the LED during shutdown.
During normal call processing operation, the YELLOW LED turns on whenever a G700
Media Gateway, an IP station, or an IP console is registered with the S8300. Likewise, it
turns off when none of the IP endpoints are registered.
Table 75: Major alarm (red LED) on page 285 through Table 79: ENET Link/Activity (green
LED) on page 287 illustrate the states of S8300 LEDs.
Table 75: Major alarm (red LED)
Major alarm
Indicator
Power on Reset
On
BIOS Boot
On
OS and SW Boot
On
System Up
Off - SW
H.248 Registered
Off - SW
Shutdown in Progress
On
Shutdown Complete
On
Issue 1 June 2005
285
LEDs
Table 76: Test – Avaya Communication Manager status (green LED)
Test – To Be Defined
Power On Reset
Off
BIOS Boot
Off
OS and SW Boot
On-SW
System Up
Off - SW
Avaya Communication Manager Running
On
H.248 Registered
Off - SW
Shutdown in Progress
Off - SW
Shutdown Complete
Off
Table 77: Active – In Use (yellow LED)
Active – In Use
Power On Reset
Off
BIOS Boot
Off
OS and SW Boot
Off
System Up
SW
H.248 Registered
On-SW
Shutdown in Progress
Off-SW
Shutdown Complete
Off
Table 78: OK to Remove (green LED)
OK to Remove
Power On Reset
Off
BIOS Boot
Off
OS and SW Boot
Off
System Up
Off
1 of 2
286 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
S8300 Media Server LEDs
Table 78: OK to Remove (green LED) (continued)
OK to Remove
H.248 Registered
Off
Shutdown in Progress
1 Hz flash
Shutdown Complete
On
2 of 2
Table 79: ENET Link/Activity (green LED)
ENET Link/Activity
Power On Reset
Off
BIOS Boot
N/A
OS and SW Boot
N/A
System Up
Link Status
H.248 Registered
Link Status
Shutdown in Progress
Unknown
Shutdown Complete
Off
S8300 LED lighting sequence
In general, S8300 LEDs light in order from top to bottom, then from left to right on the S8300
faceplate.
The following order applies during restart or boot of the S8300:
1. ALM - RED: lights up first then turns off.
2. TST - GREEN: lights up second then turns off.
3. ACT - YELLOW: lights up third then turns off.
4. OK To REMOVE - GREEN: lights up fourth then turns off.
5. LEFT LED in SERVICES jack - GREEN (10 MB link speed): lights up fifth then turns off.
6. LEFT LED in SERVICES jack - YELLOW (100 MB link speed): lights up sixth then turns off.
7. RIGHT LED in SERVICES jack - GREEN: lights up seventh then turns off.
Issue 1 June 2005
287
LEDs
G700 and Media Module LEDs
LEDs are important status indicators for technicians during on-site installation, maintenance,
troubleshooting, and repair. They encompass three major areas: Alarms, Testing, and Usage
Activity. Some LEDs are specialized to support specific procedures (such as removing the
S8300 Media Server). When alarms or problems occur, LEDs are present to indicate that
attention by a technician is needed.
LEDs appear on the G700 LED panel, and each Media Module. The G700 LEDs are the same
as those on the Avaya Cajun P330, with the following exceptions:
●
Slight modifications to two of the LEDs (OPR and SYS)
●
Addition of the Alarm LED to the LED Panel to display prominently any error condition
See “Table 2-1: Avaya P333T LED Description, in the "Avaya P333T User’s Guide" for a
complete listing of LEDs.
Some Media Modules have additional LEDs, although each Media Module has the three
standard LED. Table 80: LED Interpretation on page 288 indicates the meanings associated
with standard DEFINITY server LEDs. Although in some cases these LEDs have been
augmented or modified for the S8300 Media Server and G700 Media Gateway, it is important to
be aware of their standard meanings when viewing the system.
Table 80: LED Interpretation
Note:
Note:
Red
Upon power-up or module insanity, this LED is turned on. Upon passing
diagnostics, this LED is turned off.
Green
During power-up self testing and maintenance testing, this LED is turned on.
Yellow
This LED indicates that the module is in service.
Note:
The four multi-color specialized status LEDs that have appeared on various
DEFINITY server TN boards like the T1/E1/DS1 board (TN464) do not appear on
the Media Modules.
Note:
LEDs can also be viewed using the embedded Device Manager on the L2
Switching Processor; however, it displays LED position only, and does not
indicate status.
288 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
G700 and Media Module LEDs
LED panel location on the G700
As shown in Figure 15: G700 LED Panel Location on page 289, the LED panel is located on
the top left corner of the G700. Directly below the LED panel is Media Module slot V1, which can
be occupied by any type of Media Module. However, the S8300 Media Server can reside only in
this particular slot because of height restrictions (for a specific discussion of the S8300 LEDs,
see S8300 Media Server LEDs on page 283.
Figure 15: G700 LED Panel Location
3
ALM PWR CPU MSTR
V1
1
ALM
TST
ACT
OK TO
REMOVE
LNK COL
Tx
Rx
FDX
6
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
V2
FC Hspd LAG
EXT 1 EXT 2
SHUT DOWN
2
SERVICES
USB 1
SO
ALM
TST
ACT
SIG
EI
SM EM
SI
EO
E1/T1
V3
USB 2
V4
EXT 1
EXT 2
4
EIA 530A DCE
ALM
TST
ACT
7
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
ALM
TST
ACT
CONSOLE
9
5
msdcs830 KLC 031402
8
Figure notes:
1.
Media Module Slot #1 (V1)
5.
10/100 BaseT Ethernet Ports (Ext1,
Ext2)
2.
S8300 Services Port (Used with
cross-over ethernet cable)
6.
Media Module Slot #2 (V2)
3.
S8300 USB Series Modem
connection
7.
Media Module Slot #3 (V3)
4.
Avaya Expansion Module Slot
8.
Media Module Slot #4 (V4)
9.
Console Interface (use with serial
cable)
Figure 16: G700 LED Panel on page 290 shows an expanded view of the G700 LED panel.
Issue 1 June 2005
289
LEDs
Figure 16: G700 LED Panel
51
ALM PWR CPU MSTR
LNK COL
Tx
Rx
FDX
52
V1
ALM
TST
ACT
OK TO
REMOVE
LNK COL
Tx
Rx
FDX
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
FC Hspd LAG
V2
EXT 1 EXT 2
V3
USB 1
55
SO
ALM
TST
ACT
SIG
60
EI
61
SM EM
62
V4
EXT 2
57
58
SI
64
65
66
EO
EIA 530A DCE
ALM
TST
ACT
USB 2
EXT 1
56
63
E1/T1
SHUT DOWN
SERVICES
54
EXT 1 EXT 2
59
ALM PWR CPU MSTR
53
FC Hspd LAG
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
ALM
TST
ACT
CONSOLE
msdcled2 KLC 031402
290 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
G700 and Media Module LEDs
Front panel LEDs
The front panel includes the following LEDs (Figure 17: G700 Front Panel LEDs on page 291):
●
4 LEDs in Voice/Data Module zone (ALM, PWR, CPU, MSTR)
Note:
The LEDs labeled OPR and SYS on the P330 are labeled CPU and MSTR,
respectively, on the G700.
Note:
●
16 LEDs representing the Data Ports associated with the Personality Module or Data
Expansion Ports
●
8 LEDs in Data Function zone (LNK, COL, Tx, Rx, FDX, FC, Hspd, LAG)
●
2 LEDs (EXT 1 and EXT 2) for two 10/100 Mb data ports on the chassis
Note:
The four LEDs (ALM, PWR, CPU, MSTR) are positioned as closely as possible to
the top left corner of the LED Panel so that important motherboard-related
information can be quickly located by the service technician.
Note:
Figure 17: G700 Front Panel LEDs
51
ALM PWR CPU MSTR
LNK COL
Tx
Rx
FDX
52
53
54
55
56
57
58
FC Hspd LAG
EXT 1 EXT 2
59
60
61
62
63
64
65
66
ledcled KLC 031402
A total of 30 LEDs appear on the LED Panel for the G700. The following three LEDs have been
added to the Avaya Cajun LEDs (see “Avaya P330 Manager User Guide”):
●
RED ALM or Alarm LED
●
EXT 1 LED
●
EXT 2 LED
The G700 MSTR LED differs from the Avaya Cajun LED in that the bottom G700 in a stack of
10 G700s with the same version firmware is always elected master (therefore, its MSTR light is
lit). But, if the firmware versions are not the same, the G700 with the latest firmware version is
elected master and its MSTR light is lit. If there is only one G700 in a stack, its MSTR light is
always lit.
Issue 1 June 2005
291
LEDs
Navigating using the front panel LEDs
Navigation using the front panel LEDs on the G700 is that same as with the Avaya Cajun P330
series. “Table 2-2: Avaya P330 <--> Select buttons, in the "Avaya P333T User’s Guide". For
example, a technician can use the arrows to move left and right between the LEDs, and check
the following:
●
LNK (link)
●
Col (collision)
●
Tx (send)
●
Rx (receive)
In addition, a technician can query the status of the ports using 51-66 in the LED panel.
Use the push buttons (on the right and left of data mode LEDs) for selecting the function to be
reported simultaneously by all 16 of the Port data expansion LEDs. The function you are
selecting is indicated by a lightened LED in that Function zone. Each time you press on the right
(or on the left) push-button, the function currently lighted moves by one to the right (or to the left)
accordingly.
For example, if the COL LED is lit, all 16 Ports associated with the data expansion module LEDs
are reporting the Collision status of their respective port. If you want to select the LAG function,
press 6 times on the right push-button. Afterwards, if you want to select the Rx function, press 4
times on the left push-button.
For the G700, the LEDs display the information of ports 2 External 10/100Base-T Ethernet links
and data expansion ports 51-66. At power up the LEDs indicate the Link status of ports 51-66
and ext 1 & ext 2. Push the right button once to move the indication to Collision status of ports
51-66 and ext 1 & ext 2. Push the left button to move the indication backwards.
Note:
Note:
Eight pushes in one direction complete a full cycle of display.
If you press the right and the left push buttons simultaneously for:
Note:
●
1.5sec, the module resets the Layer 2 Switching Processor but not the Media Gateway
Processor
●
4 sec, the whole stack resets (performing slot renumbering)
●
18sec, the module enters the debug mode – module disabled for data traffic
Note:
Currently, there is no physical button or sequence of button presses defined to
reset the Media Gateway Processor or G700. Complete software resets by using
the Command Line Interface (CLI) for the Device Manager of the G700.
292 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
G700 and Media Module LEDs
RED ALM or Alarm LED
The RED ALM or Alarm LED is on the top-left most corner of the LED Panel next to other
important system LEDs (PWR, CPU, MSTR), as specified in Figure 17: G700 Front Panel
LEDs on page 291. The presence of this RED ALM LED is primarily for on-site service
technicians or dispatches. It alerts technicians of major failures that require a physical
replacement or removal of equipment. Most major G700 components controlled or monitored by
the motherboard can be a cause of illumination. This includes the Avaya VoIP Media Module,
but not other Media Modules.
Note:
The RED ALM LED lights for motherboard problems only. Check for a RED ALM
LED for problematic G700s and also check all of the Media Module LEDs for any
Media Module specific RED ALM LEDs.
Note:
Note:
If the RED ALM LED is lit on a non-VoIP Media Module, check the G700 alarm
screens and the Avaya Communication Manager alarm screens to determine
where the fault lies.
Note:
The RED ALM LED indicates the health of the G700 by lighting under two distinct
circumstances:
●
●
G700 hardware failure
●
Impaired functions of the Layer 2 Switching Processor, Media Gateway Processor, or
VoIP engine
●
Power supply voltage out of bounds
●
Unit overheating
The G700 cannot communicate to any server
The following are a few examples:
●
The RED ALM LED is lighted when two or more fans have failed.
Various warnings, alarms, and a graceful shutdown are performed based on the fan and
thermal sensor conditions.
●
The RED ALM LED is lit from the time power is applied until diagnostics end.
●
The RED ALM LED turns “OFF” when:
●
Physical conditions such as temperature are rectified and return to normal or acceptable
operating ranges.
●
The alarm is cleared manually.
Issue 1 June 2005
293
LEDs
EXT 1 LED
EXT 1 LED appears on the LED Panel (Figure 17: G700 Front Panel LEDs on page 291),
which reports the status of the first 10/100 MB/sec port (these LEDs report the 8 different
functional statuses dictated by the left and right arrow buttons).
EXT 2 LED
EXT 2 LED appears on the LED Panel (Figure 17: G700 Front Panel LEDs on page 291),
which reports the status of the second 10/100 MB/sec port (these LEDs report the 8 different
functional statuses dictated by the left and right arrow buttons).
G700 LED panel definitions
Table 81: LED Definitions on page 294 illustrates the LED definitions for the G700 LED Panel.
Table 81: LED Definitions
No.
LED Name
Description
LED States
1
ALM
Alarm Status
Color is RED
OFF - No alarms exist
ON (RED) - Alarm exists on the chassis itself
2
PWR
Alarm Status
Color is
GREEN
OFF - Power is down
ON - Power is up
Blinking - every 1.2 seconds (400ms on, 800ms off)
when 5 volts power is not available to the riser
board and the Media Modules
3
CPU
CPU Operation
Color is
GREEN
OFF - CPU is in boot operation or is running BIST
ON - CPU boot operation and BIST completed
4
MSTR
Master/Slave
Status Color is
GREEN
OFF - Slave box of the stack
ON - Master of the stack and redundant cable is not
present or not active
1 Blink every 1.5 sec - Master of the stack and
active redundant cable
a
LNK port
51-66, Ext
1-2
Port Status
Color is
GREEN
OFF - Port disabled or not existent. At phase 1, or
link fail of Giga ports.
ON - Port is enabled and link is OK.
1 Blink every 1.5 sec - Link test fail (of 10/100M
ports only at phase 1)
2 Blinks every 1.5 sec - Partition
b
COL
Port 51-66,
Ext 1-2
Collision
(GREEN)
OFF - No collision or FDX port
ON - Collision occurred on line
5
1 of 2
294 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
G700 and Media Module LEDs
Table 81: LED Definitions (continued)
No.
LED Name
Description
LED States
c
Tx
Port 51-66,
Ext 1-2
Transmit to line
(GREEN)
OFF - No transmit activity
ON - Data transmitted on line
d
Rx
Port 55-66,
Ext 1-2
Receive from
line
(GREEN)
OFF - To receive activity
ON - Data received from the line
e
FDX
Port 51-66,
Ext 1-2
Half/Full
Duplex
(GREEN)
OFF - Half Duplex mode of operation
ON - Full Duplex mode of operation, or for 10/
100Base-T ports when link test fail with
auto-negotiation enabled
f
FC*
Port 51-66,
Ext 1-2
Symmetric
Flow Control
(GREEN)
OFF - Port is in an Asymmetric Flow control mode,
or in Flow Control mode disabled, or it is in half
duplex
ON - Port is in full duplex and in a symmetric Flow
Control mode
g
HSpd
Port 51-66,
Ext 1-2
High Speed
(GREEN)
OFF - 10Base-T or for an expansion port that does
not exist
ON - 100Base-T, 100Base-F, 1000Base-X, and
OC-12, or for 10/100Base-T ports when link test fail
with auto-negotiation enabled
h
LAG
Port 51-66,
Ext 1-2
Link
Aggregation
"Trunking"
(GREEN)
OFF - No LAG defined with this port
ON - Port belongs to a LAG
6
Data
16 data
expansion ports
51-66
(GREEN)
OFF - see notes on No. 5 a-h
ON - see notes on No. 5 a-h
7
EXT 1
RJ 45 to
Non-Avaya
equipment
(GREEN)
OFF - see notes on No. 5 a-h
ON - see notes on No. 5 a-h
8
EXT 2
RJ 45 to
Non-Avaya
equipment
(GREEN)
OFF - see notes on No. 5 a-h
ON - see notes on No. 5 a-h
* For Giga ports, when auto-negotiation is enabled and the link is down, FC LED reflects the last mode
If the user resets the module/stack, then all of the module’s/stack’s LEDs light on (test lamp) for 150ms.
The COL, Tx, and Rx LED signals must be at least 150ms.
2 of 2
Issue 1 June 2005
295
LEDs
Media Module LEDs
Media Gateway physical LEDs provide the technician with information regarding the ability to
troubleshoot the Media Module as a whole.
Note:
Note:
The physical LEDs provide board level status information, while the SAT provides
port level status information.
LED Locations on the Media Modules
All Media Modules have three standard LEDs on the faceplate (Figure 18: Faceplate of Media
Modules with Standard LEDs on page 296). On the Avaya VoIP (MM760), Avaya BRI (MM720),
Avaya DCP (MM712), and Avaya Analog (MM711) Media Modules, these are the only LEDs
present. In addition, the Avaya T1/E1 Media Module (MM710) has an additional LED, as shown
in Figure 19: T1/E1 Media Module with Fourth LED on page 296.
Figure 18: Faceplate of Media Modules with Standard LEDs
ALM
TST
ACT
1
2
3
4
5
6
7
8
mmdc712 KLC 022702
Figure 19: T1/E1 Media Module with Fourth LED
SO
ALM
TST
ACT
SIG
E1/T1
EI
SM EM
SI
EO
EIA 530A DCE
mmdc710 KLC 020402
296 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
G700 and Media Module LEDs
MM710 T1/E1 Media Module LEDs
The T1/E1 Media Module has four LEDs on its faceplate (see Figure 20: T1/E1 Media Module
LEDs on page 297). Table 82: T1/E1 LEDs on page 297 shows their color and functions. The
first three are the standard LEDs, which are under software control.
Table 82: T1/E1 LEDs
Name
Color
Location
Description
ALM
RED
Top
Upon power-up, this LED is turned on. Upon passing
diagnostics this LED is turned off. During normal circuit pack
operation this LED is not turned on except for certain alarm
states.
TST
GREEN
Second
During power-up self-testing and maintenance testing
requested by the SPE, this LED is turned on.
ACT
YELLOW
Third
This LED indicates that the clock is synchronized with a
source (usually the Central Office). The LED is blinking 2700
ms ON and 300 ms OFF. This is the most common condition.
The opposite blinking of the YELLOW LED is 300 ms ON and
2700 ms OFF. This is an error condition, and indicates that
the MM710 T1/E1 Media Module is not synchronized with a
clock.
An infrequent occurrence is a steady YELLOW LED. This
indicates in-use activity, only when clock synchronization is
set to local.
SIG
GREEN
Bottom
This LED indicates whether the link to the Central Office (CO)
is up (equivalent to the TN464 circuit pack Status 3 GREEN
LED). See Figure 20: T1/E1 Media Module LEDs on
page 297.
Figure 20: T1/E1 Media Module LEDs
SO
ALM
TST
ACT
SIG
E1/T1
EI
SM EM
SI
EO
EIA 530A DCE
mmdc710 KLC 020402
Issue 1 June 2005
297
LEDs
The supported portion of the LED control message allows software to change the status of the
three standard LEDs on the T1/E1 Media Module faceplate. Power-up and alarm states are the
only conditions where hardware sets the state of the LEDs independent of ANGEL firmware
control.The exceptions to letting software turn off the LEDs are:
●
The board is in reset (RED ALM LED remains on)
●
A call is up (YELLOW ACT LED remains on while the E1 line is in-frame and at least one
voice/data call is up)
●
During board reset initialization testing (GREEN TST LED remains on until initialization
testing is complete)
Note:
For ISDN operation, the Yellow LED will be turned on if ANY port has an active
TDM connection (including the D-channel).
Note:
Synchronization
The YELLOW ACT LED on the front of the MM710 Media Module can tell you the status of that
module regarding synchronization.
●
If the YELLOW ACT LED is solidly on or off, it has NOT been defined as a synchronization
source. If it is on, one or more channels is active. If it is an ISDN facility, the D-channel will
count as an active channel and will cause the YELLOW ACT LED to be on.
●
When the MM710 is driving a clock sync source line to the G700 main clock, the YELLOW
ACT LED does not indicate port activity, but instead indicates that the MM710 is the sync
source by flashing with a regular 3-second period:
●
It is on for 2.8 seconds and flashes off for 200 milliseconds if it has been specified as a
sync source and is receiving a signal that meets minimum requirements for the interface.
●
If it has been specified as a sync source and is not receiving a signal, or is receiving a
signal that does not meet minimum requirements for the interface, then the YELLOW
ACT LED will be off for 2.8 seconds and flash on for 200 milliseconds.
T1/E1 Initialization
The T1/E1 Media Module LEDs behave in the following manner during initialization. The Angel
provides a visual indication of the Media Module’s status through the three faceplate LEDs:
●
During initialization the YELLOW ACT LED is held off, while the RED and GREEN LEDs
are on during the entire initialization sequence.
●
Upon power up or reset, if only the RED ALM LED comes on, the Angel processor is dead
or the board is being held permanently in reset.
●
Upon completion of the diagnostics and initialization, the GREEN TST LED turns off.
●
If the initialization tests fail, the RED ALM LED remains on.
●
If the tests all pass, then all LEDs are extinguished until Communication Manager starts
using the Media Module.
298 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
G700 and Media Module LEDs
Operational control
After successful initialization, the T1/E1 Media Module’s LEDs are controlled as follows:
●
The Angel lights the YELLOW ACT LED when there is at least one non-idle trunk. If
Communication Manager sends a message to drive the clock sync signals, the YELLOW
ACT LED indicates this instead of the port busy/idle status.
●
The Media Server may independently light and extinguish the three LEDs through
downlink LED Control messages, subject to the constraint that it may not turn off a
YELLOW ACT LED turned on by the Angel as a result of port activity.
●
If the Media Module resets for any reason and is not released from reset, the RED ALM
LED lights and the YELLOW ACT and GREEN TST LEDs are held off.
Issue 1 June 2005
299
LEDs
300 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Chapter 4: G700 Media Gateway Traps
This chapter applies to the G700 Media Gateway only.
SNMP Alarming on the G700
Setting up SNMP alarm reporting involves two main tasks:
●
Configure the primary server to report alarms
●
Configure the G700 to Send its Traps to the Primary Server
Configure the primary server to report alarms
The primary server may be either an S8300 Media Server or an S8700 Media Server. The
Media Server supports two methods for reporting alarms. Either method, both, or no
alarm-reporting method may be used at a given site.
●
OSS Method. The server's software applications and hardware devices under its control
can generate Operations Support System (OSS) alarms. These alarms are recorded in the
server logs, and may be reported to Avaya's Initialization and Administration System
(INADS) or another services support agency over the server's modem interface.
To activate OSS alarm notification: The server requires a USB connection to a modem that
is connected to an analog line. The modem must be configured using the Web Interface, in
the Set Modem Interface screen, and enabled to send and receive calls using the Enable/
Disable Modem screen. Configuration of the OSS alarming method can only be done
using Linux shell commands.
●
SNMP Method. SNMP traps may be sent in User Datagram Protocol (UDP) to a corporate
network management system (NMS) using the Configure Trap Destinations screen. The
OSS and SNMP alarm-notification methods operate independently of each other. Either or
both may be used. Currently, the following NMSs are supported:
●
Avaya Communication Manager Fault and Performance Manager, as a standalone
application, or integrated within
●
Avaya MultiService Network Manager
●
HP Openview
To activate SNMP alarm notification: On the server Web Interface, use the Configure Trap
Destinations screen to set up SNMP destinations in the corporate NMS.
Issue 1 June 2005
301
G700 Media Gateway Traps
Add INADS Phone Numbers and Enable Alarms to INADS
The following procedure using the primary server’s Linux shell commands administers the
dial-out modem to send alarms in the OSS method. In this example, the primary server is an
S8300, and the services support agency is Avaya’s Initialization and Administration System
(INADS).
Perform this task after all Communication Manager administration is complete.
To add INADS phone numbers and enable alarms to INADS
1. Connect your laptop to the Services port of the S8300 Media Server
Note:
Do these steps only if the S8300 is the primary controller and the customer has a
maintenance contract with Avaya. Use the information acquired from the ART
tool (see “Run the ART Tool for the INADS IP Address” in Chapter 3 of
"Installation and Upgrades for the Avaya G700 Media Gateway Controlled by an
Avaya S8300 or S8700 Media Server, 555-234-100"). Also, a USB modem must
have already been installed. See "Universal Serial Bus (USB) Modems" in
Chapter 7 of the same source.
Note:
2. Click Start > Run to open the Run dialog box
3. Type telnet 192.11.13.6 and press Enter.
4. Log in as craft.
5. At the prompt, type almcall -f INADS phone number -s second-number and press
Enter.
6. At the prompt, type almenable -d b -s y and press Enter.
7. Type almenable and press Enter to verify that the alarms are enabled.
8. Log off.
Configure the G700 to Send its Traps to the Primary Server
Configuring the G700 Media Gateway to send SNMP traps to the primary server can be
accomplished by two commands:
●
Layer 2 Switching Processor CLI command: set snmp community trap [community
string]
●
Media Gateway Processor (MGP) CLI command: set snmp trap <IP address>
enable
Configure an SNMP community string for traps
SNMP requires community strings to be used for each SNMP "request". You can set only three
community strings on the G700 — one each for read requests, write requests, and traps. The
command for traps is set snmp community trap [community string].
302 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
SNMP Alarming on the G700
To configure an SNMP community string for traps
1. Open the Run dialog box.
2. Type telnet <IP address of L2 Processor> and press Enter.
3. Log in as root.
4. At the L2 Processor CLI prompt, type set snmp community trap [community
string] and press Enter.
5. Type exit
Configure the destination for G700 SNMP traps
Events occurring on the G700 cause SNMP traps to be generated. The G700 MGP can be
configured to send SNMP traps to any network management system (NMS) in the network,
including the primary server (S8300/S8700). The MGP CLI set snmp trap command is the
way to configure the NMS network element that will receive those traps. The traps are sent in
User Datagram Protocol (UDP) on the customer’s IP network.
The command syntax is:
set SNMP trap <IP address> {enable|disable}
[{all|power|temp|app|module|config|voice|operations}]
where <IP address> is the IP address of the NMS trap receiver that will be receiving the
traps from the G700, and
[{all|power|temp|app|module|config|voice|operations}] indicates the groups
whose traps will be sent to the specified receiver. If no keywords follow the IP address entry,
then all traps will be enabled for the specified receiver.
If "enable" or "disable" is used without a trap designation keyword, then all traps is
assumed. Up to ten trap receivers can be configured.
To configure the destination for G700 SNMP traps
1. From the L2 Processor CLI, type session mgp
2. At the mg-xxx-n(super-user) prompt, type configure and press Enter.
3. At the mg-xxx-n(configure) prompt, type set snmp trap <IP address> enable and
press Enter.
4. Type exit
Issue 1 June 2005
303
G700 Media Gateway Traps
G700 Alarm Format
G700 Media Gateways (serving either as standalone port networks, or as port networks within
an IP or a Multi-Connect system) report alarms to the primary server (either an S8300 or S8700
Media Server) using SNMP traps. Like the primary server’s own alarms, alarms from a G700
Media Gateway:
●
Reside in the primary server’s alarm log
●
Can be viewed using the SAT command display alarms
●
Can be viewed using the Web Interface Display Alarms option
However, the format of these displayed alarms is slightly different. Using the G700 MO’s
Event ID #1 (the first entry in Table 83: G700 Alarms (SNMP Traps) to the Primary Media
Server on page 305) as an example, a displayed G700 alarm has the following format:
n CMG 1 WRN 07/17/2002:13:45 121.1.1.2:cmgMultipleFanFault
Within the previous alarm-display string, the value:
●
“n” is a sequential alarm ID.
●
“CMG” identifies a G700 Media Gateway as the MO.
●
“1” is the event’s ID (1st column of Table 83: G700 Alarms (SNMP Traps) to the Primary
Media Server on page 305).
This table also contains each alarm’s corresponding SNMP trap # in the 2nd column of
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server on page 305. However,
many of the MIB-defined traps have been excluded, either because:
●
A specific trap (such as, Trap #3) is the SNMP mechanism to clear an alarm logged by
another specific trap (in this case, Trap #2).
●
The specific event indicated by a trap is not severe enough to justify an entry in the
primary server’s alarm log.
●
A trap is defined, but not implemented.
●
A trap # is reserved for future use.
●
“WRN” is the event’s severity (3rd column of Table 83: G700 Alarms (SNMP Traps) to the
Primary Media Server on page 305).
●
“07/17/2002:13:45“is the event’s date and time stamp.
●
“121.1.1.2“is the IP address for Telnet access to the alarmed G700 Media Gateway
Processor (MGP).
●
“cmgMultipleFanFault” is an alarm description (4th column of Table 83: G700 Alarms
(SNMP Traps) to the Primary Media Server on page 305).
304 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
G700 Traps and Resolutions
G700 Traps and Resolutions
Although these alarms can be viewed from the primary server, they are normally resolved from
within the G700 Media Gateway. The G700 generates the following traps. Follow the error
resolution procedures in Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server on
page 305 to resolve errors indicated by these traps.
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
1
2
WRN
cmgMultipleFanFault — At least two G700 fans have been
operating at less than 90% of their nominal speed for >= 5 minutes.
(This may be an early warning of overheating.)
1. Verify there are faults in the system. Use the Avaya G700
Media Gateway Processor (MGP) Command Line Interface
(CLI) command show faults to display any faults on the
G700.
2. If there is a fan/temperature fault, check to see if the fans are
working, and/or if there is sufficient space around the G700 for
air circulation.
3. Maintenance software monitors voltages applied to the Media
Modules and other components of the G700, and compares
these to the general power supply unit (PSU) status bit. If none
of these voltages are out of tolerance, but the PSU status
indicates failure, this generates the fan fault, which will be
indicated in the show faults command output. Replace the
entire G700. Fans and the PSU are not field replaceable.
1 of 20
Issue 1 June 2005
305
G700 Media Gateway Traps
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
2
4
MIN
cmgPsuBriefFanFault — A G700’s PSU fan has been operating at
less than 90% of its nominal speed for between 5 and 15 minutes.
(This may be an early warning of overheating.)
1. Verify there are faults in the system. Use the Avaya G700
Media Gateway Processor (MGP) Command Line Interface
(CLI) command show faults to display any faults on the
G700.
2. If there is a fan/temperature fault, check to see if the fans are
working and/or if there is sufficient space around the G700 for
air circulation.
3. Maintenance software monitors voltages applied to the Media
Modules and other components of the G700, and compares
these to the general power supply unit (PSU) status bit. If none
of these voltages are out of tolerance, but the PSU status
indicates failure, this generates the fan fault, which will be
indicated in the show faults command output. Replace the
entire G700. Fans and the PSU are not field replaceable.
3
6
MIN
cmgPsuProlongedFanFault — A G700’s fan has been operating at
less than 90% of its nominal speed for >= 15 minutes. (This may be
an early warning of overheating.)
1. Verify there are faults in the system. Use the Avaya G700
Media Gateway Processor (MGP) Command Line Interface
(CLI) command show faults to display any faults on the
G700.
2. If there is a fan/temperature fault, check to see if the fans are
working and/or if there is sufficient space around the G700 for
air circulation.
3. Maintenance software monitors voltages applied to the Media
Modules and other components of the G700, and compares
these to the general power supply unit (PSU) status bit. If none
of these voltages are out of tolerance, but the PSU status
indicates failure, this generates the fan fault, which will be
indicated in the show faults command output. Replace the
entire G700. Fans and the PSU are not field replaceable.
2 of 20
306 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
G700 Traps and Resolutions
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
4
10
MIN
cmgCpuTempWarningFault — A G700’s CPU temperature sensor
has exceeded its warning threshold.
1. Verify there are faults in the system. Use the Avaya G700
Media Gateway Processor (MGP) Command Line Interface
(CLI) command show faults to display any faults on the
G700.
2. If there is a temperature fault, turn off the G700 and allow it to
cool.
3. Reboot the G700. Check to see if the fans are working and/or if
there is sufficient space around the G700 for air circulation. Use
the MGP CLI show faults command to check for fan
problems.
4. Low voltage may be responsible for slower fans. Voltage may
be reduced by a short in one of the Media Modules or a bad
power supply. If there are no fan faults, use the MGP CLI
command show voltages to display voltages applied to
components on the motherboard and to the Media Modules.
5. If the Media Module voltage is out of tolerance, systematically,
remove each Media Module to determine if one of the Media
Modules is responsible for reducing the voltage level. If one is
found, replace the Media Module.
6. If no Media Module is found to be bad, the power supply is
suspect. Replace the G700.
3 of 20
Issue 1 June 2005
307
G700 Media Gateway Traps
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
5
12
MIN
cmgDspTempWarningFault — The temperature sensor in a G700’s
DSP complex has exceeded its warning threshold.
1. Verify there are faults in the system. Use the Avaya G700
Media Gateway Processor (MGP) Command Line Interface
(CLI) command show faults to display any faults on the
G700.
2. If there is a temperature fault, turn off the G700 and allow it to
cool.
3. Reboot the G700. Check to see if the fans are working and/or if
there is sufficient space around the G700 for air circulation.
4. Low voltage may be responsible for slower fans. Voltage may
be reduced by a short in one of the Media Modules or a bad
power supply. If there are no fan faults, use the MGP CLI
command show voltages to display voltages applied to
components on the motherboard and to the Media Modules.
5. If the Media Module voltage is out of tolerance, systematically,
remove each Media Module to determine if one of the Media
Modules is responsible for reducing the voltage level. If one is
found, replace the Media Module.
6. If no Media Module is found to be bad, the power supply is
suspect. Replace the G700.
4 of 20
308 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
G700 Traps and Resolutions
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
6
14
MAJ
cmgTempShutdownFault — The temperature sensor in a G700’s
CPU has exceeded its shutdown threshold. The system is about to
begin controlled shutdown.
1. Verify there are faults in the system. Use the Avaya G700
Media Gateway Processor (MGP) Command Line Interface
(CLI) command show faults to display any faults on the
G700.
2. If there is a temperature fault, turn off the G700 and allow it to
cool.
3. Reboot the G700. Check to see if the fans are working and/or if
there is sufficient space around the G700 for air circulation.
4. Enter the MGP CLI command show voltages to determine
voltages for Media Modules and other components of the
G700. While the +12V fan supply is not directly monitored, it is
included in the general power supply unit (PSU) status bit. Use
the show faults command to determine if there is a fan
problem. If none of the monitored voltages are out of tolerance,
but the PSU status indicates failure, this would generate a fan
fault. If fans are faulty, then replace the entire G700. Fans are
not field replaceable.
5. Voltage may also be reduced by a short in one of the Media
Modules. Systematically, remove each Media Module to
determine if one of the Media Modules is responsible for
reducing the voltage levels.
5 of 20
Issue 1 June 2005
309
G700 Media Gateway Traps
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
7
16
MAJ
cmgMgpPowerFault — The voltage reading at the server’s +5.1V
power source is out of tolerance.
1. Check voltages. Enter the MGP CLI command show
voltages to determine voltages for Media Modules and other
components of the G700. Voltage may be reduced by a short in
one of the Media Modules or a bad power supply.
2. Systematically, remove each Media Module to determine if one
of the Media Modules is responsible for reducing the voltage
levels. Replace faulty Media Module.
3. If the alarm clears in 10-20 seconds, it was a probable voltage
spike. Do not replace the G700. Use a power monitor to
monitor the power line.
4. If a brown-out condition is suspected, use a power monitor to
monitor the power line.
5. If the fault persists and the show voltages command
continues to show the level is out of tolerance, then replace the
G700.
8
18
MAJ
cmgMediaModulePowerFault — The voltage reading at the Media
Modules’ -48V power source is out of tolerance.
1. Check voltages. Enter the MGP CLI command show
voltages to determine voltages for Media Modules and other
components of the G700. Voltage may be reduced by a short in
one of the Media Modules or a bad power supply.
2. Systematically, remove each Media Module to determine if one
of the Media Modules is responsible for reducing the voltage
levels. Replace faulty Media Module.
3. If the alarm clears in 10-20 seconds, it was a probable voltage
spike. Do not replace the G700. Use a power monitor to
monitor the power line.
4. If a brown-out condition is suspected, use a power monitor to
monitor the power line.
5. If the fault persists and the show voltages command
continues to show the level is out of tolerance, then replace the
G700.
6 of 20
310 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
G700 Traps and Resolutions
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
9
20
MAJ
cmgVoipPowerFault — The voltage reading at the VoIP complexes’
+3.4V power source is out of tolerance.
1. Check voltages. Enter the MGP CLI command show
voltages to determine voltages for Media Modules and other
components of the G700. Voltage may be reduced by a short in
one of the Media Modules or a bad power supply.
2. Systematically, remove each Media Module to determine if one
of the Media Modules is responsible for reducing the voltage
levels. Replace faulty Media Module.
3. If the alarm clears in 10-20 seconds, it was a probable voltage
spike. Do not replace the G700. Use a power monitor to
monitor the power line.
4. If a brown-out condition is suspected, use a power monitor to
monitor the power line.
5. If the fault persists and the show voltages command
continues to show the level is out of tolerance, then replace the
G700.
10
22
MAJ
cmgDspPowerFault — The voltage reading at the DSP units’
+1.58V power source is out of tolerance.
1. Check voltages. Enter the MGP CLI command show
voltages to determine voltages for Media Modules and other
components of the G700. Voltage may be reduced by a short in
one of the Media Modules or a bad power supply.
2. Systematically, remove each Media Module to determine if one
of the Media Modules is responsible for reducing the voltage
levels. Replace faulty Media Module.
3. If the alarm clears in 10-20 seconds, it was a probable voltage
spike. Do not replace the G700. Use a power monitor to
monitor the power line.
4. If a brown-out condition is suspected, use a power monitor to
monitor the power line.
5. If the fault persists and the show voltages command
continues to show the level is out of tolerance, then replace the
G700.
7 of 20
Issue 1 June 2005
311
G700 Media Gateway Traps
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
11
24
MAJ
cmg8620PowerFault — The voltage reading at the VoIP
Processor’s +2.5V power source is out of tolerance.
1. Check voltages. Enter the MGP CLI command show
voltages to determine voltages for Media Modules and other
components of the G700. Voltage may be reduced by a short in
one of the Media Modules or a bad power supply.
2. Systematically, remove each Media Module to determine if one
of the Media Modules is responsible for reducing the voltage
levels. Replace faulty Media Module.
3. If the MM760 Media Module is not present, the VoIP engine on
the motherboard is possibly bad. Use the show faults
command to check for VoIP faults. Replace the G700.
4. If the alarm clears in 10-20 seconds, it was a probable voltage
spike. Do not replace the G700. Use a power monitor to
monitor the power line.
5. If a brown-out condition is suspected, use a power monitor to
monitor the power line.
6. If the fault persists and the show voltages command
continues to show the level is out of tolerance, then replace the
G700.
8 of 20
312 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
G700 Traps and Resolutions
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
14
30
MAJ
cmgSyncSignalFault — Synchronization signal lost.
1. Check that provisioned clock-sync source has a good signal by
issuing a Media Gateway Processor (MGP) Command Line
Interface (CLI) command show sync timing
Procedure for setting synchronization timing sources on T1/E1 MM
or MM710:
1. Be sure that the T1/E1 MM has been added properly on the
Avaya S8300 Media Server or Avaya S8700 Media Server,
otherwise go to System Access Terminal (SAT) and enter a
add DS1 command before going to the MGP CLI and entering
a set sync interface or set sync source command.
Otherwise the MGP CLI will not allow these commands to be
executed.
2. Go to the MGP’s CLI, and first specify the primary and
secondary clock sources for synchronizing the T1/E1 span,
using the set synch interface command.
Note: You don't specify the internal clock source from the CLI only the primary and secondary. The local clock is "built-in" and
not provisionable.
3. Enter a set sync source command to set to the specific
MM710 T1/E1 Media Module to be used as the active clock
reference.
4. Verify whether or not these commands were executed by
issuing a show sync timing command to ensure that the
source is provisioned and active, or visually inspect the Yellow
LED on the MM710 Media Module.
Note: When the Yellow LED is on 2.7 seconds and off 0.3
seconds, this means the tone-clock synchronizer is in “active”
mode, and an external synchronization source is being used as
a synchronization reference. Setting the sync timing was
successful.
When the Yellow LED is on 0.3 seconds and off 2.7 seconds,
this means the tone-clock synchronizer is in “active” mode and
the internal (on-board) clock is being used as a synchronization
reference. Setting the sync timing was not successful.
9 of 20
Issue 1 June 2005
313
G700 Media Gateway Traps
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
14
30
MAJ
(cont’d)
Description / Recommendation
5. Verify whether or not these commands were executed by
issuing a show sync timing command to ensure that the
source is provisioned and active, or visually inspect the Yellow
LED on the MM710 Media Module.
Note: When the Yellow LED is on 2.7 seconds and off 0.3
seconds, this means the tone-clock synchronizer is in “active”
mode, and an external synchronization source is being used as
a synchronization reference. Setting the sync timing was
successful.
When the Yellow LED is on 0.3 seconds and off 2.7 seconds,
this means the tone-clock synchronizer is in “active” mode and
the internal (on-board) clock is being used as a synchronization
reference. Setting the sync timing was not successful.
6. If there is more than one MM710 Media Module, and they have
been set up as primary and secondary, this behavior could be
on the second and not the timing of the bus.
For more details, please consult the maintenance documentation
under LEDs and T1/E1 Media Module, or see
http://support.avaya.com/elmodocs2/S8300/cd/index.htm
15
32
MAJ
cmgVoipHardwareFault — A DSP complex serving the VoIP
engines has failed.
1. Check IP configuration.
2. Reset or replace Media Module.
16
50
cmgModuleRemove — A Media Module has been removed.
51
Reserved
52
cmgModuleInsertFault — The insertion sequence for a Media
Module has failed.
53
cmgModuleInsertSuccess — A Media Module has been inserted.
54
cmgMgBusyout — An administrator has busied-out a Media Module
or a port.
55
cmgMgRelease — An administrator has returned a busied-out
media module or port back into service.
56 –
69
Reserved
10 of 20
314 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
G700 Traps and Resolutions
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
74
cmgFirmwareDownloadBegun — A Media Gateway began
downloading a software module.
75
cmgModuleManualReset — A Media Module is beginning a
user-requested reset operation.
76
cmgVoipManualReset — A VoIP engine is beginning a
user-requested reset operation.
77
cmgDsuManualReset — An E1 or T1’s DSU is beginning a
user-requested reset operation.
78
cmgConfigUploadBegun — A Media Gateway began uploading a
configuration file.
79
cmgConfigUploadSuccess — The Media Gateway successfully
uploaded the configuration file.
11 of 20
Issue 1 June 2005
315
G700 Media Gateway Traps
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
17
90
MAJ
cmgMemoryFault — The Media Gateway Processor has detected a
low processor memory condition. If an attempt by a software
module to allocate memory fails, or if available memory falls below
four million bytes, this trap is generated. If available memory later
rises above five million bytes, this trap is cleared. If available
memory falls below a half a million bytes, the Media Gateway
Processor is automatically reset.
1. Check the Media Gateway Processor and insure that it has the
latest version of firmware installed. If it does not, install the
latest version of firmware and continue to monitor.
2. If this trap occurs infrequently and is automatically cleared, the
trap may be due to an unusual transient condition. Monitor
future traps.
3. If this trap occurs frequently and is automatically cleared, it is
likely that the Media Gateway Processor software has the
wrong limits set for its memory monitoring. These limits are
hard coded in the software. Escalate.
4. If this trap occurs and does not clear, the Media Gateway may
be functionally impaired. Do not reset the Media Gateway.
Escalate and have Tier 3 personnel capture the trap
information and the event logs for analysis.
5. If this trap occurs and the Media Gateway Processor
automatically resets, then a severe processor memory
shortage occurred. Escalate and have Tier 3 personnel capture
the trap information and the event logs for analysis.
18
92
MAJ
cmgDhcpRequestFault — The Media Gateway cannot contact its
DHCP server, or the DHCP server did not respond to a request.
1. Either correct the DHCP problem, or correct the Media
Module’s configuration file.
12 of 20
316 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
G700 Traps and Resolutions
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
19
94
MAJ
cmgFirmwareDownloadFault — An attempt to download a software
module has failed.
1. Check the event log to find the specific error.
2. Troubleshoot the specific error according to the information
found.
For example, if the string “File not found” appears in the log,
then verify that the image file:
a. Exists
b. Has the correct name
c. Resides in the correct directory
20
96
WRN
cmgProcessRestart — a software module on the Media Gateway
Processor failed. The Media Gateway Processor will attempt to
restart the failing module. A successful restart of the module will
clear this trap
1. Check the Media Gateway Processor and insure that it has the
latest version of firmware installed. If it does not, install the
latest version of firmware and continue to monitor.
2. If this trap occurs infrequently and is automatically cleared, the
trap may be due to an unusual transient condition.Monitor
future traps.
3. If the trap occurs frequently and is automatically cleared, it may
indicate an issue with a particular software module. Reset the
Media Gateway at a time convenient with the customer.
Escalate and have Tier 3 personnel capture the trap
information and the event logs for analysis.
4. If the trap occurs and does not clear, the Media Gateway may
be functionally impaired. Reset the Media Gateway at a time
convenient with the customer and consistent with the
impairment. Escalate and have Tier 3 personnel capture the
trap information and the event logs for analysis.
13 of 20
Issue 1 June 2005
317
G700 Media Gateway Traps
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
21
98
MAJ
cmgIccMissingFault — An internal communications controller,
expected in Slot 1, is missing.
1. Check for presence of S8300.
2. If present, check the G700 administration.
3. If the administration is correct, suspect the S8300.
22
100
MAJ
cmgIccAutoReset — The Media Gateway automatically reset the
internal communications controller.
1. If the problem persists, escalate.
23
102
MAJ
cmgPrimaryControllerFault — The Media Gateway cannot contact
the first controller in its controller list.
1. Verify that the controller list is correct. From the MGP CLI, enter
the command show mgc list. The IP address should match
the S8700 Media Server CLAN or the S8300 Media Server IP
addresses.
2. If needed, correct this in 'configure' mode on the MGP's CLI by
clearing the mgc list first with the clear mgc list command,
and then issuing a set mgc list with the correct IP
addresses.
3. If so, verify that the primary controller is up.
4. If so, shut down every LSP.
24
104
MAJ
cmgNoControllerFault — The Media Gateway does not have any
controllers in its controller list.
1. Verify that the controller list is empty. From the MGP CLI, enter
the command show mgc list to verify that there are no
controllers listed.
2. If none are listed, correct this by adding the correct IP address
of the S8700/S8300. In 'configure' mode on the MGP's CLI,
enter the set mgc list command with the correct IP
address.
14 of 20
318 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
G700 Traps and Resolutions
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
25
106
MAJ
cmgRegistrationFault — The Media Gateway cannot register with
any controllers in its controller list.
1. Verify that the controller list is correct. From the MGP CLI, enter
the command show mgc list. The IP address should match
the S8700 Media Server CLAN or the S8300 Media Server IP
addresses.
2. If needed, correct this in 'configure' mode on the MGP's CLI by
clearing the mgc list with the clear mgc list command, and
then issuing a set mgc list with the correct IP addresses.
3. If the IP address in the mgc list matches the S8700 Media
Server CLAN or the S8300 Media Server IP addresses, there
may be a network problem.
4. Verify that the primary controller is up.
26
108
MIN
cmgH248LinkDown — An H.248 link between the Media Gateway
and its controller is down.
1. Check the S8300 or S8700.
2. If down, bring up.
3. If not, check the G700 administration.
Since the following command causes a brief service outage, it
should only be executed at the customer’s convenience.
4. If the administration is correct, reboot the G700.
5. If the problem persists, check network connectivity. Use ping
or traceroute to the S8300/S8700 to check connectivity.
6. If the problem persists, escalate.
15 of 20
Issue 1 June 2005
319
G700 Media Gateway Traps
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
29
114
WRN
cmgMgAutoReset — The Media Gateway Processor automatically
reset (rebooted). The processor automatically resets when a critical
error occurs from which it cannot recover. The error may be
software or hardware related. It may also automatically reset in
response to a maintenance test running on the call controller. (A
reset performed at the request of a SAT or CLI command entered
by craft or Tier technical support generates a different trap
indicating a manual reset.) Finally, it may automatically reset when
it reregisters with a call controller after being out of touch for too
long. This trap is generated as the Media Gateway Processor
comes back up after resetting. If the Media Gateway Processor
resets and fails to come back up, this trap will not be generated.
1. Check to see if a maintenance test that is supposed to reset the
processor was run.
2. Check that the reset was not due to the link with the call
controlling going down. If the reset is due to a link failure with
the call controller, follow call controller link failure
troubleshooting procedures.
3. Check the Media Gateway Processor and insure that it has the
latest version of firmware installed. If it does not, install the
latest version of firmware and continue to monitor.
4. If this trap occurs infrequently, the trap may be due to an
unusual transient condition. Monitor future traps.
5. If this trap occurs and the Media Gateway Processor is
frequently resetting, manually reset the media gateway.
Escalate and have Tier 3 personnel capture the trap
information and the event logs for analysis.
6. If this trap occurs frequently and the Media Gateway Processor
is not resetting, the Media Gateway may be functionally
impaired, and is not capable of resetting itself to restore
service. If service is impaired, reset the Media Gateway
manually. Escalate and have Tier 3 personnel capture the trap
information and the event logs for analysis.
16 of 20
320 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
G700 Traps and Resolutions
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
30
116
WRN
cmgModuleAutoReset — A Media Module in the Media Gateway
automatically reset (rebooted). A Media Module automatically
resets when it fails a sanity test performed by the Media Gateway
Processor. It may also automatically reset in response to a
maintenance test running on the call controller. (A reset performed
at the request of a SAT or CLI command entered by craft or Tier
technical support generates a different trap indicating a manual
reset.).
1. Check to see if a maintenance test that is supposed to reset the
Media Module was run.
2. Check the Media Module and insure that it has the latest
version of firmware installed. If it does not, install the latest
version of firmware and continue to monitor.
3. If this trap occurs infrequently, the trap may be due to an
unusual transient condition. Monitor future traps.
4. If this trap occurs and the Media Module does not return to
service, or if this trap occurs frequently, attempt to reset the
failing module from the SAT or CLI and see if this returns it to
stable service.
5. If manually resetting the Media Module does not return it to
service, and if a spare Media Module of the same time is
available, replace the failing Media Module with the spare and
see if the spare Media Module goes into service. If so, follow
procedures for dealing with the original, bad, Media Module.
6. If the spare Media Module fails to go into service, it is of course
possible that the spare Media Module is bad as well. But that
aside, try manually resetting the Media Gateway Processor at a
time convenient to the customer and see if this restores
service. If so, the both the original and the spare Media
Modules can probably be considered okay, and the problem is
probably with the Media Gateway Processor itself. Escalate
and have Tier 3 personnel capture the trap information and the
event logs for analysis.
17 of 20
Issue 1 June 2005
321
G700 Media Gateway Traps
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
32
118
MIN
cmgModulePostFault — A Media Module failed its power-on
start-up test.
1. Reset or replace the Media Module.
34
122
MAJ
cmgConfigUploadFault — An attempt to upload a configuration file
failed.
1. Check the event log for an error message during the backup/
restore process.
2. Troubleshoot the specific error according to the information
found.
3. Retry the upload (backup) command; for example:
copy mgp-config tftp <filename> <ip address>
Since the following command causes a brief service outage, it
should only be executed at the customer’s convenience.
4. If the problem persists, reboot the G700.
18 of 20
322 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
G700 Traps and Resolutions
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
Description / Recommendation
37
128
WRN
cmgVoipAutoReset — A VoIP (Voice Over IP) module in the Media
Gateway automatically reset (rebooted). A VoIP module
automatically resets when it fails a sanity test performed by the
Media Gateway Processor. It may also automatically reset in
response to a maintenance test running on the call controller. (A
reset performed at the request of a SAT or CLI command entered
by craft or Tier technical support generates a different trap
indicating a manual reset.) It automatically resets when its IP
address is administered. Finally, it automatically resets when it fails
a ping test performed by the Media Gateway Processor against the
VoIP module's IP address.
1. Check to see if a maintenance test that is supposed to reset the
VoIP module was run.
2. Check to see if the VoIP module had its IP address
re-administered.
3. Check to see if the IP address administered on the VoIP
module is correct.
4. Check to see if the IP address of the Media Gateway itself can
be pinged. Physical or logical connectivity issues (cabling or
routing problems) in the data network can cause ping failures.
5. Check the VoIP module and insure that it has the latest version
of firmware installed. If it does not, install the latest version of
firmware and continue to monitor.
6. If this trap occurs infrequently, the trap may be due to an
unusual transient condition. Monitor future traps.
7. If this trap occurs and the VoIP module does not return to
service, or if this trap occurs frequently, attempt to reset the
failing module from the SAT or CLI and see if this returns it to
stable service.
19 of 20
Issue 1 June 2005
323
G700 Media Gateway Traps
Table 83: G700 Alarms (SNMP Traps) to the Primary Media Server (continued)
Event
ID
Trap
#
Alarm
Level
37
128
WRN
(cont’d)
Description / Recommendation
8. If manually resetting the VoIP module does not return it to
service, and if a spare VoIP module of the same type is
available, replace the failing VoIP module with the spare and
see if the spare VoIP module goes into service. If so, follow
procedures for dealing with the original, bad, VoIP module.
9. If the spare VoIP module fails to go into service, it is of course
possible that the spare VoIP module is bad, as well. There may
be a power issue, also.
10. Try manually resetting the Media Gateway Processor at a time
convenient to the customer and see if this restores service. If
so, both the original and the spare VoIP modules can probably
be considered okay, and the problem is probably with the
Media Gateway Processor itself. Capture the trap information.
If possible, capture the event logs, using the show
event-log CLI command, for analysis. Escalate.
If none of this works, capture the trap information. If possible,
capture the event logs, using the show event-log CLI
20 of 20
324 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Chapter 5: Communication Manager
Maintenance-Object Repair
Procedures
Note:
This chapter does not contain MOs for the DEFINITY Wireless Business System
(DWBS), nor MOs for messaging systems. Refer to the maintenance
documentation that accompanies these products for this information
Note:
The Communication Manager maintenance subsystem is partitioned into separate entities
called Maintenance Objects (MOs). A maintenance object can be:
●
An individual circuit pack or media module
●
A hardware component that is part of a circuit pack or media module
●
An entire subsystem
●
A set of monitors
●
A process (or set of processes)
●
A combination of processes and hardware
“Maintenance names” are recorded in the Error and Alarm logs. Individual copies of an MO are
assigned an address that defines the MO 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 (see Figure 21: Display of test board on page 326).
Issue 1 June 2005
325
Communication Manager Maintenance-Object Repair Procedures
Figure 21: Display of test board
Subsystems Maintained by Communication Manager
Communication Manager subsystems are listable using list config and, in most cases,
have some maintenance activities involved.
Note:
Note:
list config all on the Communication Manager SAT gives you information
that includes whether or not stations have been administered on a port. show mg
list_config on the G700 MGP gives you information for the installed
equipment in that G700.
G700
326 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Subsystems Maintained by Communication Manager
G700 Subsystems Maintained by Communication Manager
The G700 subsystems that are applicable to Communication Manager maintenance
considerations are identifiable by the presence of ‘angels’. Angels may be either physical or
virtual, and both types use the CCMS message. Table 84: G700 Subsystems Maintained by
Communication Manager on page 327 lists the applicable subsystems and how they are
maintained.
Table 84: G700 Subsystems Maintained by Communication Manager
Subsystem
Angel Maintenance Type
Any Media Module
Physical Angel
Messaging Daughter Board (part of the S8300)
Virtual Angel
Announcement Circuitry (part of the MGP)
Virtual Angel
G700 Media Gateway MOs
The following list shows G700 specific maintenance objects. Other maintenance objects have
been modified slightly for the G700.
●
MED-GTWY (MEDIA GATEWAY)
●
MG-ANA (ANALOG MM711)
●
MG-ANN (Voice Announcements)
●
MG-BRI (BRI Trunk Media Module MM720)
●
MG-DCP (Digital Line Media Module)
●
MG-DS1 (DS1 Interface Media Module)
●
MG-ICC (Internal Call Controller)
●
MG-VOIP (MM760 MED PRO DSP PORT)
Issue 1 June 2005
327
Communication Manager Maintenance-Object Repair Procedures
MO Groupings by MM Type
Table 85: Media Module Tests on page 328 shows MO groupings by Avaya Media Module
type.
Table 85: Media Module Tests
Media Module
Maintenance Object
T1/E1 Media Module (MM710)
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-LNK)
ISDN-PRI Signaling Group (ISDN-SGRP)
Wideband Access Endpoint Port (WAE-PORT)
Analog Media Module (MM711)
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)
BRI Trunk Media Module (MM720)
Board (BRI-MM)
ISDN Trunk Side BRI Port (TBRI-PT)
ISDN Trunk Side Signaling (TBRI-TRK)
DCP Media Module (MM712)
Board (MG-DCP)
Digital Line (DIG-LINE)
BRI Trunk Media Module (MM720)
Board (MG-BRI)
ISDN Trunk Side BRI Port (TBRI-PT)
ISDN Trunk Side Signaling (TBRI-TRK)
1 of 2
328 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Viewing Communication Manager Alarms
Table 85: Media Module Tests (continued)
Media Module
Maintenance Object
VOIP Media Module (MM760)
Board (MG-VOIP)
Voice Announcements
(Communication Manager)
Board (MG-ANN)
Announcement Ports (VAL-PT)
Ethernet Port (ETH-PT)
2 of 2
Viewing Communication Manager Alarms
The technician views Communication Manager alarms and events through commands that are
available via the Web Interface or the SAT command-line interface. See Table 86: Commands
for Viewing Communication Manager Alarms on page 329.
Table 86: Commands for Viewing Communication Manager Alarms
Command
Interface
Purpose
Description
View Current Alarms
Web Interface,
under Alarms and
Notification
View a list of outstanding
alarms against
Communication Manager
Displays a summary of alarms,
if present, followed by a
detailed table of explanation.
display alarms
SAT CLI
View logged Communication
Manager alarms
These are alarms that have not
yet been cleared, either
manually or via an Expert
System.
Command Syntax
Maintenance commands use a different command syntax depending upon whether they refer to
port network circuit packs or media gateway Media Modules.
Issue 1 June 2005
329
Communication Manager Maintenance-Object Repair Procedures
The command syntax for circuit packs is test port location.
Variable
Definition
Platform
Range
UU
Universal cabinet number
ATM PNC
1-64
CSS PNC
1-44
G600
1-64
ATM PNC
A, B, C, D, or E
CSS PNC
A, B, C, D, or E
G600
A, B, C, or D
ATM PNC
01-21
CSS PNC
01-21
G600
01-10
All
01, 02,...
C
SS
pp
Carrier designation
Circuit pack slot
2-digit port number
The command syntax for media modules is test port GGGVSpp.
Variable
Definition
Platform
Range
GGG
Media gateway number
G700
1-250
G350
1-250
V
Literal: designates media
gateway
All
N/A
S
Media module number
G700
1-9
G350
1-7, 9
All
01, 02,...
pp
2-digit port number
Full test commands can be either short or long, and can be repeated several times. For
example, in
test port location sh r 1
●
she = short
●
r = repeat
●
1 = the number of times the test should be repeated.
330 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Abort Code 1412
Abort Code 1412
Tests that do not run on the G700 abort with Abort Code 1412. Tests that abort are listed under
each MO, but are not described.
Escalation Procedure
This document is not intended to solve all levels of trouble. When the limits of these procedures
have been reached but a problem is not resolved, a technician should escalate the problem 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.
Issue 1 June 2005
331
Communication Manager Maintenance-Object Repair Procedures
ABRI-PORT (ASAI ISDN-BRI Port)
S8700 | 8710 / S8500
MO Name in Alarm Log
Alarm
Level
Initial Command to Run
Full MO Name
ABRI-POR 1
MAJ
MIN
WRN
test port location l
ASAI ISDN-BRI port
1. Use set options to set the alarm level for ABRI ports. The alarm level can be set independently for onand off-board alarms to WARNING, MINOR, or MAJOR for every ABRI port in the system.
For repair procedures, see BRI-PORT (ISDN-BRI Port) on page 685.
332 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
AC-POWER
AC-POWER
S8700 | 8710 / S8500
AC Power for AC-Powered Systems
MO Name in Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
AC-POWER
WRN
test environment UU1
AC Power
1. UU is the universal cabinet number indicated in the PORT field of the alarm log.
S8700 MC
S8700 Multi-Connect systems support three different cabinet types as PNs: multicarrier
cabinets, single-carrier cabinets and the G650 rack mounted cabinets. All types may be
powered by either an AC or DC power source. Environmental maintenance differs according to
a cabinet’s type and its power supply.
! CAUTION:
Before powering down a cabinet or carrier that contains EMBEDDED AUDIX
circuit packs (TN566), first power down the AUDIX unit to avoid damaging its
software. Instructions for powering down this unit are in EMBEDDED AUDIX
System Maintenance, 585-300-110 for the circuit pack, and in Avaya S8300 and
Avaya S8700 Media Server Library, 555-233-825.
CAUTION:
Power System for Single-Carrier Cabinet
Each single-carrier cabinet has one power supply that distributes DC power and AC ringing
voltage to the circuit pack slots in the cabinet.
AC Power Supply (WP-91153)
In an AC-powered cabinet, a single, plug-in, multi-output AC power supply is in the power
supply slot. A power cord, with a 3-prong plug on one end and an appliance connector on the
other end, connects the supply to a dedicated AC power source. The inputs to the power supply
can be (depending on list version):
●
120 VAC, 60 Hz, 15 to 20 Amp; three wires in the power cord (one hot, one neutral, and
one ground wire)
●
220 VAC or 240 VAC, 50 Hz, 10 Amp; three wires in the power cord (one hot, one neutral,
and one ground wire)
Issue 1 June 2005
333
Communication Manager Maintenance-Object Repair Procedures
The AC power supply produces the following DC outputs: +5 VDC, -5 VDC, -48 VDC, +12 VDC,
and a battery-charging voltage. The DC outputs distribute power on the cabinet backplane to
the circuit pack slots.
The AC power supply also produces AC ringing voltage. The AC ringing voltage output value
and frequency depend on the country of use. The power supply has a circuit breaker and EMI
filtering.
Nominal Power Holdover
Multicarrier Cabinets
Two types of battery holdover are available:
●
The small battery assembly provides short-term battery holdover. If AC power fails, 48
VDC batteries power the system for:
- 15 seconds in a PN cabinet
- 10 minutes in the expansion control carrier in the “A” position of a PN cabinet
●
Some AC-powered multicarrier cabinets (MCCs) contain three 48-Volt batteries and a
battery charger (397C) to provide backup power in case power is interrupted. The
holdover times are identical to those above.
Single-Carrier Cabinets
A holdover circuit in the power supply allows a system to operate normally during AC power
interruptions. When AC input power fails, reserve batteries supply power to the memory and
processor circuit packs and fans for two minutes. Every port circuit pack is inactive during this
time. The power supply contains a battery charger to charge the holdover batteries.
Error Log Entries and Test to Clear Values
Table 87: AC Power Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Test to Clear Value
01
0
Any
Any
Any
test environment UU sh r 1
513
Any
AC Power Query test
(#78)
WRN
OFF
test environment UU sh r 1
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.
334 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
AC-POWER
System Technician-Demanded Tests:
Descriptions and Error Codes
Investigate tests in the order shown. By clearing error codes associated with the Battery and
Battery Charger Query test (#5), you may clear errors from other tests in the testing sequence.
Note:
Note:
The following tests apply to J58890CE, J58890CF, and J58890CH.
Order of Investigation
D/ND1
Short Test
Sequence
Long Test
Sequence
Battery & Battery Charger Query test (#5)
X
X
ND
AC Power Query test (#78)
X
X
ND
Power Unit Query test (carrier E) (#127)
X
X
ND
Power Unit Query test (carrier D) (#127)
X
X
ND
Power Unit Query test (carrier A) (#127)
X
X
ND
Power Unit Query test (carrier B) (#127)
X
X
ND
Power Unit Query test (carrier C) (#127)
X
X
ND
Emergency Transfer Query test (#124)
X
X
ND
Cabinet Temperature Query test (#122)
X
X
ND
External Alarm Lead Query test (#120)
X
X
ND
Analog Ring Generator Initialization test (#117)
X
X
ND
Analog Ring Generator Query test (#118)
X
X
ND
1. D = Destructive; ND = Nondestructive
AC Power Query Test (#78)
This test queries either the server’s watchdog (via an Ethernet or USB interface) or an MCC
PN’s Maintenance circuit pack for status of the cabinet’s AC power.
Issue 1 June 2005
335
Communication Manager Maintenance-Object Repair Procedures
Table 88: Test #78 Power Query Test
Error
Code
Test
Result
Description / Recommendation
1000
ABRT
System resources required to run test are not available.
1. Retry the command at 1-minute intervals up to 5 times.
100
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to ABORT with error code 2000, check for
system powering problems with the PN’s A carrier. Resolve every
AC-POWER and CARR-POW (S8700 IP: RMC-ENV) alarm. Repeat
the test.
3. S8700 MC: If the test still ABORTs with error code 2000, check for
and resolve every MAINT (Maintenance circuit pack) error in a PN.
Repeat the test.
4. If the test still ABORTs with error code 2000, escalate the problem.
2029
2319
2320
2500
ABRT
Internal system error
1
FAIL
The cabinet is currently without AC power.
Note:
Note:
For a J58890CE, skip to Procedures for a J58890CE.
Procedures for a Global MCC (J58890CH)
1. For a nominal holdover system if there is no AC power at the wall
outlet, have a qualified electrician restore power to the outlet. Power
should range from 170 to 264 VAC.
2. If there is AC power at the wall outlet, then there could be a problem
with the RM0850 rectifiers, BU3200A BIU (battery interface unit), or
battery. Resolve every alarm logged against the POWER MO, and
rerun the test. If the test still fails, the BIU may be defective. Check
the BIU. If the BOD alarm LED is on, replace the BIU. For S8700 MC,
if the BOD LED is off and the BOK LED is on, then a PN’s
Maintenance circuit pack may be incorrectly reporting the problem.
Resolve every alarm against these MOs, and rerun the test.
1 of 2
336 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
AC-POWER
Table 88: Test #78 Power Query Test (continued)
Error
Code
Test
Result
Description / Recommendation
1 (cont’d)
FAIL
Procedures for a J58890CE
1. Check for AC power at the wall outlet (99–127 or 200–250 VAC).
2. If AC power is absent, then the problem is not with the system itself.
Power must be restored to the wall outlet.
If present, there could be a problem with the battery or battery
chargers. Resolve every alarm logged against POWER (battery &
battery charger), and rerun the test.
3. If the test still fails, then fuse F5 may have opened. Replace this
fuse, and rerun the test.
!
WARNING:
WARNING:
Turn off the 397C Battery Charger before inserting or
removing Fuse F5.
4. If the test still fails, then the server’s watchdog or a PN’s
Maintenance circuit pack may be incorrectly reporting the problem.
Resolve every alarm against these MOs, and rerun the test. Some
watchdog and Maintenance circuit-pack errors may not be detected
by their respective maintenance routines, but can cause many
environment tests to fail.
5. If more than two environment tests are failing, replace the suspected
circuit pack (depending on the system configuration), and rerun the
test.
100
FAIL
The cabinet is currently without AC power, and AC power maintenance
is in the middle of timing the NPH interval.
1. Follow the repair steps for error code 1.
PASS
The server’s watchdog or the PN’s Maintenance circuit pack has reported
that the cabinet has AC power.
2 of 2
Issue 1 June 2005
337
Communication Manager Maintenance-Object Repair Procedures
AC-POWER for DC-Powered Systems
MO Name in Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
AC-POWER
WRN
test environment location
AC Power
Note:
In a DC-powered multicarrier cabinet, the AC-POWER MO exists but serves no
functional purpose. Because the system cannot determine the type of power
used, the AC-POWER test should always pass or abort. See CARR-POW
(Carrier Power Supply) on page 770 for the maintenance strategy for power
components in DC cabinets.
Note:
S8700 MC supports three cabinet types for PNs: multicarrier cabinets (MCCs), single-carrier
cabinets (SCCs), and 19-inch rack mounted cabinets. Every type may be powered by either an
AC or DC power source. Environmental maintenance differs according to a cabinet’s type and
its power supply.
S8700 IP supports 19-inch rack mounted cabinets, powered by either an AC or DC power source.
Error Log Entries and Test to Clear Values
Table 89: AC Power Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Test to Clear Value
01
0
Any
Any
Any
test environment UU sh r 1
513
Any
AC Power Query test
(#78)
WRN
OFF
test environment UU sh r 1
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.
338 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
AC-POWER
System Technician-Demanded Tests:
Descriptions and Error Codes
Investigate tests in the order presented below. Clearing error codes associated with the one test
may also clear errors generated from other tests in the sequence.
Table 90: System Technician-demanded tests: AC-Power
Order of Investigation
Short Test
Sequence
Long Test
Sequence
D/ND1
Battery & Battery Charger Query test (#5)
X
X
ND
AC Power Query test (#78)
X
X
ND
Power Unit Query test (carrier E) (#127)
X
X
ND
Power Unit Query test (carrier D) (#127)
X
X
ND
Power Unit Query test (carrier A) (#127)
X
X
ND
Power Unit Query test (carrier B) (#127)
X
X
ND
Power Unit Query test (carrier C) (#127)
X
X
ND
Emergency Transfer Query test (#124)
X
X
ND
Cabinet Temperature Query test (#122)
X
X
ND
External Alarm Lead Query test (#120)
X
X
ND
Analog Ring Generator Initialization test (#117)
X
X
ND
Analog Ring Generator Query test (#118)
X
X
ND
1. D = Destructive; ND = Nondestructive
Issue 1 June 2005
339
Communication Manager Maintenance-Object Repair Procedures
AC Power Query Test (#78)
AC Power Query Test (#78) is not valid for DC-powered cabinets and should always abort or
pass. S8700 IP will always abort.
Table 91: Test #78 Power Query Test
Error
Code
Test
Result
Description / Recommendation
1000
ABRT
System resources required to run test are not available.
100
2000
ABRT
Response to the test request was not received within the allowable
time period.
1. Retry the command at 1-minute intervals up to 5 times.
2029
2319
2320
2500
ABRT
S8700 MC
FAIL
A PN’s Maintenance circuit pack is incorrectly reporting an AC power
problem. If this test fails, there is a problem with a Maintenance circuit
pack. Replace the suspected circuit pack, and run the test again.
S8700 MC
PASS
Since this test is invalid for DC-powered cabinets, this result simply
indicates that a PN’s Maintenance circuit pack is handling this test
properly.
Any
Internal system error.
S8700 MC:
1. Retry the command at 1-minute intervals up to 5 times.
340 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ADM-CONN (Administered Connection)
ADM-CONN (Administered Connection)
S8700 | 8710 / S8500
MO Name
in Alarm
Log
Alarm
Level
Initial Command to Run
Full Name of MO
ADM-CONN
MAJ
MIN
WRN
status administered-connection n 1
Administered
Connection
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. Failures
to establish a connection generate an error whether they occur on an initial try, a retry, a fast
retry, a re-dial or an auto-restoration. 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.
●
Software determines that failure to establish a connection is due to a mistake in
administration. See Table 92: Administered Connection Error Log Entries on page 341.
Error Log Entries and Test to Clear Values
Table 92: Administered Connection Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Test to Clear
Value
0, 29
Any
None
Any
OFF
None
1, 28 (a, b)
Any
None
Any
OFF
None
2 (c)
Any
None
Any
OFF
None
1 of 2
Issue 1 June 2005
341
Communication Manager Maintenance-Object Repair Procedures
Table 92: Administered Connection Error Log Entries (continued)
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Test to Clear
Value
6, 21, 31, 127 (d)
Any
None
Any
OFF
None
16 (a)
Any
None
Any
OFF
None
17 (e)
Any
None
Any
OFF
None
18, 102 (f)
Any
None
Any
OFF
None
22 (a, g)
Any
None
Any
OFF
None
34, 42, 44, 58 (h)
Any
None
Any
OFF
None
38, 41 (i)
Any
None
Any
OFF
None
43, 81
Any
None
Any
OFF
None
50 (a)
Any
None
Any
OFF
None
52 (a)
Any
None
Any
OFF
None
54
Any
None
Any
OFF
None
65, 66, 69 (a)
Any
None
Any
OFF
None
82
Any
None
Any
OFF
None
88 (a)
Any
None
Any
OFF
None
91, 95, 96, 97, 98,
99, 100, 111
Any
None
Any
OFF
None
2 of 2
For ADM-CONN Errors
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.
342 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ADM-CONN (Administered Connection)
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.
c. Error 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.
e. Error 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 allotted time (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.
h. Error 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.
Issue 1 June 2005
343
Communication Manager Maintenance-Object Repair Procedures
ADX8D-BD (AUDIX Circuit Pack)
S8700 | 8710 / S8500
MO Name in Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
ADX8D-BD
MIN
WRN
test board location sh
AUDIX circuit pack
The ADX8D-BD MO defines a TN566/TN2169 EMBEDDED AUDIX circuit pack (also called
DEFINITY AUDIX) operating in DP (digital-port) mode.
For port-level problems, see ADX8D-PT (AUDIX Digital Port) on page 345.
For circuit-pack-level problems, see XXX-BD (Common Port Circuit Pack/Media Module) on
page 2539.
EMBEDDED AUDIX consists of two circuit packs that occupy 5 slots on a port carrier. The tests
described in this manual apply only to switch-side maintenance which tests a circuit pack’s
components related to the TDM-bus interface. The AUDIX system has an extensive
maintenance strategy that is described in EMBEDDED AUDIX System Maintenance,
585-300-110.
344 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ADX8D-PT (AUDIX Digital Port)
ADX8D-PT (AUDIX Digital Port)
S8700 | 8710 / S8500
MO Name in Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
ADX8D-PT
MIN
test port location l
AUDIX digital port
ADX8D-PT
WRN
test port location sh
AUDIX digital port
The ADX8D-PT MO represents a port on a TN566/TN2169 EMBEDDED AUDIX circuit pack
(also called DEFINITY AUDIX) operating in DP (digital-port) mode. The maintenance strategy
for ports on the TN566 operating in control-link mode is described in ADX16A-PT.
The tests described in this section apply only to switch-side maintenance that tests a circuit
pack’s components related to the TDM-bus interface. The AUDIX system has an extensive
maintenance strategy that is described in EMBEDDED AUDIX System Maintenance,
585-300-110.
AUDIX resides on a combined pair of circuit packs: the TN566 MFB (multifunction board) and
the TN2169 ALB (alarm board). Because of its size, this combination occupies 5 slots, but only
1 slot is functional as far as the switch is concerned. The other 4 slots are seen by the switch as
“AUDIX-reserved” slots (or ADXDP-RS/ADX8D-RS).
In DP mode the TN566 pack supports up to 8 voice ports, each with a primary and a secondary
information channel. Ports are administered in increments of two. When a call to a station with
an AUDIX login is not answered, AUDIX answers the call using one of the available voice ports.
Unlike other AUDIX systems, EMBEDDED AUDIX is not an adjunct.
! CAUTION:
Never do any of the following without first shutting down AUDIX. Follow
instructions on the TN566/TN2169 faceplate:
CAUTION:
●
Remove EMBEDDED AUDIX circuit packs
●
Cycle power to a carrier containing EMBEDDED AUDIX circuit packs
●
Remove power to a carrier containing EMBEDDED AUDIX circuit packs
Issue 1 June 2005
345
Communication Manager Maintenance-Object Repair Procedures
Error Log Entries and Test to Clear Values
Table 93: EMBEDDED AUDIX Digital Port Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Test to Clear Value
0 (a)
0
Any
Any
Any
test port location sh r 1
1 (b)
40987
None
WRN
OFF
1 (c)
1 to 20
None
WRN
OFF
15 (d)
Any
None
18 (e)
0
busyout port
location
WRN
OFF
23 (f)
0
None
WRN
OFF
None
WRN
ON
130 (g)
release port location
test port location sh
257 (h)
40971
None
513 (i)
Any
None
1537 (j)
40968
None
WRN
OFF
1793
Voice & Ctrl.
Local Loop (#13)
MIN
WRN1
ON
test port location l r 3
2049
NPE Crosstalk
test (#9)
MIN
WRN1
ON
test port location l r 3
2305 (k)
40967
None
3840 (l)
40965
None
3840 (m)
41029
None
1. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in set options.
Notes:
a. Error 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
procedures.
346 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ADX8D-PT (AUDIX Digital Port)
b. Error Type 1, Aux Data 40987: the user may experience a noisy port or link, due to an
off-board problem that is detected by the port circuit. If so, replace the circuit pack (see
caution at the beginning of this section). Once the problem is resolved, the alarm is retired
after a predetermined time.
c. Error Type 1, Aux Data 1 to 20: At least 15 off-board problems have been detected with
the link to the voice port. When an error with the link is detected, an on-board counter is
incremented. Also see Note (a).
d. Error Type 15: internal type error that occurs when an audit request fails.
e. Error Type 18: the port is busied-out by command. Use release port location to
release the port.
f. Error Type 23: the circuit pack is administered but not physically installed. The alarm will
clear when a circuit pack is inserted.
g. Error Type 130: the circuit pack was removed or has been insane for more than
21 minutes. To clear the error, reinsert or replace the AUDIX circuit pack (see Caution at the
beginning of this section).
h. Error Type 257: Something is interfering with transmission to the voice port. This is usually
an on-board problem and can be ignored if there are no user complaints.
i. Error Type 513: AUDIX is not available to the switch, possibly due to a busyout on the
AUDIX system. See EMBEDDED AUDIX System Maintenance, 585-300-110, if necessary.
j. Error Type 1537: An in-line maintenance error has generated an off-board warning due to
some problem with the link to the voice port. This can be ignored if there are no user
complaints. If the problem persists, replace the circuit pack (see Caution at the beginning of
this section). Once the problem is resolved, the alarm is retired after a certain period of time.
k. Error Type 2305: the link between the circuit pack and the voice port successfully reset. No
craft action is necessary.
l. Error Type 3840, Aux Data 40965: no voice ports are connected to the EMBEDDED
AUDIX circuit pack. No maintenance action is required.
m. Error Type 3840, Aux Data 41029: the message buffer in the circuit pack is full.
Issue 1 June 2005
347
Communication Manager Maintenance-Object Repair Procedures
System Technician-Demanded Tests:
Descriptions and Error Codes
Investigate tests in the order presented when you are inspecting errors in the system.
Order of Investigation
Short Test
Sequence
Long Test
Sequence
D/ND1
Voice and Control Channel Local Looparound test (#13)
X
ND
NPE Crosstalk test (#9)
X
ND
1. D = Destructive; ND = Nondestructive
NO-OP Tests
The maintenance strategy for EMBEDDED AUDIX emulates the one for DIG-LINE. NO-OP
Tests apply only to DIG-LINE and not to EMBEDDED AUDIX. NO-OP tests always return PASS.
●
Electronic Power Feed test (#11)
●
Station Lamp Updates test (#16)
●
Station (Digital) Audits test (#17)
NPE Crosstalk Test (#9)
NPE Crosstalk Test (#9) verifies that this port’s NPE channel talks on the selected time slot and
that it never crosses over to time slots reserved for other connections. An NPE that is not
working correctly may cause 1-way and noisy connections. This test is part of a port’s long test
sequence, and it executes in about 20 to 30 seconds.
348 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ADX8D-PT (AUDIX Digital Port)
Crosstalk testing is performed on both the primary (for voice) and the secondary (for data)
information channel associated with each EMBEDDED AUDIX port. If NPE Crosstalk Test (#9)
fails on either channel, the voice port is taken out of service.
Table 94: Test #9 NPE Crosstalk Test
Error
Code
Test
Result
Description / Recommendation
1
ABRT
During testing of the primary information channel, system resources may
not have been available. Also, the port may have been busy during the test.
1. Check the port status.
2. Use display port location to determine the voice port extension
of the port. Use status station to determine the service state of the
port. If the service state indicates that the port is active, wait until it is
idle.
3. Retry the command at 1-minute intervals up to 5 times.
2
ABRT
System resources may not have been available, or the port may have been
busy during the test.
1. Retry the command at 1-minute intervals up to 5 times.
1000
ABRT
System resources required to run this test are not available. The port may
be active.
1. Use display port location to determine the voice port extension
of the port. Use status station to determine the service state of the
port. If the service state indicates that the port is active, wait until it is
idle before retesting.
2. Retry the command at 1-minute intervals up to 5 times.
1001
ABRT
System resources required to run this test are not available.
1. Retry the command at 1-minute intervals up to 5 times.
1002
ABRT
The system could not allocate time slots for the test. The system may be
under heavy traffic conditions, or it may have time slots out-of-service due
to TDM-BUS errors.
1. If the system has no TDM-BUS errors and is not handling heavy traffic,
retry the command at 1-minute intervals up to 5 times.
1 of 2
Issue 1 June 2005
349
Communication Manager Maintenance-Object Repair Procedures
Table 94: Test #9 NPE Crosstalk Test (continued)
Error
Code
Test
Result
Description / Recommendation
1003
ABRT
The system could not allocate a tone receiver for the test. The system may
be oversized for the number of Tone Detectors present, or some Tone
Detectors may be out of service.
1. Resolve any TTR-LEV errors.
2. Resolve any TONE-PT errors.
3. Retry the command at 1-minute intervals up to 5 times.
1004
ABRT
The port was put in use during the test. The test has been aborted.
1. Use display port location to determine the voice port extension
of the port. Use status station to determine the service state of the
port. If the port is active, wait until it is idle before testing.
1020
ABRT
Test disabled by background testing.
1. Use status station to determine when the voice port is available
for testing.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
1
2
FAIL
The NPE of the tested port is transmitting in error. This causes noisy and
unreliable connections. Failure code 1 indicates that the Crosstalk test
failed on the primary channel. Failure code 2 indicates that the Crosstalk
test failed on the secondary channel.
1. Replace the circuit pack.
PASS
The port is using its allocated time slots correctly.
1. To be sure that this is not an intermittent problem, repeat this test up to
10 times to make sure it continues to pass.
2. If complaints still exist, examine the connections.
2 of 2
Voice and Control Channel Local Loop Test (#13)
Voice and Control Channel Local Loop Test (#13) checks the information and control channels
between a server and the EMBEDDED AUDIX port circuit. First, the primary information (voice)
channel loop back test is run.
350 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ADX8D-PT (AUDIX Digital Port)
While the primary information channel is still looped around, the Control Channel Looparound
test is performed. The Looparound test for the secondary information (data) channel is then
performed. This is the same test as the primary information channel’s loop-around test.
Next, a Conference test is implemented for the primary information channel. This is the same
test as Conference test (#6).
Only one value (Pass, Fail, or Abort) is generated as a result of the four tests run. If any tests fail
or abort, the sequence stops.
Table 95: Test #13 Voice and Control Channel Local Loop Test
Error
Code
Test
Result
Description / Recommendation
ABRT
Internal system error.
1. Retry the command at 1-minute intervals up to 5 times. Then try (b).
1000
ABRT
System resources required to run this test are not available. The port may
be active.
1. Use display port location to determine the voice port extension
of the port. Use status station to determine the service state of the
port. If the service state indicates that the port is active, wait until it is
idle before retesting.
2. Retry the command at 1-minute intervals up to 5 times.
1001
ABRT
System resources required for this test are not available.
1. Retry the command at 1-minute intervals up to 5 times.
1002
ABRT
The system could not allocate time slots for the test. The system may be
under heavy traffic conditions, or may have time slots that are
out-of-service due to TDM-BUS errors.
1. If the system has no TDM-BUS errors and is not handling heavy traffic,
retry the command at 1-minute intervals up to 5 times.
1003
ABRT
The system could not allocate a tone receiver for the test. The system may
be oversized for the number of Tone Detectors present, or some Tone
Detectors may be out of service.
1. Resolve any TTR-LEV errors.
2. Resolve any TONE-PT errors.
3. If neither condition exists, retry the command at 1-minute intervals up
to 5 times.
1 of 2
Issue 1 June 2005
351
Communication Manager Maintenance-Object Repair Procedures
Table 95: Test #13 Voice and Control Channel Local Loop Test (continued)
Error
Code
Test
Result
Description / Recommendation
1004
ABRT
The port was put in use during the test.
1. Use display port location to determine the voice port extension
of the port. Use status station to determine the service state of the
port. If the service state indicates that the port is active, wait until it is
idle before retesting.
2. Retry the command at 1-minute intervals up to 5 times.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
7
FAIL
Conference test failed on the primary channel. Some users may notice a
disruption in service. In extreme cases, the conferencing feature may not
work at all.
14
FAIL
The primary voice channel is not transmitting properly. User impact may
range from no noticeable effect to loss of use of this port.
15
FAIL
The control channel between the processor and the EMBEDDED AUDIX
circuit pack is not transmitting properly. User impact may range from no
noticeable effect to loss of use of this port.
16
FAIL
The secondary voice channel is not transmitting properly. User impact may
range from no noticeable effect to loss of use of this port.
None
FAIL
The test failed for reasons external to the EMBEDDED AUDIX circuit pack.
1. Use test board location sh to run circuit tests to check the Tone
Generator circuit and the Tone Detector circuit.
2. Resolve any problems that are detected on the Tone Generator circuit
or Tone Detector circuit.
3. If both circuit packs are functioning properly and the test still fails,
replace the EMBEDDED AUDIX circuit pack (see caution at the
beginning of this section).
PASS
Voice and Control Channel Local Loop test passed. Every channel is
transmitting properly.
1. To be sure that this is not an intermittent problem, repeat this test up to
10 times, and see whether it continues to pass.
2. If complaints still exist, examine the connections.
2 of 2
352 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ADX16D-B (16-Port AUDIX Circuit Pack)
ADX16D-B (16-Port AUDIX Circuit Pack)
S8700 | 8710 / S8500
MO Name in Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
ADX16D-B
MIN
test board location sh
AUDIX circuit pack
ADX16D-B
WRN
test board location sh
AUDIX circuit pack
The ADX16D-BD MO represents a TN566/TN2169 EMBEDDED AUDIX circuit pack
combination operating in 16-port mode digital (DP). For circuit-pack-level problems, see
XXX-BD (Common Port Circuit Pack/Media Module) on page 2539. Port-level maintenance is
covered by ADX16D-PT.
EMBEDDED AUDIX consists of two circuit packs that occupy 5 slots on a port carrier. The tests
described in this manual apply only to switch-side maintenance that tests a circuit pack’s
components related to the TDM-bus interface. The AUDIX system has an extensive
maintenance strategy of its own that is described in DEFINITY AUDIX System Release 3.2.4
Maintenance, 585-300-110.
Issue 1 June 2005
353
Communication Manager Maintenance-Object Repair Procedures
ADX16A-BD (AUDIX Circuit Pack)
S8700 | 8710 / S8500
MO Name in Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
ADXCL-BD
ADX16A-B
MIN
WRN
test board location sh
AUDIX circuit pack
The ADX16A-BD MO represents a TN566/TN2169 EMBEDDED AUDIX circuit pack
combination operating in control-link (CL) mode. For circuit-pack-level problems, see XXX-BD
(Common Port Circuit Pack/Media Module) on page 2539. Port-level maintenance is covered
by ADX16A-PT.
EMBEDDED AUDIX consists of two circuit packs that occupy 5 slots on a port carrier. The tests
described in this manual apply only to switch-side maintenance that tests a circuit pack’s
components related to the TDM-bus interface. The AUDIX system has an extensive
maintenance strategy that is described in EMBEDDED AUDIX System Maintenance,
585-300-110.
354 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ADX16D-P (16-Port AUDIX Digital Port)
ADX16D-P (16-Port AUDIX Digital Port)
S8700 | 8710 / S8500
MO Name in Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
ADX16D-P
MIN
WRN
test port location l
AUDIX Digital port
! CAUTION:
Never do any of the following without first shutting down AUDIX. Follow the
instructions on the TN566/TN2169 faceplate:
CAUTION:
●
Remove EMBEDDED AUDIX circuit packs
●
Cycle power to a carrier containing EMBEDDED AUDIX circuit packs
●
Remove power to a carrier or cabinet containing EMBEDDED AUDIX circuit pack
The ADX16D-P MO represents a port on a TN566/TN2169 EMBEDDED AUDIX circuit pack
operating in digital-port (DP) mode. The maintenance strategy for ports on the TN566 operating
in control-link mode is described in ADX16A-PT.
The tests described in this section apply only to switch-side maintenance that tests a circuit
pack’s components related to the TDM-bus interface. The AUDIX system has an extensive
maintenance strategy that is described in DEFINITY AUDIX System Release 3.2.4
Maintenance, 585-300-110.
AUDIX resides on a combined pair of circuit packs: the TN566 Multifunction board (MFB) and
the TN2169 Alarm board (ALB). Because of its size this combination occupies 5 slots, but the
system sees only 1 slot as functional. The other 4 slots are seen by the switch as
“AUDIX-reserved” slots (or ADX16-RES/ADX16D-RS).
In 16-port DP mode, the TN566 pack supports up to 16 voice ports, each with a primary and a
secondary information channel. Ports are administered in increments of two. When a call to a
station with an AUDIX login is not answered, AUDIX answers the call using one of the available
voice ports.
Unlike other AUDIX systems, EMBEDDED AUDIX is not an adjunct.
Issue 1 June 2005
355
Communication Manager Maintenance-Object Repair Procedures
Error Log Entries and Test to Clear Values
Table 96: EMBEDDED AUDIX Digital Port Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/
Off
Board
Test to Clear Value
0 (a)
0
Any
Any
Any
test port location sh r 1
1 (b)
40987
None
WRN
OFF
1 (c)
1 to 20
None
WRN
OFF
15 (d)
Any
None
18 (e)
0
busyout port
location
WRN
OFF
23 (f)
0
None
WRN
OFF
None
WRN
ON
130 (g)
release port location
test port location sh
257 (h)
40971
None
513 (i)
Any
None
1537 (j)
40968
None
WRN
OFF
1793
Voice and Control
Local Loop Test
(#13)
MIN
WRN1
ON
test port location l r 3
2049
NPE Crosstalk
test (#9)
MIN
WRN1
ON
test port location l r 3
2305
(k)
40967
None
3840 (l)
40965
None
3840
(m)
41029
None
1. Minor alarms may be downgraded to Warning alarms based on the values used in set options.
Notes:
a. 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 the recommended procedures
356 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ADX16D-P (16-Port AUDIX Digital Port)
b. Error Type 1 with Aux Data 40987: The user may experience a noisy port or link, due to an
off-board problem that is detected by the port circuit. If so, replace the circuit pack (see
caution at the beginning of this section). Once the problem is resolved, the alarm is retired
after a predetermined time.
c. Error Type 1: At least 15 off-board problems have been detected with the link to the voice
port. When an error with the link is detected, an on-board counter is incremented. Also see
Note a above.
d. Error Type 15: An internal type error that occurs when an audit request fails.
e. Error Type 18: The port is busied-out by command. Release the port with release port
location.
f. Error Type 23: The circuit pack is administered but not physically installed. The alarm will
clear when a circuit pack is inserted.
g. Error Type 130: The circuit pack has been removed or has been insane for more than
21-minutes. To clear the error, reseat or replace the AUDIX circuit pack (see caution at the
beginning of this section).
h. Error Type 257: Something is interfering with transmission to the voice port. This is usually
an on-board problem and can be ignored if there are no user complaints.
i. Error Type 513: AUDIX is not available to the switch, possibly due to a busyout on the
AUDIX system. Refer to DEFINITY AUDIX System Release 3.2.4 Maintenance,
585-300-110.
j. Error Type 1537: An in-line maintenance error has generated an off-board warning due to
some problem with the link to the voice port. This can be ignored if there are no user
complaints. If the problem persists, replace the circuit pack (see caution at the beginning of
this section). Once the problem is resolved, the alarm is retired after a certain period of time.
k. Error Type 2305: The link between the circuit pack and the voice port is successfully reset.
No craft action is necessary.
l. Error Type 3840 with Aux Data 40965: No voice ports are connected to the EMBEDDED
AUDIX circuit pack. No maintenance action is required.
m. Error Type 3840 with Aux Data 41029: The message buffer in the circuit pack is full.
Issue 1 June 2005
357
Communication Manager Maintenance-Object Repair Procedures
System Technician-Demanded Tests:
Descriptions and Error Codes
Investigate tests in the order presented.
Long Test
Sequence
D/ND1
Voice and Control Channel Local Looparound test (#13)
X
ND
NPE Crosstalk test (#9)
X
ND
Order of Investigation
Short Test
Sequence
1. D = Destructive; ND = Nondestructive
NO-OP Tests
The maintenance strategy for EMBEDDED AUDIX emulates the one for DIG-LINE. The tests
listed below apply only to DIG-LINE and not to EMBEDDED AUDIX. These tests always return
PASS.
●
Electronic Power Feed test (#11)
●
Station Lamp Updates test (#16)
●
Station (Digital) Audits test (#17)
●
Digital Terminal Remote Looparound test (#1201)
NPE Crosstalk Test (#9)
NPE Crosstalk Test (#9) verifies that this port’s NPE channel talks on the selected time slot and
that it never crosses over to time slots reserved for other connections. If the NPE is not working
correctly, one-way and noisy connections may be observed. NPE Crosstalk Test (#9) is part of a
port’s long test sequence, and it executes in about 20 to 30 seconds.
Crosstalk testing is performed on both the primary (for voice) and the secondary (for data)
information channel associated with each EMBEDDED AUDIX port. If this test fails on either
channel, the voice port is taken out-of-service.
358 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ADX16D-P (16-Port AUDIX Digital Port)
Table 97: Test #9 NPE Crosstalk Test
Error
Code
Test
Result
Description / Recommendation
1
ABRT
During testing of the primary information channel, system resources may
not have been available. Also, the port may have been busy during the test.
1. Check the port status.
2. Use display port location to determine the voice port extension
of the port. Use status station to determine the service state of the
port. If the port is active, it is unavailable for this test. Wait until the port
is idle.
3. Retry the command at 1-minute intervals up to 5 times.
2
ABRT
System resources may not have been available, or the port may have been
busy during the test.
1. Verify that the port’s status is idle.
2. Retry the command at 1-minute intervals up to 5 times.
1000
ABRT
System resources required to run this test are not available. The port may
be active.
1. Use display port location to determine the voice port extension
of the port. Use status station to determine the service state of the
port. If the port is active, it is unavailable for certain tests. Refer to
“Status” commands in Maintenance SAT Commands in Maintenance
Commands Reference (03-300191), for a full description of every
possible state. Wait until the port is idle before testing.
2. If the port’s status is idle, retry the command at 1-minute intervals up to
5 times.
1001
ABRT
System resources required to run this test are not available.
1. Retry the command at 1-minute intervals up to 5 times.
1002
ABRT
The system could not allocate time slots for the test. The system may be
under heavy traffic conditions, or it may have time slots out-of-service due
to TDM-BUS errors.
1. If the system has no TDM-BUS errors and is not handling heavy traffic,
retry the command at 1-minute intervals up to 5 times.
1 of 2
Issue 1 June 2005
359
Communication Manager Maintenance-Object Repair Procedures
Table 97: Test #9 NPE Crosstalk Test (continued)
Error
Code
Test
Result
Description / Recommendation
1003
ABRT
The system could not allocate a tone receiver for the test. The system may
be oversized for the number of Tone Detectors present, or some Tone
Detectors may be out of service.
1. Resolve any TTR-LEV errors.
2. Resolve any TONE-PT errors.
1004
ABRT
The port was put in use during the test. The test has been aborted.
1. Use display port location to determine the voice port extension
of the port. Use status station to determine the service state of the
port. If the port is active, it is unavailable for certain tests. Refer to
“Status” commands in Maintenance SAT Commands in Maintenance
Commands Reference (03-300191) for explanations of every possible
state. Wait until the port is idle before testing.
1020
ABRT
Test disabled via background testing.
1. Use status station to determine when the voice port is available
for testing.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
1, 2
FAIL
The NPE of the tested port was found to be transmitting in error. This
causes noisy and unreliable connections. Failure code 1 indicates that the
Crosstalk test failed on the primary channel. Failure code 2 indicates that
the Crosstalk test failed on the secondary channel.
1. Replace the circuit pack (see caution at the beginning of this section).
PASS
The port is using its allocated time slots correctly.
1. To verify that this is not an intermittent problem, repeat this test up to 10
times, and make sure it continues passing.
2. If complaints still exist, examine the connections.
2 of 2
360 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ADX16D-P (16-Port AUDIX Digital Port)
Voice and Control Channel Local Loop Test (#13)
This test checks the information and control channels between the server the EMBEDDED
AUDIX port circuit. The server sends a message to loop around both the information and control
channels for the port. First, the primary information (voice) channel loop back test is run.
While the primary information channel is still looped around, the Control Channel Looparound
test is performed. The loop-around test for the secondary information (data) channel is then
performed. This test is the same as the primary information channel’s loop-around test.
Next, a Conference test is implemented for the primary information channel. This test is the
same as Conference Test #6.
Only one value (Pass, Fail, or Abort) is generated as a result of the four tests run. If any test
fails or aborts, the sequence is stopped.
Table 98: Test #13 Voice and Control Channel Local Loop Test
Error
Code
Test
Result
Description / Recommendation
ABRT
Internal system error
1. Retry the command at 1-minute intervals up to 5 times.
1000
ABRT
System resources required to run this test are not available. The port may
be active.
1. Use display port location to determine the voice port extension
of the port. Use status station to determine the service state of the
port. Wait until the port is idle before testing.
2. Retry the command at 1-minute intervals up to 5 times.
1001
ABRT
System resources required to run this test are not available.
1. Retry the command at 1-minute intervals up to 5 times.
1002
ABRT
The system could not allocate time slots for the test. The system may be
under heavy traffic conditions, or it may have time slots that are
out-of-service due to TDM-BUS errors.
1. 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.
1003
ABRT
The system could not allocate a tone receiver for the test. The system may
be oversized for the number of Tone Detectors present, or some Tone
Detectors may be out of service.
1. Resolve any TTR-LEV errors.
2. Resolve any TONE-PT errors.
3. Retry the command at 1-minute intervals up to 5 times.
1 of 2
Issue 1 June 2005
361
Communication Manager Maintenance-Object Repair Procedures
Table 98: Test #13 Voice and Control Channel Local Loop Test (continued)
Error
Code
Test
Result
Description / Recommendation
1004
ABRT
The port was put in use during the test. The test has been aborted.
1. Use display port location to determine the voice port extension
of the port. Use status station to determine the service state of the
port. If the port is active, wait until it is idle before retesting.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
Could not allocate the necessary system resources for this test.
1. Retry the command at 1-minute intervals up to 5 times.
7
FAIL
Conference test failed on the primary channel. In some cases, users may not
notice a disruption in service. In extreme cases, the conferencing feature may
not work at all.
14
FAIL
The primary voice channel is not transmitting properly. User impact may
range from no noticeable effect to loss of use of this port.
15
FAIL
The control channel between the processor and AUDIX is not transmitting
properly. User impact may range from no noticeable effect to loss of use of
this port. This failure could also be disruptive to other users.
16
FAIL
The secondary voice channel is not transmitting properly. User impact may
range from no noticeable effect to loss of use of this port.
None
FAIL
The test failed for reasons external to the AUDIX.
1. Run circuit tests to check the Tone Generator circuit and the Tone
Detector circuit using test board location s.
2. Resolve any problems detected on the Tone Generator circuit or Tone
Detector circuit.
3. If both circuit packs are functioning properly and the test still fails,
replace the AUDIX (see caution at the beginning of this section).
PASS
Voice and Control Channel Local Loop test passed. Every channel are
transmitting properly.
1. To be sure that this is not an intermittent problem, repeat this test up to
10 times, and see whether it continues to pass.
2. If complaints still exist, examine the connections.
2 of 2
362 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ADX16A-PT (AUDIX Analog Line/Control Link)
ADX16A-PT (AUDIX Analog Line/Control Link)
S8700 | 8710 S8500
MO Name in
Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
ADXCL-PT
or ADX16A-P
MIN
test port location l
AUDIX Analog Line/ Control Link
ADXCL-PT
or ADX16A-P
WRN
test port location sh
AUDIX Analog Line/ Control Link
! CAUTION:
Never do any of the following without first shutting down AUDIX. Follow the
instructions on the TN566/TN2169 faceplate:
CAUTION:
●
Remove EMBEDDED AUDIX circuit packs
●
Cycle power to a carrier containing EMBEDDED AUDIX circuit packs
●
Remove power to a carrier containing EMBEDDED AUDIX circuit packs
The ADX16A-PT MO represents a port on a TN566/TN2169 EMBEDDED AUDIX circuit pack
that is operating in control-link (CL) mode. For circuit-pack-level problems (ADX16A-BD or
ANL-16-BD), see XXX-BD (Common Port Circuit Pack/Media Module) on page 2539. For
port-level problems with AUDIX operating in digital-port mode, see:
●
ADX8D-PT (AUDIX Digital Port) on page 345
●
ADX16D-P (16-Port AUDIX Digital Port) on page 355
The tests described in this section apply only to switch-side maintenance that tests a circuit
pack’s components related to the TDM-bus interface. The AUDIX system has an extensive
maintenance strategy that is described in DEFINITY AUDIX System Release 3.2.4
Maintenance, 585-300-110.
AUDIX resides on a combined pair of circuit packs: the TN566 Multifunction board (MFB) and
the TN2169 Alarm board (ALB). Because of its size this combination occupies 5 slots, but only 1
slot is functional as far as the switch is concerned. The other 4 slots are seen by the switch as
“AUDIX-reserved” slots.
In CL mode the TN566 pack supports up to 16 voice ports. When a call to a station with an
AUDIX login is not answered, AUDIX answers the call using one of the available voice ports.
Unlike other AUDIX systems, EMBEDDED AUDIX is not an adjunct.
Issue 1 June 2005
363
Communication Manager Maintenance-Object Repair Procedures
Error Log Entries and Test to Clear Values
Table 99: EMBEDDED AUDIX Analog Line/Control Link Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Test to Clear Value
01
0
Any
Any
Any
test port location sh r 1
1 (a)
40977
None
18
0
busyout
station ext
WRN
ON
release station extension
23 (b)
0
None
WRN
OFF
None
WRN
ON
test port location sh
130
(c)
257
(d)
40973
None
513
(e)
Any
None
1025
(f)
Looparound test
(#161)
MIN
WRN2
ON
test port location l r 2
1281
Conference test
(#7)
MIN
WRN2
ON
test port location l r 2
1537
NPE Crosstalk test
(#6)
MIN
WRN2
ON
test port location l r 2
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.
2. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in set options.
Notes:
a. Error Type 1 is an in-line error that can only be resolved over time. No terminal equipment
was present when ringing was attempted. Execute test port location s.
b. Error Type 23: The circuit pack was logically administered but not physically installed. The
alarm will clear when the circuit pack is installed.
c. Error Type 130: The circuit pack was removed or has been insane for more than
11 minutes. To clear the error, reseat or replace the circuit pack.
364 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ADX16A-PT (AUDIX Analog Line/Control Link)
d. Error Type 257 is an in-line error and can only be resolved over time. Ringing voltage is
absent. If only one analog circuit pack in the system has this problem, replace the circuit
pack. If only analog circuit packs on a particular carrier have this error, the ringing generator
may not be connected to this carrier. If analog circuit packs on many carriers have this error,
check the ringing generator.
e. Error Type 513: AUDIX is not available to the switch. Check the AUDIX system, referring to
DEFINITY AUDIX System Release 3.2.4 Maintenance, 585-300-110.
f. Error Type 1025: The TDM bus is out of service. See TDM-BUS (TDM Bus) on page 2237.
System Technician-Demanded Tests:
Descriptions and Error Codes
Investigate tests in the order presented. By clearing error codes associated with the
Looparound test (#161), you may also clear errors generated from other tests in the testing
sequence.
Long Test
Sequence
D/ND1
Looparound test (#161)
X
ND
Conference test (#7)
X
ND
NPE Crosstalk test (#6)
X
ND
Order of Investigation
Short Test
Sequence
1. D = Destructive; ND = Nondestructive
NO-OP Tests
The maintenance strategy for EMBEDDED AUDIX emulates the one for ANL-16-L. The tests
listed below apply only to ANL-16-L and not to EMBEDDED AUDIX. These tests always return
PASS.
●
Battery Feed test (#35)
●
Audits and Updates test (#36)
●
Station Present test (#48)
Tests 36 and 48 ABORT when AUDIX is not running.
Issue 1 June 2005
365
Communication Manager Maintenance-Object Repair Procedures
NPE Crosstalk Test (#6)
This test verifies that this port’s NPE channel talks on the selected time slot and never crosses
over to time slots reserved for other connections. If the NPE is not working correctly, one-way
and noisy connections may be observed. This test is part of the long test sequence and
executes in about 25 seconds.
Table 100: Test #6 NPE Crosstalk Test
Error
Code
Test
Result
Description / Recommendation
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1000
ABRT
System resources required to run this test are not available. The port may
be busy with a valid call.
1. Use display port location to determine the station extension.
Use status station to determine the service state of the port. If the
port is active, it is unavailable for certain tests. Wait until the port is idle
before testing.
2. Retry the command at 1-minute intervals up to 5 times.
1001
ABRT
Could not allocate the necessary system resources to run this test.
1002
ABRT
The system could not allocate time slots for the test. The system may be
under heavy traffic conditions or it may have time slots out-of-service due to
TDM-BUS errors.
1. If the system has no TDM-BUS errors and is not handling heavy traffic,
then retry the command at 1-minute intervals up to 5 times.
1003
ABRT
The system could not allocate a tone receiver for the test. The system may
be oversized for the number of Tone Detectors present, or some Tone
Detectors may be out of service.
1. Resolve any TTR-LEV errors.
2. Resolve any TONE-PT errors.
3. Retry the command at 1-minute intervals up to 5 times.
1 of 2
366 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ADX16A-PT (AUDIX Analog Line/Control Link)
Table 100: Test #6 NPE Crosstalk Test (continued)
Error
Code
Test
Result
Description / Recommendation
1004
ABRT
The port was seized by a valid call during the test. The test has been
aborted.
1. Use display port location to determine the station extension.
Use status station to determine the service state of the port. If the
port is active, it is unavailable for certain tests. Wait until the port is idle
before testing.
2. Retry the command at 1-minute intervals up to 5 times.
1005
ABRT
This condition indicates that the test is not applicable when the analog port is
used in a combined modem pool. This error can be ignored.
1018
ABRT
Test disabled via administration.
1. To enable the test for the particular analog station being tested, enter
change station extension.
2. Enter y in the Test field.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2012
ABRT
System could not respond to this request.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
Any
FAIL
The NPE of the tested port was found to be transmitting in error. This
causes noisy and unreliable connections.
1. Replace the circuit pack.
PASS
The port is correctly using its allocated time slots. User-reported troubles on
this port should be investigated by using other port tests, by examining
station wiring, or by examining the station.
2 of 2
Issue 1 June 2005
367
Communication Manager Maintenance-Object Repair Procedures
Conference Circuit Test (#7)
This test verifies that the NPE channel for the port being tested can correctly perform the
conferencing function.
Table 101: Test #7 Conference Circuit Test
Error
Code
Test
Result
Description / Recommendation
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1000
ABRT
System resources required to run test are not available. The port may be
busy with a valid call.
1. Use display port location to determine the station extension.
Use status station to determine the service state of the port. If the
port is active, wait until it is idle before retesting.
2. Retry the command at 1-minute intervals up to 5 times.
1004
ABRT
The port was seized by a valid call during the test. The test has been
aborted.
1. Use display port location to determine the station extension.
Use status station to determine the service state of the port. If the
port is active, wait until it is idle before testing.
2. Retry the command at 1-minute intervals up to 5 times.
1018
ABRT
Test disabled by administration. This only applies to analog stations.
1. To enable the test for the analog station being tested, enter change
station extension and enter y in the Test field.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
Could not allocate the necessary system resources for this test.
1. Retry the command at 1-minute intervals up to 5 times.
Any
FAIL
The NPE of the tested port did not conference the tones correctly. This
causes noisy and unreliable connections.
1. Replace the circuit pack.
PASS
The port can correctly conference multiple connections. User-reported
troubles on this port should be investigated by using other port tests and by
examining station, trunk, or external wiring.
368 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ADX16A-PT (AUDIX Analog Line/Control Link)
Loop-Around Test (#161)
This test is designed to check the on-board transmission capabilities of the NPE on the analog
port.
Table 102: Test #161 Loop-Around Test
Error
Code
Test
Result
Description / Recommendation
ABRT
Could not allocate the necessary system resources for this test.
1. Retry the command at 1-minute intervals up to 5 times.
1000
ABRT
System resources required to run this test are not available. The port may
be busy with a valid call.
1. Use display port location to determine the station extension.
Use status station to determine the service state of the port. If the
port is active, wait until it is idle before testing.
2. If the port status is idle, retry the command at 1-minute intervals up to 5
times.
1002
ABRT
The system could not allocate time slots for the test. The system may be
under heavy traffic conditions or it may have time slots out-of-service due to
TDM-BUS errors.
1. If the system has no TDM-BUS errors and is not handling heavy traffic,
retry the command at 1-minute intervals up to 5 times.
1003
ABRT
The system could not allocate a tone receiver for the test. The system may
be oversized for the number of Tone Detectors present, or some Tone
Detectors may be out of service.
1. Resolve any TTR-LEV errors.
2. Resolve any TONE-PT errors.
3. If neither condition exists, retry the command at 1-minute intervals up to
5 times.
1004
ABRT
The port was seized by a valid call during the test. The test has been
aborted.
1. Use display port location to determine the station extension.
Use status station to determine the service state of the port. If the
port is active, wait until it is idle before testing.
2. Retry the command at 1-minute intervals up to 5 times.
1 of 2
Issue 1 June 2005
369
Communication Manager Maintenance-Object Repair Procedures
Table 102: Test #161 Loop-Around Test (continued)
Error
Code
Test
Result
Description / Recommendation
1018
ABRT
Test disabled by administration.
1. To enable the test for the particular analog station, enter change
station extension.
2. Enter y in the Test field.
2000
ABRT
Response to the test was not received within the allowable time period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
FAIL
The reflective loop-around test failed. This causes noisy or unreliable
connections or other users calling this port may hear an echo.
1. Replace the circuit pack.
PASS
The port is able to provide an analog transmission path to the station
equipment. User-reported troubles on this port should be investigated by
using other port tests, by examining station wiring, or by examining the
station.
2 of 2
370 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
AESV-LNK (AE Services Link)
AESV-LNK (AE Services Link)
S8700 | 8710 / S8500 / S8300
MO Name in Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
AESV-LNK
MAJ
WRN
test aesvcs-server
Application Enablement
Services (AESVCS)
Link
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 AESVCS Server are established and torn down.
AESVCS Links that are connected to the same AESVCS Server are grouped into an AESVCS
Session.
Error Log Entries and Test to Clear Values
Table 103: AESV-LNK Error Log Entries
Error Type
Aux
Data
Associated
Test
513 (a)
AESVCS
Link
Heartbeat
Test (#1324)
769 (b)
1537 (c)
2561 (d)
Any
Alarm
Level
On/Off
Board
Test to Clear Value
WRN
Off
none
Log
only
Log
only
Log
only
Notes:
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 is 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
due to the “leaky bucket” strategy. If the hyperactivity persists, escalate the problem.
Issue 1 June 2005
371
Communication Manager Maintenance-Object Repair Procedures
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 is generated against this condition. Escalate if the error persists.
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 is 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.
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 and 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 connection. Escalate if the problem persists.
1 of 2
372 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
AESV-LNK (AE Services Link)
Aux Data
Description
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 connection. Escalate if the problem persists.
2 of 2
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.
System Technician-Demanded Tests:
Descriptions and Error Codes
Investigate tests in the order shown. By clearing error codes associated with the AESVCS Link
Heartbeat Test (#1324), you might clear errors from other tests in the testing sequence.
Order of Investigation
D/ND1
Short Test
Sequence
Long Test
Sequence
AESVCS Link Heartbeat Test (#1324)
X
X
ND
AESVCS Session Level Link Status Test
(#1323)
X
X
ND
1. D = Destructive; ND = Nondestructive
AESVCS Link Heartbeat Test (#1324)
The 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.
Table 104: AESVCS Link Heartbeat Test (#1324)
Error
Code
Test
Result
Description / Recommendation
FAIL
The heartbeat test failed.
1. Check the network connectivity and check the AE Server.
1 of 2
Issue 1 June 2005
373
Communication Manager Maintenance-Object Repair Procedures
Table 104: AESVCS Link Heartbeat Test (#1324) (continued)
Error
Code
Test
Result
Description / Recommendation
PASS
The heartbeat test passed.
2 of 2
AESVCS Session Level Link Status Test (#1323)
The AESVCS Session Level Link Status Test determines if any AESVCS Links are associated
with a given AESVCS Session.
Table 105: AESVCS Session Level Link Status Test (#1323)
Error
Code
Test
Result
Description / Recommendation
1124
ABORT
AE Services Server is disabled on the AE Services Administration page
of the IP Services form
FAIL
No AESVCS links are associated with this session.
PASS
At least one AESVCS link is assigned.
374 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
AESV-SESS (AE Services Session)
AESV-SESS (AE Services Session)
S8700 | 8710 / S8500 / S8300
MO Name in Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
AESV-SESS
MAJ
WRN
test aesvcs-server
Application Enablement
Services (AESVCS
Session)
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.
Error Log Entries and Test to Clear Values
Table 106: AESV-SESS Error Log Entries
Error Type
Aux
Data
Associated
Test
513 (a)
1-16
769 (b)
1-16
1025 (c)
1-16
MAJ
1537 (d)
1-16
Log
only
2561 (e)
1-16
Log
only
AESVCS
Link
Heartbeat
Test (#1324)
Alarm
Level
On/Off
Board
Test to Clear Value
WRN
Off
none
Off
test aesvcs-server
Log
only
Notes:
a. Error 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
due to the “leaky bucket” strategy. Refer to AESV-LNK (AE Services Link) on page 371
section for more information.
Issue 1 June 2005
375
Communication Manager Maintenance-Object Repair Procedures
b. Error 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
filed 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 section for
more information.
c. Error Type 1025 is displayed when no AESVCS Links are left in an AESVCS Session. This
alarm is cleared when Communication Manager associates a new AESVCS Link to the
session. The Aux Data filed contains the link ID of the last AESVCS Link deleted from the
session.
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 filed 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
section for more information.
e. Error Type 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
section for more information.
System Technician-Demanded Tests:
Descriptions and Error Codes
Investigate tests in the order shown. By clearing error codes associated with the AESVCS Link
Heartbeat Test (#1324), you might clear errors from other tests in the testing sequence.
Order of Investigation
D/ND1
Short Test
Sequence
Long Test
Sequence
AESVCS Link Heartbeat Test (#1324)
X
X
ND
AESVCS Session Level Link Status Test (#1323)
X
X
ND
1. D = Destructive; ND = Nondestructive
376 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
AESV-SESS (AE Services Session)
AESVCS Link Heartbeat Test (#1324)
The 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.
Table 107: AESVCS Link Heartbeat Test (#1324)
Error
Code
Test
Result
Description / Recommendation
FAIL
The heartbeat test failed.
1. Check the network connectivity and check the AE Server.
PASS
The heartbeat test passed.
AESVCS Session Level Link Status Test (#1323)
The AESVCS Session Level Link Status Test determines if any AESVCS Links are associated
with a given AESVCS Session.
Table 108: AESVCS Session Level Link Status Test (#1323)
Error
Code
Test
Result
Description / Recommendation
1124
ABORT
AE Services Server is disabled on the AE Services Administration page
of the IP Services form
FAIL
No AESVCS links are associated with this session.
PASS
At least one AESVCS link is assigned.
Issue 1 June 2005
377
Communication Manager Maintenance-Object Repair Procedures
ALARM-PT (Alarm Port)
S8700 | 8710 / S8500 / S8300
MO Name in Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
ALARM-PT
MIN
test port location l
Alarm-Port
ALARM-PT
WRN
test port location sh
Alarm-Port
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 ports ability to
detect an external device alarm. The related MO, EXT-DEV ADMIN? Y (External Device
Alarm) on page 1246, is used for the off-board external device alarm.
Error Log Entries and Test to Clear Values
Table 109: ALARM-PT Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Test to Clear Value
0 (a)
0
Any
Any
Any
test port location sh r 1
15 (b)
Any
Audits and Updates
(#36)
18
0
busyout station
extension
WRN
OFF
release station extension
None
WRN
ON
test port location sh
130 (c)
Notes:
a. Error 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
procedures.
b. Error Type 15 is a software audit error that does not indicate any hardware malfunction.
Run the short test sequence, and investigate errors.
c. Error Type 130 indicates that the circuit pack or Media Module was removed or has been
insane for more than 11 minutes. To clear the error, reseat or replace the circuit pack or
Media Module
378 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ALARM-PT (Alarm Port)
System Technician-Demanded Tests:
Descriptions and Error Codes
Investigate tests in the order presented in the table below. For example, by clearing error codes
associated with the Battery Feed test (#35), you may also clear errors generated from other
tests in the testing sequence.
Order of Investigation
Short Test
Sequence
Long Test
Sequence
D/
ND1
Battery Feed test (#35)
X
X
ND
Station Status and Translation Audits and Updates test
(#36)
X
X
ND
1. D = Destructive; ND = Nondestructive
Battery Feed Test (or Port Diagnostic Test) (#35)
The battery feed chip provides power to the telephone equipment, signaling, rotary dial pulsing,
transmission, and balance. This test checks the signaling and switchhook capabilities of the
battery feed chip by terminating the port, applying battery, and trying to detect a current.
Table 110: Test #35 Battery Feed Test
Error
Code
Test
Result
Description / Recommendation
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
ABRT
Internal system error.
1. Retry the command at 1-minute intervals a maximum of 5 times.
1000
ABRT
System resources required to run this test are not available. The port may
be reporting an external device alarm.
1. Before retesting, 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.
1 of 3
Issue 1 June 2005
379
Communication Manager Maintenance-Object Repair Procedures
Table 110: Test #35 Battery Feed Test (continued)
Error
Code
Test
Result
Description / Recommendation
1000
ABRT
System resources required to run this test are not available. The port may
be busy with a valid call. Use display port location to determine the
station extension, attendant number, or trunk group/member number of the
port. Use status station, status attendant, or status trunk to
determine the service state of the port. If the service state indicates that the
port is in use, then the port is unavailable for certain tests. You must wait
until the port is idle before retesting. Attendants are always in use
(off-hook) if the handset is plugged in and the port is not busied out.
1. If the port status is idle, then retry the command at 1-minute intervals a
maximum of 5 times.
1004
ABRT
The port received an EXT-DEV failure during the test. The test has been
aborted.
1. Before retesting, 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.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
Could not allocate the necessary system resources to run this test. This
could be due to a failure to seize the port.
1. Retry the command at 1-minute intervals up to 5 times.
FAIL
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.
1. Before retesting, enter test external-device-alarm port
location to determine whether the port is reporting an EXT-DEV
failure. Wait until the port has no EXT-DEV failures before retesting.
2. Retry the command at 1-minute intervals up to 5 times.
PASS
The port’s battery feed chip is able to provide power to the external device
alarm to detect contact closure.
2 of 3
380 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ALARM-PT (Alarm Port)
Table 110: Test #35 Battery Feed Test (continued)
Error
Code
Test
Result
Description / Recommendation
0
NO
BOARD
The test could not relate the internal ID to the port (no board). This could
be due to incorrect translations, no board is inserted, an incorrect board is
inserted, or an insane board is inserted.
1. Check to ensure that the board translations are correct. enter list
config, and resolve any problems that are found.
2. If the board was found to be correctly inserted in step 1, enter
busyout board location
3. Enter reset board location
4. Enter release board location
5. Enter test board location long
This should re-establish the linkage between the internal ID and the port. If
this is not the case, check to ensure that there is a valid board inserted.
3 of 3
Station Status and Translation Audits and Updates Test (#36)
Port Updates Test (#36)
For an analog line port that is administered as an external alarm, this test is limited to updating
the software with the switchhook state.
This test sends port level translation data from switch processor to the circuit pack to assure
that the translation is correct. The port audit operation verifies the consistency of the current
state of the port in the switch software.
Table 111: Test #36 Station Status and Translation Audits and Updates
Error
Code
Test
Result
Description / Recommendation
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1 of 3
Issue 1 June 2005
381
Communication Manager Maintenance-Object Repair Procedures
Table 111: Test #36 Station Status and Translation Audits and Updates (continued)
Error
Code
Test
Result
Description / Recommendation
1000
ABRT
The test was aborted because system resources required to run this test
were not available. The port may be busy with a valid call. Use display
port PCSSpp to determine the station extension of the port. Use status
station to determine the service state of the port. If the service state
indicates that the port is in use, then the port is unavailable for certain
tests. You must wait until the port is idle before retesting.
1. If the port is idle, retry the command at 1-minute intervals a maximum
of 5 times.
1004
ABRT
The port received an EXT-DEV failure during the test. The test has been
aborted.
1. Before retesting, 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.
1006
ABRT
This port has been busied out by command.
1. Check Error Log for Error Type 18 (port busied out). If present, use
release port location to release the port and run the test again.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1
FAIL
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.
1. Before retesting, enter test external-device-alarm port
location to determine whether the port is reporting an EXT-DEV
failure. Wait until the port has no EXT-DEV failures.
2. If the port has no EXT-DEV failures, retry the command at 1-minute
intervals up to 5 times.
7
FAIL
The translation update failed. This does not indicate a hardware problem
but may be an internal software error.
2 of 3
382 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ALARM-PT (Alarm Port)
Table 111: Test #36 Station Status and Translation Audits and Updates (continued)
Error
Code
0
Test
Result
Description / Recommendation
PASS
The software and the port processor have the same status.
NO
BOARD
The test could not relate the internal ID to the port (no board). This could
be due to incorrect translations, no board is inserted, an incorrect board is
inserted, or an insane board is inserted.
1. Check to ensure that the board translations are correct. Enter list
config, and resolve any problems that are found.
2. If the board was found to be correctly inserted in step 1, enter
busyout board location
3. Enter reset board location
4. Enter release board location
5. Enter test board location long. This should re-establish the
linkage between the internal ID and the port. If this is not the case,
dispatch to check to ensure that there is a valid board inserted.
3 of 3
Issue 1 June 2005
383
Communication Manager Maintenance-Object Repair Procedures
ANL-16-L (16-Port Analog Line)
S8700 | 8710 / S8500
MO Name in Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
ANL-16-L
MIN
test port location l
16-Port Analog Line
ANL-16-L
WRN
test port location sh
16-Port Analog Line
The circuit packs listed below provide 16 analog line ports for single-line voice terminals. The
table below indicates which circuit packs are equipped with lightning protection (for
off-premises, out-of -building stations), and which ones support the neon message waiting lamp
feature.
16-Port Analog Line Circuit Packs
Circuit Pack
TN468B
Off- Premises
Neon
y
TN479
TN746
y
TN746B
y
TN2135
y
TN2144
y
TN2149
y
TN2180
y
y
S8700 | 8710 / S8500
These circuit packs provide 16 ports for analog voice terminals. The TN746, TN468, and TN749
support only single-line, on-premises/in-building, analog voice terminals, and not off-premises
stations, since these circuit packs are not equipped with lightning protection. The TN746B,
TN2144, TN2149, and TN468B support both on-premises and off-premises (that is,
out-of-building) analog voice terminals. The TN468, TN468B, TN479, TN2135, TN2144, and
TN2149 do NOT support the neon message waiting feature.
No maintenance of the terminal connected to the 16-Port Neon Analog Line circuit pack is
performed, except to determine whether or not the terminal is connected. Failures of the neon
message waiting lamp power and the common ringing application circuitry are reported as part
of common port circuit pack errors; see errors 1281 and 1793 in XXX-BD (Common Port Circuit
Pack/Media Module) on page 2539.
384 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-16-L (16-Port Analog Line)
Ringing Caused by Maintenance Testing
Test #48 may cause some terminal equipment to ring briefly during daily maintenance. If this
ringing is disturbing the customer or the terminal equipment, it should be disabled in the Tests
field of the change station extension screen. Be aware that this action will also disable
Tests #6, 7, 161, and 35.
Error Log Entries and Test to Clear Values
Table 112: 16-Port Analog Line Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/
Off
Board
Test to Clear Value
0 (a)
0
Any
Any
Any
test port location sh r 1
1(b)
40960
40975
40977
none
15(f)
Any
Audits and Updates
(#36)
18
0
busyout station
extension
WRN
ON
release station extension
None
WRN
ON
test port location sh
130(g)
257(h)
40973
none
513(i)
Station Present (#48)
WRN
OFF
test port location sh r 2
769
Battery Feed test
(#35)
MIN
WRN1
ON
test port location sh r 2
1025
Looparound (#161)
MIN
WRN1
ON
test port location l r 2
1281
Conference test (#7)
MIN
WRN1
ON
test port location l r 2
1537
NPE Crosstalk (#6)
MIN
WRN1
ON
test port location l r 2
1. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in set options.
Issue 1 June 2005
385
Communication Manager Maintenance-Object Repair Procedures
Notes:
a. Error 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
procedures.
b. Error Type 1: These are in-line errors and can only be resolved over time.
c. 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.
d. 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 test port
location, and follow the procedure for Test #48.
e. Aux Data 40977 indicates that no terminal equipment was connected when ringing was
attempted. Run the short test via test port location, and follow the procedure for the
results of Test #48.
f. Error Type 15 is a software audit error that does not indicate any hardware malfunction.
Run short test sequence, and investigate associated errors.
g. Error Type 130: the circuit pack has been removed or has been insane for more than 11
minutes. To clear the error, reseat or replace the circuit pack.
h. Error Type 257: This is an in-line error and can only be resolved over time. This error
indicates that ringing voltage is absent. If only 1 analog circuit pack in the system has this
problem, then replace the circuit pack. If only analog circuit packs on a particular carrier
have this error, then the ringing generator may not be connected to this carrier. If analog
circuit packs on many carriers have this error, then it is probably a problem with the ringing
generator.
i. Error Type 513: Associated 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 #6, 7, 161, and 35.
386 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-16-L (16-Port Analog Line)
System Technician-Demanded Tests:
Descriptions and Error Codes
Investigate tests in the order presented. By clearing error codes associated with the Battery
Feed test (#35), you may also clear errors generated from other tests in the testing sequence.
Order of Investigation
Short Test
Sequence
Long Test
Sequence
D/ND1
Battery Feed test (#35)
X
X
ND
Station Present test (#48)
X
X
ND
Looparound test (#161)
X
ND
Conference test (#7)
X
ND
NPE Crosstalk test (#6)
X
ND
X
ND
Station Status and Translation Audits and Updates test
(#36)
X
1. D = Destructive; ND = Nondestructive
NPE Crosstalk Test (#6)
One or more Network Processing Elements (NPEs) reside on each circuit pack with a TDM Bus
interface. The NPE controls port connectivity and gain, and provides conference functions on a
per-port basis.
This test verifies that this port’s NPE channel talks on the selected time slot and never crosses
over to time slots reserved for other connections. If the NPE is not working correctly, one-way
and noisy connections may be observed. This test is usually part of the long test sequence and
executes in about 20 to 30 seconds.
Table 113: Test #6 NPE Crosstalk Test
Error
Code
Test
Result
Description / Recommendation
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1 of 4
Issue 1 June 2005
387
Communication Manager Maintenance-Object Repair Procedures
Table 113: Test #6 NPE Crosstalk Test (continued)
Error
Code
Test
Result
Description / Recommendation
1000
ABRT
System resources required to run test are not available. The port may be
busy with a valid call. This result is also reported for the system’s
Music-On-Hold port when it is off-hook, which it usually is.
1. Enter display port location to determine the station’s
extension. Enter status station extension to determine the
service state of the port. If the port is active, wait until it is idle.
2. Retry the command at 1-minute intervals up to 5 times.
1001
ABRT
System resources required to run test are not available. This could be due
to a failure to seize the port.
1. Retry the command at 1-minute intervals up to 5 times.
1002
ABRT
The system could not allocate time slots for the test. The system may be
under heavy traffic conditions or have time slots out-of-service due to
TDM-BUS errors.
1. 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.
1003
ABRT
The system could not allocate a tone receiver for the test. The system
may be oversized for the number of Tone Detectors present, or some
Tone Detectors may be out of service.
1. Resolve any TTR-LEV errors.
2. Resolve any TONE-PT errors.
3. If neither condition exists, retry the command at 1-minute intervals up
to 5 times.
1004
ABRT
The port was seized by a valid call during the test. The test has been
aborted.
1. Use the display port location command to determine the
station extension. Use status station to determine the service
state of the port. If the port is active, wait until the it is idle before
testing.
2. Retry the command at 1-minute intervals up to 5 times.
1005
ABRT
The test was aborted due to a configuration problem. This test may not be
applicable, or it may be disruptive to terminal equipment other than a voice
terminal (for example, the modem pool member or Music On Hold).
2 of 4
388 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-16-L (16-Port Analog Line)
Table 113: Test #6 NPE Crosstalk Test (continued)
Error
Code
Test
Result
Description / Recommendation
1018
ABRT
The test has been disabled by administration. The default for the Test field
on the station screen is y. Determine why this field has been set to “no” on
this station (this may be due to the ringing application Test #48, that can
be customer or terminal disturbing.
1. To enable the test for a particular station being tested, enter change
station extension and set the Test field on the station screen to
y.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
System resources required to run test are not available. This could be due
to a failure to seize the port.
1. Retry the command at 1-minute intervals up to 5 times.
Any
FAIL
This test can fail due to either on- or off-board problems. Off-board
problems include EXP-PN and EXP-INTF faults, (S8700 IP: RMC-ENV
faults), TDM-BUS faults, and faults associated with the Tone Detectors/
Tone Generators. Clear every off-board problem before replacing the
board. A TDM-BUS problem is usually the result of a faulty board
connected to the backplane, or bent pins on the backplane.
1. Resolve any EXP-PN and EXP-INTF errors.
S8700 IP: Resolve any RMC-ENV errors.
2. Resolve any TDM-BUS errors.
3. Resolve any TONE-BD or TONE-PT errors.
4. Test the board when the faults from steps 1, 2, and 3 are cleared.
Replace the board only if the test fails.
PASS
The port is correctly using its allocated time slots. User-reported troubles on
this port should be investigated by using other port tests, by examining
station wiring, or by examining the station.
3 of 4
Issue 1 June 2005
389
Communication Manager Maintenance-Object Repair Procedures
Table 113: Test #6 NPE Crosstalk Test (continued)
Error
Code
Test
Result
Description / Recommendation
0
NO
BOARD
The test could not relate the internal ID to the port (no board). This could
be due to incorrect translations, no board is inserted, an incorrect board is
inserted, or an insane board is inserted.
1. Verify that the board’s translations are correct. Enter list config,
and resolve any problems.
2. If the board was found to be correctly inserted in step 1, enter
busyout board location
3. Enter reset board location
4. Enter release board location
5. Enter 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.
4 of 4
Conference Circuit Test (#7)
This test verifies that the NPE channel for the port being tested can correctly perform the
conferencing function.
Table 114: Test #7 Conference Circuit Test
Error
Code
Test
Result
Description / Recommendation
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1000
ABRT
System resources required to run this test are not available. The port may
be busy with a valid call. This result is also reported for the system’s
Music-On-Hold port when it is off-hook, which it usually is.
1. Enter display port location to determine the station’s extension.
Enter status station extension to determine the service state of
the port. If the port is active, wait until it is idle.
2. Retry the command at 1-minute intervals up to 5 times.
1 of 3
390 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-16-L (16-Port Analog Line)
Table 114: Test #7 Conference Circuit Test (continued)
Error
Code
Test
Result
Description / Recommendation
1004
ABRT
The port was seized by a valid call during the test. The test has been
aborted.
1. Use display port location to determine the station extension.
Use status station to determine the service state of the port. If
the port is active, wait until it is idle.
2. Retry the command at 1-minute intervals up to 5 times.
1005
ABRT
The test was aborted due to a configuration problem. This test may not be
applicable, or it may be disruptive to terminal equipment other than a voice
terminal (for example, the modem pool member or Music On Hold).
1018
ABRT
The test has been disabled by administration. The default for the Test field
on the station screen is y. Determine why this field is n on this station. This
may be due to the ringing application Test #48, which can be customer or
terminal disturbing.
1. To enable the test for the particular analog station being tested, enter
change station extension and set the Test field on the station
to y.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
System resources required to run this test are not available.
1. Resolve any TONE-PT errors.
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.
Any
FAIL
The NPE of the tested port did not conference the tones correctly. This
causes noisy and unreliable connections.
1. Enter display port and status station to determine whether
the station is idle. If the station is idle, enter test port for this port.
2. If the test continues to fail, enter busyout port and release port,
and retest.
3. If the test still fails, replace the board.
PASS
The port can correctly conference multiple connections. User-reported
troubles on this port should be investigated by using other port tests and by
examining station, trunk, or external wiring.
2 of 3
Issue 1 June 2005
391
Communication Manager Maintenance-Object Repair Procedures
Table 114: Test #7 Conference Circuit Test (continued)
Error
Code
Test
Result
Description / Recommendation
0
NO
BOARD
The test could not relate the internal ID to the port (no board). This could
be due to incorrect translations, no board is inserted, an incorrect board is
inserted, or an insane board is inserted.
1. Verify that the board’s translations are correct. Enter list config,
and resolve any problems.
2. If the board was found to be correctly inserted in step 1, enter
busyout board location
3. Enter reset board location
4. Enter release board location
5. Enter 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.
3 of 3
Battery Feed Test (or Port Diagnostic Test) (#35)
The battery feed chip provides power to the telephone equipment, signaling, rotary dial pulsing,
transmission, and balance. This test checks the signaling and switchhook capabilities of the
battery feed chip by terminating the port, applying battery and detecting the resulting current.
Note:
Note:
For the TN746B, Test #35 does not actually run and instead always returns
PASS. Test #35 operates in the normal manner for TN746.
Table 115: Test #35 Battery Feed Test
Error
Code
Test
Result
Description / Recommendation
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1 of 3
392 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-16-L (16-Port Analog Line)
Table 115: Test #35 Battery Feed Test (continued)
Error
Code
Test
Result
Description / Recommendation
1000
ABRT
System resources required to run this test are not available. The port may
be busy with a valid call. This result is also reported for the system’s
Music-On-Hold port when it is off-hook, which it usually is.
1. Enter display port location to determine the station’s extension.
Enter status station extension to determine the service state of
the port. If the port is active, wait until it is idle.
2. Retry the command at 1-minute intervals up to 5 times.
1004
ABRT
The port was seized by a valid call during the test.
1. Use display port location to determine the station extension.
Use status station to determine the service state of the port. If the
port is active, wait until it is idle.
2. Retry the command at 1-minute intervals up to 5 times.
1005
ABRT
The test was aborted due to a configuration problem. This test may not be
applicable, or it may be disruptive to terminal equipment other than a voice
terminal (for example, the modem pool member or Music On Hold).
1018
ABRT
The test has been disabled by administration. The default for the Test field
on the station screen is y. Determine why this field was set to n on this
station. It may be due to the ringing application Test #48, which can be
customer or terminal disturbing.
1. To enable the test for the particular analog station being tested, enter
change station extension and set the Test field on the station to
y.
S8700
| 8710
S8500
S8300
1392
ABRT
This port is currently a TTI port and the test will not execute on it.
1. Verify that the port is a TTI port using either display port, which
shows that the port is a TTI port) or list config, which shows a t for
the port.
2. If the port is not a TTI port, escalate the problem. If both commands
indicate that the port is a TTI port, the abort is correct for the test, and
no action is necessary.
2 of 3
Issue 1 June 2005
393
Communication Manager Maintenance-Object Repair Procedures
Table 115: Test #35 Battery Feed Test (continued)
Error
Code
Test
Result
Description / Recommendation
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
FAIL
The port's battery feed chip is unable to supply sufficient power to the
terminal equipment. This could be a marginal test, and the terminal
equipment may be operating satisfactorily.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to fail, determine whether the customer is
experiencing problems on this line. Replace the circuit pack only if the
customer is experiencing problems.
0
PASS
The port’s battery feed chip is able to provide power to the station equipment
to detect on-/off-hook, but may not be able to supply power for touch-tones.
If touch-tones are inoperative on this station, then replace the circuit pack
because this port is inoperative. User-reported troubles on this port should
be investigated by using other port tests, by examining station wiring, or by
examining the station.
NO
BOARD
The test could not relate the internal ID to the port (no board). This could
be due to incorrect translations, no board is inserted, an incorrect board is
inserted, or an insane board is inserted.
1. Verify that the board’s translations are correct. Enter list config,
and resolve any problems.
2. If the board was found to be correctly inserted in step 1, enter busyout
board
3. Enter reset board location
4. Enter release board location
5. Enter 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.
3 of 3
394 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-16-L (16-Port Analog Line)
Station Status and Translation Audits and Updates Test (#36)
This test updates the analog port’s message lamp state (if it has one) and translations with
information in the software.
Table 116: Test #36 Station Status and Translation Audits and Updates
Error
Code
Test
Result
Description / Recommendation
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1004
ABRT
The port was seized by a valid call during the test. The test has been
aborted.
1. Use display port location to determine the station extension.
Use status station to determine the service state of the port. If the
port is active, wait until it is idle.
2. Retry the command at 1-minute intervals up to 5 times.
3. If the test continues to abort and the port is not in use, escalate the
problem.
1005
ABRT
The test was aborted due to a configuration problem. This test may not be
applicable, or it may be disruptive to terminal equipment other than a voice
terminal (for example, the modem pool member or Music On Hold).
1006
ABRT
This port has been busied out by command, or taken out-of-service by the
failure of the NPE Crosstalk test.
1. Look in the error log for error type 18 (port busied out) for this port. If
this error is present, release the port with release station
extension, and run the test again.
2. Check the error log for error type 1025 (NPE crosstalk test failed) for
this port. If this error is present, investigate the errors associated with
the NPE Crosstalk test (#6).
3. Make sure that the terminal is connected and in service, and then
retest.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1 of 2
Issue 1 June 2005
395
Communication Manager Maintenance-Object Repair Procedures
Table 116: Test #36 Station Status and Translation Audits and Updates (continued)
Error
Code
Test
Result
Description / Recommendation
1
FAIL
This does not indicate a hardware problem. The switchhook audit failed.
The other updates were not performed because of this failure. This may
occur when the audit is performed at the same time the terminal equipment
goes off-hook.
1. Use status station to determine when the port is available.
2. Retry the command at 1-minute intervals up to 5 times.
5
FAIL
This may be an internal software error. The message waiting lamp update
failed. The translation and ringer updates were not performed because of
this failure.
7
FAIL
The translation update failed. There may be an internal software error. The
ringer update was not performed because of this failure.
8
FAIL
This does not indicate a hardware problem. There may be an internal
software error. The ringer update failed.
1. Retry the command at 1-minute intervals up to 5 times.
0
PASS
The software and the port processor have the same status. User-reported
troubles on this port should be investigated by using other port tests, by
examining station wiring, or by examining the station.
NO
BOARD
The test could not relate the internal ID to the port (no board). This could be
due to incorrect translations, no board is inserted, an incorrect board is
inserted, or an insane board is inserted.
1. Verify that the board’s translations are correct. Enter list config
and resolve problems.
2. If the board was found to be correctly inserted in step 1, enter busyout
board
3. Enter reset board location
4. Enter release board location
5. Enter 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.
2 of 2
396 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-16-L (16-Port Analog Line)
Station Present Test (or Ringing Application Test) (#48)
This test applies momentary ringing voltage to the terminal equipment and monitors resulting
current flow to determine whether terminal equipment is connected to the port. This test may
cause some terminal equipment to ring briefly during daily maintenance. If this ringing disturbs
the customer or the terminal equipment, you can disable it via the Tests field on the change
station screen. However, on some software releases, Tests #6, 7, 161, and 35 are disabled.
Table 117: Test #48 Station Present Test
Error
Code
Test
Result
Description / Recommendation
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1000
ABRT
System resources required to run this test are not available. The port may
be busy with a valid call.
1. If the port status is idle, then retry the command at 1-minute intervals a
maximum of 5 times.
1004
ABRT
The port was seized by a valid call during the test. The test has been
aborted.
1. Use display port location to determine the station extension.
2. Use status station to determine the service state of the port. If
the service state indicates that the port is active, wait until it is idle.
3. Retry the command at 1-minute intervals up to 5 times.
1005
ABRT
The test was aborted due to a configuration problem. This test may not be
applicable, or it may be disruptive to terminal equipment other than a voice
terminal (for example, the modem pool member or Music On Hold).
1008
ABRT
Could not allocate a ringing circuit. Either every ringing circuit is active or
the ringing generator is either defective or incorrectly wired.
Retry the command at 1-minute intervals up to 5 times.
1. If the test continues to abort, look for RING-GEN errors in the Error
Log. If an ABORT 1008 occurs for this test on other circuit packs as
well, then the ringing generator may be defective or is incorrectly
wired. If it does not occur on other ports, then all four ring phases are
active.
1 of 3
Issue 1 June 2005
397
Communication Manager Maintenance-Object Repair Procedures
Table 117: Test #48 Station Present Test (continued)
Error
Code
Test
Result
Description / Recommendation
1018
ABRT
The test has been disabled by administration. The default for the Test field
on the station screen is y. Determine why this field was set to n on this
station. It may be due to the brief ringing disturbance that this test may
cause.
1. To enable the test for the particular analog station being tested, enter
change station extension and set the Test field on the station
to y.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
Could not allocate necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
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.
3. Check all of the wiring between the station equipment and the switch.
Then, run the test again.
4. If the test still fails, the set may be defective. Check the set, and
replace it, if necessary.
5. Some terminal equipment could fail even when it is connected
properly. If this is the case, disable the test using change station
extension (enter n into the Test field). Note that this action also
disables Tests 6, 7, 161, and 35 on this port.
PASS
The station is connected properly to the switch. This test may also pass if
no terminal equipment is connected and the terminal is located very far
from the switch. Investigate user-reported troubles on this port by using
other port tests or by examining the station and its wiring.
2 of 3
398 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-16-L (16-Port Analog Line)
Table 117: Test #48 Station Present Test (continued)
Error
Code
Test
Result
Description / Recommendation
0
NO
BOARD
The test could not relate the internal ID to the port (no board). This could
be due to incorrect translations, no board is inserted, an incorrect board is
inserted, or an insane board is inserted.
1. Verify that the board’s translations are correct. Enter list config,
and resolve any problems.
2. If the board was found to be correctly inserted in step 1, enter
busyout board location
3. Enter reset board location
4. Enter release board location
5. Enter 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.
3 of 3
Loop-Around Test (#161)
This test checks the on-board transmission capabilities of the NPE, the codec, and the battery
feed chip of the analog port. The test passes if the signal measured by the Tone Detector is
within acceptable limits.
Table 118: Test #161 Loop-Around Test
Error
Code
Test
Result
Description / Recommendation
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1000
ABRT
System resources required to run this test are not available. The port
may be busy with a valid call.
1. Use display port location to determine the station extension.
2. Use status station to determine the service state of the port. If
the port is active, wait until it is idle.
3. Retry the command at 1-minute intervals up to 5 times.
1 of 4
Issue 1 June 2005
399
Communication Manager Maintenance-Object Repair Procedures
Table 118: Test #161 Loop-Around Test (continued)
Error
Code
Test
Result
Description / Recommendation
1002
ABRT
The system could not allocate time slots for the test. The system may be
under heavy traffic conditions or it may have time slots out-of-service due
to TDM-BUS errors.
1. If the system has no TDM-BUS errors and is not handling heavy
traffic, retry the command at 1-minute intervals up to 5 times.
1003
ABRT
The system could not allocate a tone receiver for the test. The system
may be oversized for the number of Tone Detectors present, or some
Tone Detectors may be out of service.
1. Resolve any TTR-LEV errors.
2. Resolve any TONE-PT errors.
3. If neither condition exists, retry the command at 1-minute intervals up
to 5 times.
1004
ABRT
The port was seized by a valid call during the test. The test has been
aborted.
1. Use display port location to determine the station extension.
Use status station to determine the service state of the port. If
the port is active, wait until it is idle.
2. Retry the command at 1-minute intervals up to 5 times.
1005
ABRT
This test is not run on ports administered as External Alert, Announcement
or combined modem pool ports. This error can be ignored.
1018
ABRT
The test has been disabled by administration. The default for the Test
field on the station screen is y. Determine why this field was set to n on
this station. It may be due to the ringing application Test #48, which can
be customer or terminal disturbing.
1. To enable the test for the particular analog station being tested, enter
change station extension.
2. Enter y in the Test field.
2 of 4
400 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-16-L (16-Port Analog Line)
Table 118: Test #161 Loop-Around Test (continued)
Error
Code
Test
Result
Description / Recommendation
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
Could not allocate the necessary system resources to run this test. This
could be due to a failure to seize the port.
1. Retry the command at 1-minute intervals up to 5 times.
FAIL
The reflective loop around test failed. This could cause noisy or
unreliable connections, or users calling this port may hear an echo. The
problem can also be off-board.
1. Since the test may be affected by a line seizure, repeat the test at
1-minute intervals up to 5 times.
2. Run circuit pack tests to check the IPSI Tone Generator circuit or
Tone Generator circuit pack and the IPSI Tone Detector circuit or
Tone Detector circuit pack by using test board location
short.
3. Resolve any problems on the Tone Generator circuit or the Tone
Detector circuit.
4. If the Tone Generator and Tone Detector circuits are functioning
properly and the test still fails and a voice terminal is connected and
wired properly, replace the analog line circuit pack.
PASS
The port is able to provide an analog transmission path to the station
equipment. User-reported troubles on this port should be investigated by
using other port tests, by examining station wiring, or by examining the
station.
3 of 4
Issue 1 June 2005
401
Communication Manager Maintenance-Object Repair Procedures
Table 118: Test #161 Loop-Around Test (continued)
Error
Code
Test
Result
Description / Recommendation
0
NO
BOARD
The test could not relate the internal ID to the port (no board). This could
be due to incorrect translations, no board is inserted, an incorrect board
is inserted, or an insane board is inserted.
1. Verify that the board’s translations are correct. Enter list config,
and resolve any problems.
2. If the board was found to be correctly inserted in step 1, enter
busyout board location
3. Enter reset board location
4. Enter release board location
5. Enter 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.
4 of 4
402 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-BD (Analog Line Circuit Pack)
ANL-BD (Analog Line Circuit Pack)
S8700 | 8710 / S8500
MO Name in
Alarm Log
Alarm
Level
Initial Command to Run
Full Name Of MO
ANL-BD
MIN
WRN
test board location sh
8-Port Analog Line circuit pack
ANL-BD
MIN
WRN
test board location sh
8-Port Neon Analog Line circuit pack
ANL-BD
MIN
WRN
test board location sh
16-Port Neon Analog Line circuit
pack
See XXX-BD (Common Port Circuit Pack/Media Module) on page 2539 for circuit pack-level
errors. See also ANL-16-L (16-Port Analog Line) on page 384 for related line information.
See also ANL-LINE (8-Port Analog Line) on page 404 for related line information.
Issue 1 June 2005
403
Communication Manager Maintenance-Object Repair Procedures
ANL-LINE (8-Port Analog Line)
Error log entries and tests also apply to ANL-NE-L (8-Port Analog Line).
S8700 | 8710 / S8500
MO Name in Alarm
Log
Alarm
Level
Initial Command To Run
Full Name of MO
ANL-LINE
MIN
test port location l
8-Port Analog Line
ANL-LINE
WRN
test port location sh
8-Port Analog Line
ANL-NE-L
MIN
test port location l
8-Port Neon Analog Line
ANL-NE-L
WRN
test port location sh
8-Port Neon Analog Line
The 8-port Analog Line circuit packs,
TN712
TN411 [G3rV2]
TN742
TN443 [G3r V2]
TN769
TN443 [G3r V2]
TN467 [G3r V2]
each provide eight ports for single-line, on or off-premises analog endpoints such as analog
voice terminals, queue warning level lamps, recorded announcements, dictation machines,
PAGEPAC paging equipment, external alerting devices, modems, fax machines, and AUDIX
voice ports. Only the TN769 supports a neon message waiting lamp.
Note:
Note:
PAGEPAC™ is a registered trademark of Harris Corporation, Dracon Division.
Test #48 may cause some terminal equipment to ring briefly during daily maintenance, which
may disturb the customer or the terminal equipment. Test #47 may cause a false alarm when
the port is connected to certain off-premises equipment, non-voice terminal equipment, or loop
equipment. In either case, the tests can be disabled by entering n in the Tests field on the
change station extension screen. Be aware that this will disable Tests 6, 35, 47, and 48.
No maintenance of the terminal connected to the 8-Port Analog Line circuit pack or 8-Port Neon
Analog Line circuit pack is performed, except to determine whether or not the terminal is
connected. Failures of the common ringing application circuitry and the neon message waiting
lamp power (ANL-NE-L only) are reported as errors 1281and 1793 against XXX-BD (Common
Port Circuit Pack) in Table 907: Common Port Circuit Pack Maintenance Error Log Entries on
page 2544.
404 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-LINE (8-Port Analog Line)
Hardware Error Log Entries and Test to Clear Values
Table 119: 8-Port Analog Line Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/
Off
Board
Test to Clear Value
0 (a)
0
Any
Any
Any
test port location sh r 1
1 (b)
40960
40975
40977
None
15 (c)
Any
Audits and Updates
(#36)
18
0
busyout station
extension
WRN
OFF
release station extension
130
(d)
None
WRN
ON
test port location sh
257
(e)
Station Present test
(#48)
WRN
OFF
test port location sh r 3
513
Battery Feed test (#35)
MIN
WRN
ON
test port location sh r 2
1
769 (f)
Loop Around &
Conference (47)
1025
NPE Crosstalk test (#6)
test port location l r 3
MIN
WRN
1
ON
test port location l r 3
1281
(g)
1793
(g)
1. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in set options.
Notes:
a. Error 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
procedures.
Issue 1 June 2005
405
Communication Manager Maintenance-Object Repair Procedures
b. Error Type 1: These are in-line errors that can only be resolved over time.
Aux Data 40960: 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: the terminal equipment was on-hook when ring-tip was detected during
ringing. This usually indicates a failure in the terminal equipment or the type of terminal has
a low ringer impedance. Call the terminal equipment and verify that the terminal rings. If
the terminal doesn’t ring, then replace it. Otherwise, enter test port location, and
follow the procedure for Test #48.
Aux Data 40977: no terminal equipment was connected when ringing was attempted. Run
test port location sh, and follow the procedure for the results of Test #48.
c. Error Type 15: software audit error, does not indicate any hardware malfunction. Run short
test sequence, and investigate errors (if any).
d. Error Type 130: the circuit pack was removed or has been insane for more than 11 minutes.
To clear the error, reinsert or replace the circuit pack.
e. Error Type 257: Associated Test #48 may cause some terminal equipment to ring briefly
during daily maintenance. If this ringing is disturbing the customer or the terminal
equipment, it should be disabled via change station extension. However, on some
releases of the software, this will disable Tests #6, 47, and 35 as well as Test #48.
f. Error Type 769: Associated Test #47 may cause a false alarm when the port is connected
to off-premises equipment, some non-voice terminal equipment, and some loop equipment.
If this causes a false alarm, use change station, and change the Tests field to n to
disable the test.
g. Error Types 1281 and 1793: See XXX-BD (Common Port Circuit Pack/Media Module) on
page 2539.
System Technician-Demanded Tests:
Descriptions and Error Codes
Investigate tests in the order presented. By clearing error codes associated with the Battery
Feed test (#35), you may also clear errors generated from other tests in the testing sequence.
Order of Investigation
Short Test
Sequence
Long Test
Sequence
D/ND1
Battery Feed test (#35)
X
X
ND
Station Present test (#48)
X
X
ND
X
ND
NPE Crosstalk test (#6)
406 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-LINE (8-Port Analog Line)
Order of Investigation
Short Test
Sequence
Long Test
Sequence
Loop Around and Conference test (#47)
Station Status and Translation Audits and Updates test (#36)
X
D/ND1
X
ND
X
ND
1. D = Destructive; ND = Nondestructive
NPE Crosstalk Test (#6)
One or more NPEs (Network Processing Elements) reside on each circuit pack with a TDM-bus
interface. The NPE controls port connectivity and gain, and provides conferencing functions on
a per-port basis. The NPE Crosstalk test verifies that this port’s NPE channel talks on the
selected time slot and never crosses over to time slots reserved for other connections. If the
NPE is not working correctly, 1-way and noisy connections may be observed. This test is
usually only part of a port’s long test sequence and executes in about 20 to 30 seconds.
Table 120: Test #6 NPE Crosstalk Test
Error
Code
Test
Result
Description / Recommendation
1000
ABRT
System resources required to run this test are not available. The port may
be busy with a valid call. This result is also reported for the system’s
Music-on-Hold port when it is off-hook, which it usually is.
1. Enter display port location to determine the station’s extension.
Enter status station extension to determine the service state of
the port. If the port is active, it will be unavailable for certain tests.
Wait until the port is idle before retesting.
2. When the port is idle, retry the command at 1-minute intervals up to 5
times.
1001
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1002
ABRT
The system could not allocate time slots for the test. The system may be
under heavy traffic conditions or it may have time slots out-of-service due
to TDM-BUS errors.
1. If the system has no TDM-BUS errors and is not handling heavy traffic,
repeat test at 1-minute intervals up to 5 times.
2. If the test continues to abort, escalate the problem.
1 of 4
Issue 1 June 2005
407
Communication Manager Maintenance-Object Repair Procedures
Table 120: Test #6 NPE Crosstalk Test (continued)
Error
Code
Test
Result
Description / Recommendation
1003
ABRT
The system could not allocate a tone receiver for the test. The system
may be oversized for the number of Tone Detectors present or some Tone
Detectors may be out-of-service.
1. Resolve TTR-LEV errors.
2. Resolve TONE-PT errors.
3. Retry the test at 1-minute intervals up to 5 times.
1004
ABRT
The port was seized by a valid call during the test. The test has been
aborted.
1. Use display port location to determine the station extension.
Use status station to determine the service state of the port. If the
service state indicates that the port is active, then the port is
unavailable for certain tests. Wait until the port is idle before retesting.
2. Retry the command at 1-minute intervals up to 5 times.
3. If the test continues to abort and the port is idle, escalate the problem.
1005
ABRT
The test was aborted due to a configuration problem. This code occurs
under either of the following conditions:
1. This test may not be applicable, or it may be disruptive to terminal
equipment other than a voice terminal (for example, a modem pool
member or music on hold).
2. The circuit pack is one of the following:
- TN742 vintage 13, 14, or 15
- TN769 vintage 3, 4, or 5
1018
ABRT
Test disabled by administration. The default for the Test field on the station
screen is y; thus, you may want to determine why this field has been set to
n on this station (this may be due to the ringing application test 48, which
can be customer or terminal disturbing).
1. To enable the test for a particular station, enter change station
extension and set the Test field to y.
1020
ABRT
The test did not run due to a previously existing error on the specific port or
a more general circuit pack error.
1. Examine Error Log for existing errors against this port or the circuit
pack and attempt to diagnose the previously existing error.
2 of 4
408 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-LINE (8-Port Analog Line)
Table 120: Test #6 NPE Crosstalk Test (continued)
Error
Code
Test
Result
Description / Recommendation
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
System resources required to run this test are not available. Either a
system allocation to get information about the port or to put the port into a
service state failed or the attempt to put the port in connection with a tone
source failed (this could be a Tone-Clock problem). The Tone-Clock and
Tone Detectors could be having a communication problem. For example,
the companding modes could be out of synchronization.
1. Retry the command at 1-minute intervals up to 5 times.
3 of 4
Issue 1 June 2005
409
Communication Manager Maintenance-Object Repair Procedures
Table 120: Test #6 NPE Crosstalk Test (continued)
Error
Code
Test
Result
Description / Recommendation
Any
FAIL
This test can fail due to either on- or off-board problems. Off-board
problems of concern include EXP-PN, EXP-INTF, and RMC-ENV faults,
TDM-BUS faults, and faults associated with the Tone Detectors/Tone
Generators. Clear every off-board problem before replacing the board.
Keep in mind that a TDM-BUS problem is usually the result of a faulty
board connected to the backplane or bent pins on the backplane.
1. Resolve any EXP-PN, EXP-INTF, and RMC-ENV errors.
2. Resolve TDM-BUS errors.
3. Resolve TONE-BD or TONE-PT errors.
4. Test the board when the faults from steps 1, 2, and 3 are cleared.
Replace the board only if the test fails.
PASS
The port is correctly using its allocated time slots. User-reported troubles on
this port should be investigated by using other port tests, by examining
station wiring, by examining the station, and by ensuring that the terminal is
correctly translated as off-premises or on-premises.
Note:
0
NO
BOARD
Note:
This test always passes for circuit packs TN712 prior to
Vintage 14 and TN742 prior to Vintage 6.
The test could not relate the internal ID to the port (no board). This could
be due to incorrect translations, no board is inserted, an incorrect board is
inserted, or an insane board is inserted.
1. Verify that the board’s translations are correct. Enter list config,
and resolve any problems that are found.
2. If the board was found to be correctly inserted in step 1, enter
busyout board location
3. Enter reset board location
4. Enter release board location
5. Enter test board location long
This should re-establish the linkage between the internal ID and the port. If
not, dispatch to verify that a valid board is inserted.
4 of 4
410 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-LINE (8-Port Analog Line)
Battery Feed Test (or Port Diagnostic Test) (#35)
The battery feed chip provides power to the telephone equipment, signaling, rotary dial pulsing,
transmission, and balance. This test checks the signaling and switchhook capabilities of the
battery feed chip by terminating the port, applying battery, and trying to detect a current.
Table 121: Test #35 Battery Feed Test Results
Error
Code
Test
Result
Description / Recommendation
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1000
ABRT
System resources required to run this test are not available. The port may
be busy with a valid call. This result is also reported for the system’s
Music-on-Hold port when it is off-hook, which it usually is.
1. Enter display port location to determine the station’s extension.
Enter status station extension to determine the service state of
the port. Refer to Maintenance SAT Commands in the Maintenance
Commands Reference (03-300191), for a full description of every
possible state. If the port is active, it will be unavailable for certain
tests. Wait until the port is idle before retesting.
2. When the port is idle, retry the command at 1-minute intervals up to 5
times.
1004
ABRT
System resources required to run this test are not available. The port may
be busy with a valid call.
1. Use display port location to determine the station extension.
Use status station to determine the service state of the port. If the
service state indicates that the port is active, then the port is
unavailable for certain tests. Refer to Maintenance SAT Commands in
the Maintenance Commands Reference (03-300191), for a full
description of every possible state. Wait until the port is idle before
retesting.
2. Retry the command at 1-minute intervals up to 5 times.
3. If the test continues to abort and the port is idle, escalate the problem.
1 of 3
Issue 1 June 2005
411
Communication Manager Maintenance-Object Repair Procedures
Table 121: Test #35 Battery Feed Test Results (continued)
Error
Code
Test
Result
Description / Recommendation
1005
ABRT
The test was aborted due to a configuration problem. This error code
occurs under either of the following conditions:
1. This test may not be applicable, or it may be disruptive to terminal
equipment other than a voice terminal (for example, the modem pool
member or music on hold).
2. The circuit pack is one of the following:
- TN742 vintages 13,14, and 15
- TN769 vintages 3, 4, and 5
1018
ABRT
Test disabled via administration. The default for the Test field on the is y.
Determine why this field was set to n on this station. It may be due to the
ringing application Test E48, which can be customer or terminal disturbing.
1. To enable the test for a particular station, enter change station
extension and set the Test field to y.
1392
ABRT
This port is currently a TTI port and the test will not execute on it.
1. Verify that the port is a TTI port using either the display port
command (the display shows that the port is a TTI port) or list
config (the display shows a t for the port).
2. If either list config or display port indicate that the port is not
a TTI port, escalate the problem. If both commands indicate that the
port is a TTI port, the abort is correct for the test, and no action is
necessary.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
System resources required to run this test are not available. Either a
system allocation to get information about the port or to put the port into a
service state failed or the attempt to put the port in connection with a tone
source failed (this could be a Tone-Clock problem). The Tone-Clock and
Tone Detectors could be having a communication problem. For example,
the companding modes could be out of synchronization.
1. Retry the command at 1-minute intervals up to 5 times.
2 of 3
412 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-LINE (8-Port Analog Line)
Table 121: Test #35 Battery Feed Test Results (continued)
Error
Code
Test
Result
Description / Recommendation
FAIL
The port’s battery feed chip is unable to supply sufficient power to the
terminal equipment. This may occur when the test is performed at the
same time that the terminal equipment goes off-hook.
1. Use status station to determine when the port is available for
testing. When the port becomes available for testing, retry the
command at 1-minute intervals a minimum of five times.
2. If the test continues to fail, determine whether the customer is
experiencing problems on this line. Replace the circuit pack only if the
customer is experiencing problems.
PASS
The port’s battery feed chip is able to provide power to the station
equipment to detect on-/off-hook. However, the battery feed chip may still
be unable to provide power for touch-tones. If tones are heard when
buttons are pressed, then the battery feed chip is functioning correctly;
otherwise, replace the circuit pack because this port is defective.
User-reported troubles on this port should be investigated by using other
port tests, by examining station wiring, by examining the station, and by
ensuring that the terminal is correctly translated as off-premises or
on-premises.
Note:
0
NO
BOARD
Note:
This test always passes for circuit packs TN712 prior to
Vintage 14 and TN742 prior to Vintage 6.
The test could not relate the internal ID to the port (no board). This could
be due to incorrect translations, no board is inserted, an incorrect board is
inserted, or an insane board is inserted.
1. Verify that the board’s translations are correct. Enter list config,
and resolve any problems that are found.
2. If the board was found to be correctly inserted in step 1, enter
busyout board location
3. Enter reset board location
4. Enter release board location
5. Enter test board location long
This should re-establish the linkage between the internal ID and the port. If
not, dispatch to verify that a valid board is inserted.
3 of 3
Issue 1 June 2005
413
Communication Manager Maintenance-Object Repair Procedures
Station Status and Translation Audits and Updates Test (#36)
This test updates the analog port’s message lamp state (if it has one) and translations (such as
station type, dial type, network connection) with information kept in the software. The software
is updated with the switchhook state reported by the port processor. When the ringer is in the
off state, this test also turns off the station’s ringer to prevent constant ringing caused by
defective hardware.
Table 122: Test #36 Station Status and Translation Audits and Updates Test
Error
Code
1004
Test
Result
Description / Recommendation
ABRT
Could not allocate the necessary system resources to run this test.
ABRT
System resources required to run this test are not available. The port may
be busy with a valid call.
1. Use display port location to determine the station extension.
Use status station to determine the service state of the port. If
the service state indicates that the port is active, then the port is
unavailable for certain tests. Wait until the port is idle before retesting.
2. Retry the command at 1-minute intervals up to 5 times.
3. If the test continues to abort and the port is idle, escalate the problem.
1005
ABRT
The test was aborted due to a configuration problem. This error code
occurs under either of the following conditions:
1. This test may not be applicable, or it may be disruptive to terminal
equipment other than a voice terminal (for example, the modem pool
member or music on hold).
2. The circuit pack is one of the following:
- TN742 vintages 13,14, and 15
- TN769 vintages 3, 4, and 5
1 of 3
414 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-LINE (8-Port Analog Line)
Table 122: Test #36 Station Status and Translation Audits and Updates Test (continued)
Error
Code
Test
Result
Description / Recommendation
1006
ABRT
This port has been busied out by command or taken out-of-service by the
failure of the NPE Crosstalk test.
1. Look in the Error Log for Error Type 18 (port busied out) for this port. If
this error is present, then release the port with release station
extension and run the test again.
2. Look in the Error Log for Error Type 1025 (NPE Crosstalk test failed)
for this port. If this error is present, then investigate the errors
associated with the NPE Crosstalk test (#6) first.
3. Make sure that the terminal is connected and in service, and then
retest.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1
FAIL
This does not indicate a hardware problem. The switchhook audit failed,
and the other updates were not performed because of this failure. This
condition may occur when the audit is performed at the same time that the
terminal equipment goes off-hook. Use status station to determine
when the port is available for testing.
1. When the port becomes available for testing, retry the command at
1-minute intervals up to 5 times.
5
FAIL
This does not indicate a hardware problem but may indicate an internal
software error. The message waiting lamp update failed. The translation
and ringer updates were not performed because of this failure.
7
FAIL
The translation update failed. The ringer update was not performed
because of this failure. This does not indicate a hardware problem but may
be an internal software error.
8
FAIL
This does not indicate a hardware problem but may be an internal software
error. The ringer update failed.
1. Retry the command at 1-minute intervals up to 5 times.
2 of 3
Issue 1 June 2005
415
Communication Manager Maintenance-Object Repair Procedures
Table 122: Test #36 Station Status and Translation Audits and Updates Test (continued)
Error
Code
0
Test
Result
Description / Recommendation
PASS
The software and the port processor have the same status. User-reported
troubles on this port should be investigated by using other port tests, by
examining station wiring, by examining the station, and by ensuring that the
terminal is correctly translated as off-premises or on-premises.
Note: This test always passes for circuit packs TN712 prior to vintage 14
and TN742 prior to vintage 6.
NO
BOARD
The test could not relate the internal ID to the port (no board). This could
be due to incorrect translations, no board is inserted, an incorrect board is
inserted, or an insane board is inserted.
1. Verify that the board’s translations are correct. Enter list config,
and resolve any problems that are found.
2. If the board was found to be correctly inserted in step 1, enter
busyout board location
3. Enter reset board location
4. Enter release board location
5. Enter test board location long
This should re-establish the linkage between the internal ID and the port. If
not, dispatch to verify that a valid board is inserted.
3 of 3
Looparound and Conference Test (#47)
Each Analog port consists of:
●
An NPE (Network Processing Element) for port connectivity and gain, and conferencing
functionality
●
A codec that converts TDM Bus digital signals to analog
●
A battery feed chip that provides power to the telephone set for signaling, dial pulsing,
transmission, and balance.
This test is designed to check the on-board transmission capabilities of the NPE, the codec, and
the battery feed chip of the Analog port. A Tone Detector and a Tone Generator talk and listen
on the same pair of time slots as the Analog port. The Analog port is then instructed to go into
loop around mode (see Figure 22: Analog Looparound and Conference Test on page 417). The
test passes if the signal measured by the Tone Detector is within acceptable limits.
416 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-LINE (8-Port Analog Line)
The Conference Circuit test verifies that the NPE channel for the port being tested can correctly
perform the conferencing function. Test #47 also tests the operation of the port conference
circuits in the NPE for three and four parties. In addition, a test is run to measure noise. The
NPE is instructed to listen to several different tones and conference the tones together. The
resulting signal is then measured by a Tone Detector port. If the level of the tone is within a
certain range, the test passes.
The noise test is performed by filtering out the tone, and then measuring inherent port noise.
Note:
Note:
This looparound test is sensitive to the length of the loop, the equipment in the
loop, or the equipment terminating the loop, such as off-premises stations. If this
test is causing a false alarm, use change station for this station and change
the Tests field to n, to disable the test.
Figure 22: Analog Looparound and Conference Test
BFC
BFC: Battery Feed Chip
NPE: Network Processing Element
CODEC
Analog
Line
Port
Tone
Detector
Tone
Generator
NPE
TDM BUS
Table 123: Test #47 Loop Around and Conference Test
Error
Code
Test
Result
Description / Recommendation
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1 of 5
Issue 1 June 2005
417
Communication Manager Maintenance-Object Repair Procedures
Table 123: Test #47 Loop Around and Conference Test (continued)
Error
Code
Test
Result
Description / Recommendation
7
ABRT
The port was seized by a user for a valid call.
1. Enter display port location to determine the station’s
extension. Enter status station extension to determine the
service state of the port. If the port is active, it will be unavailable for
certain tests. Wait until the port is idle before retesting.
2. If the port is idle, retry the command at 1-minute intervals up to 5
times.
1000
ABRT
System resources required to run this test were not available. The port
may be busy with a valid call. (This could be a Music-on-Hold port.)
1. Enter display port location to determine the station’s
extension. Enter status station extension to determine the
service state of the port. If the port is active, it will be unavailable for
certain tests. Wait until the port is idle before retesting.
2. If the port is idle, retry the command at 1-minute intervals up to 5
times.
1002
ABRT
The system could not allocate time slots for the test. The system may be
under heavy traffic conditions or it may have time slots out-of-service due
to TDM-BUS errors.
1. If the system has no TDM-BUS errors and is not handling heavy traffic,
repeat test at 1-minute intervals up to 5 times.
1003
ABRT
The system could not allocate a tone receiver for the test. The system
may be oversized for the number of Tone Detectors present or some Tone
Detectors may be out-of-service.
1. Resolve TTR-LEV errors.
2. Resolve TONE-PT errors.
3. If neither condition exists, retry the test at 1-minute intervals up to 5
times.
1004
ABRT
The port has been seized for a valid call during the conference or noise
test.
1. If the circuit pack is a TN742 of Vintage 10 or less, this test is not valid.
Otherwise, proceed with step 2.
2. When the port is available for testing, retry the command at 1-minute
intervals up to 5 times.
2 of 5
418 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-LINE (8-Port Analog Line)
Table 123: Test #47 Loop Around and Conference Test (continued)
Error
Code
Test
Result
Description / Recommendation
1005
ABRT
The test was aborted due to a configuration problem. This error code
occurs under either of the following conditions:
●
This test may not be applicable, or it may be disruptive to terminal
equipment other than a voice terminal (for example, a modem pool
member or music on hold).
●
The circuit pack is one of the following:
- TN742 vintage 13, 14, or 15
- TN769 vintage 3, 4, or 5
1018
ABRT
Test disabled by administration. The default for the Test field is y.
Determine why the field is n on this station. It may be due to the ringing
application test 48, which can be customer or terminal disturbing.
1. To enable the test for a particular station, enter change station
extension and set the Test field on the Station screen to y.
1392
ABRT
This port is currently a TTI port and the test will not execute on it.
1. Verify that the port is a TTI port using either display port to show
that the port is a TTI port, or list config, where the display shows
a t for the port.
2. If either list config or display port indicate that the port is not
a TTI port, escalate the problem. If both commands indicate that the
port is a TTI port, the abort is correct for the test, and no action is
necessary.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
System resources required to run this test are not available. Either a
system allocation to get information about the port or to put the port into a
service state failed or the attempt to put the port in connection with a tone
source failed (this could be a Tone-Clock problem). The Tone-Clock and
Tone Detectors could be having a communication problem. For example,
the companding modes could be out of synchronization.
1. Retry the command at 1-minute intervals up to 5 times.
3 of 5
Issue 1 June 2005
419
Communication Manager Maintenance-Object Repair Procedures
Table 123: Test #47 Loop Around and Conference Test (continued)
Error
Code
Test
Result
Description / Recommendation
7
FAIL
The conference test or the noise test failed. This could cause noisy or
unreliable connections, or users calling this port may hear an echo. The
problem can also be off-board, as described below.
13
The reflective loop around with gain set to low and the 600-ohm balance
failed. This will cause noisy or unreliable connections.
14
The reflective loop around test (with the gain set to high, using RC balance)
failed. This could cause noisy or unreliable connections. The problem can
also be off-board, as described below.
15
The nonreflective loop-around test failed. This could cause noisy or
unreliable connections, or users calling this port may hear an echo. The
problem can also be off-board as described below.
1. Disconnect the terminal equipment from the circuit pack at the
cross-connect and run the test again.
2. If the test fails again, replace the circuit pack and reconnect the
terminal equipment. If the test passes the second time, then the test
results were affected by the terminal equipment connected to the port.
In this case, ignore the results of this test if every other test passes or
aborts and the station is operating properly. Failure of test 47 does not
cause an alarm. If there are failures of other tests, then investigate
those errors. User reported troubles with this port should be
investigated by using other port tests, by examining station wiring, and
by examining the station to ensure that it is correctly translated as
off-premises or on-premises.
If the Looparound and Conference circuit test fails for every port on a circuit
pack, a -5 Volt power problem is indicated. If a TN736 or TN752 power unit
circuit pack is present, either the 631DB AC power unit or the 676B DC
power unit may be defective. (The 631DB power unit is used in a medium
cabinet powered by an AC source. The 645B power unit is used in a
medium cabinet powered by a DC power source.) The system may contain
a TN736 or TN752 power unit circuit pack or a 631DB AC power unit, but
not both types of power units. To investigate problems with the power unit,
see the RMC-ENV MO (S8700 IP), or the CARR-POW MO (S8700 MC). If a
red LED is lit on TN736 or TN752 power unit circuit pack, replace the pack.
If the test fails on more than 1 port, check for errors on the TONE-BD or the
TONE-PT. If errors, take appropriate actions. When the tone errors are
cleared, rerun the test.
4 of 5
420 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-LINE (8-Port Analog Line)
Table 123: Test #47 Loop Around and Conference Test (continued)
Error
Code
Test
Result
Description / Recommendation
PASS
The port is able to provide an analog transmission path to the station
equipment. User-reported troubles on this port should be investigated by
using other port tests, by examining station wiring, by examining the station,
and by ensuring that the terminal is correctly translated as off-premises or
on-premises.
Note:
0
NO
BOARD
Note:
This test always passes for circuit packs TN712 prior to
vintage 14 and TN742 prior to vintage 6.
The test could not relate the internal ID to the port (no board). This could
be due to incorrect translations, no board is inserted, an incorrect board is
inserted, or an insane board is inserted.
1. Verify that the board’s translations are correct. Enter list config,
and resolve any problems that are found.
2. If the board was found to be correctly inserted in step 1, enter
busyout board location
3. Enter reset board location
4. Enter release board location
5. Enter test board location long
This should re-establish the linkage between the internal ID and the
port. If not, dispatch to verify that a valid board is inserted.
5 of 5
Station Present Test (or Ringing Application Test) (#48)
This test provides a burst of ringing current to the terminal equipment and detects that current
flows. This test is to ascertain whether or not terminal equipment is connected to the port.
This test may cause some terminal equipment to ring briefly during daily maintenance. If this
ringing is disturbing the customer or the terminal equipment, it should be disabled using the
Tests field of the station administration screen. However, on some releases of the software, this
action disables Tests #6, 47, and 35, as well as Test #48.
Issue 1 June 2005
421
Communication Manager Maintenance-Object Repair Procedures
Table 124: Test #48 Station Present Test
Error
Code
Test
Result
Description / Recommendation
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1000
ABRT
System resources required to run this test were not available. The port
may be busy with a valid call.
1. Use display port location to determine the station’s extension.
Use status station extension to determine the service state of
the port. If the port is active, it will be unavailable for certain tests.
Wait until the port is idle before retesting.
2. If the port is idle, retry the command at 1-minute intervals up to 5
times.
3. Check for phone left off-hook or for wiring problems.
1004
ABRT
System resources required to run this test are not available. The port may
be busy with a valid call.
1. Use display port location to determine the station extension.
Use status station to determine the service state of the port. If
the service state indicates that the port is active, then the port is
unavailable for certain tests. Wait until the port is idle before retesting.
2. Retry the command at 1-minute intervals up to 5 times.
3. If the test continues to abort and the port is idle, escalate the problem.
1005
ABRT
The test was aborted due to a configuration problem. This error code
occurs under either of the following conditions:
1. This test may not be applicable, or it may be disruptive to terminal
equipment other than a voice terminal (for example, the modem pool
member or music on hold).
2. The circuit pack is:
●
TN742 vintages 13, 14, and 15
●
TN769 vintages 3, 4, and 5
1 of 3
422 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-LINE (8-Port Analog Line)
Table 124: Test #48 Station Present Test (continued)
Error
Code
Test
Result
Description / Recommendation
1008
ABRT
Could not allocate a ringing circuit for one of the following reasons:
●
Every ringing circuit is active.
●
The ringing generator is defective.
●
It is incorrectly wired.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort, look for RING-GEN errors in the Error
Log. If an ABORT 1008 occurs for Test #48 on other circuit packs as
well, then the ringing generator may be defective or incorrectly wired.
If it does not occur on other ports, then that circuit pack is currently
using all four ringing phases.
1018
ABRT
The test was disabled by administration. The default for the Test field is y;
thus, you may want to determine why this field has been set to “n” on this
station (this may be due to the ringing application Test #48, which can be
customer or terminal disturbing).
1. To enable the test for a particular station, enter change station
extension and set the Test field to y.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
System resources required to run this test are not available. Either a
system allocation to get information about the port or to put the port into a
service state failed or the attempt to put the port in connection with a tone
source failed (this could be a Tone-Clock problem). The Tone-Clock and
Tone Detectors could be having a communication problem. For example,
the companding modes could be out of synchronization.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort, escalate the problem.
2 of 3
Issue 1 June 2005
423
Communication Manager Maintenance-Object Repair Procedures
Table 124: Test #48 Station Present Test (continued)
Error
Code
Test
Result
Description / Recommendation
FAIL
The terminal equipment is not connected to the circuit pack or the ringing
generator may have failed.
1. Remotely test the equipment.
2. If the test fails again, look for RING-GEN errors in the error log. If
present, see RING-GEN (Analog Ring Generator) on page 1942
(analog ring generator) maintenance.
3. Check all of the wiring between the station equipment and the switch.
Then, run the test again.
4. If the test still fails, the set may be defective. Check the set, and
replace it, if necessary.
5. Some terminal equipment (such as a modem) could fail even when it is
connected properly. If this is the case, disable the test using change
station extension (enter n into the Test field). Note that this
action also disables Tests 6, 7, 161, and 35 on this port.
0
PASS
The station is connected properly to the switch. This test may also pass if
no terminal equipment is connected and the terminal is located very far from
the switch. Investigate user-reported troubles on this port by using other
port tests or by examining the station and its wiring.
NO
BOARD
The test could not relate the internal ID to the port (no board). This could
be due to incorrect translations, no board is inserted, an incorrect board is
inserted, or an insane board is inserted.
1. Verify that the board’s translations are correct. Enter list config
and resolve any problems.
2. If the board was found to be correctly inserted in step 1, enter
busyout board location
3. Enter reset board location
4. Enter release board location
5. Enter test board location long
This should re-establish the linkage between the internal ID and the port. If
not, dispatch to verify that a valid board is inserted.
3 of 3
424 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANL-NE-L (8-Port Analog Line)
ANL-NE-L (8-Port Analog Line)
See ANL-LINE (8-Port Analog Line) on page 404.
S8700 | 8710 / S8500
This maintenance object covers the neon message waiting lamp power on the 8-port analog
line board.
Issue 1 June 2005
425
Communication Manager Maintenance-Object Repair Procedures
AN-LN-PT (Analog Line Port)
S8700 | 8710 / S8500 / S8300 / G700
MO Name in Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
AN-LN-PT
MIN
test port location l
Analog Line port
AN-LN-PT
WRN
test port location sh
Analog Line port
The TN793B/TN2793B Analog Line (w/ Caller ID) and the TN797 Analog Trunk and Line circuit
packs both support AN-LN-PT.
The TN793B/TN2793B Analog Line circuit pack (w/ Caller ID) provides 24 ports for voice
terminals and supports both on-premises and off-premises analog voice terminals.
Note:
Note:
For DEFINITY G3i, si, and csi systems the TN793B/TN2793B analog line circuit
pack supports analog data modules. When assigned, analog data modules
provide access to the NetPkt (TN794 circuit pack) data ports. To activate an
analog data module you must assign the port location on the data screen and
connect a modem to the port. The analog data module can be used for
connection to a CDR output, or other adjuncts as needed. These ports are tested
like any other analog port on the circuit pack.
For S8500, S8700 products, CDR data is moved via LAN to a CDR adjunct.
The TN797 Analog Trunk and Line circuit pack provides 8 ports, each of which may be
administered in any of several ways, as described in MO TR-LN-BD.
S8300 / G700: The MM711 Analog Trunk and Line Media Module provides 8 ports, each of which
may be administered in any of several ways, as described in MO MG-ANA.
Note:
Note:
Although the AN-LN-PT MO is provided for the G700 Media Gateways,
AN-LN-PT only partially supports the MM711 Analog Media Module.
Ringing caused by maintenance testing
Test #48 may cause some terminal equipment to ring briefly during daily maintenance. If this
ringing disturbs the customer or the terminal equipment, disable it in the 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.
G700: Tests #6, 7, and 161 abort on the G700 with Error Code 1412.
426 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
AN-LN-PT (Analog Line Port)
Error log entries and test to clear values
Table 125: Analog line port error log entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/
Off
Board
Test to Clear Value
0 (a)
0
Any
Any
Any
test port location sh r 1
1 (b)
40960
40975
40977
none
15 (c)
Any
Audits and Updates test (#36)
18
0
busy station extension
WRN
ON
release station extension
None
WRN
ON
test port location sh
130 (d)
257 (e)
40973
None
513 (f)
Station Present test (#48)
WRN
OFF
test port location sh r 2
769
Battery Feed test (#35)
MIN
WRN1
ON
test port location sh r 2
1025
Looparound test (#161)
MIN
WRN2
ON
test port location l r 2
1281
Conference test (#7)
MIN
WRN2
ON
test port location l r 2
1537
NPE Crosstalk test (#6)
MIN
WRN2
ON
test port location l r 2
1. Minor alarms on this MO may be downgraded to Warning alarms based on the values used in set
options.
Notes:
a. Error 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
procedures.
b. 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.
Issue 1 June 2005
427
Communication Manager Maintenance-Object Repair Procedures
●
Aux Data 40975 indicates that the terminal equipment was on-hook when ring-tip was
detected during ringing. This usually indicates a failure in the terminal equipment or the
type of terminal has a low ringer impedance.
1. Call the terminal equipment and verify that the terminal rings.
2. If the terminal does not ring, replace it.
3. Otherwise, run test port location, and follow the procedure for Test #48.
●
40977 indicates that no terminal equipment was connected when ringing was attempted.
Run test port location sh, and follow the procedure for the results of Test #48.
c. Error Type 15: this is a software audit error that does not indicate any hardware
malfunction. Run the short test sequence, and investigate any associated errors.
d. Error Type 130: this error type indicates that 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.
e. Error Type 257: this is an in-line error and can only be resolved over time. This error
indicates that ringing voltage is absent.
S8700 | 8710 / S8500
●
If only 1 analog circuit pack in the system has this problem, replace the circuit pack.
●
If only analog circuit packs on a particular carrier have this error, the ringing generator
may not be connected to this carrier.
●
If analog circuit packs on many carriers have this error, it is probably a problem with the
ringing generator.
S8300 / G700
●
If not resolved over time, replace the media module.
f. Error Type 513:Test #48 can cause some terminal equipment to ring briefly during daily
maintenance.
1. If this disturbs the customer or the terminal equipment, disable it by setting the Tests
field on the change station extension form to n. On some software releases, this
also disables Tests #6, 7, 161, and 35.
S8300 / G700: In the G700, Tests #6, 7, and 161 abort with Error Code 1412.
428 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
AN-LN-PT (Analog Line Port)
System technician-demanded tests: descriptions and error codes
Investigate tests in the order presented. By clearing error codes associated with the Battery
Feed test (#35), you may clear errors generated from other tests in the sequence.
Order of Investigation
Short
Test
Sequence
Long Test
Sequence
D/
ND1
Battery Feed test (#35)
X
X
ND
Station Present test (#48)
X
X
ND
Analog Looparound test (#161)
S8300 / G700: This test aborts with Error Code 1412.
X
ND
Conference test (#7)
S8300 / G700: This test aborts with Error Code 1412.
X
ND
NPE Crosstalk test (#6)
S8300 / G700: This test aborts with Error Code 1412.
X
ND
X
ND
Station Status and Translation Audit and Update test
(#36)
X
1. D = Destructive; ND = Nondestructive
NPE Crosstalk Test (#6)
S8300 / G700: This test aborts with Error Code 1412.
This test verifies that the port’s NPE channel talks on the selected time slot and never crosses
over to time slots reserved for other connections. If the NPE is not working correctly, one-way
and noisy connections may be observed. This test is usually part of the long test sequence and
executes in about 20 to 30 seconds.
Table 126: Test #6 NPE Crosstalk Test
Error
Code
Test
Result
Description / Recommendation
ABRT
Necessary system resources could not be allocated to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort, escalate the problem.
1 of 4
Issue 1 June 2005
429
Communication Manager Maintenance-Object Repair Procedures
Table 126: Test #6 NPE Crosstalk Test (continued)
Error
Code
Test
Result
Description / Recommendation
1000
ABRT
System resources are unavailable. The port may be busy with a valid call.
This result is also reported for the system’s Music-On-Hold port when it is
off-hook, which it usually is.
1. Enter display port location to determine the station’s extension.
2. Enter status station extension to determine the service state of
the port.
3. If the port is active, wait until it is idle. Retry the command at 1-minute
intervals up to 5 times.
4. If the test continues to abort, escalate the problem.
1001
ABRT
System resources required to run test are not available. This could be due
to a failure to seize the port.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort, escalate the problem.
1002
ABRT
The system could not allocate time slots for the test. The system may be
under heavy traffic conditions or have time slots out-of-service due to
TDM-BUS errors.
1. Refer to TDM-BUS to diagnose any active TDM-BUS errors.
2. If the system has no TDM-BUS errors and is not handling heavy traffic,
retry the command at 1-minute intervals up to 5 times.
3. If the test continues to abort, escalate the problem.
1003
ABRT
The system could not allocate a tone receiver for the test. The system may
be oversized for the number of Tone Detectors present or some Tone
Detectors may be out-of-service.
1. Resolve any TTR-LEV errors in the Error Log.
2. Resolve any TONE-PT errors in the Error Log.
3. If neither condition exists, retry the command at 1-minute intervals up
to 5 times.
4. If the test continues to abort, escalate the problem.
2 of 4
430 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
AN-LN-PT (Analog Line Port)
Table 126: Test #6 NPE Crosstalk Test (continued)
Error
Code
Test
Result
Description / Recommendation
1004
ABRT
A valid call seized the port during the test and aborted the test.
1. Use display port location to determine the station extension.
2. Use status station extension to determine the service state of
the port.
3. If the port is active, wait until it is idle before testing. Retry the
command at 1-minute intervals up to 5 times.
4. If the test continues to abort, escalate the problem.
1005
ABRT
This test was aborted due to a configuration problem. The test is not
applicable for this type of analog port. This error can be ignored.
1018
ABRT
Administration has disabled the test. The default for the Test field on the
station screen is y. Determine why this field has been set to n on this
station (this may be due to the ringing application Test #48, which can be
disturbing to customer or terminal equipment).
1. To enable the test for a particular station being tested, enter change
station extension.
2. Enter y in the Test field.
S8300
G700
ABRT
This test does not execute on a G700 Media Gateway.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1412
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
System resources required to run test are not available. This could be due
to a failure to seize the port.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort, escalate the problem.
3 of 4
Issue 1 June 2005
431
Communication Manager Maintenance-Object Repair Procedures
Table 126: Test #6 NPE Crosstalk Test (continued)
Error
Code
Test
Result
Description / Recommendation
Any
FAIL
This test can fail due to either on- or off-board problems. Off-board
problems include TDM-BUS faults, EXP-PN, EXP-INTF, and RMC-ENV
faults, and faults associated with the Tone Detectors/Tone Generators.
Clear every off-board problem before replacing the board.
1. A TDM-BUS problem is usually the result of a faulty board connection
to the backplane, or bent pins on the backplane. Resolve any
TDM-BUS errors in the error log.
2. Resolve any any EXP-PN, EXP-INTF, and RMC-ENV errors in the
error log.
3. Resolve any TONE-BD and/or TONE-PT errors in the error log.
4. Test the board when the faults from steps 1, 2, and 3 are cleared.
Replace the board only if the test fails.
0
PASS
The port is correctly using its allocated time slots. Investigate user-reported
troubles on this port by running other port tests, by examining station wiring,
or by inspecting the station.
NO
BOARD
The test could not relate the internal ID to the port (no board). This result
could be due to incorrect translations, no board is inserted, an incorrect
board is inserted, or an insane board is inserted.
1. Check to make sure that the board translations are correct. Enter
list configuration and resolve any problems.
2. If the board is correctly inserted, enter busy board location
3. Enter reset board location
4. Enter release board location
5. Enter test board location long
This should re-establish the link between the internal ID and the port. If not,
verify that a valid board is inserted.
4 of 4
Conference Circuit Test (#7)
S8300 / G700: This test aborts with Error Code 1412.
This test verifies that the NPE channel for the port being tested correctly performs the
conferencing function.
432 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
AN-LN-PT (Analog Line Port)
Table 127: Test #7 Conference Circuit Test
Error
Code
Test
Result
Description / Recommendation
ABRT
Necessary system resources could not be allocated to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort, escalate the problem.
1000
ABRT
System resources are unavailable. The port may be busy with a valid call.
This result is also reported for the system’s Music-On-Hold port when it is
off-hook, which it usually is.
1. Enter display port location to determine the station’s extension.
2. Enter status station extension to determine the service state of
the port.
3. If the port is active, wait until it is idle. Retry the command at 1-minute
intervals up to 5 times.
4. If the test continues to abort, escalate the problem.
1004
ABRT
A valid call seized the port during the test and aborted the test.
1. Use display port location to determine the station extension.
2. Use status station extension to determine the service state of
the port.
3. If the port is active, wait until it is idle before testing. Retry the
command at 1-minute intervals up to 5 times.
4. If the test continues to abort, escalate the problem.
1005
ABRT
This test was aborted due to a configuration problem. The test is not
applicable for this type of analog port. This error can be ignored.
1018
ABRT
Administration has disabled the test. The default for the Test field on the
station screen is y. Determine why this field has been set to n on this
station (this may be due to the ringing application Test #48, which can be
disturbing to customer or terminal equipment).
1. To enable the test for a particular station being tested, enter change
station extension.
2. Enter y in the Test field.
S8300
G700
ABRT
This test does not execute on a G700 Media Gateway.
1412
1 of 2
Issue 1 June 2005
433
Communication Manager Maintenance-Object Repair Procedures
Table 127: Test #7 Conference Circuit Test (continued)
Error
Code
Test
Result
Description / Recommendation
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
System resources required to run this test are not available.
1. Resolve any TONE-PT errors in the error log.
2. If there are no TONE-PT errors, retry the command at 1-minute
intervals up to 5 times.
3. If the test continues to abort, escalate the problem.
Any
FAIL
The NPE of the tested port did not conference the tones correctly. This
causes noisy and unreliable connections.
1. 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 board.
0
PASS
The port can correctly conference multiple connections. Investigate
user-reported troubles on this port by running other port tests; by examining
station, trunk, or external wiring; or by inspecting the station.
NO
BOARD
The test could not relate the internal ID to the port (no board). This result
could be due to incorrect translations, no board is inserted, an incorrect
board is inserted, or an insane board is inserted.
1. Check to make sure that the board translations are correct. Enter list
configuration, and resolve any problems.
2. If the board is correctly inserted, enter busy board location
3. Enter reset board location
4. Enter release board location
5. Enter test board location long
This should re-establish the link between the internal ID and the port. If not,
verify that a valid board is inserted.
2 of 2
434 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
AN-LN-PT (Analog Line Port)
Battery Feed Test (or Port Diagnostic Test) (#35)
The battery feed chip provides power to the telephone equipment, signaling, rotary dial pulsing,
transmission, and balance. This test checks the signaling and switchhook capabilities of the
battery feed chip by terminating the port, applying battery power, and detecting the resulting
current.
Table 128: Test #35 Battery Feed Test
Error
Code
Test
Result
Description / Recommendation
ABRT
Necessary system resources could not be allocated to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort, escalate the problem.
1000
ABRT
System resources are unavailable. The port may be busy with a valid call.
This result is also reported for the system’s Music-On-Hold port when it is
off-hook, which it usually is.
1. Enter display port location to determine the station’s
extension.
2. Enter status station extension to determine the service state of
the port.
3. If the port is active, wait until it is idle. Retry the command at 1-minute
intervals up to 5 times.
4. If the test continues to abort, escalate the problem.
1004
ABRT
A valid call seized the port during the test and aborted the test.
1. Use display port location to determine the station extension.
2. Use status station extension to determine the service state of
the port.
3. If the port is active, wait until it is idle before testing. Retry the
command at 1-minute intervals up to 5 times.
4. If the test continues to abort, escalate the problem.
1005
ABRT
This test was aborted due to a configuration problem. The test is not
applicable for this type of analog port. This error can be ignored.
1 of 3
Issue 1 June 2005
435
Communication Manager Maintenance-Object Repair Procedures
Table 128: Test #35 Battery Feed Test (continued)
Error
Code
Test
Result
Description / Recommendation
1018
ABRT
Administration has disabled the test. The default for the Test field on the
station form is y. Determine why this field has been set to n on this station
(this may be due to the ringing application Test #48, which can be
disturbing to customer or terminal equipment).
1. To enable the test for a particular station being tested, enter change
station extension.
2. Enter y in the Test field.
1392
ABRT
This port is currently a TTI port and the test does not execute on it.
1. Verify that the port is a TTI port:
●
Enter the display port location command (the display shows
that the port is a TTI port).
●
Enter list configuration (the display shows a t for the port).
2. If both commands indicate that the port is a TTI port, the abort is
correct for the test, and no action is necessary.
3. If either command indicates that the port is not a TTI port, escalate the
problem.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
System resources required to run this test are not available.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort, escalate the problem.
FAIL
The port's battery feed chip is unable to supply sufficient power to the
terminal equipment. This test result might be marginal, and the terminal
equipment may be operating satisfactorily.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to fail, determine whether the customer is
experiencing problems on this line. Replace the circuit pack or media
module only if the customer is experiencing problems.
2 of 3
436 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
AN-LN-PT (Analog Line Port)
Table 128: Test #35 Battery Feed Test (continued)
Error
Code
Test
Result
Description / Recommendation
PASS
The port’s battery feed chip is able to provide sufficient power to the station
equipment to detect on-/off-hook, but may not be able to supply power for
touch-tones.
1. If touch-tones are inoperative on this station, replace the circuit pack or
media module, because this port is inoperative.
2. Investigate user-reported troubles on this port by running other port
tests, by examining station wiring, or by inspecting the station.
0
NO
BOARD
The test could not relate the internal ID to the port (no board). This result
could be due to incorrect translations, no board is inserted, an incorrect
board is inserted, or an insane board is inserted.
1. Check to make sure that the board translations are correct. Enter
list configuration, and resolve any problems.
2. If the board is correctly inserted, enter busy board location
3. Enter reset board location
4. Enter release board location
5. Enter test board location long
This should re-establish the link between the internal ID and the port. If not,
verify that a valid board is inserted.
3 of 3
Station Status and Translation Audit and Update Test (#36)
This test updates the analog port’s message lamp state (if it has one) and translations with
information in the software.
Table 129: Test #36 Station Status and Translation Audit and Update
Error
Code
Test
Result
Description / Recommendation
ABRT
Necessary system resources could not be allocated to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort, escalate the problem.
1 of 3
Issue 1 June 2005
437
Communication Manager Maintenance-Object Repair Procedures
Table 129: Test #36 Station Status and Translation Audit and Update (continued)
Error
Code
Test
Result
Description / Recommendation
1004
ABRT
A valid call seized the port during the test and aborted the test.
1. Use display port location to determine the station extension.
2. Use status station extension to determine the service state of
the port.
3. If the port is active, wait until it is idle before testing. Retry the
command at 1-minute intervals up to 5 times.
4. If the test continues to abort, escalate the problem.
1005
ABRT
This test was aborted due to a configuration problem. The test is not
applicable for this type of analog port. This error can be ignored.
1006
ABRT
The port is out-of-service. The busy station extension has been
given to this port. If the port is on a circuit pack, it may have been taken
out-of-service by the failure of the NPE Crosstalk test.
1. Look for error type 18 (port busied out) for this port. If this error is
present, release the port with release station extension, and
run the test again.
2. If the port is on a circuit pack, check for error type 1537 (NPE
Crosstalk test failed) for this port. If this error is present, investigate
the errors associated with the NPE Crosstalk test (#6).
3. Make sure that the terminal is connected and in service, and then
retest.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
System resources required to run this test are not available.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort, escalate the problem.
2 of 3
438 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
AN-LN-PT (Analog Line Port)
Table 129: Test #36 Station Status and Translation Audit and Update (continued)
Error
Code
Test
Result
Description / Recommendation
1
FAIL
The switchhook audit failed. This result does not indicate a hardware
problem. The other updates were not performed because of this failure.
This may occur if the audit is performed at the same time the terminal
equipment goes off-hook.
1. Use status station extension to determine when the port is
available.
2. Retry the command at 1-minute intervals up to 5 times.
3. If the test continues to fail, escalate the problem.
5
FAIL
The message waiting lamp update failed. This may be an internal software
error. The translation and ringer updates were not performed because of
this failure.
7
FAIL
The translation update failed. There may be an internal software error. The
ringer update was not performed because of this failure.
8
FAIL
The ringer update failed. There may be an internal software error.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to fail, escalate the problem.
0
PASS
The software and the port processor have the same status. Investigate
user-reported troubles on this port by running other port tests, by examining
station wiring, or by inspecting the station.
NO
BOARD
The test could not relate the internal ID to the port (no board). This result
could be due to incorrect translations, no board is inserted, an incorrect
board is inserted, or an insane board is inserted.
1. Check to make sure that the board translations are correct. Enter
list configuration, and resolve any problems.
2. If the board is correctly inserted, enter busy board location
3. Enter reset board location
4. Enter release board location
5. Enter test board location long
This should re-establish the link between the internal ID and the port. If not,
verify that a valid board is inserted.
3 of 3
Issue 1 June 2005
439
Communication Manager Maintenance-Object Repair Procedures
Station Present Test (or Ringing Application Test) (#48)
This test applies momentary ringing voltage to the terminal equipment and monitors resulting
current flow to determine whether terminal equipment is connected to the port. This test may
cause some terminal equipment to ring briefly during daily maintenance. If this ringing disturbs
the customer or the terminal equipment, you can disable it via the Tests field on the change
station extension screen. However, on some software releases, Tests #6, 7, 161, and 35
also are disabled.
S8300 / G700: In the G700, Tests #6, 7, and 161 abort with Error Code 1412.
Table 130: Test #48 Station Present Test
Error
Code
Test
Result
Description / Recommendation
ABRT
Necessary system resources could not be allocated to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort, escalate the problem.
1000
ABRT
System resources are unavailable. The port may be busy with a valid call.
This result is also reported for the system’s Music-On-Hold port when it is
off-hook, which it usually is.
1. Enter display port location to determine the station’s
extension.
2. Enter status station extension to determine the service state of
the port.
3. If the port is active, wait until it is idle. Retry the command at 1-minute
intervals up to 5 times.
4. If the test continues to abort, escalate the problem.
1004
ABRT
A valid call seized the port during the test and aborted the test.
1. Use display port location to determine the station extension.
2. Use status station extension to determine the service state of
the port.
3. If the port is active, wait until it is idle before testing. Retry the
command at 1-minute intervals up to 5 times.
4. If the test continues to abort, escalate the problem.
1005
ABRT
This test was aborted due to a configuration problem. The test is not
applicable for this type of analog port. This error can be ignored.
1 of 3
440 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
AN-LN-PT (Analog Line Port)
Table 130: Test #48 Station Present Test (continued)
Error
Code
Test
Result
Description / Recommendation
1008
ABRT
A ringing circuit could not be allocated. Either every ringing circuit is
active, the ringing generator is defective, or it is incorrectly wired.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort, look for RING-GEN errors in the Error
Log.
3. If ABORT 1008 occurs for this test on other circuit packs as well, the
ringing generator may be defective or is incorrectly wired (see
RING-GEN (Analog Ring Generator) on page 1942.
4. If an ABORT 1008 does not occur on other ports, then all four ring
phases are active.
1018
ABRT
Administration has disabled the test. The default for the Test field on the
station screen is y. Determine why this field has been set to n on this
station (this may be due to the ringing application Test 48, which can be
disturbing to customer or terminal equipment).
1. To enable the test for a particular station being tested, enter change
station extension.
2. Enter y in the Test field.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
System resources required to run this test are not available.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort, escalate the problem.
2 of 3
Issue 1 June 2005
441
Communication Manager Maintenance-Object Repair Procedures
Table 130: Test #48 Station Present Test (continued)
Error
Code
Test
Result
Description / Recommendation
FAIL
The terminal equipment is not connected to the circuit pack. Some
terminal equipment, such as modems, may fail even when connected
properly.
1. Remotely test the terminal equipment.
2. If the test fails again, resolve any RING-GEN errors in the error log, if
present.
3. Check all of the wiring between the station equipment and the switch.
Then, run the test again.
4. If the test still fails, the terminal equipment may be defective. Check
and replace it, if necessary.
5. Some terminal equipment might fail even when it is connected
properly. If this is the case, disable the test using change station
extension (enter n into the Test field). Note that this action also
disables Tests 6, 7, 35, and 161 on this port.
PASS
The station is connected properly to the switch. Investigate user-reported
troubles on this port by running other port tests, by examining station wiring,
or by inspecting the station.
Note:
0
NO
BOARD
Note:
This test may also pass if no terminal equipment is
connected and the terminal is located very far from the
switch.
The test could not relate the internal ID to the port (no board). This result
could be due to incorrect translations, no board is inserted, an incorrect
board is inserted, or an insane board is inserted.
1. Check to make sure that the board translations are correct. Enter
list configuration, and resolve any problems.
2. If the board is correctly inserted, enter busy board location
3. Enter reset board location
4. Enter release board location
5. Enter test board location long
This should re-establish the link between the internal ID and the port. If not,
verify that a valid board is inserted.
3 of 3
442 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
AN-LN-PT (Analog Line Port)
Analog Looparound Test (#161)
S8300 / G700: This test aborts with Error Code 1412.
This test checks the on-board transmission capabilities of the NPE, the codec, and the battery
feed chip of the analog port. The test passes if the signal measured by the Tone Detector is
within acceptable limits.
Table 131: Test #161 Analog Looparound Test
Error
Code
Test
Result
Description / Recommendation
ABRT
Necessary system resources could not be allocated to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort, escalate the problem.
1000
ABRT
System resources are unavailable. The port may be busy with a valid call.
This result is also reported for the system’s Music-On-Hold port when it is
off-hook, which it usually is.
1. Enter display port location to determine the station’s extension.
2. Enter status station extension to determine the service state of
the port.
3. If the port is active, wait until it is idle. Retry the command at 1-minute
intervals up to 5 times.
4. If the test continues to abort, escalate the problem.
1002
ABRT
The system could not allocate time slots for the test. The system may be
under heavy traffic conditions or have time slots out-of-service due to
TDM-BUS errors.
1. Refer to “TDM-BUS” to diagnose any active TDM-BUS errors.
2. If the system has no TDM-BUS errors and is not handling heavy traffic,
retry the command at 1-minute intervals up to 5 times.
3. If the test continues to abort, escalate the problem.
1 of 4
Issue 1 June 2005
443
Communication Manager Maintenance-Object Repair Procedures
Table 131: Test #161 Analog Looparound Test (continued)
Error
Code
Test
Result
Description / Recommendation
1003
ABRT
The system could not allocate a tone receiver for the test. The system may
be oversized for the number of Tone Detectors present or some Tone
Detectors may be out-of-service.
1. Resolve any TTR-LEV errors in the Error Log.
2. Resolve any TONE-PT errors in the Error Log.
3. If neither condition exists, retry the command at 1-minute intervals up to
5 times.
4. If the test continues to abort, escalate the problem.
1004
ABRT
A valid call seized the port during the test and aborted the test.
1. Use display port location to determine the station extension.
2. Use status station extension to determine the service state of
the port.
3. If the port is active, wait until it is idle before testing. Retry the
command at 1-minute intervals up to 5 times.
4. If the test continues to abort, escalate the problem.
1005
ABRT
This test was aborted due to a configuration problem. The test is not
applicable for this type of analog port. This error can be ignored.
1018
ABRT
Administration has disabled the test. The default for the Test field on the
station screen is y. Determine why this field has been set to n on this
station (this may be due to the ringing application Test 48, which can be
disturbing to customer or terminal equipment).
1. To enable the test for a particular station being tested, enter change
station extension.
2. Enter y in the Test field.
S8300
G700
ABRT
This test does not execute on a G700 Media Gateway.
1412
2 of 4
444 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
AN-LN-PT (Analog Line Port)
Table 131: Test #161 Analog Looparound Test (continued)
Error
Code
Test
Result
Description / Recommendation
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
System resources required to run this test are not available.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort, escalate the problem.
FAIL
The reflective loop-around test failed. This could cause noisy or unreliable
connections, or users calling this port may hear an echo. The problem can
also be off-board.
1. Since a line seizure may affect the test, repeat the test at 1-minute
intervals up to 5 times.
2. Use test board location short to run circuit pack tests to check
the Tone Generator and the Tone Detector circuits on the IPSIs or the
Tone Generator/Tone Detector circuit packs.
3. Resolve any problems on the Tone Generator or the Tone Detector
circuit.
4. If the Tone Generator and Tone Detector circuits are functioning
properly, determine whether a voice terminal is connected and wired
properly. Resolve any problems found.
5. If the test still fails, replace the analog line circuit pack.
PASS
The port provides an analog transmission path to the station equipment.
Investigate user-reported troubles on this port by running other port tests, by
examining station wiring, or by inspecting the station.
3 of 4
Issue 1 June 2005
445
Communication Manager Maintenance-Object Repair Procedures
Table 131: Test #161 Analog Looparound Test (continued)
Error
Code
Test
Result
Description / Recommendation
0
NO
BOARD
The test could not relate the internal ID to the port (no board). This result
could be due to incorrect translations, no board is inserted, an incorrect
board is inserted, or an insane board is inserted.
1. Check to make sure that the board translations are correct. Enter list
configuration, and resolve any problems.
2. If the board is correctly inserted, enter busy board location
3. Enter reset board location
4. Enter release board location
5. Enter test board location long
This should re-establish the link between the internal ID and the port. If
not, verify that a valid board is inserted.
4 of 4
446 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANN-BD (Announcement circuit pack)
ANN-BD (Announcement circuit pack)
Note:
MO Name in Alarm
Log
Alarm
level
Initial command to run
Full name of MO
ANN-BD
MIN
test board location l
Announcement Circuit Pack
ANN-BD
WRN
test board location l
Announcement Circuit Pack
Note:
The information contained in ANN-BD refers only to the TN750-series of circuit
packs. Expressions such as "announcement circuit pack" and "announcement
board" are to be interpreted to mean the TN750-series only.
The TN750 Announcement circuit pack is a service circuit which provides an integrated means
for recording announcements that can be played back on demand by call processing as part of
a calling feature (for example, announcements on hunt group calls). There are 16
Announcement Ports on the Announcement circuit pack. Each port can play any integrated
announcement, independently of the other ports. In addition to the 16 Announcement Ports, the
Announcement circuit pack also has one Data Line Circuit Port (port 17). The Data Line Circuit
Port is used for uploading/downloading the announcement memory to/from the memory card. If
there are any errors associated with port 17, refer to DAT-LINE (Data Line Port) on page 870. If
there are any errors associated with any other port, refer to ANN-PT (announcement port) on
page 465.
Note:
Note:
TN750C is required if your system has multiple TN750x announcement boards
(up to ten are allowed). Only one TN750A/B may be present in the system with
up to nine additional TN750C boards. All ten boards may be TN750C. The
announcements from a TN750A/B can be saved and restored to a TN750C, but
once the announcements are recorded onto a TN750C they are not backward
compatible with the TN750A/B.
The Announcement circuit pack has two processors on it. The first processor, or Angel, controls
the circuit pack and communicates with the switch via the control channel on the TDM Bus. The
second processor, or Speech Processor (SP), controls the speech memory and
announcements. Digital speech is converted from its TDM Bus form to an internal storage form
(for recording) and vice versa (for playbacks) by the 140AY device on the circuit pack, which
has 16 channels (one for each Announcement Port).
Issue 1 June 2005
447
Communication Manager Maintenance-Object Repair Procedures
General notes
Here are a few important general notes that apply to any problem on the Announcement circuit
pack. The user should read this before attempting to work on the TN750 Announcement circuit
pack or Announcement Ports, especially if the circuit pack needs to be replaced.
1. The TN750 Announcement circuit pack retains all integrated announcements as long as the
circuit pack has power. For this reason, whenever there is a problem with either the
Announcement circuit pack or an Announcement Port that may require the circuit pack to be
reset, it is always best to try to reset the circuit pack via reset board PCSS first. If that
does not work, replace the circuit pack. Announcements are preserved through a software
reset, but they are lost when the circuit pack is reseated.
2. If a customer has announcements on the Announcement circuit pack, then announcements
must be saved on the memory card to ensure that they are not lost. This should be done as
soon as the announcements are recorded on the circuit pack (or whenever they are
changed), assuming that the circuit pack is in proper working order (see Note).
Note:
Note:
Unlike translations, announcements are NEVER automatically saved to the
memory card.
3. Save announcements replaces the TN750x announcement file on the memory card.
Care must be taken not to mistakenly enter this command and, as a result, destroy a valid
file on the memory card.
4. Restore announcements replaces the TN750x Announcement circuit pack speech
memory with the announcement file on the memory card. Care must be taken not to
mistakenly enter this command, destroying valid speech memory, especially if the memory
card does not have a valid announcement file on it.
5. Whenever the TN750x Announcement circuit pack is replaced, announcements must
always be rerecorded or downloaded to the new circuit pack. Otherwise, call processing is
not able to use the pack.
6. If announcement speech memory is corrupted, announcements should not be saved [that
is, if the Announcement Checksum Test (#209) fails, or if the speech sounds corrupted on
playback]. This can ruin a good announcement file on the memory card and potentially
cause errors/alarms on any circuit pack to which the new file is downloaded. However, if the
customer does not have a valid announcement file on the memory card, announcements
can be saved in an effort to try to retain some of them (all of the announcements recorded
may not be corrupted).
7. Due to a hardware fault in the TN750 announcement board, the following sequence of
events may cause the announcement file to become corrupted and unusable:
a. Fill the board with recorded announcements.
b. Delete the last few announcements recorded.
c. Re-record the announcements deleted.
448 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANN-BD (Announcement circuit pack)
If the announcement file becomes corrupted, the only solution is to re-record all
announcements. To do this, follow these steps:
d. Remove the announcement board.
e. Remove the tape cartridge from the tape drive. Do this so that announcements are not
automatically restored from tape.
f. Re-insert the announcement board.
g. Re-record all announcements.
h. Insert the tape cartridge in the tape drive.
i. Enter save announcements to save all the announcements on the tape.
This hardware fault is fixed in the TN750B announcement board. However, the TN750B
board will not automatically correct an announcement file which has previously been
corrupted by a TN750 board. The only way to correct an announcement file corrupted by
the TN750 board is to follow the steps above.
Announcement administration
A brief description of the integrated announcement administration is given here to aid in
troubleshooting the Announcement circuit pack and its ports. In many cases, it is necessary to
record, play back, and/or delete announcements to resolve an alarm. It may also be necessary
to save and restore announcements as part of the maintenance procedures. For a complete
description of integrated announcement administration, please refer to Administrator Guide for
Avaya Communication Manager, 03-300509.
Announcement session
Announcements can be recorded, played back, and deleted from an announcement session. A
station’s COS needs to include console permissions in order for that station to be able to enter
an announcement session. To enter an announcement session, go off-hook on a station that
has console permissions and enter the appropriate Feature Access Code (FAC), administered
as Announcement access code on the FACs form. Dial tone should be returned at this point.
Enter the extension of the announcement that needs to be recorded, deleted, or played back.
Again, dial tone should be heard. To record an announcement, press station keypad digit 1,
record after the tone, and hang up when done. To play back an announcement, press 2. To
delete an announcement, press 3 (confirmation tone is given if the delete worked).
Announcements can also be played back by simply calling the announcement extension
associated with them.
Issue 1 June 2005
449
Communication Manager Maintenance-Object Repair Procedures
Uploading/Downloading announcements
Integrated announcements on the TN750 Announcement circuit pack can be uploaded to the
memory card with save announcements. Likewise, integrated announcements can be
downloaded to the Announcement circuit pack with restore announcements. Both of these
commands require a free data module of NETCON type to be administered, a data module of
announcement type (on the Announcement circuit pack) to be administered, and a memory
card. These commands are useful in maintaining the customer’s recorded announcements.
Depending on system traffic, announcement uploads and/or downloads take between 30 and
45 minutes.
The system automatically tries to download the Announcement circuit pack five minutes after it
is inserted. This automatic download procedure is aborted if:
●
An announcement is recorded within 10 minutes of circuit pack insertion.
●
An announcement download is invoked sooner with the restore announcements.
●
No announcement and/or NETCON data module is administered.
●
Either the announcement data module is busy or all the administered NETCON data
modules are busy.
●
No memory card is in the system.
●
The memory card in the system does not have a valid announcement file saved on it.
Hardware error log entries and test to clear values
Table 132: Announcement circuit pack error log entries
Error
type
Aux
data
Associated test
Alarm
level
(See
WRN
message)
On/
Off
board
Test to clear value
0 (a)
0
Any
Any
Any
test board PCSS sh r 1
1 (b)
0
Circuit pack removed or SAKI Test (#53)
MIN
ON
2 (c)
None
14 (d)
1 to 64
Announcement Checksum (209)
18
0
busyout board PCSS
WRN
OFF
23 (e)
0
None
WRN
OFF
release board PCSS
1 of 2
450 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANN-BD (Announcement circuit pack)
Table 132: Announcement circuit pack error log entries (continued)
Error
type
Aux
data
125 (f)
Associated test
Alarm
level
(See
WRN
message)
On/
Off
board
None
MIN
ON
Test to clear value
170
0
None
MIN
ON
217 (g)
0
None
WRN
OFF
257
65535
Control Channel Test (#52)
MIN
ON
257 (h)
Any
None
267 (g)
0
None
WRN
OFF
513 (i)
Any
None
1025 (j)
4363
NPE Audit Test (#50)
1281 (k)
17699
None
1538 (l)
Any
None
MIN
ON
Angel-SP Handshake (#208)
MIN
ON
test board PCSS l r 3
MIN
ON
test board PCSS sh r 3
1793
17680
2049
(m) (n)
test board PCSS l
In-line Error
Clock Match Inquiry (#212)
17674
test board PCSS l r 20
In-line Error
2305
140AY Loop Around (#210)
MIN
ON
test board PCSS sh r 3
2561
Super Frame Match Inquiry (211)
MIN
ON
test board PCSS sh r 3
MIN
ON
test board PCSS sh r 3
17676
In-line Error
Announcement Checksum (#209)
2817
(m)
17682
In-line Error
17699
In-line Error
3840 (j)
Any
None
3999 (o)
Any
None
2 of 2
!
WARNING:
WARNING:
All alarms are upgraded to MAJOR when the BASE Tone Generator is set to 12
(France).
Issue 1 June 2005
451
Communication Manager Maintenance-Object Repair Procedures
Notes:
a. 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.
b. Error Type 1: the circuit pack totally stopped functioning or it was physically removed from
the system.
Note:
Note:
The alarm is logged about 11 minutes after the circuit pack has been removed
and/or SAKI Test (#53) fails.
If the circuit pack is not in the system, insert a circuit pack (in the same slot as the error
indicates) to resolve this error. Or, if the circuit pack is in the system and the red LED is on,
follow the instructions for "Red (alarm)" in RIGHT LED in SERVICES jack - GREEN: lights
up seventh then turns off. on page 287.
Note:
Note:
The alarm is logged about 11 minutes after the circuit pack has been removed
and/or SAKI Test (#53) fails.
!
WARNING:
WARNING:
Reseating and/or replacing the circuit pack results in loss of integrated
announcements (TN750/B only). See General notes on page 465 near the
beginning of this Maintenance procedure.
c. Error Type 2: Check the Class of Restriction (COR) administered for the Data Line
extension assigned to the TN750 for uploading and downloading announcements. The
extension can be found by using list data-module.
d. Error Type 14: logged when the Announcement Checksum Test (#209) fails. The Aux Data
indicates the number of the first defective announcement found. This number corresponds
to the announcement numbers on the announcement form. The extension relating to the
announcement can be determined by display announcement. This error only appears
in the Error Log in conjunction with Error Type 2817. Follow the procedures for Error Type
2817 to troubleshoot Error Type 14.
e. Error Type 23: the circuit pack has been logically administered but not physically installed.
The alarm is cleared when the circuit pack is installed.
f. Error Type 125: the wrong circuit pack is inserted in the slot where this circuit pack is
logically administered. To resolve this problem, either remove the wrong circuit pack and
insert the logically administered circuit pack OR use change circuit-pack to
readminister this slot to match the circuit pack inserted.
g. Error Type 217 and 267: there is more than one TN750 Announcement circuit pack
inserted in the system. Remove the alarmed circuit pack.
h. Error Type 257: transient communication problems with this circuit pack. This error is not
service-affecting and no action is required.
452 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANN-BD (Announcement circuit pack)
i. Error Type 513: when reported with Aux Data in the range of 4352 to 4358, the circuit pack
has reported a hardware failure on the circuit pack. The circuit pack should be replaced.
Replacing the circuit pack results in loss of integrated announcements (TN750/B only). See
General notes on page 465 near the beginning of this Maintenance procedure.
j. Error Types 1025 and 3840: not service-affecting, no action is required.
k. Error Type 1281: the speech processor (SP) found a fault in the speech main memory
(SMM) (that is, it found one or more faulty memory locations). Whenever this error is
logged, error 2817 is also logged [see Note (m)], which causes the maintenance system to
run the Announcement Checksum Test (#209) to determine if the bad memory location was
being used by an announcement.
l. Error Type 1538: the hyperactive circuit pack is out-of-service and may exhibit one or more
of the following symptoms:
1. The tests run on the ports of this circuit pack are returning with a NO-BOARD.
2. A busyout/release of the circuit pack has no effect on test results.
3. A list configuration command shows that the circuit pack and ports are properly
installed.
The system tries to restore the circuit pack within 15 minutes. If the error recurs after 15
minutes, replace the circuit pack. (Refer to Reseating and replacing circuit packs in
Maintenance Procedures (03-300192).)
m. Error Types 2049 and 2817: logged in conjunction with Error Type 1281, Aux Data 17699.
Because Error Type 1281 means that a defective speech memory location was found, [see
Note (k)] the announcement checksum error is also logged. This causes the Announcement
Checksum Test (#209) to run, which determines if the defective memory location has
corrupted any recorded announcements. If the Checksum Test passes, the faulty memory
location is currently not being used, and the SP marks the location as faulty to ensure that
future announcements do not attempt to use it.
Note:
Note:
As memory locations are marked faulty, the amount of available memory
decreases, which decreases the total amount of announcement time available on
the circuit pack.
n. Error Type 2049: transient error that does not cause an alarm can occasionally occur
during a SPE, TDM BUS, or Tone Clock interchange. It is possible for a marginal
Tone-Clock circuit pack to cause this error against the ANN-BD without alarming the
TONE-BD. If this error occurs again, replacing the Tone-Clock circuit pack may clear up this
error. See the FAIL case in the Clock Match Inquiry Test (#212).
o. Error type 3999: the circuit pack sent a large number of control channel messages to the
switch within a short period of time. If error type 1538 is also present, then the circuit pack
was taken out-of-service due to hyperactivity. If error type 1538 is not present, then the
circuit pack has not been taken out-of-service, but it has generated 50% of the messages
necessary to be considered hyperactive. This may be completely normal during heavy
traffic periods. However, if this error type is logged when the circuit pack is being lightly
used, it may indicate a problem with the circuit pack or the equipment attached to it.
Issue 1 June 2005
453
Communication Manager Maintenance-Object Repair Procedures
System technician-demanded tests: descriptions and error codes
Investigate tests in the order presented in Table 133: System Technician-demanded tests:
ANN-BD on page 454. By clearing error codes associated with the first test, you may clear other
errors in the sequence.
For a complete description of these tests, refer to the XXX-BD (Common Port Circuit Pack/
Media Module) on page 2539.
Table 133: System Technician-demanded tests: ANN-BD
Order of investigation
Short test
sequence
Long test
sequence
Reset
board
sequence
D/ND1
Control channel loop-around test (#52)
X
ND
Angel-speech processor (sp) handshake (#208)
X
ND
Clock match inquiry test (#212)
X
X
ND
Super frame match inquiry test (#211)
X
X
ND
140AY loop around test (#210)
X
X
ND
Announcement checksum test (#209)
X
X
ND
X
ND
Connection Audit Test (#50) (a)
SAKI Sanity Test (#53) (a)
X
1. D = Destructive, ND = Nondestructive
Angel-speech processor (sp) handshake test (#208)
This test checks the integrity of the communication link between the two processors on the
Announcement circuit pack.
!
WARNING:
WARNING:
Failure of this test indicates that the Speech Processor is insane and results in
the loss of all integrated announcements on the circuit pack.
454 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
D
ANN-BD (Announcement circuit pack)
Table 134: TEST #208 angel-speech processor (SP) handshake test
Error
code
Test
result
Description/ Recommendation
2000
ABRT
Response to the test request was not received within the allowable time
period. If Error Type 1538 is present in the Error Log, follow the maintenance
strategy recommended for this Error Type.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
ABRT
Internal system error.
1. Retry the command at 1-minute intervals a maximum of 5 times.
FAIL
Test failed. Circuit pack cannot be used. Announcement speech memory is
cleared when this test fails. Therefore, when the problem has been resolved,
announcements must be rerecorded or downloaded to the circuit pack.
1. Reset the circuit pack via reset board PCSS and then run this test
again. If the test continues to fail, replace the circuit pack and then run
this test again.
2. If there are recurring alarms on this circuit pack caused by this test
failing, replace the circuit pack even if Step 1 works.
!
WARNING:
PASS
WARNING:
Replacing the circuit pack results in loss of integrated
announcements. See General notes on page 465.
The communications link between the two processors on the Announcement
circuit pack is functioning properly. User-reported troubles on this circuit pack
should be investigated using other circuit pack and port tests. Refer to
ANN-PT (announcement port) on page 465 for a description of the port tests.
Announcement checksum test (#209)
Associated with every recorded announcement is a checksum. In this test, the SP checks a
stored global checksum covering all recorded announcements against a calculated one and
returns the results to the maintenance system. If the global checksum failed, maintenance
requests the SP to check each individual announcement’s checksum.
Issue 1 June 2005
455
Communication Manager Maintenance-Object Repair Procedures
If the test fails, then it returns the total number of defective announcements found. In addition,
associated with each failure is an error in the Error Log (Error Type 14). The Aux Data indicates
the number of the first defective announcement found. This number corresponds to the
announcement numbers on the announcement form. The extension relating to the
announcement can be determined by display announcement.
Table 135: TEST #209 announcement checksum test
Error
code
Test
result
Description/ Recommendation
0
ABRT
An error code of 0 indicates that the announcement file has been corrupted
due to a hardware fault in the TN750 board. Follow step #7 under General
notes on page 465 at the beginning of this section.
1023
ABRT
There are no announcements currently recorded on the circuit pack.
1024
ABRT
This abort code is given for the following reasons:
1. An announcement upload or download is in progress.
2. An announcement upload or download is requested when this test is
running.
3. A record is in progress.
4. A record request comes in when this test is running.
If an announcement upload or download is in progress, status
data-module <announcement data extension> should show that the
announcement data port is connected to a NETCON data channel, and the
"card-in-use" LED for the memory card is on (to determine the extension of
the announcement data module, use list data-module).
See Note (a) at end of table for more information.
1. Wait until the blocking event is finished, and then run this test again. An
upload or download could take up to 45 minutes to complete, and a
recording session is finished as soon as the station that was making the
recording is placed on-hook.
2. If the test continues to abort, and a record or upload/download is not in
progress, escalate the problem.
2000
ABRT
Response to the test request was not received within the allowable time
period. If Error Type 1538 is present in the Error Log, follow the
maintenance strategy recommended for this Error Type.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1 of 3
456 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANN-BD (Announcement circuit pack)
Table 135: TEST #209 announcement checksum test (continued)
Error
code
Test
result
Description/ Recommendation
ABRT
Internal system error.
1. Retry the command at 1-minute intervals a maximum of 5 times.
0-256
FAIL
Test failed. The error code indicates the total number of defective
announcements that were found.
When TEST #209 fails with error code 0, the Global Checksum failed on the
board, but no individual Checksum failed.
Note:
Note:
Since the announcements are recorded digitally, it is possible
for the Announcement Checksum Test to fail but still have all
the announcements sound uncorrupted. When an individual
announcement fails the Checksum Test, always listen to the
announcement first before taking any action (an
announcement can be played back by dialing the
announcement extension associated with the announcement
number). If the announcement sounds corrupted, then
rerecord it or delete it.
1. Look in the Error Log to determine the number of the first defective
announcement. Play back the announcement. If the announcement
sounds defective, rerecord it or delete it. If the error code was greater
than one (indicating that there is more than one defective
announcement), run this test again and repeat this step.
2. If after deleting and rerecording all defective announcements, the
checksum test still fails, reset the circuit pack using reset board
PCSS and run this test again.
3. If the test still continues to fail, reseat the circuit pack and restore all
announcements with an appropriate time estimate (for example, 40
minutes.) Then rerecord the lost announcements (that is, those
recorded since the last save operation) and run this test again.
4. If the test still continues to fail, replace the circuit pack, and run this test
again.
!
WARNING:
WARNING:
Replacing the circuit pack results in loss of integrated
announcements. See General notes on page 465 near the
beginning of this Maintenance procedure.
2 of 3
Issue 1 June 2005
457
Communication Manager Maintenance-Object Repair Procedures
Table 135: TEST #209 announcement checksum test (continued)
Error
code
Test
result
Description/ Recommendation
PASS
All recorded announcements checksum correctly, indicating that the speech
main memory is functioning properly. User-reported troubles on this circuit
pack should be investigated using other circuit pack and port tests. Refer to
ANN-PT (announcement port) on page 465 Maintenance documentation for
a description of the port tests.
3 of 3
Notes:
a. The Announcement circuit pack can exhibit a condition that does not allow recording.
If the circuit pack gets locked into this state (this is an extremely rare condition), two of the
Announcement Ports on the circuit pack will be unusable by software, one of which is the
record port. Also, save/restore announcements will not work, since the record port
looks busy to the circuit pack. Note that software does not have any way of knowing this,
and attempts to use the ports.
If the circuit pack is locked into this state, the following symptoms are observed:
1. When attempting to record an announcement, users hear the proper record tone, but the
announcement do not record (they do not know it until the announcement is played
back).
2. Performing a test board long when the circuit pack is in this state yield the following
abort codes:
●
Ports 1 AND 9 abort Test #206 with code 1024
●
Ports 1 AND 9 abort Test #205 with code 2000
●
Board level Tests #209 and #210 abort with code 1024
3. Save/restore announcements times out with:
Error encountered, can’t complete request
The Announcement circuit pack lock-up can be cleared remotely by performing a soft reset
to the circuit pack:
●
busyout board PCSS (this command drops all calls in progress on the Announcement
circuit pack)
●
Reset circuit pack using reset board PCSS
●
Release circuit pack using release board PCSS
458 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANN-BD (Announcement circuit pack)
140AY loop around test (#210)
This test checks the integrity of the record channel on the Announcement circuit pack
(Announcement Port 1). The main function of the 140AY device is to accept Pulse Code
Modulation (PCM)/Adaptive Differential Pulse Code Modulation (ADPCM) samples and
compress/expand the samples using ADPCM. This test connects a Tone Generator to one port
(Announcement Port 1, the recording port), and a Tone Detector to another port (Announcement
Port 9). A tone is generated by the Tone Generator on the first port and looped through the
140AY device to the second port. The Tone Detector then responds with a tone present/absent
message. The 140AY Loop Around Test is repeated at three different speech compression
rates.
Since this test involves sending a tone through two different ports, the Playback Speech
Memory Array (PSMA) Test (#206) is run on the two ports first to make sure that they are
working properly. See ANN-PT (announcement port) on page 465 for a description of this test.
Table 136: TEST #210 140AY loop around test
Error
code
Test
result
Description/ Recommendation
1-3
ABRT
Response to the test request was not received within the allowable time
period. The error code indicates at which speech compression rate the test
aborted (one being the first rate tested, three being the last).
1. Retry the command at 1-minute intervals a maximum of 5 times.
10
ABRT
The PSMA Test (#206) failed on Announcement Port 1.
1. Refer to ANN-PT (announcement port) on page 465 Maintenance
documentation, Test #206.
90
ABRT
The PSMA Test (#206) failed on Announcement Port 9.
1. Refer to ANN-PT (announcement port) on page 465 Maintenance
documentation, Test #206.
1000
ABRT
System resources required to run this test are not available. This test needs
Announcement Ports 1 and 9 to run. One of the ports may be in use on a
valid call.
1. Retry the command at 1-minute intervals a maximum of 5 times.
2. If the test continues to abort and Ports 1 and 9 are not in use, escalate
the problem.
1 of 3
Issue 1 June 2005
459
Communication Manager Maintenance-Object Repair Procedures
Table 136: TEST #210 140AY loop around test (continued)
Error
code
Test
result
Description/ Recommendation
1002
ABRT
The system could not allocate time slots for the test. The system may be
under heavy traffic conditions or it may have time slots out-of-service due to
TDM-BUS errors. Refer to TDM-BUS (TDM Bus) on page 2237 Maintenance
documentation to diagnose any active TDM-BUS errors.
1. If system has no TDM-BUS errors and is not handling heavy traffic,
repeat test at 1-minute intervals a maximum of 5 times.
1003
ABRT
The system could not allocate a tone receiver for the test. The system may
be oversized for the number of Tone Detectors present or some Tone
Detectors may be out-of-service.
1. Look for TTR-LEV errors in the Error Log. If present, refer to the
TTR-LEV (TTR Level) on page 2370.
2. Look for TONE-PT errors in the Error Log. If present, refer to the
TONE-PT (Tone Generator) on page 2353.
3. If neither condition exists, retry the test at 1-minute intervals a maximum
of 5 times.
1007
ABRT
The Announcement circuit pack thinks that Port 1 or Port 9 is busy.
1. Retry the command at 1-minute intervals a maximum of 5 times.
2. If the test continues to abort, follow the Announcement Port
maintenance procedures for Ports 1 and 9.
1024
ABRT
Announcement circuit pack blocked the test because an announcement
download is in progress. If an announcement download is in progress,
status data-module <announcement data extension> should
show that the announcement data port is connected to a NETCON data
channel, and the "card-in-use" LED for the memory card should be on (to
determine the extension of the announcement data module, use list
data-module). See Note (a) at end of table for more information.
1. Wait until download is finished (can take up to 45 minutes), and then run
the test again.
2. If the test continues to abort and there is no download in progress,
escalate the problem.
2000
ABRT
Response to the test request was not received within the allowable time
period. If Error Type 1538 is present in the Error Log, follow the maintenance
strategy recommended for this error type.
1. Retry the command at 1-minute intervals a maximum of 5 times.
2 of 3
460 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANN-BD (Announcement circuit pack)
Table 136: TEST #210 140AY loop around test (continued)
Error
code
Test
result
Description/ Recommendation
2007
ABRT
The Announcement circuit pack thinks that Port 1 or Port 9 is busy.
1. Retry the command at 1-minute intervals a maximum of 5 times.
2. If the test continues to abort, follow the Announcement Port
maintenance procedures for Ports 1 and 9.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals a maximum of 5 times.
ABRT
Internal system error.
1. Retry the command at 1-minute intervals a maximum of 5 times.
1-3
FAIL
Test failed. The error code indicates at which speech compression rate the
test actually failed (one being the first rate tested, three being the last).
1. Reset the circuit pack via reset board PCSS and then run this test
again. If the test still fails, replace the circuit pack (see Warning) and run
this test again.
2. If there are recurring alarms on this circuit pack caused by this test
failing, replace the circuit pack even if Step 1 works (see Warning).
!
WARNING:
PASS
WARNING:
Replacing the circuit pack results in loss of integrated
announcements. See General notes on page 465.
The record channel on the Announcement circuit pack is functioning properly.
User-reported troubles on this circuit pack should be investigated using other
circuit pack and port tests. Refer to ANN-PT (announcement port) on
page 465 for a description of the port tests.
3 of 3
Notes:
a. The Announcement circuit pack can exhibit a condition that does not allow recording.
If the circuit pack gets locked into this state (this is an extremely rare condition), two of the
Announcement Ports on the circuit pack will be unusable by software, one of which is the
record port. Also, save/restore announcements will not work since the record port
looks busy to the circuit pack. Note that software does not have any way of knowing this,
and attempts to use the ports.
If the circuit pack is locked into this state, the following symptoms are observed:
Issue 1 June 2005
461
Communication Manager Maintenance-Object Repair Procedures
1. When attempting to record an announcement, users hear the proper record tone, but the
announcement does not record (they do not know it until the announcement is played
back).
2. Performing a test board long when the circuit pack is in this state yields the
following abort codes:
●
Ports 1 AND 9 abort Test #206 with code 1024
●
Ports 1 AND 9 abort Test #205 with code 2000
●
Board level Tests #209 and #210 abort with code 1024
3. Save/restore announcements times out with Error encountered, can’t complete
request
The Announcement circuit pack lock-up can be cleared remotely by performing a soft reset
to the circuit pack:
●
busyout board PCSS (this command drops all calls in progress on the Announcement
circuit pack)
●
Reset circuit pack using reset board PCSS
●
Release circuit pack using release board PCSS
Super frame match inquiry test (#211)
The super frame is a means by which the SP synchronizes with the 140AY device on the
Announcement circuit pack. If the super frame is not synchronized, the SP is not able to
properly process record/playback requests. Both the SP and the hardware generate a super
frame pulse. When these two pulses are out of synch, the SP sets a flag to indicate the
mismatch. When this test is run, the state of this flag is returned.
Table 137: TEST #211 super frame match inquiry
Error
code
Test
result
Description/ Recommendation
2000
ABRT
Response to the test request was not received within the allowable time
period. If Error Type 1538 is present in the Error Log, follow the maintenance
strategy recommended for this Error Type.
1. Retry the command at 1-minute intervals up to 5 times.
1 of 2
462 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANN-BD (Announcement circuit pack)
Table 137: TEST #211 super frame match inquiry (continued)
Error
code
Test
result
Description/ Recommendation
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
ABRT
Internal system error.
1. Retry the command at 1-minute intervals a maximum of 5 times.
FAIL
Test failed. Announcement playbacks should sound corrupted.
1. Reset the circuit pack via reset board PCSS and then run this test
again. If the test continues to fail, replace the circuit pack (see Warning).
2. If there are recurring alarms on this circuit pack caused by this test
failing, replace the circuit pack even if Step 1 works (see Warning).
!
WARNING:
PASS
WARNING:
Replacing the circuit pack results in loss of integrated
announcements. See General notes on page 465 near the
beginning of this Maintenance procedure.
The SP can properly process record/playback requests. User-reported
troubles on this circuit pack should be investigated using other circuit pack
and port tests. Refer to ANN-PT (announcement port) on page 465 for a
description of the port tests.
2 of 2
Clock match inquiry test (#212)
This test is supported to determine the state of the clock generation circuitry on the
Announcement circuit pack. This circuitry is used for controlling various pieces of the hardware,
like the 140AY device. It is also used to synchronize the Announcement circuit pack with the
clock that is on the backplane.
Table 138: TEST #212 clock match inquiry test
Error
code
Test
result
Description/ Recommendation
2000
ABRT
Response to the test request was not received within the allowable time
period. If Error Type 1538 is present in the Error Log, follow the maintenance
strategy recommended for this Error Type.
1 of 2
Issue 1 June 2005
463
Communication Manager Maintenance-Object Repair Procedures
Table 138: TEST #212 clock match inquiry test (continued)
Error
code
Test
result
Description/ Recommendation
2100
ABRT
Could not allocate the necessary system resources to run this test.
ABRT
Internal system error.
1. Retry the command at 1-minute intervals a maximum of 5 times.
FAIL
Test failed. Announcements recorded or played back while the clock circuitry
is not functioning properly sound distorted. The ANN-BD may be defective or
the Active Tone-Clock circuit pack (TONE-BD) may be marginal and is
causing this test to fail.
1. Reset the circuit pack via reset board PCSS and then run this test
again. If the test continues to fail, proceed to Step 2 or 3 as applicable.
!
WARNING:
FAIL
WARNING:
Replacing the circuit pack results in loss of integrated
announcements. See General notes on page 465 near the
beginning of this Maintenance procedure.
2. Replace the ANN-BD. Rerun the test. If the test continues to fail, replace
the Tone-Clock circuit pack.
!
WARNING:
WARNING:
Replacing the TONE-BD causes a COLD 2 reset. See
Replacing the IPSI or Tone-Clock Circuit Pack on page 2337.
Replacing the ANN-BD results in loss of integrated
announcements. See General notes on page 465 near the
beginning of this Maintenance procedure.
3. If there are recurring alarms on this circuit pack caused by this test
failing, replace the ANN-BD even if the previous steps were successful.
PASS
Announcement record/playbacks should have clear sound quality.
User-reported troubles on this circuit pack should be investigated using other
circuit packs and port tests. Refer to ANN-PT (announcement port) on
page 465 for a description of the port tests.
2 of 2
464 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANN-PT (announcement port)
ANN-PT (announcement port)
MO Name in
Alarm Log
Alarm
level
Initial command to run
Full name of MO
ANN-PT
MIN
test port location l
Announcement Port
ANN-PT
WRN
test port location l
Announcement Port
The TN750 Announcement circuit pack is a service circuit pack that provides an integrated
means for recording announcements that can be played back on demand by call processing as
part of a calling feature (that is, announcements on hunt group calls). There are 16
Announcement Ports on the Announcement circuit pack. Each port can play any integrated
announcement, independently of the other ports. If there are any errors associated with the
circuit pack, refer to ANN-BD (Announcement circuit pack) on page 447.
The Announcement circuit pack has two processors on it. The first processor, or Angel, controls
the circuit pack, and communicates with the switch via the control channel on the TDM Bus. The
second processor, or SP, controls the speech memory and announcements. Digital speech is
converted from its TDM Bus form to an internal storage form (for recording) and vice versa (for
playbacks) by the 140AY device on the circuit pack, which has 16 channels (one for each
Announcement Port).
General notes
Here are a few very important general notes that apply to any problem on the TN750
Announcement circuit pack. The user should read this before attempting to work on the TN750
Announcement circuit pack or Announcement Ports, especially if the circuit pack needs to be
replaced.
1. The TN750/B Announcement circuit pack retains all integrated announcements as long as
the circuit pack has power. For this reason, whenever there is a problem with either the
Announcement circuit pack or an Announcement Port that may require the circuit pack to be
reset, it is always better to try to reset the circuit pack via reset board PCSS first and, if
that does not work, then try to reseat it. Announcements are preserved through a software
reset, but they are lost when the circuit pack is reseated.
2. If a customer has announcements on the Announcement circuit pack, then announcements
must be saved on the system tape to ensure that they are not lost. This should be done as
soon as the announcements are recorded on the circuit pack (or whenever they are
changed), assuming that the pack is in proper working order (see Note).
Note:
Note:
Unlike translations, announcements are NEVER automatically saved to the
memory card.
Issue 1 June 2005
465
Communication Manager Maintenance-Object Repair Procedures
3. Save announcements replaces the announcement file on the card with the
Announcement circuit pack speech memory. Care must be taken not to mistakenly enter
this command, thereby destroying a valid file on tape.
4. Restore announcements replaces the Announcement circuit pack speech memory with
the announcement file on the card. Care must be taken not to mistakenly enter this
command, thereby destroying valid speech memory (especially if the card does not have a
valid announcement file on it).
5. Whenever the Announcement circuit pack is replaced, announcements must always be
re-recorded or downloaded to the new circuit pack. Otherwise, call processing is not able to
use the circuit pack.
6. If announcement speech memory is corrupted, announcements should not be saved, that
is, if the Announcement Checksum Test (#209) fails or if the speech sounds corrupted on
playback. This can ruin a good announcement file and potentially cause errors/alarms on
any circuit pack to which the new file is downloaded. However, if the customer does not
have a valid announcement file, then announcements can be saved in an effort to try to
retain some of them (all of the announcements recorded may not be corrupted).
7. Although Announcement Port 5 and Data Line Circuit Port 17 on the Announcement circuit
pack are logically two separate ports, they are physically the same port. Therefore, if one of
the ports is in use, the other one will be busy. Also, if Announcement Port 5 is out-of-service,
the Data Line Circuit Port is taken out-of-service. However, if the Data Line Circuit Port is
out-of-service, the Announcement Port remains in-service.
Announcement administration
A brief description of the integrated announcement administration is given here to aid in the
troubleshooting of the Announcement circuit pack and its ports. In many cases, it is necessary
to record, play back, and/or delete announcements to resolve an alarm. It may also be
necessary to save and restore announcements as part of the maintenance procedures. For a
complete description of integrated announcement administration, please refer to Administrator
Guide for Avaya Communication Manager, 03-300509.
466 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANN-PT (announcement port)
Announcement session
Announcements can be recorded, played back, and deleted from an announcement session. A
station’s COS needs to include console permissions in order for that station to be able to enter
an announcement session. To enter an announcement session, go off-hook on a station that
has console permissions and enter the appropriate FAC (administered as Announcement
access code on the FACs form). Dial tone should be returned at this point. Enter the extension
of the announcement that needs to be recorded, deleted or played back. Again, dial tone should
be heard. To record an announcement, press station keypad digit 1, record after the tone, and
hang up when done. To play back an announcement, press station keypad digit 2. To delete an
announcement, press station keypad digit 3 (confirmation tone is given if the delete worked).
Announcements can also be played back by simply calling the announcement extension
associated with them.
Uploading/Downloading announcements
Integrated announcements on the TN750 Announcement circuit pack can be uploaded to the
memory card with save announcements. Similarly, integrated announcements can be
downloaded to the Announcement circuit pack with restore announcements. Both of these
commands require a free data module of NETCON type to be administered, a data module of
announcement type (on the Announcement circuit pack) to be administered, and a memory
card. These commands are useful in maintaining the customer’s recorded announcements.
Depending on system traffic, announcement uploads/downloads take between 30 and 45
minutes.
The system automatically tries to download the Announcement circuit pack five minutes after it
is inserted. This automatic download procedure is aborted if:
Note:
●
An announcement is recorded within 10 minutes of circuit pack insertion.
●
An announcement download is invoked sooner with the administration terminal restore
announcements command.
●
There is no announcement and/or NETCON data module administered.
●
Either the announcement data module is busy or all the administered NETCON data
modules are busy.
●
There is no memory card in the system.
●
The memory card in the system does not have a valid announcement file saved on it.
Note:
Unlike translations, there is no provision in the system for automatically saving
announcements to the memory card.
Issue 1 June 2005
467
Communication Manager Maintenance-Object Repair Procedures
Announcement Board Locked Condition
The Announcement circuit pack can exhibit a condition that does not allow recording.
If the circuit pack gets locked into this state (this is an extremely rare condition), two of the
announcement ports on the circuit pack (one of which is the record port) will be unusable by
software. Also, save/restore announcements will not work since the record port looks
busy to the circuit pack. Note that software does not have any way of knowing this and will
attempt to use the ports.
If the circuit pack is locked into this state, the following symptoms will be observed:
1. When attempting to record an announcement, users will hear the proper record tone, but
the announcement will not record (they will not know it until the announcement is played
back).
2. Performing a test board long when the circuit pack is in this state will yield the
following abort codes:
●
Ports 1 AND 9 abort Test 206 with code 1024.
●
Ports 1 AND 9 abort Test 205 with code 2000.
●
Board-level Tests 209 and 210 abort with code 1024.
3. The save/restore announcements times out with:
Error encountered, can’t complete request
The Announcement circuit pack lock-up can be cleared remotely by performing a soft reset to
the circuit pack:
●
busyout board location (this command drops every call in progress on the
Announcement circuit pack).
●
Reset circuit pack using reset board location.
●
Release board using release board location.
468 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANN-PT (announcement port)
Hardware error log entries and test to clear values
Table 139: Announcement port error log entries
Error
Type
Aux
data
Associated test
Alarm
level
On/
Off
board
Test to clear value
0 (a)
0
Any
Any
Any
test port PCSSpp sh r 1
Playback Speech
Memory Array
(PSMA) Test (#206)
MIN
ON
test port PCSSpp sh r 3
The port was busied
out
WRN
OFF
release port PCSSpp
130 (b)
None
WRN
ON
test port PCSSpp sh
257
Channel
Administration
Memory Array
(CAMA) Test (#205)
MINOR
ON
test port PCSSpp l r 3
MINOR
ON
test port PCSSpp sh r 3
1
18
0
17667
513
140AY Channel
Sanity Inquiry Test
(#222)
17684
769 (c)
In-line error
In-line error
None
Notes:
a. 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.
b. 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.
c. Error Type 769 is logged and the port is alarmed when an alarm is raised on the
Announcement circuit pack because of a faulty condition with a common circuit pack
resource. Any one of the following alarmed errors on the Announcement circuit pack causes
this error to be logged against the Announcement Port: 1793, 2049, 2305, 2561. Follow the
ANN-BD (Announcement circuit pack) maintenance documentation to resolve these alarms.
When the corresponding circuit pack alarm is cleared, this alarm clears.
Issue 1 June 2005
469
Communication Manager Maintenance-Object Repair Procedures
System technician-demanded tests: descriptions and error codes
Investigate tests in the order presented. By clearing error codes associated with the Channel
Administration Memory Array (CAMA) Test, you may also clear other errors.
Table 140: Announcement port system technician-demanded tests
Order of investigation
Short test
sequence
Long test
sequence
D/ND1
X
ND
Channel administration memory array (cama) test (#205)
Playback speech memory array (PSMA) test (#206)
X
X
ND
140AY channel sanity inquiry test (#222)
X
X
ND
1. D = Destructive; ND = Nondestructive
Channel administration memory array (CAMA) test (#205)
This test is a memory device that stores information used to control the 140AY device. The
Angel asynchronously feeds the CAMA with the control information. During the CAMA test, the
Angel writes patterns into the CAMA, reads them back, and verifies that they match. If the
patterns do not match, the test fails. This test is run periodically by the switch maintenance and
by the Announcement circuit pack in the background.
Table 141: TEST #205 channel administration memory array (CAMA) test
Error
code
Test
result
Description/ Recommendation
1000
ABRT
System resources required to run this test are not available. The port may
be in use on a valid call.
1. Retry the command at 1-minute intervals a maximum of 5 times.
2000
ABRT
Response to the test request was not received within the allowable time
period. See Note (a) at end of table for more information.
2100
ABRT
Could not allocate the necessary system resources to run this test.
ABRT
Internal system error.
1. Retry the command at 1-minute intervals a maximum of 5 times.
1 of 2
470 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANN-PT (announcement port)
Table 141: TEST #205 channel administration memory array (CAMA) test (continued)
Error
code
Test
result
Description/ Recommendation
FAIL
Test failed. Announcements played back on this port may sound corrupted.
1. Reset the circuit pack via reset board PCSS and then run this test
again. If the test continues to fail, replace the circuit pack (see Warning).
2. If there are recurring alarms on this port caused by this test failing,
replace the circuit pack even if Step 1 works (see Warning).
!
WARNING:
PASS
WARNING:
Replacing the circuit pack results in loss of integrated
announcements. Refer to General notes on page 465.
This test verifies that the Angel processor can properly set up this port for
playbacks. User-reported troubles on this circuit pack should be investigated
using other port and circuit pack tests. (Refer to ANN-BD (Announcement
circuit pack) on page 447 for a description of the circuit pack tests.)
2 of 2
Notes:
a. The Announcement circuit pack can exhibit a condition that does not allow recording.
If the circuit pack gets locked into this state (this is an extremely rare condition), two of the
Announcement Ports on the circuit pack (one of which is the record port) is unusable by
software. Also, save/restore announcements do not work because the record port looks
busy to the circuit pack. Note that software does not have any way of knowing this and attempts
to use the ports.
If the circuit pack is locked into this state, the following symptoms are observed:
●
When attempting to record an announcement, users hear the proper record tone, but the
announcement does not record (they do not know it until the announcement is played
back).
●
Performing a test board location long when the circuit pack is in this state yields
the following abort codes:
●
●
Ports 1 AND 9 abort Test #206 with code 1024
●
Ports 1 AND 9 abort Test #205 with code 2000
●
Board level Tests #209 and #210 abort with code 1024
Save/restore announcements times out with Error encountered, can’t complete
request
Issue 1 June 2005
471
Communication Manager Maintenance-Object Repair Procedures
Clear the Announcement circuit pack lock-up remotely by performing a soft reset to the circuit
pack:
1. busyout board location (this command drops all calls in progress on the
Announcement circuit pack)
2. Reset circuit pack using reset board location
3. Release circuit pack using release board location
Playback speech memory array (PSMA) test (#206)
The PSMA test checks the integrity of a playback channel’s interface to the speech memory and
the TDM Bus. The SP has an internal buffer that contains a specific 256-byte sequence. During
this test, the byte sequence is "played" through the 140AY device onto the TDM Bus. A General
Purpose Tone Detector is used to confirm that the proper sequence was played. This test is
very important. It is the only test that actually checks an Announcement Port’s ability to play
back an announcement on the TDM Bus. If the test fails, the Tone Detector returns the number
of bytes that did not match the expected sequence. The larger the number, the more severe the
problem with that port. If this test fails, announcements played over this port should sound
corrupted.
It is the only test that actually checks an Announcement Port’s ability to play back an
announcement on the TDM Bus. If the test fails, the Tone Detector returns the number of bytes
that did not match the expected sequence. The larger the number, the more severe the problem
with that port. If this test fails, announcements played over this port should sound corrupted.
Table 142: TEST #206 playback speech memory array (PSMA) test
Error
code
Test
result
Description/ Recommendation
1000
ABRT
System resources required to run this test are not available. The port may be
in use on a valid call.
1. Retry the command at 1-minute intervals a maximum of 5 times.
1002
ABRT
The system could not allocate time slots for the test. The system may be
under heavy traffic conditions or it may have time slots out-of-service due to
TDM-BUS errors. Refer to TDM-BUS (TDM Bus) on page 2237 to diagnose
any active TDM-BUS errors.
1. If system has no TDM-BUS errors and is not handling heavy traffic,
repeat the test at 1-minute intervals a maximum of 5 times.
1 of 3
472 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANN-PT (announcement port)
Table 142: TEST #206 playback speech memory array (PSMA) test (continued)
Error
code
Test
result
Description/ Recommendation
1003
ABRT
The system could not allocate a tone receiver for the test. The system may
be oversized for the number of Tone Detectors present or some Tone
Detectors may be out-of-service.
1. Look for TTR-LEV errors in the Error Log. If present, refer to TTR-LEV
(TTR Level) on page 2370.
2. Look for TONE-PT errors in the Error Log. If present, refer to TONE-PT
(Tone Generator) on page 2353.
3. If neither condition exists, retry the test at 1-minute intervals a maximum
of 5 times.
1024
ABRT
Announcement circuit pack blocked the test because an announcement
download is in progress. If an announcement download is in progress,
status data-module <announcement data extension> should
show that the announcement data port is connected to a NETCON data
channel, and the memory card should be active. (To determine the extension
of the announcement data module, use list data-module.)
See Note (a) at end of table for more information.
1. Wait until download is finished (could take a maximum of 45 minutes),
and then run the test again.
2. If the test continues to abort and there is no download in progress,
escalate the problem.
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals a maximum of 5 times.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals a maximum of 5 times.
ABRT
Internal system error.
1. Retry the command at 1-minute intervals a maximum of 5 times.
2 of 3
Issue 1 June 2005
473
Communication Manager Maintenance-Object Repair Procedures
Table 142: TEST #206 playback speech memory array (PSMA) test (continued)
Error
code
Test
result
Description/ Recommendation
1
to
254
FAIL
Test failed. The error code indicates the number of byte count errors found
by the Tone Detector.
1. Reset the circuit pack via reset board PCSS and then run this test
again. If the test continues to fail, replace the circuit pack (see Warning).
2. If there are recurring alarms on this port caused by this test failing,
replace the circuit pack even if Step 1 works (see Warning).
!
WARNING:
255
FAIL
WARNING:
Replacing the circuit pack results in loss of integrated
announcements. Refer to General notes on page 465.
Test failed. The Announcement Port and the Tone Detector never
synchronized. Check for active GPTD-PT errors, and refer to GPTD-PT
(General-Purpose Tone Detector Port) on page 1308 to diagnose them first.
1. If there are no active GPTD-PT errors, reset the circuit pack via reset
board PCSS and then run this test again. If the test continues to fail,
replace the circuit pack (see Warning).
2. If there are recurring alarms on this port caused by this test failing,
replace the circuit pack even if Step 1 works (see Warning).
!
WARNING:
PASS
WARNING:
Replacing the circuit pack results in loss of integrated
announcements. Refer to General notes on page 465.
This port can cleanly play announcements. User-reported troubles on this
pack should be investigated using other port and circuit pack tests. Refer to
ANN-BD (Announcement circuit pack) on page 447 for a description of the
circuit pack tests.
3 of 3
Notes:
The Announcement circuit pack can exhibit a condition that does not allow recording.
If the circuit pack gets locked into this state (this is an extremely rare condition), two of the
Announcement Ports on the circuit pack (one of which is the record port) will be unusable by
software. Also, save/restore announcements will not work, since the record port looks
busy to the circuit pack. Note that software does not have any way of knowing this and attempts
to use the ports.
474 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANN-PT (announcement port)
If the circuit pack is locked into this state, the following symptoms are observed:
●
When attempting to record an announcement, users hear the proper record tone, but the
announcement does not record (they do not know it until the announcement is played
back).
●
Performing a test board location long when the circuit pack is in this state yields
the following abort codes:
●
●
Ports 1 and 9 abort Test #206 with code 1024
●
Ports 1 and 9 abort Test #205 with code 2000
●
Board level Tests #209 and #210 abort with code 1024
The restore announcements command times out with Error encountered, can’t
complete request
The Announcement circuit pack lock-up can be cleared remotely by performing a soft reset to
the circuit pack:
1. busyout board location (this command drops all calls in progress on the
Announcement circuit pack)
2. Reset circuit pack using reset board location
3. Release circuit pack using release board location
140AY channel sanity inquiry test (#222)
The Angel keeps a sanity status bit for each of the 16 channels on the 140AY device. This test
queries the Angel to determine the status for a particular channel. If a channel is insane, that
implies that announcements cannot be played back on that channel.
Table 143: TEST #222 140AY channel sanity inquiry test
Error
code
Test
result
Description/ Recommendation
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals a maximum of 5 times.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals a maximum of 5 times.
ABRT
Internal system error.
1. Retry the command at 1-minute intervals a maximum of 5 times.
1 of 2
Issue 1 June 2005
475
Communication Manager Maintenance-Object Repair Procedures
Table 143: TEST #222 140AY channel sanity inquiry test (continued)
Error
code
Test
result
Description/ Recommendation
FAIL
Test failed. Announcements cannot be played back over this port.
1. Reset the circuit pack via reset board PCSS and then run this test
again. If the test continues to fail, replace the circuit pack (see Warning).
2. If there are recurring alarms on this port caused by this test failing,
replace the circuit pack even if Step 1 works (see Warning).
!
WARNING:
PASS
WARNING:
Replacing the circuit pack results in loss of integrated
announcements. Refer to General notes on page 465.
Announcements can be played back over this port. User-reported troubles on
this pack should be investigated using other port and circuit pack tests. Refer
to the ANN-BD (Announcement circuit pack) on page 447 for a description of
the circuit pack tests.
2 of 2
476 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANNOUNCE (announce)
ANNOUNCE (announce)
●
MO Name in Alarm Log
Alarm
level
Initial command to run
Full name of MO
ANNOUNCE
none
none
ANNOUNCEMENT
The ANNOUNCE MO logs an error in the hardware error log if save announcements or
restore announcements does not complete successfully, or the system fails to restore
announcements from the memory card at boot time.
Figure 23: Connection of announcement circuit pack to the system on page 477 shows the
connection of the Announcement Circuit Pack to the system. To save or restore
announcements, an ANNOUNCEMENT Data Extension must be administered, and at least one
DATA-CHL (Network Control Data Channel) must be in the in-service/idle state.
Figure 23: Connection of announcement circuit pack to the system
TN798 Processor
Switch Software Applications
Data-CHL
Software
Data-CHL
Software
Data-CHL
Software
Data-CHL
Software
PR-MAINT
DATA
CHL4
CARD-MEM
Network Control
DATA
CHL1
DATA
CHL2
DATA
CHL3
TDM bus
Announcement
Circuit Pack
cydmacps RPY 062397
Issue 1 June 2005
477
Communication Manager Maintenance-Object Repair Procedures
Hardware error log entries
Table 144: ANNOUNCE error log entries
Error
type
Aux
data
Associated test
1 (a) (d)
any
None
257 (d)
any
None
513 (b) (d)
0
None
769 (d)
0
None
1025 (c) (d)
any
None
Alarm
level
On/Off
board
Test to clear value
Notes:
a. Error Type 1: occurred while saving announcements. See Table 145: Aux data error codes
and recommended repair procedures on page 478.
b. Error Type 513: User pressed cancel while announcements were being saved.
c. Error Type 1025: Error occurred while restoring announcements. See Table 145: Aux data
error codes and recommended repair procedures on page 478.
d. Error Types 1, 257, 513, 769, 1025: The port field for this error contained the active PE
complex when the error occurred.
Aux data error codes and recommended repair procedures
Table 145: Aux data error codes and recommended repair procedures
Aux data
Description/ Recommendation
9000
through
9031
CARD-MEM errors
Check and resolve CARD-MEM errors and alarms.
1 of 3
478 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ANNOUNCE (announce)
Table 145: Aux data error codes and recommended repair procedures (continued)
Aux data
Description/ Recommendation
32001
Internal system error.
1. Check other ANNOUNCE errors and take corrective action. If there are no
other ANNOUNCE errors, do the following:
2. Retry the command at 2-minute intervals a maximum of 3 times.
3. If restore announcements fails, escalate the problem.
32002
Announcement circuit pack is in use.
1. Retry the command at 2-minute intervals a maximum of three times.
2. If restore announcements fails, escalate the problem.
32003
Announcement port is in use.
1. Wait for all Announcement ports to become available.
2. Enter save/restore announcements.
32004
There are no announcements recorded on the Announcement Circuit Pack. Save
announcements does not prevent the destroying of the announcement file on
tape [286 systems] or on the memory card [386 systems].
32005
Integrated announcement circuit pack is not present. The Announcement Circuit
Pack is not inserted, or it is defective.
1. Enter list config to check for the presence of the circuit pack in the
system.
2. If the Announcement Circuit Pack is present, use test board PCSS to
check the status of the Announcement Circuit Pack.
32006
Announcement Data Module not available.
1. Use status to check the status of the Announcement Data Module.
32007
Announcement Data Module out of service.
1. Use status to check the status of the Announcement Data Module.
32008
Announcement data is being saved or loaded.
1. Retry the command at 2-minute intervals a maximum of three times.
2. If save/restore announcements fails, escalate the problem.
2 of 3
Issue 1 June 2005
479
Communication Manager Maintenance-Object Repair Procedures
Table 145: Aux data error codes and recommended repair procedures (continued)
Aux data
Description/ Recommendation
32009
Required DATA-CHL is not administered or out of service. (A DATA-CHL is
required to save or restore announcements.)
1. Add a DATA-CHL if none is administered.
2. If a DATA-CHL is administered, use status to check the status of all
DATA-CHLs. At least one DATA-CHL should be in the in-service/idle state.
32010
32013
DATA-CHL is not administered, or it is unavailable. (A DATA-CHL is required to
save or restore announcements.)
1. Add a DATA-CHL if none is administered.
2. If a DATA-CHL is administered, use status to check the status of all
DATA-CHLs. At least one DATA-CHL should be in the in-service/idle state.
32012
Required Announcement Data Module is not administered.
1. Add an Announcement Data Module and repeat the command.
32015
Time of day not set.
1. Set the time of day, and reenter save/restore announcements.
32016
Internal system errors.
Check for any other ANNOUNCE errors and take corrective action.If there are no
other announcements errors, do the following:
1. Retry the command at 2-minute intervals a maximum of three times.
2. If save/restore announcements fails, escalate the problem.
3 of 3
480 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ASAI-ADJ (ASAI Adjunct)
ASAI-ADJ (ASAI Adjunct)
S8700 | 8710 / S8500
Refer to BRI-SET, Various Adjuncts on page 708.
Issue 1 June 2005
481
Communication Manager Maintenance-Object Repair Procedures
ASAI-BD (Multi-Application Platform Board)
S8700 | 8710 / S8500
MO Name in
Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
ASAI-BD
MIN
test board location
ASAI-BD
ASAI-BD
WRN
test board location
ASAI-BD
Maintenance testing of the common circuit pack 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 error conditions that result
in server-controlled testing.
For MAPD board insertion, the switch makes an additional board query if any of the following
circuit packs are inserted:
Circuit Pack
Vintage
TN754
49
TN556
49,
80 or
greater
TN800
any
For any of the previous initial board uplinks, the switch queries the board for administration data
as well as reporting the switch software release and the system type.
For the native mode, the response to the board query downlink messages consists of several
CCMS uplink messages that identify the true board code, vintage, suffix, emulation type, and
number of reserved slots needed.
Note:
Note:
Refer to LAN-BD Maintenance documentation for circuit pack level errors. See
also ASAI-PT on page 494 and ASAI-EPT on page 484 for related line
information. See the following exceptions listed below:
●
Hyperactivity: Currently, the common circuit pack is considered “hyperactive” if the
Service Dispatcher receives 200 uplink messages from the circuit pack in a 10-second
period. Since MAPD has 32 ports, the hyperactivity limit increases to 500 uplink
messages per 10 seconds. The switch issues an alarm when the limit reaches 400;
when it reaches 500 up-link messages in 10 seconds, the board is taken out of service.
482 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ASAI-BD (Multi-Application Platform Board)
●
LED use: The LED Control message 038x requests the Angel to drive the red, amber,
and green LEDs on the face plate of a typical port board on or off. Only the MAPD’s red
LED is controlled by this message. Yellow and green change requests the MAPD
receives from the switch drive LCD behavior rather than LED behavior. The system
continues to send the same LED control messages to the MAPD that the system
currently sends to every other port board. The MAPD handles proper interpretation of
these messages. You should note that the PC on the MAPD and the switch itself control
the LEDs and the LCD on the MAPD.
●
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.
Issue 1 June 2005
483
Communication Manager Maintenance-Object Repair Procedures
ASAI-EPT
S8700 | 8710 / S8500
MO Name in Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
ASAI-EPT
MAJ1
test station extension
ASAI-Adjunct
1. The alarm level for ASAI adjuncts is adminisered using set options. The alarm level can be set
independently for on- and off-board alarms toWARNING, MINOR, or MAJOR for every ASAI
adjunct in the system.
The maintenance strategy for this endpoint MO is built on maintenance facilities offered in the
Avaya ISDN-BRI protocol and in the ASAI adjuncts. Currently there are no facilities in the
protocol that provide for maintenance of set data features.
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:
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.
Error Log Entries and Test to Clear Values
Table 146: ASAI-EPT Error Log Entries
Error
Type
Aux
Data
Associated
Test
Alarm
Level
ASAI-EPT
On/ Off
Board
Test to Clear Value
0 (a)
0
Any
Any
Any
test ASAI-ADJ
2 (b)
2-102
None
257 (c)
Any
BRI Layer 3 query
MAJ
WRN1
OFF
test station ext r 2
test data-module ext r 2
351 (d)
0
none
WRN
OFF
busyout and release station
513 (e)
0
None
769 (f)
0
None
MAJ
OFF
2561 (g)
0
None
1 of 2
484 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ASAI-EPT
Table 146: ASAI-EPT Error Log Entries (continued)
Error
Type
Aux
Data
Associated
Test
25622566 (h)
0
None
2567 (i)
0
None
2568 (j)
0
None
3329 (k)
Any
Signaling Link status (#626)
35843839 (l)
Any
None
3841 (m)
4095
Any
None
Alarm
Level
ASAI-EPT
On/ Off
Board
MAJ
WRN†
OFF
Test to Clear Value
2 of 2
1. Major alarms on this MO may be downgraded to Warning alarms based on the value used in set options.
Notes:
a. Error 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
procedures.
Issue 1 June 2005
485
Communication Manager Maintenance-Object Repair Procedures
b. 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)
17
TM200 (Management Information message
Timer 2)
102
TASAI (ASAI Routing Timer)
The switch sent a message to an endpoint that did not respond in the allotted time. This
may be due to failure of the point-to-point signaling link or because of a problem in the ASAI
adjunct. To repair:
●
Execute test station extension and perform the associated repair procedures for
those tests.
c. 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:
486 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ASAI-EPT
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 Maintenance SAT Commands in Maintenance Commands Reference (03-300191) 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:
1. Execute test station extension and perform the associated repair procedures.
2. Check the health of the adjunct by following the recommended repair procedures of the
manufacturer of the adjunct if the preceding step does not resolve the problem.
d. 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.
e. 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.
f. 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.
g. Error Type 2561: the ASAI-EPT message was not transmitted because the PKT-CTRL
(Packet Control circuit pack) transmit buffers are exhausted. Frequent or persistent
occurrence of these events may indicate a hardware problem or traffic overload on the
PKT-CTRL, the signaling link, or the ASAI adjunct. Follow the repair procedures for the
PKT-CTRL. If these attempts fail, re-engineering the traffic on the PKT-CTRL, signaling
link, or adjunct may be necessary.
Issue 1 June 2005
487
Communication Manager Maintenance-Object Repair Procedures
h. 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
PKT-CTRL, 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
PKT-CTRL, signaling link, or adjunct may be necessary.
i. Error Type 2567: This version of ASAI is not supported. Check the software version that is
running on the ASAI adjunct.
j. Error Type 2568: The adjunct identification is invalid. Check the vendor ID or software
running on the ASAI adjunct.
k. 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-CTRL or the
PKT-BUS, or they have 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 Test #626. The alarm is
retired when the signaling link is re-established to the endpoint or adjunct.
l. 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, then 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, then the ASAI cause value is equal to the error type
minus 3584. The adjunct sent this value to the switch.
Table 147: ASAI cause values on page 489 contains a description of the various ASAI
cause values and recommended system technician actions associated with the cause
value.
m. 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, then 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, then the ASAI cause code is equal to the error type
minus 3840. The endpoint sent this value to the switch.
488 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ASAI-EPT
Table 147: ASAI cause values
Code
Explanation
Recommendation
0
Unrecognized
ASAI Protocol
Operation.
Requested ASAI protocol is not implemented by switch or adjunct.
Aux Data field of error log entry contains protocol identifier for
unrecognized operation.
1. Consult switch and adjunct documentation to determine which
set of operations is supported by switch and the adjunct.
Turning off adjunct operations not implemented by the switch
may resolve the problem.
34
No circuit or
channel
available
A resource on the switch is unavailable for a call. For BRI
endpoints, this cause value is not logged. For ASAI, this condition
means that there are no available trunks for an outgoing call
request.
1. Verify that the adjunct is administered to support the trunk
capabilities of the switch.
2. Investigate trunk-group status by issuing status trunk from
the SAT or by requesting trunk-group queries from the adjunct.
3. Perform trunk diagnostic procedures outlined in this manual.
40
Resources
not available.
No available internal resources to service switch or adjunct request.
Exceeds system transaction capacity for adjunct or switch.
1. May require re-engineering of adjunct services.
1 of 3
Issue 1 June 2005
489
Communication Manager Maintenance-Object Repair Procedures
Table 147: ASAI cause values (continued)
Code
Explanation
Recommendation
50
Requested
facility not
subscribed
Requested facility is implemented, but not administered. Potential
administration problem with endpoint or adjunct.
For BRI endpoints:
1. Verify the switch administration of endpoint using display
station or display data-module.
2. If step 1 does not resolve the problem, refer to the endpoint’s
service manual and verify administration on the endpoint.
For ASAI adjuncts:
1. Display the Customer Optional Features screen (administration
screen) on the switch to determine which ASAI capabilities are
turned on in the switch.
2. Verify that the adjunct is administered to support the identical
capabilities as the switch. If there is a mismatch in the
administered capabilities, then 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
capability not
currently
available
Requested bearer capability is implemented, but not administered.
No B channel is administered. See code 50 above.
63
Service or
option not
available
Requested ASAI capability or resource is not available on the switch
or adjunct. More than one adjunct may be contending for the same
switch resource. Potential administration mismatch between the
resource domains administered on the switch and those
administered on the adjunct.
1. Verify that no overlapping administration of switch resources (for
example, requesting notifications on a single domain by multiple
adjuncts 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
service not
implemented
Requested service not implemented in switch or endpoint.
2 of 3
490 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ASAI-EPT
Table 147: ASAI cause values (continued)
Code
Explanation
Recommendation
69
Requested
facility not
implemented
Requested service not supported in switch or endpoint.
Service or
option not
implemented
Requested service or option (or combination of selected options) is
not supported (implemented) in switch or the adjunct.
Invalid CRV
An invalid CRV was sent by the adjunct.
79
81
1. Consult switch and endpoint documentation to determine
service support.
1. 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.
1. This may indicate a CRV inconsistency between the switch and
the adjunct. See the CallVisor protocol reference manual.
87
Internal switch
audit
There is an inconsistency in switch data records.
1. There is no action needed, since the switch has corrected the
data inconsistency.
3 of 3
System Technician-Demanded Tests:
Descriptions and Error Codes
Investigate errors associated with the circuit pack and port first. Clearing these error codes may
also clear errors against the endpoint. When every circuit pack and port error has been cleared,
but errors still exist against the endpoint, investigate errors in the table below.
Order of Investigation
Signaling Link Status test (#626)
Short Test
Sequence
Long Test
Sequence
X
X
D/ND
Nondestructive
BRI Layer 3 Query Test (#629)
This test is not used by the ASAI-ADJ MO. For information about this test, see BRI-SET,
Various Adjuncts on page 708.
Issue 1 June 2005
491
Communication Manager Maintenance-Object Repair Procedures
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 ASAI type of endpoint is:
●
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).
Table 148: Test #626 Signaling Link Status Test
Error
Code
Test
Result
Description / Recommendation
1139
ABRT
The PN’s packet bus is out-of-service.
1. Follow the repair procedures for the packet bus.
2. After completing step 1, execute test port location long and
review the results of the BRI Port Local LAN Looparound test (#618) to
verify the repair.
1141
ABRT
The PKT-CTRL is out-of-service.
1. Refer to PKT-CTRL maintenance documentation.
S8700
| 8710
S8500:
ABRT
The circuit pack, port, or station may have been busied out.
1. Look in the Error Log for Error Type 18 (busied out) for ASAI-BD,
ASAI-PT, or ASAI-EPT.
1187
2. If this Error Type is present for ASAI-EPT only, use release
station and run the test again.
3. If this Error Type is present for ASAI-PT and ASAI-EPT, use release
port and run the test again.
4. If this Error Type is present for ASAI-BD, ASAI-PT, and ASAI-EPT, use
release board and run the test again.
2012
ABRT
Internal system error
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1 of 2
492 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ASAI-EPT
Table 148: Test #626 Signaling Link Status Test (continued)
Error
Code
Test
Result
Description / Recommendation
1113
FAIL
The signaling link is not “bound” to the adjunct. For ASAI adjuncts this
error indicates that the link is disconnected at Layer 2. Since the signaling
link associated with the endpoint has been identified by administration, the
link is only “unbound” from the endpoint when it is disconnected.
1. Execute status bri-port location and see BRI-PORT
(ISDN-BRI Port) on page 685.
PASS
The signaling link is connected at Layer 2 and “bound” to the ASAI adjunct.
2 of 2
Issue 1 June 2005
493
Communication Manager Maintenance-Object Repair Procedures
ASAI-PT
S8700 | 8710 / S8500
MO Name in Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
ASAI-PT
MAJ1,2
test port location l
ASAI ISDN BRI port
ASAI-PT
WRN
test port location l
ASAI ISDN BRI port
1. The alarm level for ASAI adjunct ports may be administered using set options. The alarm level
can be set independently for on- and off-board alarms toWARNING, MINOR, or MAJOR for every
ASAI adjunct port in the system.
2. All 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 see 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. This port type is administered as an ASAI-BD
on the TN800 circuit pack.
The TN800 circuit pack is a PC-based platform that allows interaction of multiple applications
with Avaya™ Communication Manager. Communication Manager software (native mode)
supports emulation of three types of port MOs on this board. The type of ports to be emulated
are defined by the applications running on the TN800. The TN800 can support up to 32 ports
(time slots) at a time.
The TN800 connects to the switch through a single slot in the backplane, however its width is
not limited to one slot. The number of slots occupied by the TN800 is supplied by the board
during its insertion. The TN800 (Release 5 and higher) is three slots wide. The blank (reserve)
slots are to the left of the functional slot.
In non-native mode the TN800 is recognized as TN556, TN2181, TN754, or TN746 based on
the switch software and the application running on the TN800. In non-native mode only one
type of port MO runs at any time, and the port type depends on the application running on the
TN800. If the TN800 fails diagnostics in non-native mode, the system’s alarm and error logs
would show a failure for the board type the TN800 is emulating.
494 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ASAI-PT
Error Log Entries and Test to Clear Values
Table 149: ASAI-PT Error Log Entries
Error
Type
Aux
Data
Associated
Test
Alarm Level
ASAIPORT
On/Off
Board
Test to Clear Value
0 (a)
0
Any
Any
Any
test port location sh r 1
1 (b)
(a)
Level 1
Status
inquiry
(#621)
MAJ1
OFF
test port location sh r 2
513 (c)
0
none
(b)
ON
1537 (d)
46210
CRC Error
counter
(#623)
MAJ1
OFF
3841 (e)
46208
None
3844 (f)
46223
None
3845 (g)
46211
None
3846 (h)
TEI
None
1. Major and Minor alarms may be downgraded to warning alarms based on the value used in set options.
Notes:
a. Error 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
procedures.
b. Error Type 1: Level 1 Status inquiry fails or when the BRI circuit pack detects that Level 1
has been deactivated on the port. The Aux Data field contains one of the following values:
Blank
This indicates that the Level 1 Status inquiry failed.
32773
This is a message from the ASAI-Line circuit pack indicating Level 1 has been
deactivated.
Refer to the repair procedures for Test #621.
Issue 1 June 2005
495
Communication Manager Maintenance-Object Repair Procedures
c. Error Type 513: The circuit pack is having problems transmitting data to the packet bus,
thus affecting the conveyance of signaling information over the D channel. This error
occurs when the packet bus transmit FIFO buffer overflows. This condition probably
indicates a hardware problem as well. The ASAI-PORT alarm level is MAJOR with aux data
0. Use troubleshooting procedures for both on-board hardware problems and potential
off-board packet-bus problems.
d. Error Type 1537: The port received an invalid frame over the D channel. When the cyclical
redundancy check (CRC) errors exceed 5 within 15 minutes, the port is taken out of service
for 5 seconds. If 5 more CRC errors are received within 15 minutes of the first set of 5
errors, the port is taken out of service for one minute. If 5 more CRC errors are received
within 15 minutes of the last 5, the port is taken out of service for 15 minutes.
This error is most likely due to a problem with the wiring to the set or adjunct, interference
on the wiring due to a noise source, or no termination (an open circuit). It usually does not
indicate a problem with the circuit pack.
●
Check the wiring to the endpoints or the adjunct.
●
If the problem persists, replace the endpoints or adjuncts.
e. 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).
f. 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 Overflow Counter test (#625).
g. Error Type 3845: the BRI Port Local LAN Looparound test (#618) fails. Run the long test
sequence, and note the results of Test #618.
h. Error Type 3846: the TEI (Terminal Endpoint Identifier) 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 make sure that both are using the
same TEI.
496 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ASAI-PT
System Technician-Demanded Tests:
Descriptions and Error Codes
Investigate tests in the order presented. By clearing error codes associated with the ASAI Port
Local LAN Looparound test (#618), you may also clear errors generated from other tests in the
testing sequence.
Table 150: System Technician-Demanded Tests: ASAI-PT
Long Test
Sequence
D/ND1
X
D
X
ND
CRC Error Counter test (#623)
X
ND
Layer 1 Transmission Error Counter test (#624)
X
ND
Receive FIFO Overflow Error Counter test (#625)
X
ND
X
ND
Order of Investigation
Short Test
Sequence
ASAI Port Local LAN Looparound test (#618)
Level 1 Status Inquiry test (#621)
Clear Error Counters (#270)
X
X
1. D = Destructive, ND = Nondestructive
BRI Port Local LAN Loop-Around Test (#618)
This test is destructive.
This test verifies the connectivity of a BRI port across the LAN Bus and executes only if the port
is out-of-service. The test aborts if calls associated with the port are in-progress. Failures of
this test indicate either on-board faults associated with the ASAI-PT hardware on the circuit
pack or problems with the LAN Bus, which is used to form connectivity between the switch and
the ASAI-PT.
The dotted lines in Figure 24: BRI Port Local LAN Loop-Around Path on page 498 show how a
loop-around test is performed across the packet bus for the D channel.
Issue 1 June 2005
497
Communication Manager Maintenance-Object Repair Procedures
Figure 24: BRI Port Local LAN Loop-Around Path
PACKET
INTERFACE
.
.
. . . . . . . . . . . . . . . . . . . .
.
. . . . . . . . . . . . . . . . . . . . .
. .
. .
. .
. . .
.
.
.
.
.
PACKET BUS
BRI LINE
CIRCUIT
PACK
Table 151: Test #618 BRI Port Local LAN Looparound
Error
Code
Test
Result
Description / Recommendation
1015
ABRT
The port is not in the out-of-service state.
1. Display the Port Status screen using status bri-port location
to determine which stations or adjuncts are on this port.
2. Use the extension shown on this screen in status station to
determine whether the station or adjunct is active.
3. If the port is active, wait until it is idle, and use busyout port
location to place it in the out-of-service state and repeat this test.
!
WARNING:
WARNING:
Since the busyout command is destructive, using this
command prior to the port being idle causes every
transaction associated with the ASAI on the port to be torn
down. Note that 3rd-party calls established by an ASAI
adjunct remain connected even though the port is taken
out-of-service.
1 of 2
498 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ASAI-PT
Table 151: Test #618 BRI Port Local LAN Looparound (continued)
Error
Code
Test
Result
Description / Recommendation
1139
ABRT
The PN’s packet bus is out-of-service.
1. Follow the repair procedures for the packet bus.
2. After completing step 1, execute test port long location and
review the results of the BRI Port Local LAN Looparound test to verify
the repair.
1141
ABRT
The PKT-CTRL is out-of-service.
1. Follow the repair procedures for the PKT-CTRL.
2. Enter test port long location and review the results of the BRI
Port Local LAN Looparound test to verify the repair.
2012
ABRT
Internal system error
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
FAIL
The loop-around test has failed.
1. If the test fails repeatedly, attempt to reset the circuit pack if the other
ports on the board are idle. Reset the circuit pack by issuing the
busyout board location and reset board locations.
2. If the test fails again, execute test pkt P on the management
terminal. If this fails, follow the failure procedures the in PKT-BUS
section.
3. If the tests executed in step 2 pass, the problem is local to the BRI
board. Replace the circuit pack.
PASS
The BRI Port Local LAN Looparound test has passed.
2 of 2
Level 1 Status Inquiry Test (#621)
This test determines the state of the transmission facility of a BRI port at the Level 1 (L1) or
physical layer. L1 can be in one of two possible states: Activated 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 adjunct administered on this port. This test
passes if the state of L1 is activated. This test also passes if software has taken this port out of
service.
Issue 1 June 2005
499
Communication Manager Maintenance-Object Repair Procedures
The Deactivated state indicates a problem with the ASAI 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 ASAI 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 in response to a
busyout port location request.
Table 152: Test #621 Level 1 Status Inquiry
Error
Code
Test
Result
Description / Recommendation
1187
ABRT
The board, port, or station may have been busied-out by a technician.
1. Look in the Error Log for Error Type 18 (port busied out) for this port
and ASAI-BD (board busied out). If this error type is present for
ASAI-PT only, then release the port using release port
location and run the test again. If the error is present for both
ASAI-BD and ASAI-PT, then release the board with release port
location and run the test again.
Note:
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.
2. Make sure the terminal is connected.
3. Retry the command at 1-minute intervals up to 5 times.
2000
ABRT
Response was not received from the circuit pack within the allowable time
period.
1. If the test aborts repeatedly up to 5 times, reset the circuit pack using
busyout board location and reset board location.
2. If the test aborts again, replace the circuit pack.
2012
ABRT
Internal system error
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1 of 2
500 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ASAI-PT
Table 152: Test #621 Level 1 Status Inquiry (continued)
Error
Code
Test
Result
Description / Recommendation
3
FAIL
Received a status of Level 1 Deactivated; the port is out of service.
1. Enter status bri-port location to verify that the service state
of the port is out-of-service. If the port is not out of service, escalate
the problem, or else proceed to step 2.
2. If the port has been placed out-of-service using busyout port
location, use release port location. Then enter test
port long location and review the results of Level 1 Status
Inquiry test. If this test still fails, proceed to step 3.
3. After executing test port long location review the results of
every test. Follow the repair procedures for any tests that fail. Verify
repair of the problem by executing test port location and by
determining that the Level 1 Status test passes.
4. If the test continues to fail for this reason, escalate the problem.
PASS
This test indicates that Level 1 is activated, or that software has taken the
port out of service.
2 of 2
CRC Error Counter Test (#623)
This test reads and clears the BRI port’s CRC error counter maintained on the BRI-LINE circuit
pack. This counter is incremented by the circuit pack when it receives a frame from the
endpoint or adjunct with a bad CRC over the D channel. The test passes if the value of the
counter is 0 (the error is cleared). If the counter is not 0, the test fails and the value of the
counter is displayed in the Error Code field. A CRC 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 (for example,
electrical motors or generators), or no termination (open circuit). It usually does not indicate a
problem with the BRI circuit pack. This test is used for verifying the repair of the problem.
Issue 1 June 2005
501
Communication Manager Maintenance-Object Repair Procedures
Table 153: Test #623 CRC Error Counter Test
Error
Code
Test
Result
Description / Recommendation
2000
ABRT
Response was not received from the circuit pack within the allowable time
period.
1. If the test aborts repeatedly up to 5 times, reset the circuit pack using
busyout board location and reset board location.
2. If the test aborts again, replace the circuit pack.
! CAUTION:
CAUTION:
2012
ABRT
Do not leave the circuit pack busied out.
Internal system error
1. Retry the command at 1-minute intervals up to 5 times.
Any
FAIL
The BRI circuit pack is still detecting CRC errors. The Error Code field
contains the value of the counter.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to fail, review the results of other tests in the long
test sequence. Pay particular attention to the results of the Level 1
Status Inquiry test. Follow the repair procedures for any of the
executed tests if they fail; otherwise, proceed to step 3.
3. If the tests for the endpoints or adjunct pass and the CRC error counter
test continues to fail, check the wiring to the endpoints or adjunct. If
the wiring appears to be OK, escalate the problem.
Layer 1 Transmission Error Counter Test (#624)
This test reads and clears the BRI port’s Layer 1 Transmission error counter maintained on the
ASAI 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 adjunct (verify that the wiring meets
the configuration rules defined in DEFINITY® Communications System Generic 1 and Generic
3i Wiring, 555-204-111. It does not indicate a problem with the TN800 circuit pack. This test is
useful for verifying the repair of the problem.
502 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ASAI-PT
Table 154: Test #624 Layer 1 Transmission Error Counter Test
Error
Code
Test
Result
Description / Recommendation
2000
ABRT
Response was not received from the circuit pack within the allowable time
period.
1. If the test aborts repeatedly up to 5 times, reset the circuit pack using
busyout board location and reset board location.
2. If the test aborts again, replace the circuit pack.
2012
ABRT
Internal system error
2100
ABRT
Could not allocate necessary system resources to run test.
1. Retry the command at 1-minute intervals up to 5 times.
Any
FAIL
The TN800 circuit pack is still detecting errors of this type. The Error Code
field contains the value of this counter.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to fail, review the results of other tests in the long
test sequence. Note the results of the Level 1 Status Inquiry test.
Follow the repair procedures for any of the executed tests if they fail.
Otherwise, go to the next step.
3. Replace the circuit pack.
PASS
The Layer 1 Transmission error counter was read correctly and has a value
of 0.
Receive FIFO Error Counter Test (#625)
This test reads and clears the BRI port’s Receive FIFO error counter maintained on the TN800
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 hardware fault is causing the
receive buffers not to be emptied properly. This test is useful for verifying the repair of the
problem.
Issue 1 June 2005
503
Communication Manager Maintenance-Object Repair Procedures
Table 155: Test #625 Receive FIFO Error Counter Test
Error
Code
Test
Result
Description / Recommendation
2000
ABRT
Response was not received from the circuit pack within the allowable time
period.
1. If the test aborts repeatedly up to 5 times, reset the circuit pack using
busyout board location and reset board location.
2. If the test aborts again, replace the circuit pack.
2012
ABRT
Internal system error
2100
ABRT
Could not allocate necessary system resources to run test.
1. Retry the command at 1-minute intervals up to 5 times.
Any
FAIL
The TN800 circuit pack is still detecting errors of this type. The Error Code
field contains the value of this counter.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to fail, review the results of other tests in the long
test sequence. Note the results of the Level 1 Status Inquiry test.
Follow repair procedures for any of the tests that fail. Otherwise, go to
the next step.
3. If the tests for the endpoints or adjunct pass and the Layer 1
Transmission Error Counter test continues to fail, check the wiring to
the endpoints or adjunct.
PASS
The Layer 1 Transmission error counter was read correctly and has a value
of 0.
504 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ASAI-PT
Clear Error Counters Test (#270)
There are various error counters associated with each ASAI-PT. This test clears those counters
and triggers the auditing of layer-3 reinitialization. This test is used only to send messages to
the ASAI-PT and should not abort nor fail. ASAI uses a fixed TEI value of 1.
Table 156: Test #270 Clear Error Counters
Error
Code
Test
Result
Description / Recommendation
Any
ABRT
This test should never abort.
Any
FAIL
This test should never fail.
1. Retry the command at 1-minute intervals up to 5 times.
PASS
The message to clear the error counters of the ASAI-PT has been sent.
Issue 1 June 2005
505
Communication Manager Maintenance-Object Repair Procedures
ASAI-RES (TN800 reserve slot)
Error log entries and tests also apply to E-DIG-RES.
S8700 | 8710 / S8500
MO Name in
Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
ASAI-RES
NONE
NONE
TN800 ASAI reserve slot
E-DIG-RE
NONE
NONE
TN800 DIG reserve slot
There are no tests associated with these MOs. Both the test board and busyout board
commands abort when either is attempted on a reserved slot. An error message indicates the
slot is associated with the circuit pack that the TN800 is emulating, but the requested operation
is not valid.
The TN800 MAPD (Multi-Application Platform) circuit pack connects to the switch through a
single slot in the backplane. The number of slots occupied by the MAPD pack is supplied by the
board when inserted. The TN800 in R5EM is three slots wide. The TN800 requires 2 reserve
slots to its left. The reserve (blank) slots are to left of the functional slot and are place holders
on the switch, and do not have any interaction with the switch.
Each instance of these MOs represents a reserve slot associated with respective circuit pack
mode in which the MAPD is working.
506 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-BCH (ATM B-Channel Trunk)
ATM-BCH (ATM B-Channel Trunk)
S8700 | 8710 / S8500
MO Name in
Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
ATM-BCH
MAJ1
test port location l
ATM B-Channel Trunk
ATM-BCH
MIN
test port location l
ATM B-Channel Trunk
ATM-BCH
WRN
test port location sh
ATM B-Channel Trunk
1. A MAJOR alarm on a trunk means that alarms on these trunks are not downgraded by
set options, and at least 75% of the trunks in this trunk group are alarmed.
ATM-BCH explains how to test and repair TN230x ATM Interface circuit packs (TN2305 and
TN2306) that have ATM B-channel trunks administered for ATM Circuit Emulation Service
(CES).
For additional repair information, see also ATM-DCH (ATM D-Channel Port) on page 522,
ATM-SGRP (ATM Signaling Group) on page 598 and PKT-BUS (Packet Bus) on page 1790.
For maintenance instructions for TN230x circuit packs that are administered as Expansion
Interfaces for ATM network connectivity, see ATM-INTF (TN2305/6) on page 573.
ATM Circuit Emulation Service
Under ATM Circuit Emulation Service, you simulate ISDN-PRI circuits by assigning ATM ports
to signaling groups. Each signaling group represents a PRI circuit, and the ports in the group
represent the D channel and B channels of that circuit. B channels must also be assigned to
ISDN-PRI trunk groups. TN230x circuit packs support up to 248 ports per circuit pack.
Signaling Group Components
B (bearer) channels (ATM-BCH) transmit digitized voice or data, while a separate D channel
(ATM-DCH) handles call-control signaling. One D channel handles signaling for a group of B
channels that combine to form a signaling group (ATM-SGRP).
Issue 1 June 2005
507
Communication Manager Maintenance-Object Repair Procedures
B-Channel Service States
The ISDN specification defines two service state categories for B channels as listed in
Table 157: ATM ISDN service states on page 508.
Table 157: ATM ISDN service states
Category
Description
Service states
In-Service (INS)
B channel is in normal
operating state
Active
A call is connected over
the B channel.
Idle
There is no call on the
B channel.
Out-of-Service/
Far-End (OOS/FE)
The switch has not successfully negotiated B-channel connection as
of yet. Calls cannot be placed or received.
When you first administer a B channel, the switch initializes the
B channel to this state while it tries to negotiate a connection to the far
end. If the request times out with no response from the far end, the
switch leaves the B channel in the OOS/FE state.
Out-of-Service/
Near-End (OOS/NE)
The NPE Crosstalk test has failed, or the trunk is busied out. Calls
cannot be placed or received.
Maintenance/
Far-End (MTC/FE)
A request has timed out with no response from the far end after
signaling is in place and B channels are in service. Calls can be
received but not placed, and stable calls are unaffected.
Maintenance/
Near-End (MTC/NE)
The signaling channel (ISDN-LNK) has been busied out, possibly after
test trunk grp#/mem# long. Calls cannot be placed or received,
but stable calls are unaffected.
Pending states
The switch is waiting for a reply from the far end. Pending service
states remain in effect until the near end receives a response or times
out.
Pending-in-Service
The near end is waiting for a response to a transition-to-service
request.
PendingMaintenance
The near end is waiting for a transition-to-maintenance-service
request (US and other country-protocol-1 systems).
508 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-BCH (ATM B-Channel Trunk)
B-Channel Alarms
The Maintenance/Far-End and Out-Of-Service/Far-End states generate warning alarms
displayed with status trunk grp#/mem#.
Table 158: ATM-BCH alarms by service state
Service state
Alarm1
Possible cause
Possible solution
Out-of-Service/NE
WRN
Trunk busied out
Release the port (release trunk
grp#/mem#).
MIN
NPE Crosstalk test
(#6) failed
Replace ATM circuit pack.
None
ATM circuit pack
lost signal or there
is a circuit pack
problem.
Install circuit pack or cable. Check circuit
pack using procedures in ATM-BCH.
Check far-end switch status.
WRN
Unadministered far
end
Administer the corresponding trunk on
the far-end switch.
WRN
Far-end busied out
Check the status of the far-end switch.
None
Maintenance
message timed out
waiting for reply
Wait 2 minutes after the pending state
clears, and check the service state.
None
ISDN test call in
progress (test
trunk long)
Wait for the test to finish and recheck.
None
System link busied
out
Check link status. Run release link
link#.
WRN
Signaling channel
down for over 90
sec.
See ATM-SGRP (ATM Signaling
Group) on page 598 or ATM-DCH (ATM
D-Channel Port) on page 522.
WRN
Repeated lack of
response to
messages sent to
the far end
Wait. Maintenance software resends
messages periodically. Or run test
trunk grp#/mem# or test
signaling-grp grp#.
WRN
The far-end trunk
is being tested.
Check status of the far-end switch. Wait
for testing to finish.
None
Normal operating
state
Out-of-Service/FE
Pending/
In-Service
Pending/Maint
Maint/NE
Maint/FE
In-Service
1. ATM-BCH alarms; alarms against other MOs may also be present.
Issue 1 June 2005
509
Communication Manager Maintenance-Object Repair Procedures
Error Log Entries and Test to Clear Values
Table 159: ATM-BCH Error Log entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Test to Clear Value
0 (a)
0
Any
Any
Any
test port location
1(b)
Any
None
test port location
18
0
busyout trunk grp/
mbr
release trunk grp/mbr
None
129 (c)
WRN
OFF
130 (d)
test port location
test port location
257(e)
Any
Service State Audit test
(#256)
513(f)
Any
None
769(g)
Any
Service State Audit test
(#256)
test port location
1793
(h)
Any
None
test port location
3073(i)
Any
Service State Audit test
(#256)
test port location
3585(j)
Any
None
none
3841
(k)
Any
None
test port location
WRN
WRN
OFF
OFF
test port location
none
Notes:
a. Error 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
procedures.
b. Error Type 1: the two ends of the ATM trunk do not agree on the ISDN call state. Possible
causes:
●
Received a DISConnect or RELease COMplete message with cause value 52 (outgoing
calls barred)
●
Received a DISConnect or RELease COMplete message with cause value 54 (incoming
calls barred)
510 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-BCH (ATM B-Channel Trunk)
●
Outgoing call renegotiated by the far end to another B channel in the absence of SETUP
message glare
●
Near end attempted a call on a B channel that the far end has marked OOS
When running the short test sequence, pay close attention to the results of the Call State
Audit test (#257).
c. Error Type 129: the far-end switch changed its ISDN service state to either out-of-service
or maintenance. This may be a temporary condition because the far end is testing that
trunk or a hardware problem with the trunk. Outgoing calls may not be allowed over that
trunk.
1. Investigate the trunk’s status (status trunk grp#/mem#).
d. Error Type 130: the circuit pack has been removed or has been insane for more than 11
minutes.
1. Reinsert or replace the circuit pack to clear the error.
e. Error Type 257: SETUP received for a B channel that is in an invalid service state. Service
states may be incompatible at the two ends of the trunk. A normal call was received while
the B channel was MTC/FE, MTC/NE, OOS/FE, or OOS/NE or a test call was received
while the B channel was OOS/FE or OOS/NE.
f. Error Type 513: RELease COMplete message received with cause value 82 (nonexistent
channel). The B channel may not be administered at the far end. The trunk has been
placed in the OOS/FE state.
g. Error Type 769: inconsistent SERVice or SERVice ACKnowledge message. Possible
causes:
●
SERVice or SERVice ACKnowledge message received containing a change status that
is more available than the previously-transmitted SERVice message.
●
Unsolicited SERVice ACKnowledge message received containing a change status that
does not match the current B-channel state.
ISDN-PRI service-state negotiation rules have been violated and may indicate that a
pending service-state audit is failing. The system:
●
cancels the maintenance timer
●
increments the Service State Audit counter
●
attempts a Service State Audit
When running the short test sequence, pay close attention to the results of the Service State
Audit test (#256).
h. Error Type 1793: TN230x circuit pack failed. The maintenance system
●
places the trunk in the OOS/NE state
●
sends a SERvice message to the far end (if possible) containing a change status of OOS
for the B channel
●
returns the trunk to service when the ATM trunk circuit pack reports the failure cleared
Issue 1 June 2005
511
Communication Manager Maintenance-Object Repair Procedures
i. Error Type 3073: Service State Audit attempt failed. See Service State Audit Test (#256) on
page 514. Calls can be received but not placed until the test passes and the trunk state
returns to In-Service.
1. Check the trunk’s status (status trunk grp#/mem#).
j. Error Type 3585: ISDN RESTART message received. Active calls have been dropped.
The following Aux Data values (Error Type 3585 only) below represent the trunk’s ISDN call
state at the time Error 3585 occurred. This information can be useful if users report
dropped calls on the ISDN-PRI trunks.
Aux Data
Description
0
An idle trunk received a restart.
10
An ISDN RESTART from the far end has unexpectedly cleared a call in the
ACTIVE state (call stable, parties talking).
4
7
8
260 263
An ISDN RESTART from the far end has unexpectedly cleared a RINGING call.
1
3
6
9
265
An ISDN RESTART from the far end has unexpectedly cleared a call before the
call entered the RINGING state.
11
12
19
531 267
268
An ISDN RESTART from the far end has unexpectedly cleared a call that was
already in the process of clearing.
If this condition occurs frequently, the far end may be trying to clear trunks that
appear to be in the “hung” state.
k. Error Type 3841: the far end rejected an ATM CES trunk selected by the near end 10 times.
The ATM CES trunk may not be administered on the far end.
1. Get the physical name of the ATM trunk by noting the decimal number in the Aux Data
field.
2. Check administration for the named trunk on the far end.
3. If problems persist, then busyout the ATM trunk to take it out of the hunt group.
The WARNING alarm retires automatically whenever a called endpoint answers an
outgoing or incoming call that uses the alarmed trunk.
512 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-BCH (ATM B-Channel Trunk)
System Technician-Demanded Tests:
Descriptions and Error Codes
Investigate tests in the order presented. When you clear one of the error codes associated with
a given test, you clear errors generated by other tests in the testing sequence.
Table 160: System Technician-Demanded Tests: ATM-BCH
Short
Test
Sequence
Long Test
Sequence
D/ND1
Signaling Link State Check test (#255)
X
X
ND
Service State Audit test (#256)
X
X
ND
Call State Audit test (#257)
X
X
ND
X
ND
Order of Investigation
ISDN Test Call test (#258)
1. D = Destructive, ND = Nondestructive
Signaling Link State Audit Test (#255)
This nondestructive test checks the status of the TN230x ATM-CES Interface circuit pack and
the ATM D-channel (ATM-DCH) trunk, which are both important elements to the health of the
ATM-BCH trunk.
Table 161: Test #255 Signaling Link State Audit Test
Error
Code
Test
Result
Description / Recommendation
None
ABRT
Internal system error
0
ABRT
1114
ABRT
1. Retry the command up to 5 times at 1-minute intervals.
Signaling link in transitional state
1. Retry the command up to 5 times at 1-minute intervals.
1018
ABRT
Maintenance disabled
1. Enable maintenance. Enter y in the Maintenance Tests field on the
change trunk-group screen.
1 of 2
Issue 1 June 2005
513
Communication Manager Maintenance-Object Repair Procedures
Table 161: Test #255 Signaling Link State Audit Test (continued)
Error
Code
Test
Result
Description / Recommendation
4
FAIL
Signaling channel problem
1. Look for errors or alarms against ATM-SGRP (ATM Signaling
Group) on page 598 and ATM-DCH (ATM D-Channel Port) on
page 522.
8
FAIL
TN230x circuit pack failed
1. See ATM-INTF (TN2305/6) on page 573.
PASS
Signaling link OK.
2 of 2
Service State Audit Test (#256)
This test checks the service state of the trunk.
Country protocol 1
If the interface uses country protocol 1 (includes USA), the service-state audit executes in every
trunk service state. It queries the service state on the far end and waits 2 minutes for a reply. If
the first request times out, the service-state audit asks again. If the request times out again, it
logs error 3073 and resends the request every 15 minutes. It places in-service trunks in the
MAINTENANCE/FAR-END state (outgoing calls blocked, incoming calls accepted). Incoming
calls trigger an immediate service-state audit without waiting for the end of a 15-minute cycle.
Any other country protocol
If the interface uses some other country protocol, the service-state audit executes only on
trunks that are in the OUT-OF-SERVICE/FAR-END state. It asks the far-end switch to bring the
trunk back into the IN-SERVICE state and waits 2 minutes for a reply. If the first request times
out, the service-state audit asks again. If the request times out again, it leaves the trunk in the
OUT-OF-SERVICE/FAR-END state and tries again in 1 hour.
Note:
Note:
PASS for this test only means that a message to the far end was successfully
sent.
To check the service state of the ATM-BCH trunk, run status trunk grp#/mem#.
514 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-BCH (ATM B-Channel Trunk)
Table 162: Test #256 Service State Audit Test
Error
Code
Test
Result
Description / Recommendation
1000
ABRT
Needed resources not available, port on a call or initializing
1. Run status trunk grp#/mem#.
2. Check the results of Test #255.
1018
ABRT
Maintenance disabled
1. Enable maintenance by entering y in the Maintenance Tests field on
the change trunk-group screen.
1113
ABRT
Signaling link failed
1. Run status trunk grp#/mem#.
2. Check the results of Test #255.
3. See ATM-SGRP (ATM Signaling Group) on page 598.
1114
ABRT
Signaling link in transitional state
1. Retry the command up to 5 times at 1-minute intervals.
1116
ABRT
Trunk not in Out-of-Service/Far-end state and country protocol other than 1
1117
ABRT
Service-state audit message outstanding
1. Wait 2 minutes, then try again.
2100
ABRT
Could not allocate needed resources
1. Retry the command up to 5 times at 1-minute intervals.
1113
FAIL
Signaling link failed
1. See ATM-SGRP (ATM Signaling Group) on page 598 and ISDN-PLK
(ISDN-PRI Signaling Link Port) on page 1423.
FAIL
Internal system error
1. Retry the command up to 5 times at 1-minute intervals.
PASS
PASS
1. Wait 4 minutes, then check the Error Log for any new Error Type 3073.
●
If there are none, both sides of the ISDN connection agree on the
service state. The negotiation succeeded.
●
If there is a new 3073 error, then the negotiation failed (the request
timed out).
Issue 1 June 2005
515
Communication Manager Maintenance-Object Repair Procedures
Call State Audit Test (#257)
This test audits the internal call state by asking the far-end switch for the ISDN call state. The
test is particularly useful when you are trying to clear a hung call. If the internal call state on the
near end differs from that on the far end, the call is torn down.
The ISDN specification allows up to 2 minutes for a reply. If a reply is not received within the 2
minute window, the test logs a protocol time-out violation against the associated signaling
channel (ATM-DCH, Error Type 1).
Note:
Note:
PASS simply means that an appropriate message was composed and sent to the
far-end switch.
Table 163: Test #257 Call State Audit Test
Error
Code
Test
Result
Description / Recommendation
1018
ABRT
Maintenance disabled
1. Enable maintenance by entering y in the Maintenance Tests field on
the change trunk-group screen.
1019
ABRT
Audit already in progress
1. Wait 2 minutes, and try again.
1113
ABRT
Signaling link failed
1. Check the results of Test #255 (Signaling Link State check).
1114
ABRT
Signaling link in transitional state
1. Retry the command up to 5 times at 1-minute intervals.
1116
ABRT
Trunk out-of-service
1. Check the trunk service state (status trunk grp#/mem#).
2100
ABRT
Could not allocate needed resources
1. Retry the command up to 5 times at 1-minute intervals.
FAIL
Internal system error
1. Retry the command up to 5 times at 1-minute intervals.
PASS
PASS
1. Wait 4 minutes, then check the Error Log for call-state mismatches. If
a call state mismatch is found, the call is torn down.
516 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-BCH (ATM B-Channel Trunk)
ISDN Test Call Test (#258)
This nondestructive test performs a far-end loop-around test over an ATM-BCH trunk if:
●
The trunk is IN-SERVICE, MAINTENANCE/NEAR-END, or OUT-OF-SERVICE/
NEAR-END.
●
No calls are active on the trunk.
●
The system uses country protocol 1 (including US), or the far end has loop-around
capability.
The test sets up a call to a far-end switch over the ATM-BCH trunk. Then the digital port on a
TN711D Maintenance/Test circuit pack sends a bit pattern to the far end and back. If the
received pattern matches that sent, the test passes. If there are differences, it fails.
Synchronous Test Calls
You can initiate a synchronous outgoing test call (including a test call for ISDN-PRI trunks) with
these commands:
●
test trunk grp#/mem# long (repeat#)
●
test board location long (repeat#)
●
test port location long (repeat#)
Table 164: Test #258 ISDN Test Call
Error
Code
Test
Result
Description / Recommendation
4
ABRT
Signaling channel problem
1. Look for errors or alarms against ATM-SGRP (ATM Signaling
Group) on page 598 and ATM-DCH (ATM D-Channel Port) on
page 522.
8
ABRT
TN230x circuit-pack problem
1. See ATM-INTF (TN2305/6) on page 573.
1004
ABRT
B channel is active.
1. See if a call is active. Run status trunk grp#/mem#.
2. If the service state is In-Service/Idle, retry the test.
1005
ABRT
Bad configuration (for example, no Maintenance/Test circuit pack)
1. Make sure that the Maintenance/Test circuit pack is inserted.
2. Repeat the test.
1 of 5
Issue 1 June 2005
517
Communication Manager Maintenance-Object Repair Procedures
Table 164: Test #258 ISDN Test Call (continued)
Error
Code
Test
Result
Description / Recommendation
1018
ABRT
Test call disabled
1. Set the Maintenance field on the Trunk Group screen to y.
1020
ABRT
TN230x circuit-pack problem
1. See ATM-INTF (TN2305/6) on page 573.
1024
ABRT
Maintenance/Test digital port active
1. Wait until amber and green LEDs on the Maintenance/Test circuit pack
are OFF.
2. Rerun the test.
3. If the problem persists, see M/T-DIG (Maintenance/Test Digital Port) on
page 1709.
1113
ABRT
Signaling link failed
1. Check the results of Test #255 (Signaling Link State Check test).
1116
ABRT
Switch could not change the service state
1. See if calls are active. Run status trunk grp#/mem#.
2. If a call is active, proceed as for Error Code 1119.
If not, check the Error and Alarm Logs and see ATM-TRK (Circuit
Emulation Service Circuit Pack) on page 617.
1117
ABRT
ISDN service message outstanding
1. Wait 2 minutes. Then try again.
1118
ABRT
Far-end not administered
1. Check the administration of the far end of the ATM trunk. Run status
trunk grp#/mem#.
2. Try the test again.
1119
ABRT
Test call aborted, normal call attempted
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.
2 of 5
518 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-BCH (ATM B-Channel Trunk)
Table 164: Test #258 ISDN Test Call (continued)
Error
Code
Test
Result
Description / Recommendation
1120
ABRT
Trunk OUT-OF-SERVICE/FAR-END
3. Try to change the service state via Test #256 (Service State Audit test).
4. Try the test again.
1122
ABRT
No test-line number for the far-end switch
1. Check the Trunk Group screen.
1123
ABRT
No Feature Access Code administration for this Facility test
1. Check the Dial Plan and Feature Administration forms.
2000
2012
None
ABRT
2035
ABRT
Internal system error
1. Retry the command up to 5 times at 1-minute intervals.
Call timed out
1. Wait 1 minute, and try again.
2036
–
2037
ABRT
2038
–
2039
ABRT
Internal system error
1. Retry the command up to 5 times at 1-minute intervals.
Problem reading test data
1. Wait 1 minute, and then try again.
2. If the test aborts again, there is a serious internal problem.
2040
ABRT
Internal system error
1. Retry the command up to 5 times at 1-minute intervals.
2041
ABRT
Call timed out
1. Wait 1 minute, and try again.
2066
ABRT
Could not establish test call
1. Retry the command up to 5 times at 1-minute intervals.
2067
ABRT
Call timed out
1. Wait 1 minute, and try again.
3 of 5
Issue 1 June 2005
519
Communication Manager Maintenance-Object Repair Procedures
Table 164: Test #258 ISDN Test Call (continued)
Error
Code
Test
Result
Description / Recommendation
2074
ABRT
Bit and Block Error query failed
1. Retry the command up to 5 times at 1-minute intervals.
2. If the test continues to abort, there may be a serious internal problem in
the Maintenance/Test Digital port. See M/T-DIG (Maintenance/Test
Digital Port) on page 1709.
2075
ABRT
Internal system error
1. Retry the command up to 5 times at 1-minute intervals.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
2201
–
2205
ABRT
2206
ABRT
Internal system error
1. Retry the command up to 5 times at 1-minute intervals.
Could not allocate needed resources
1. Retry the command at 1-minute intervals up to 5 times.
2208
ABRT
Internal system error
1. Retry the command at 1-minute intervals up to 5 times.
2209
–
2210
ABRT
2211
ABRT
Could not allocate needed resources
1. Follow recommendations for ABORT code 2100.
Internal system error.
1. Retry the command at 1-minute intervals up to 5 times.
2212
ABRT
Call terminated by unexpected disconnect
1. Wait 1 minute and then try again.
2213
ABRT
Call timed out
1. Wait 1 minute, and try again.
2214
ABRT
Call terminated by unexpected disconnect
1. Wait 1 minute and then try again.
2215
–
2219
ABRT
Internal system error
1. Retry the command at 1-minute intervals up to 5 times.
4 of 5
520 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-BCH (ATM B-Channel Trunk)
Table 164: Test #258 ISDN Test Call (continued)
Error
Code
Test
Result
Description / Recommendation
2220
ABRT
Call terminated prematurely
1. Wait 1 minute, and try again.
2221
–
2226
ABRT
2227
ABRT
Internal system error
1. Retry the command at 1-minute intervals up to 5 times.
Could not allocate needed resources
1. Retry the command at 1-minute intervals up to 5 times.
2042
FAIL
Test data corrupt
PASS
Test pattern intact. If the synchronous test call was performed (long test
sequence), the communications path is operating properly.
5 of 5
Issue 1 June 2005
521
Communication Manager Maintenance-Object Repair Procedures
ATM-DCH (ATM D-Channel Port)
S8700 | 8710 / S8500
MO Name in
Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
ATM-DCH
MIN
test port location l
ATM D-Channel
ATM-DCH
WRN
test port location sh
ATM D-Channel
Note:
TN230x circuit packs are not interchangeable. Always replace an ATM circuit
pack with the same type.
Note:
ATM-DCH uses the existing ISDN-PLK or D-channel maintenance strategy with modifications.
The ATM circuit pack can be administered for up to 8 Circuit Emulation Service (CES) or
signaling groups, each with its own D channel, as opposed to one D channel for an entire DS1
circuit pack.
Note:
Due to the dual personalities and the number of D channels that the ATM board
can possess, the in-line errors and signaling port LAN loopback test has been
moved to the MO ATM-TRK (Circuit Emulation Service Circuit Pack) on
page 617. When an in-line error is sent due to packet-bus errors, the ATM circuit
pack MO receives the error, not ATM-DCH.
Note:
The D-channel ISDN-PRI interface is emulated for ATM-CES and uses out-of-band signaling to
transmit control messages between two endpoints. User information or bearer channels (B
channels) carry digitized voice and digital data and are assigned to DS1 ISDN trunks or PRI
endpoints. Call-control signaling for the B channels is combined and carried over the separate
ISDN-PRI Signaling Link port D channel.
Problems with ATM-DCH affects every associated B channel, since call-control signaling cannot
reach the far-end switch or terminal adapter. Stable calls can remain operational, but no new
calls can be made. In turn, ATM-DCH depends on the:
●
TN230X ATM Trunk circuit pack where it resides
●
Packet bus that provides the link to the processor
When working ATM-DCH alarms or errors, also investigate
●
ATM-TRK (Circuit Emulation Service Circuit Pack) on page 617
●
PKT-BUS (Packet Bus) on page 1790
522 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-DCH (ATM D-Channel Port)
Hardware Error Log Entries and Test to Clear Values
Table 165: ATM D-channel Error Log entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Test to Clear Value
0 (a)
0
Any
Any
Any
test port location
18 (b)
0
busyout port
location
WRN
OFF
release port location
130 (c)
None
WRN
ON
test port location
1793 (d)
Signaling Link Board
check (#643)
test board location l
Notes:
a. Error 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
procedures.
b. Error Type 18: D channel busied out; no calls possible over this D channel.
c. Error Type 130: circuit pack removed or has been insane for more than 11 minutes. To
clear the error, reinsert or replace the circuit pack.
d. Error Type 1793: ATM Trunk circuit pack failed the Signaling Link Board check (#643).
Resolve any ATM-TRK errors in the Error Log.
System Technician-Demanded Tests:
Descriptions and Error Codes
The command to test the ATM-DCH MO is test port location, where location is for
ports 9-32.
Table 166: System Technician-Demanded Tests: ATM-DCH
Order of Investigation
Signaling Link Board check
(#643)
Short Test
Sequence
X
Long Test
Sequence
X
D/ND
Nondestructive
Issue 1 June 2005
523
Communication Manager Maintenance-Object Repair Procedures
Signaling Link Board Check (#643)
This nondestructive test checks the health of the ATM TN230X trunk circuit pack’s hardware.
The test runs on a periodic or scheduled basis, during initialization testing, and upon demand.
Note:
The board-level maintenance is handled independently of the ATM-CES
signaling link maintenance, raising the possibility of inconsistent states.
Note:
Error
Code
Test
Result
Description / Recommendation
ABRT
Internal system error
1. Retry the command at 1-minute intervals up to 5 times.
8
FAIL
The TN230X circuit pack is not in-service.
1. Check the Error Log for ATM-TRK errors and resolve any using
ATM-TRK (Circuit Emulation Service Circuit Pack) on page 617.
PASS
The ATM TN230X circuit pack is in-service.
524 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
ATM-EI (Expansion Interface Circuit Pack)
S8700 MC
MO Name in Alarm Log
Alarm
Level
Initial Command to
Run
Full Name of MO
ATM-EI
MAJ
test board location
ATM Expansion Interface
circuit pack
ATM-EI
MIN
test board location
ATM Expansion Interface
circuit pack
ATM-EI
WRN
test board location
ATM Expansion Interface
circuit pack
ATM-EI covers the ATM circuit pack administered as an Expansion Interface (ATM-EI) for ATM
Port-Network Connectivity (ATM PNC). The ATM-EI provides PNC between a S8700
Multi-Connect server and every PN through the ATM switch.
The circuit packs listed in Table 167: ATM-EI circuit packs for S8700 Multi-Connect on
page 525 are ATM-EI boards if they are administered to support ATM Port Network Connectivity
(ATM PNC) for S8700 MC.
Table 167: ATM-EI circuit packs for S8700 Multi-Connect
Note:
Note:
Circuit pack
Fiber
Echo cancellation
TN2305
Multimode
Y
TN2306
Single mode
Y
Note:
TN230x circuit packs are not interchangeable. Always replace an ATM circuit
pack with the same type.
Note:
ATM switch maintenance is not covered in this section. When S8700
Multi-Connect system maintenance software suspects the ATM switch
connections, it raises appropriate Communication Manager alarms.
To clear any ATM switch faults, refer to the particular ATM switch’s
documentation.
Issue 1 June 2005
525
Communication Manager Maintenance-Object Repair Procedures
LEDs
The ATM Interface circuit pack has three LEDs:
●
Red indicates some alarm condition.
●
Green indicates maintenance testing in progress.
●
Amber provides useful visual information regarding the operating mode of the ATM-EI and
possible error conditions.
The possible LED states are in Table 168.
Table 168: ATM Interface LED codes
LED
LED Status
Condition
Red
Steady on
Board is not healthy
Never on
Normal conditions
Red
and
Green
Red LED solid on
Green LED 200 msec on; 200 msec off
Board is in the processes of booting
Green
Steady on1
Maintenance is running tests on the
board
100 msec on - 100 msec off
No links to the board
Amber
100 msec on -100 msec off
Fiber Loss of Signal (LOS), LOF,
MS_RDI, MS_AIS, LCD, HP_RDI,
HP_AIS, LOP, PSC
Amber
500 msec on; 500 msec off
Signal to the ATM switch is down
Amber
2 sec on; 0.2 sec off
ATM-EI is Expansion Archangel (EAA)
Amber
Steady on
ATM-EI active (Center Stage Switch PN)
Amber
Never on
ATM-EI standby
1. The green LED flashes between tests.
526 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
ATM-EI-Related Commands
The following commands can be helpful in resolving ATM-EI problems:
add atm pnc
list measurements atm
busyout/release atm pnc
remove atm pnc
busyout/release board
reset board
change atm pnc (pnc duplication)
status atm pnc
display atm pnc
status cabinet
list atm oam-statistics
status port-network
list atm pnc
test board
Replacing an ATM-EI Circuit Pack
Standard Reliability
1. Enter busyout atm pn# (this is service-affecting) at the SAT.
2. Replace the ATM PNC circuit pack, and reconnect the fiber.
3. Enter release atm pnc.
4. Wait 2½ minutes for board insertion.
5. Enter list sys-link to verify that the links are up.
6. Enter test board location, and verify that every test passes.
Duplex or High Reliability
There is 1 ATM-EI circuit pack in each PN.
1. Enter busyout atm pnc # at the SAT.
Note:
Note:
If the ATM-EI is in a PN, this is service-affecting.
2. Replace the circuit pack.
3. Enter release atm pnc.
4. Wait 2½ minutes for board insertion.
5. Enter list sys-link to verify that the links are up.
6. Enter test board location, and verify that every test passes.
Issue 1 June 2005
527
Communication Manager Maintenance-Object Repair Procedures
Critical Reliability
There are 2 ATM-EI circuit packs in each PN.
1. Enter status pnc at the SAT. If the board is on the active side, enter reset pnc
interchange to switch the active ATM-EI board to the standby side.
2. Enter busyout pnc-standby.
3. Enter busyout atm pnc # a-pnc or b-pnc.
4. Replace the circuit pack.
5. Enter release atm pnc #.
6. Enter release pnc-standby.
7. Wait 2½ minutes for board insertion.
8. Enter test board location, and verify that every test passes.
Basic ATM PNC Administration
Note:
This section contains basic administration information only. Refer to ATM
Installation, Upgrades, and Administration using Avaya Communication Manager,
555-233-124, for more detailed information.
Note:
ATM PNC connections involve administering
●
1 ATM-EI board in each PN (standard, duplex, or high reliability)
●
2 ATM-EI boards in each PN (critical reliability)
Adding ATM PNC Connections
Standard, Duplex or High Reliability
1. If the ATM-EI circuit pack is absent or if the circuit pack is present but in a PN, use the
change circuit-pack command to add circuit pack translations.
2. Enter add atm pnc n (connection number), and administer the circuit pack’s location and
its ATM address.
Critical Reliability
1. Enter change system-parameters duplication, and change the Enable Operation
of PNC Duplication field to n.
2. If the ATM-EI circuit pack is absent or is present but in a PN that does not yet have PNC
connectivity to it, use the change circuit-pack command to add circuit pack translation
for the missing circuit pack.
528 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
3. Enter add atm pnc n (connection number), and administer the circuit pack location and
ATM address.
4. Enter change system-parameters duplication, and change the Enable Operation
of PNC Duplication field to y.
Removing ATM PNC Connections
Standard, Duplex or High Reliability
Note:
Note:
These systems are not equipped with PNC duplication.
1. Enter busyout atm pnc n (connection number).
2. Enter remove atm pnc n (connection number).
Critical Reliability
1. Enter status pnc, and ensure that the A-PNC is active.
If not, request a PNC interchange using the reset pnc interchange command.
2. Enter busyout pnc-standby.
3. Enter change system-parameters duplication, and change the Enable Operation
of PNC Duplication field to n.
4. Enter busyout atm pnc n (PN’s number).
5. Enter remove atm pnc n (PN’s number) to remove both ATM-EI boards, or enter change
atm pnc to remove the B-side ATM-EI board.
6. Enter change system-parameters duplication, and change the Enable Operation
of PNC Duplication field to y.
Changing Circuit Pack Location or ATM Address
Standard, Duplex or High Reliability
Note:
Note:
These systems are not equipped with PNC duplication.
1. Remove the ATM PNC connection (see Removing ATM PNC Connections on page 529).
2. Add an ATM PNC connection (see Adding ATM PNC Connections on page 528).
A-side ATM-EI—Critical Reliability
1. Remove the ATM PNC connection (see Removing ATM PNC Connections on page 529).
2. Add an ATM PNC connection (see Adding ATM PNC Connections on page 528).
Issue 1 June 2005
529
Communication Manager Maintenance-Object Repair Procedures
B-side ATM-EI—Critical Reliability
1. Enter status pnc, and ensure that the A-PNC is active.
If not, request a pnc interchange using reset pnc interchange.
2. Enter busyout pnc-standby.
3. Enter list config carrier, and verify that an ATM circuit pack is assigned for the new
location. If not, add the ATM circuit pack’s translations.
4. Enter busyout atm pnc n (connection number) b-pnc.
5. Enter change atm pnc n (connection number) and change circuit pack location for the B
side.
6. Enter release pnc-standby.
Changing ATM Address of Standby
ATM PNC EI, Critical Reliability
1. Enter busy pnc-standby.
2. Enter change atm pnc n (connection number), and change the ATM address for the
standby side.
3. Enter release pnc-standby.
Error Log Entries and Test to Clear Values
Table 169: ATM-EI Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Test to Clear Value
0 (a)
0
Any
Any
Any
test board location
None
MIN
ON
2 (b)
18 (c)
0
busyout board
location
WRN
OFF
23 (d)
0
None
WRN
OFF
125 (e)
None
MIN
ON
131 (f)
None
MIN
ON
Expansion Interface
Control Channel test
(#316)
MAJ
ON
257-259
(g)
Any
release board location
test board location r 2
1 of 3
530 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Table 169: ATM-EI Error Log Entries (continued)
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Test to Clear Value
513 (h)
Any
ATM Crosstalk test
(#1298)
MIN
ON
test board long
location
769 (i)
34
35
ATM Board Error
Query (1259)
WRN
OFF
test board location
770 (i)
31
ATM Board Error
Query (#1259)
WRN
OFF
test board location
771 (i)
26
ATM Board Error
Query (#1259)
WRN
OFF
test board location
1024–
1151 (j)
Any
None
WRN
MIN
ON
test board location
1153 (k)
None
WRN
ON
test board location
1281 (l)
ATM Board Error
Query (1259)
MAJ
OFF
test board location r 1
1537
(m)
12
None
MIN
ON
1538 (n)
0
None
MIN
ON
1793 (o)
13
None
MIN
ON
2049 (p)
15
None
MIN
OFF
test board location r 4
2050 (p)
Expansion Interface
Lock Query (#304)
MIN
OFF
test board location r 4
2305 (q)
None
MIN
ON
2309 (q)
Packet interface test
(#598)
MIN
ON
test board location r 2
2561 (r)
Expansion Interface
2-way Transmission
test (#241)
MAJ
OFF
test board location r 3
2817 (s)
Any
ATM Board DSP test
(#1293)
MIN
ON
test board location
2818 (s)
Any
None
MIN
ON
test board location
3329 (t)
3
LANHO critical error
MAJ
OFF
2 of 3
Issue 1 June 2005
531
Communication Manager Maintenance-Object Repair Procedures
Table 169: ATM-EI Error Log Entries (continued)
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Test to Clear Value
3585 (u)
ATM Framer
Looparound (#1260)
MAJ
ON
test board location l
3586 (u)
ATM Framer
Looparound (#1260)
MAJ
ON
test board location l
3841 (v)
3842
(w)
None
3843 (x)
3999 (y)
Any
None
Any (z)
32767
None
3 of 3
Notes:
a. Error 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
procedures.
b. Error Type 2: The on-board DUART chip failed. This results in communication failure
between the PN’s Maintenance board and the ATM-EI board. The Maintenance board
should have a red LED lit, because the link to the ATM-EI is down in this PN.
1. Reset the board with reset board location.
2. If the board does not recover, replace the board.
c. Error Type 18: The ATM-EI circuit pack has been busied out.
1. Release the circuit pack (release board location).
d. Error Type 23: An ATM-EI circuit pack has been administered with the add atm pnc n
command, but the circuit pack has not been inserted into the system.
1. Insert an ATM-EI circuit pack at this location.
e. Error Type 125: A wrong circuit pack is located in the slot where the ATM-EI circuit pack is
logically administered.
1. Either remove the wrong circuit pack and insert the ATM-EI circuit pack or remove the
ATM-EI administration (see Basic ATM PNC Administration on page 528).
2. Remove the ATM-INTF administration and re-administer the slot (change circuit-pack) to
match the circuit-pack that is physically present in this slot.
532 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
f. Error Type 131: An ATM-EI circuit pack has been removed from the slot for 5 minutes.
1. Insert the ATM-EI circuit pack into its administered slot.
2. Another way to resolve or prevent this alarm is to remove the ATM-EI administration (see
Basic ATM PNC Administration on page 528), then remove the ATM-INTF administration
(change circuit-pack).
It is possible that the ATM-EI could be held in reset by the PN’s Maintenance board and is
not inserted in the system.
3. Try issuing test maint P long on the maintenance board in the same PN.
g. Error Type 257: Expansion Interface Control Channel test (#316) failed (board cannot
communicate on the TDM bus control channel). Follow the suggested test procedures.
Error Type 258: The archangel is out of sequence (Aux Data indicates angel number).
Error type 259: The expansion archangel link (EAL) to the active ATM-EI board is down.
See SYS-LINK (System Links) on page 2175.
h. Error Type 513: The ATM Crosstalk test failed. The board is either writing to or reading
from a TDM time slot that is not allocated to the board.
1. Test the board (test board location), and follow the test procedures suggested for
this test. In random tests of a single DSP during low or high traffic, the same DSP can be
tested more than once.
i. Error Types 769 and 770: are board-degraded alarm errors that result when the ATM
switch is sending corrupted cells or excessive AAL/LAPD retransmissions (off-board ATM
cell corruption errors). These errors indicate the detection of a problem in handling ATM
cells that are received from the fiber interface.
Aux Data for these Error Types:
Error Type
Aux Data
Description
769
34
Excessive AAL-5 retransmission requests
769
35
Excessive LAPD retransmission requests
770
25
Uncorrectable ATM cell headers – threshold
771
26
VPI, VCI pair unknown
The problem is most likely not on the ATM-EI circuit pack reporting the errors, but it could be
due to one or more of the following reasons:
●
The fiber is not snugly connected to either the board or the ATM switch.
●
The PN’s packet bus is corrupting the cells. See PKT-BUS (Packet Bus) on page 1790
(Aux Data 35 only).
●
The fiber between the ATM switch and the ATM-EI is too long (greater than 2 km for
multimode fiber). Use loopback to see if the fiber is corrupting the cells.
Issue 1 June 2005
533
Communication Manager Maintenance-Object Repair Procedures
●
Some other ATM-EI board is not receiving the cells properly.
●
The intervening ATM switch is dropping the ATM cells due to a shortage of bandwidth, or
S8700 MC is using more than the subscribed bandwidth.
Error Type 771: The ATM switch is sending cells with unknown VPI and VCI address
(wrong connection).
1. Ensure that the ATM-EI board address on the ATM switch matches the ATM-EI (ATM)
address on the S8700 Multi-Connect side.
j. Error Types 1024-1151: These errors represent problems detected by the ATM-EI board in
response to SETUP and ADDPARTY requests from software.
●
The Error Types and descriptions are in Table 170: ATM Error Types 1024 - 1151 on
page 534.
●
Aux Data values represent PN and angel numbers and are in Table 171: Error Type
1024-1151 Aux Data values (XXYYY) converted to slot number on page 536.
Table 170: ATM Error Types 1024 - 1151
Error
Type
Description
General problem
1024
Next node unreachable
1056
DTL Transit not my node ID
ATM protocol stack on
ATM-EI3 circuit pack
1 of 3
534 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Table 170: ATM Error Types 1024 - 1151 (continued)
Error
Type
Description
General problem
1088
1104
ATM-EI circuit pack received a request with an
invalid connection identifier.
1089
1105
ATM-EI circuit pack received a request with a
reference to an unknown VC token.
1090
1106
ATM-EI circuit pack did not have enough
resources (memory) for the requested operation.
1091
1107
Internal failure in the local protocol stack. This can
occur when the connection to the ATM switch
failed, perhaps because the:
Firmware-detected problems
on the ATM-EI circuit pack.
Note: Error Types 1088–1103
are reported by the board that
is originating the connection.
Error Types 1104–1119 are
reported by the board that is
terminating the connection. In
most cases, when the
terminating board reports one
of these errors, the originating
board also reports an
ATM-NTWK error for the same
event (usually with Error Type
21).
●
ATM switch rebooted
●
fiber between the ATM switch and the
ATM-EI circuit pack disconnected
1092
1108
ATM-EI circuit pack received a request for which
the referenced VC was in the wrong call state.
1093
1109
ATM-EI circuit pack received a request for which
the VPI/VCI pair was invalid or out of range.
1094
1110
ATM-EI circuit pack received a request to add a
party to an existing VC. The add party request
failed, and a retry was not possible.
1095
1111
ATM-EI circuit pack in link recovery after the lower
ATM layer (Q.SAAL portion of the protocol stack)
failed. This can occur when the connection to the
ATM switch failed, perhaps because the:
● ATM switch rebooted
● fiber between the ATM switch and the
ATM-EI circuit pack disconnected
1096
1112
ATM-EI circuit pack received an error from the
local protocol stack for which no more detailed
cause was specified.
1102
ATM-EI circuit pack asked to create more
connections that it was capable of creating.
1103
ATM-EI circuit pack detected an illegal message
from software.
Check the Error Log for CONN-M proc errors for
more information.
2 of 3
Issue 1 June 2005
535
Communication Manager Maintenance-Object Repair Procedures
Table 170: ATM Error Types 1024 - 1151 (continued)
Error
Type
Description
General problem
1113
Problems detected by the
board terminating the
connection
3 of 3
1. Test the ATM-EI circuit pack (test board location) and investigate further based on
each test’s results. If every test passes, the error was a transient problem.
Aux Data values: For Setup and Add Party connection request failure type, the port-network
and the angel number of the destination ATM-EI circuit pack are logged Aux Data values in
the form XXYYY, where
●
port-network number = XX
●
angel number = YYY
Aux Data values for WSP Setup (XX = WSP number, YYY = location code).
Since you need to know the slot number also, Table 171: Error Type 1024-1151 Aux Data
values (XXYYY) converted to slot number on page 536 converts the Aux Data to slot
numbers.
Table 171: Error Type 1024-1151 Aux Data values (XXYYY) converted to slot number
Slot
Carrier
A
B
C
D
E
Failure type
Failure type
Failure type
Failure type
Failure type
Slot
#
Set
up
Add
Party
WSP
Set
up
Set
up
Add
Party
WSP
Set
up
Set
up
Add
Party
WSP
Set
up
Set
up
Add
Party
WSP
Set
up
Set
up
Add
Party
WSP
Set
up
1
28
528
828
66
566
866
98
598
898
34
534
834
02
502
802
2
29
529
829
67
567
867
99
599
899
35
535
835
03
503
803
3
30
530
830
68
568
868
100
600
900
36
536
836
04
504
804
4
31
531
831
69
569
869
101
601
901
37
537
837
05
505
805
5
56
556
856
70
570
870
102
602
902
38
538
838
06
506
606
6
57
557
857
71
571
871
103
603
903
39
539
839
07
507
607
7
58
558
858
72
572
872
104
604
904
40
540
840
08
508
808
1 of 2
536 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Table 171: Error Type 1024-1151 Aux Data values (XXYYY) converted to slot number
Slot
Carrier
A
B
C
D
E
Failure type
Failure type
Failure type
Failure type
Failure type
Slot
#
Set
up
Add
Party
WSP
Set
up
Set
up
Add
Party
WSP
Set
up
Set
up
Add
Party
WSP
Set
up
Set
up
Add
Party
WSP
Set
up
Set
up
Add
Party
WSP
Set
up
8
59
559
859
73
573
873
105
605
905
41
541
841
09
509
809
9
60
560
860
74
574
874
106
606
906
42
542
842
10
510
810
10
61
561
861
75
575
875
107
607
907
43
543
843
11
511
811
11
62
562
862
76
576
876
108
608
908
44
544
844
12
512
812
12
63
563
863
77
577
877
109
609
909
45
545
845
13
513
813
13
88
588
888
78
578
878
110
610
910
46
546
846
14
514
814
14
89
589
889
79
579
879
111
611
911
47
547
847
15
515
815
15
90
590
890
80
580
880
112
612
912
48
548
848
16
516
816
16
91
591
891
81
581
881
113
613
913
49
549
849
17
517
817
17
92
592
892
82
582
882
114
614
914
50
550
850
18
518
818
18
93
593
893
83
583
883
115
615
915
51
551
851
19
519
819
19
94
594
894
84
584
884
116
616
916
52
552
852
20
520
820
20
95
595
895
85
585
885
117
617
917
53
553
853
21
521
821
21
NA
NA
NA
86
586
886
118
618
918
54
554
854
22
522
822
22
NA
NA
NA
87
587
887
119
619
919
55
555
855
23
523
823
2 of 2
k. Error type 1153: The ATM connection audit found some discrepancy in the firmware’s VC
token numbers and live VCs. The problem is rectified in firmware and no action is needed.
Issue 1 June 2005
537
Communication Manager Maintenance-Object Repair Procedures
l. Error Type 1281: The loss of high-level signal indicating operational problems of equipment
located outside of the circuit pack and the fiber connected to the board. Aux Data values
are listed in Table 172: Error type 1281 Aux Data and repair procedures on page 538.
Table 172: Error type 1281 Aux Data and repair procedures
Aux
Data
Alarm
Description
Repair procedure
15
SYSCLOCK
failed
The board is not locked to the TDM backplane clock signal. This is
probably due to a Tone-Clock problem.
1. Check for TDM-BUS or TONE-BD errors in the Error Log.
2. If no other problems are present, reset the circuit pack (reset
board location)
16
Loss of Signal:
LOS
The fiber is not connected properly to the ATM-EI board or ATM
switch (or to the multiplexer section [MUX] if present).It is possible
that the board transceivers are not functioning properly.
1. Run test board location.
2. If Test #1259 fails, connect a fiber back-to-back in a looped
mode (one strand of fiber connecting the transmit transceiver to
the receive transceiver of the board) and see if the amber LED
flash goes away. If it does the problem is off-board.
3. If the amber LED continues to flash, replace the circuit pack.
17
Loss of Frame:
LOF
The fiber signal cannot obtain or maintain STM-1/OC-3 framing.
1. Try to move the fiber on the ATM switch side to a different port.
This could require administration on the ATM switch.
2. If the problem persists, reset the circuit pack (reset board
location).
18
Multiplexer
Section Alarm
Indication
Signal:
MS_AIS
There is a major problem on the far end (between multiplexer
section [MUX] and the switch) that prohibits the circuit pack from
sending a valid signal.
1. See if the ports at the MUX and/or the ATM switch are
connected snugly.
2. Run test board location.
3. If Test #1259 fails with Error Code 18, connect a fiber
back-to-back in a looped mode (one strand of fiber connecting
the transmit transceiver to the receive transceiver of the board)
and see if the amber LED flash goes away.
4. If it does, the problem is off-board.
5. If the amber LED continues to flash, replace the circuit pack; if
the error persists, escalate the problem.
1 of 3
538 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Table 172: Error type 1281 Aux Data and repair procedures (continued)
Aux
Data
Alarm
Description
Repair procedure
19
Multiplexer
Section
Remote Defect
Indicator:
MS_RDI
The far end is detecting a major problem with the signal that this
board is transmitting.
1. Make sure the ATM switch port (or a MUX port, if present
between ATM switch and the ATM-EI board) is the same as the
ATM-EI circuit pack’s cable interface.
2. Run test board location.
3. If Test #1259 fails with Error Code 19, connect a fiber
back-to-back in a looped mode (one strand of fiber connecting
the transmit transceiver to the receive transceiver of the board)
and see if the amber LED flash goes away.
4. If it does the problem is off-board.
5. If the amber LED continues to flash, replace the circuit pack; if
the error persists, escalate the problem.
20
Loss of pointer:
LOP
ATM framer chip is unable to access the payload part of the signal.
1. Reset the board (reset board location).
2. If the error persists replace the board.
21
Path Signal
Error (PSL)
(STM1/
SONET)
The incoming signal payload is not set up for transmission of ATM
data.
1. Make sure the ATM switch port (or a MUX port, if present
between ATM switch and the ATM-EI board) is the same as the
ATM-EI circuit pack’s cable interface.
22
High-level Path
Alarm
Indication
Signal:
HP_AIS
The payload is invalid.
1. Make sure the ATM switch port (or a MUX port, if present
between ATM switch and the ATM-EI board) is the same as the
ATM-EI circuit pack’s cable interface.
2. Run test board location.
3. If Test #1259 fails with Error Code 22, connect a fiber
back-to-back in a looped mode (one strand of fiber connecting
the transmit transceiver to the receive transceiver of the board)
and see if the amber LED flash goes away.
4. If it does the problem is off-board.
5. If the amber LED continues to flash, replace the circuit pack.
2 of 3
Issue 1 June 2005
539
Communication Manager Maintenance-Object Repair Procedures
Table 172: Error type 1281 Aux Data and repair procedures (continued)
Aux
Data
Alarm
Description
Repair procedure
23
High-level path
Remote defect
Indicator:
HP_RDI
The far end is detecting a major problem with the signal that this
board is transmitting. The transmitted payload is invalid.
1. Make sure the ATM switch port (or a MUX port, if present
between ATM switch and the ATM-EI board) is the same as the
ATM-EI circuit pack’s cable interface.
2. Run test board location. If the Test #1259 fails with Error
Code 23, connect a fiber back-to-back in a looped mode (one
strand of fiber connecting the transmit transceiver to the
receive transceiver of the board) and see if the amber LED
flash goes away.
3. If it does the problem is off-board.
4. If the amber LED continues to flash, replace the circuit pack.
24
Loss of cell
delineation
(LCD)
On board ATM framer chip is not able to frame cells based on the
cell header.
1. Reset the board (reset board location).
2. If the error persists, replace the board.
27
SIGCON_DO
WN ATM
switch high
level signal.
The board cannot communicate with the ATM switch.
1. Busyout the board (busyout board location).
2. Test the board (test board long location).
3. If Test #1260 fails, replace the board.
4. If Test #1260 passes, make sure the ATM address on both the
S8700 Multi-Connect and the ATM switch sides are the same
for this board.
5. If the address is the same, change the port on the ATM switch
side. This could require administration on the ATM switch.
6. If the error is resolved, the problem is on the ATM switch port.
3 of 3
m. Error Type 1537: LAN bus time out. The circuit pack is transmitting a packet larger than
1,024 bytes. Replace the circuit pack.
n. Error Type 1538: A hyperactive ATM-EI circuit pack is generating an abnormal amount of
control messages to the processor. When this error is generated, the system automatically
resets the ATM-EI.
Duplicated PNC?
Then:
Yes
service to the PN is disrupted
No
the system switches to the standby PNC
1. Enter reset board location for this ATM-EI circuit pack.
2. If the same error persists, replace the ATM-EI circuit pack.
540 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
o. Error Type 1793: LANHO transmit FIFO overflow error (the transmit FIFO RAM buffers on
the circuit pack overflowed). This most likely indicates a hardware problem on the circuit
pack, because the speed of the LAN/packet bus is much higher than the speed of the link
connected to the port.
1. Test this ATM-EI circuit pack (test board location).
2. If Test #598 fails again, replace the ATM-EI circuit pack.
p. Error Types 2049 and 2050: The ATM-EI is out of lock with the backplane system clock.
1. Test this ATM-EI circuit pack (test board location).
2. If Test #304 fails, follow the repair procedures suggested for this test.
q. Error Type 2305: Too many parity errors on data received from the LAN/packet bus (could
be due to packet-bus problems).
1. Test the ATM-EI circuit pack (test board location).
2. If Test #598 fails, follow the repair procedures suggested for this test.
3. If the test passes, look for and resolve any PKT-BUS (packet bus) alarms/errors.
4. If there are no PKT-BUS errors and the problem persists, escalate the problem.
Error Type 2309: The packet-interface chip (LANHO) is malfunctioning.
5. Test the ATM-EI circuit pack (test board location).
6. If Test #598 fails, follow the repair procedures suggested for this test.
r. Error Type 2561: ATM-EI 2-way transmission failure (circuit pack is having problems
creating connections to other PNs in the system).
1. Test the ATM-EI circuit pack (test board location).
2. Follow the repair procedures suggested for Test #241.
s. Error Types 2817 and 2818: A DSP test failure detected along the circuit path of the
ATM-EI circuit pack.
Error Type
Description
Aux Data indicates
2817
DSP test failure
The Aux Data field contains the following
information about the failed DSPs:
X is the number of talker DSPs
Y is the number of listener DSPs
Z is the number of echo-cancelling DSPs
2818
One or more DSPs failed
DSP number that has failed
1. Test the ATM-EI circuit pack (test board location).
2. Follow the repair procedures suggested for Test #1258.
Issue 1 June 2005
541
Communication Manager Maintenance-Object Repair Procedures
t. Error Type 3329: The on-board LANHO chip is insane, possibly due to a problem in
packet-bus arbitration, the transmission line frame, or the circuit pack itself. The circuit pack
cannot talk to the packet bus.
If the packet bus is alarmed:
1. Resolve any PKT-BUS errors. The probability of this error being related to a packet-bus
problem increases with the number of other circuit packs using the bus that are also
showing this error.
If the packet bus is not alarmed:
2. Reset the circuit pack (reset board location).
3. If the problem persists, replace the ATM-EI circuit pack.
If the system has a duplicated PNC, and the in-line error received is from an active ATM-EI,
the system switches to the standby PNC.
! CAUTION:
CAUTION:
If the system does not have duplicated PNC, services to the PN could be
disrupted.
u. Error Types 3585 and 3586: (Major board alarm) A failure of critical components involved
in the operation of the circuit pack, and the switch can no longer recognize the circuit pack.
If the system has a duplicated PNC and the in-line error received is from an active ATM-EI,
the system switches to standby PNC.
! CAUTION:
CAUTION:
If the system does not have duplicated PNC, services to the PN could be
disrupted.
Error Type 3585
Aux Data (Error Type 3585 only):
Aux
Data
Description
1
ATM framer failure
2
NCE failed (only from ATM-EIs in PN)
4
TDM_PLD_FAILED
5
DSP_ALL FAILED
6
Receive Network Processor (RNP) failure
7
Transmit Network Processor (TNP) failure
8
MEMORY read/write failure
542 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
1. If the system has duplicated PNC:
a. Test the ATM-EI (test board location l).
b. If Error 3585 is detected again, or if the board is not recognized anymore, replace the
ATM-EI circuit pack.
2. If the system does not have duplicated PNC and the circuit pack is in a PN:
a. Replace the ATM-EI circuit pack.
Error Type 3586: Framer Looparound test (#1260) failed.
Aux Data (Error Code 3586 only):
Aux Data
Description
2
Packet path failed
3
Circuit path failed
4
TDM loop cannot be created
5
Packet loop cannot be created
3. If Error Type 3586 is detected again, replace the circuit pack.
v. Error Type 3841: The board received a message from the switch that it does not recognize,
and the board responded with an inconsistent down link error message. This error does not
affect service, and no action is required.
w. Error Type 3842: The circuit pack received data from the packet bus faster than it could
distribute the data to its endpoint. This circuit pack should be able to recover by itself, and
no action is necessary.
x. Error Type 3843: The firmware on the circuit pack is reporting a resource that is low. This
error does not affect service and no action is required.
y. Error Type 3999: The circuit pack sent a large number of control channel messages to the
switch within a short period of time.
If
Then
Error Type 1538 is also
present
Circuit pack is taken out of service
Error Type 1538 is absent
Circuit pack is not taken out of service, but has generated
50% of the messages necessary to be considered
hyperactive.
This can be normal during heavy traffic.
If the error is logged during light traffic, it can indicate a
problem with the circuit pack or the equipment attached to it.
Issue 1 June 2005
543
Communication Manager Maintenance-Object Repair Procedures
z. Aux Data 32767 for any error log entry indicates that an alarmed ATM-EI was busied out
and then released. When this occurs, existing service-affecting alarms must be preserved.
Typically, every alarm is resolved when the ATM-EI is released. Therefore, the Alarm and
Error Logs must be repopulated with the alarms present at time of busyout. This Aux Data
indicates that existing Error Type and Error Log time stamps are no longer valid because
they were lost when the circuit pack was released.
System Technician-Demanded Tests:
Descriptions and Error Codes
Investigate tests in the order presented. By clearing error codes associated with the Expansion
Interface 2-Way Transmission test (#241), you can also clear errors generated from other tests
in the sequence.
Table 173: System Technician-Demanded Tests: ATM-EI
Order of Investigation
Expansion Interface 2-Way Transmission
test (#241)
Short Test
Sequence
Long Test
Sequence
X
X
ND
X
D
ATM Board Framer Looparound test (#1260)
Reset
Board
Sequence
D/
ND1
Expansion Interface Lock Query test (#304)
X
X
ND
ATM Board Error Query test (#1259)
X
X
ND
ATM Expansion Interface Reset (#1256)
ATM board DSP test(#1293) for TN2305 and
TN2306 circuit packs.
ATM Cross Talk test(#1298) for TN2305 and
TN2306 circuit packs
X
X
X
ND
X
ND
1. D = Destructive, ND = Nondestructive
Note:
D
Note:
To get a better indication of a problem’s location, test both ATM-EI circuit packs
on the associated fiber link, whether the circuit packs are both ATM-EI circuit
packs or not.
544 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Expansion Interface 2-Way Transmission Test (#241)
This test is nondestructive and applies to every ATM-EI, both active and standby. It is run as
part of craft short and long testing, periodic, scheduled, initialization, and error analysis testing.
The test sets up a connection between a Tone-Clock in one cabinet and a Tone Detector in a
separate cabinet and transmits a digital test count between the PNs. The ATM-EIs used to set
up this connection are chosen by maintenance, not call processing. After the connection is
checked for dial-tone, the connection is torn down and re-established in the opposite direction.
For this test, the second ATM-EI can reside in any PN outside the tested ATM-EI’s PN.
Therefore, if the test should fail in either direction, the test is repeated with a different PN, if
available. This aids the fault isolation procedure.
The test results indicate if the test failed in one or both directions. The test aborts if the ATM-EIs
do not exist on both ends (for example, the EIs are not administered correctly). If the test
passes, the TDM and ATM framer interfaces of both ATM-EIs are functioning properly. If the
test fails, a series of tests are run on the board. Figure 25: Expansion Interface 2-Way
Transmit Test #241 PN X and PN Y represent any of 44 possible PNs. on page 545 shows a
schematic of this test.
Figure 25: Expansion Interface 2-Way Transmit Test #241
PN X and PN Y represent any of 44 possible PNs.
TDM bus
(PN X)
ATM
circuit
pack
Tone
clock
ATM
circuit
pack
TDM bus
(PN Y)
Tone
detector
ATM
switch
Tone
detector
PNC mode
Tone
clock
PNC mode
iodf2way AWF 040699
Table 174: Expansion Interface 2-Way Transmission Test (#241)
Error
Code
Test
Result
Description / Recommendation
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1002
ABRT
The system could not allocate time slots for the test. The system could be
under heavy traffic conditions or it can have time slots out of service due
to TDM-BUS errors.
1. If the system has no TDM-BUS errors and is not handling heavy
traffic, retry the command at 1-minute intervals up to 3 times.
1 of 8
Issue 1 June 2005
545
Communication Manager Maintenance-Object Repair Procedures
Table 174: Expansion Interface 2-Way Transmission Test (#241) (continued)
Error
Code
Test
Result
Description / Recommendation
1003
ABRT
The system could not allocate a tone receiver for the test. The system
may be oversized for the number of Tone Detectors present, or some
Tone Detectors may be out of service.
1. Resolve any TTR-LEV errors.
2. Verify that at least one Tone Detector resides in this PN. (Even
without a TTR-LEV error, the tested circuit pack’s PN could be missing
a Tone Detector.)
If missing, the test always aborts for this circuit pack, without harming
the system.
Note:
Note:
A TN2182 Tone-Clock circuit pack in a PN must be of
vintage B or newer. If an earlier vintage resides in a PN,
this test always aborts with this abort code.
3. Resolve any TONE-PT errors.
4. If neither condition exists, retry the command at 1-minute intervals up
to 3 times.
2 of 8
546 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Table 174: Expansion Interface 2-Way Transmission Test (#241) (continued)
Error
Code
Test
Result
Description / Recommendation
1033
ABRT
The test cannot run because either the ATM-EI board is not administered,
or there were no other PNs administered that had its ATM-EI board
in-service.
1. Ensure that the board is administered as ATM PNC Expansion
Interface circuit pack.
2. If the board is administered as ATM-EI circuit pack, then there has
been some change in the ability of the ATM-EI circuit pack in the other
PNs to communicate with the ATM-EI on the other end of its
connection.
3. Using status port x (the port-network number where the board is
administered), see if both ACL and EAL are up to this board. If not,
see the service procedure for SYS-LINK.
4. Check the Error Log for Error Type 1281 with Aux Data 27 (board
cannot talk to the ATM switch). See Table 172: Error type 1281 Aux
Data and repair procedures on page 538 for repair procedures.
5. If present, check both the ATM switch and the Communication
Manager translations for consistent ATM addresses. Reset the board,
and see if the problem resolves.
6. Repeat Test #241. If it continues to abort with this abort code, replace
the board.
1394
ABRT
ABORT
1. See Table 172: Error type 1281 Aux Data and repair procedures on
page 538 (Error Type 1281) with Aux Data 27 (board cannot talk to the
ATM switch), and if present, check both the ATM switch and the
Communication Manager translations for consistent ATM addresses.
2. Reset the board and see if the problem resolves.
3. Repeat the test.
3 of 8
Issue 1 June 2005
547
Communication Manager Maintenance-Object Repair Procedures
Table 174: Expansion Interface 2-Way Transmission Test (#241) (continued)
Error
Code
Test
Result
Description / Recommendation
1395
ABRT
This test cannot run on an ATM-EI circuit pack if it is part of the B-side
PNC and Duplicated PNC is not enabled.
1. If this test needs to run on this ATM-EI circuit pack, enable PNC with
the change system-parameters duplication command.
2. Prevent the system from doing a PNC interchange by executing the
set PNC lock command.
3. Repeat this test.
1413
ABRT
This test requires the use of a Tone-Clock circuit in each of the PNs used
in this test. This abort code indicates that a Tone-Clock circuit is absent
from one of the PNs.
1. Verify that an IPSI or Tone-Clock circuit pack resides in the same PN
as the ATM PNC Expansion Interface circuit pack under test.
2. In ATM PNC configurations, make sure that there is at least one other
PN besides the PN where the ATM-EI circuit pack under test resides
that contains a Tone-Clock circuit.
1414
ABRT
The active Tone-Clock circuit in one of the PNs being used for the test has
a MAJOR or MINOR alarm logged against it.
1. Enter display alarms and resolve any TONE-BD and TONE-PT
alarms.
1956
ABRT
ACL to the board is not up. See ACL status with list sys-link and
follow the repair procedures for SYS-LINK.
2000
ABRT
Response to the test request was not received within the allowable time
period.
2100
ABRT
System resources required to run this test are not available.
2500
ABRT
Internal system error
1. Retry the command at 1-minute intervals up to 3 times.
FAIL
The test tone was not detected correctly in either direction.
1. Test the active Tone-Clocks in the PNs for which the ATM-EI circuit
pack under test provides a link. This determines if the dial tone is
supplied.
4 of 8
548 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Table 174: Expansion Interface 2-Way Transmission Test (#241) (continued)
Error
Code
Test
Result
Description / Recommendation
10MM
FAIL
The failure codes only apply to a system equipped with an ATM Switch.
The letters “MM” refer to the distant or far-end PN, and “NN” to the
near-end ATM-EI under test.
The test tone was detected correctly in forward direction (data sent from
the PN where the circuit pack under test resides and detected correctly in
port network MM), but not the opposite direction.
1. Test the active Tone-Clocks on the “MM” PN and the PN where the
ATM-EI under test resides (test tone-clock location). This
determines if a dial tone is supplied.
2. Ensure that the ATM address of the ATM-EI circuit pack under test
matches the ATM address on the ATM switch for the port to which this
circuit pack is connected. Refer to ATM Installation, Upgrades, and
Administration using Avaya Communication Manager, 555-233-124,
for the procedure to check the ATM port address on the ATM switch.
3. Run Test #241 on the active ATM-EI in port network MM. If this test
fails with Error Code 10NN or 30NN, go back to step 2.
4. If the address was the same, replace the active ATM-EI circuit pack on
port network MM.
5. If this test fails with Error Code 20NN or 40NN, replace ATM-EI circuit
pack that had the initial problem.
5 of 8
Issue 1 June 2005
549
Communication Manager Maintenance-Object Repair Procedures
Table 174: Expansion Interface 2-Way Transmission Test (#241) (continued)
Error
Code
Test
Result
Description / Recommendation
20MM
FAIL
The failure codes only apply to a system equipped with an ATM Switch.
The letters “MM” refer to the distant or far-end PN, and “NN” to the near-end
ATM-EI under test.
6. The test tone was detected correctly in reverse direction (data sent
from port network MM was detected correctly in the PN where the
circuit pack under test resides, but not the opposite direction).
7. Test the active Tone-Clock on the “MM” PN and the PN where the
ATM-EI under test resides (test tone-clock location). This
determines if dial tone is supplied.
8. Ensure that the ATM address of the active ATM-EI circuit pack under
test matches the ATM address on the ATM switch for the port to which
this circuit pack is connected. Refer to ATM Installation, Upgrades,
and Administration using Avaya Communication Manager,
555-233-124, for the procedure to check the ATM port address on the
ATM switch.
9. Run Test #241 on the active ATM-EI in port network MM. If this test
fails with Error Code 20NN or 40NN, go back to step 2.
If the address was the same, replace the active ATM-EI circuit pack on
port network MM.
If this test fails with Error Code 10NN or 30NN, replace ATM-EI circuit
pack with the initial problem.
6 of 8
550 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Table 174: Expansion Interface 2-Way Transmission Test (#241) (continued)
Error
Code
Test
Result
Description / Recommendation
30MM
FAIL
The failure codes only apply to a system equipped with an ATM Switch.
The letters “MM” refer to the distant or far-end PN, and “NN” to the near-end
ATM-EI under test.
The test failed for the first connection from the ATM-EI board under test to
another PN, and the test tone was detected correctly in the forward
direction (data sent from the PN where the circuit pack under test resides
was detected correctly in port network MM, but not the opposite direction).
1. Test the active Tone-Clock on the “MM” PN and the PN where the
ATM-EI under test resides (test tone-clock location). This
determines if dial tone is supplied.
2. Ensure that the ATM address of the ATM-EI circuit pack under test
matches the ATM address on the ATM switch for the port to which this
circuit pack is connected. Refer to for the procedure to check the ATM
port address on the ATM switch.
3. Run Test #241 on the active ATM-EI in port network MM. If this test
fails with Error Code 10NN or 30NN, go back to step 2.
If the address was the same, replace the active ATM-EI circuit pack on
port network MM.
If this test fails with Error Code 20NN or 40NN, replace ATM-EI circuit
pack with the initial problem.
7 of 8
Issue 1 June 2005
551
Communication Manager Maintenance-Object Repair Procedures
Table 174: Expansion Interface 2-Way Transmission Test (#241) (continued)
Error
Code
Test
Result
Description / Recommendation
40MM
FAIL
Failure code only applies to a system equipped with an ATM Switch. The
letters “MM” refer to the distant or far-end PN, and “NN” to the near-end
ATM-EI under test.
The test failed for the first connection from the ATM-EI board under test to
another PN, and the test tone was detected correctly in the reverse
direction (data sent from port network MM was detected correctly in the PN
where the circuit pack under test resides), but not the opposite direction.
1. Test for the Active Tone-Clocks on port network MM and the PN where
the ATM-EI under test resides. This determines if dial tone is
supplied.
2. Ensure that the ATM address of the active ATM-EI circuit pack in port
network MM matches the ATM address on the ATM switch for the port
to which this circuit pack is connected. Refer to ATM Installation,
Upgrades, and Administration using Avaya Communication Manager,
555-233-124, for the procedure to check the ATM port address on the
ATM switch.
3. Run Test #241 on the active ATM-EI in port network MM. If this test
fails with Error Code 20NN or 40NN, go back to step 2.
If the address was the same, replace the active ATM-EI circuit pack on
port network MM.
If this test fails with Error Code 10NN or 30NN, replace ATM-EI circuit
pack with the initial problem.
0
PASS
Tone successfully transmitted in both directions. Both ATM-EI boards and
their lightwave transceivers are functioning properly.
NO
BOARD
No board was detected by the test.
1. Resolve either wrong board (Error 125) or no board (Error 131)
issues.
2. Check that the board is properly translated and inserted. If so, check
for hyperactivity (Error 1538). If hyperactive, use reset board
location.
3. Run the test again. If it fails, the ID chip on board could be bad.
Replace the board and retest.
8 of 8
552 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Expansion Interface Lock Query Test (#304)
This test is nondestructive and is used to query the ATM and EI circuit packs (both active and
standby) for its status concerning lock to the backplane system clock. It is run as part of
periodic, scheduled, initialization, and error analysis testing. When an in-line, “out-of-lock”
report comes in, this test is run to check the circuit pack’s status. The ATM-EI responds with “in
lock” or “out of lock.” If the response is “in lock,” the test passes; if the response is “out of lock,”
the test fails.
Table 175: Test #304 Expansion Interface Lock Query Test (#304)
Error
Code
Test
Result
Description / Recommendation
2000
ABRT
Response to the test request was not received within the allowable time
period.
2100
ABRT
Could not allocate the necessary system resources to run this test.
2500
ABRT
Internal system error
1. Retry the command at 1-minute intervals up to 3 times.
FAIL
A PN’s unduplicated ATM-EI circuit pack responded incorrectly, or a PN’s
active ATM-EI circuit pack could not communicate with the PN’s circuit
packs.
1. If the PN’s active ATM-EI circuit pack is failing and duplicated PNC is
enabled:
a. Enter reset PNC interchange to switch to the standby PNC.
b. Repeat the short test sequence.
c. If test continues to fail, enter reset board location to reset the
ATM-EI circuit pack.
2. If the PN’s unduplicated ATM-EI circuit pack is failing:
a. Enter display errors and display alarms, and follow the
associated repair procedures for TDM-CLK, TONE-BD, or SYNC
alarms/errors.
b. Repeat the short test sequence.
c. If test continues to fail, replace the circuit pack or transceiver.
PASS
Communication from software to the ATM-EI circuit pack is functioning
correctly.
1 of 2
Issue 1 June 2005
553
Communication Manager Maintenance-Object Repair Procedures
Table 175: Test #304 Expansion Interface Lock Query Test (#304) (continued)
Error
Code
Test
Result
Description / Recommendation
0
NO
BOARD
No board was detected by the test.
1. Check the error log for wrong board (error 125) or no board (error 131).
Resolve either of these issues.
2. Check that the board is properly translated and inserted. If so, check
for hyperactivity (error 1538). If hyperactive, use reset board
location.
3. Run the test again. If it fails, the NCE chip on board could be bad.
Replace the board and retest.
2 of 2
Expansion Interface Control Channel Test (#316)
This test is nondestructive. If an ATM-EI circuit pack is an active ATM-EI in the PN (amber LED
on long/off short), the Expansion Interface Control Channel test checks to see if the ATM-EI
circuit pack can communicate with other circuit packs in the PN using the PN’s TDM bus.
If the circuit pack is a standby ATM-EI (amber LED off), this test queries the ATM PNC
Expansion Interface circuit pack for information about its type and vintage.
Table 176: Expansion Interface Control Channel Test #316
Error
Code
Test
Result
Description / Recommendation
2000
ABRT
Response to the test request was not received within the allowable time
period.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 3 times.
2500
ABRT
Internal system error
1. Retry the command at 1-minute intervals up to 3 times.
1 of 2
554 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Table 176: Expansion Interface Control Channel Test #316 (continued)
Error
Code
Test
Result
Description / Recommendation
FAIL
A PN’s unduplicated ATM-EI circuit pack responded incorrectly, or a PN’s
active ATM-EI circuit pack could not communicate with the PN’s circuit
packs.
1. If the PN’s active ATM-EI circuit pack is failing and duplicated PNC is
enabled:
a. Enter reset PNC interchange to switch to the standby PNC.
b. Repeat the short test sequence.
c. If test continues to fail, enter reset board location to reset the
ATM-EI circuit pack.
2. If the PN’s unduplicated ATM-EI circuit pack is failing:
a. Enter display errors and display alarms, and follow the
associated repair procedures for TDM-CLK, TONE-BD, or SYNC
alarms/errors.
b. Repeat the short test sequence.
c. If test continues to fail, replace the circuit pack or transceiver.
PASS
The ATM-EI circuit pack did respond correctly to test. Communication from
software to the ATM-EI circuit pack is functioning.
1. Refer to other ATM-EI circuit pack tests if the link is not functioning
correctly.
0
NO
BOARD
No board was detected by the test.
1. Resolve any wrong board (Error 125) or no board (Error 131) issues.
2. Check that the board is properly translated and inserted. If so, check
for hyperactivity (Error 1538). If hyperactive, use reset board
location.
3. Run the test again. If it fails, the NCE chip on board could be bad.
Replace the board and retest.
2 of 2
Packet Interface Test (#598)
This test is nondestructive and attempts to send a data packet from the TN1655 Packet
Interface circuit pack through any ATM PNC Expansion Interface circuit packs. The path the
data packet takes depends on the location of the ATM PNC Expansion Interface circuit pack
being tested and whether the system has duplicated port-network connectivity.
Issue 1 June 2005
555
Communication Manager Maintenance-Object Repair Procedures
The Packet Interface Looparound test checks the packet-bus interface circuitry on this board.
The on-board LANHO chip sends a data stream to the bus, retrieves it back, and checks for its
consistency. If the data is consistent, the test passes; otherwise, it fails. The test aborts if the
specified PN’s packet bus has an active minor alarm or is out of service. This test runs as a part
of initialization, periodic or scheduled error analysis, and demand-test sequences. Figure 26
shows a schematic of the test.
Figure 26: Packet Interface Test (#598)
ATM
circuit
pack
LAN bus
(PN X)
LANHO
chip
iodfchip AWF 040699
PNC mode
Table 177: Packet Interface Test (#598)
Error
Code
Test
Result
Description / Recommendation
2000
ABRT
Response to the test request was not received within the allowable time
period.
1. Retry the command at 1-minute intervals up to 3 retries.
2. If the test fails repeatedly, attempt to reset the circuit pack.
3. If the test continues to fail, replace the circuit pack.
2012
ABRT
Internal system error
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
ANY
FAIL
The transmitted data packet was not received correctly by the Packet
Interface circuit pack. The failure can be in the ATM-EI under test, the
DS1C-BD circuit packs, or the intervening Center Stage components.
1. Retry the command at 1-minute intervals up to five times.
2. If the test continues to fail, replace the circuit pack.
PASS
The Packet Interface test passed.
556 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
ATM Board Error Query Test (#1259)
This test is nondestructive. The ATM circuit pack firmware maintains counters for some of the
on- and off-board errors. The maintenance software queries the board for its health information
to do error analysis. These alarms have assigned priority: if a higher priority alarm occurs, the
remaining alarms are not reported to the software (through the inline errors), avoiding
unnecessary up-link, in-line error message traffic. This is run as a part of a craft demand test
sequence periodic testing, initialization, and error analysis.
Table 178: ATM Board Error Query Test (#1259)
Error
Code
Test
Result
Description / Recommendation
2000
ABRT
Response to the test was not received within the allowable time period.
2100
ABRT
System resources required to run this test are not available.
1. Retry the command at 1-minute intervals up to 3 times.
2500
ABRT
Internal system error
1. Retry the command at 1-minute intervals up to 3 times.
XXYY
FAIL
On-board hardware or off-board signaling errors on the board. XX
indicates the on-board hardware error, and YY indicates the off-board
errors on the as shown in Table 179: XX Error Codes, Test #1259 (ATM
Board Error Query Test) on page 558 or Table 180: YY Error Codes, Test
#1259 (ATM Board Error Query Test) on page 559.
1. Resolve any errors in error logs.
0
PASS
No service effecting errors or alarms were detected on the circuit pack.
NO
BOARD
No board was detected by the test.
1. Check the Error Log for wrong board (Error Type 125) or no board
(Error Type 131). Resolve either of these issues, if applicable.
2. Check that the board is properly translated and inserted. If so, check
for hyperactivity (Error Type 1538). If hyperactive, use reset board
location.
3. Run the test again. If it fails, the NCE chip on board could be bad.
Replace the board and retest.
Issue 1 June 2005
557
Communication Manager Maintenance-Object Repair Procedures
Table 179: XX Error Codes, Test #1259 (ATM Board Error Query Test)
XX Aux Data
Description
1
ATM framer chip failed
2
NCE chip failed
3
LANHO critical error
4
TDM Prog. logic device failed
5
Every on-board DSP failed
6
Receive network processor failed
7
Transmit network processor failed
8
Memory read failed
9
Dual UART chip failed
10
LANHO receive parity error
11
LANHO FIFO overflow error
12
LAN Bus timeout
13
LANHO Xmit FIFO overflow
14
One or more on-board DSPs failed
558 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Table 180: YY Error Codes, Test #1259 (ATM Board Error Query Test)
YY Aux Data
Description
15
Backplane clock failed
16
Loss of signal
17
Loss of frame
18
Multiplexer Section Alarm indication signal error
19
Multiplexer Section remote defect indicator error
20
Loss of pointer
21
Path signal level mismatch
22
High level path alarm indication signal
23
High level path remote defect indicator
24
Loss of cell delineation
25
Uncorrectable headers sent by the ATM switch
26
Too many cells with invalid Virtual Path Indicator (VPI)/Virtual
Circuit Indicator (VCI) combination
27
The signaling link between the board and the ATM switch is
down.
28
Board to the ATM switch connection is down
34
Excessive AAL-5 (ATM signaling protocol) retransmission
requests
35
Excessive LAPD retransmission requests
37
ATM CLP (cell loss priority) bit. See ATM-NTWK (ATM
Network Error) on page 576.
38
ATM congestion indicator. See ATM-NTWK (ATM Network
Error) on page 576.
39
ATM cell underrun. See ATM-NTWK (ATM Network Error) on
page 576.
40
ATM cell overrun. See ATM-NTWK (ATM Network Error) on
page 576.
41
Lost ATM cell. See ATM-NTWK (ATM Network Error) on
page 576.
Issue 1 June 2005
559
Communication Manager Maintenance-Object Repair Procedures
ATM Board Framer Loop-Around Test (#1260)
This test is destructive.
Note:
This test can be run on the standby PNC only if the board is busied out.
Note:
This test places the ATM circuit pack in ATM framer loop-around mode. Once the board
receives this message, it creates a dummy virtual circuit that originates and ends on the same
board, without leaving the board. This test verifies both the TDM path and the Packet Path. If
the TDM test path passes, then the packet path is tested. Definitions of each test path are:
●
The circuit (TDM) path: one of the Tone Generators sends a bit pattern through a TDM
bus time slot to the ATM framer. The pattern is converted into ATM cells and looped back
to the ATM-EI board, which converts the cell back into the bit pattern and puts it on a
pre-determined time slot. A Tone Detector tests for the bit pattern and reports the test
result. This test verifies that a large portion of the ATM-EIs circuit paths are functioning
correctly. Figure 27: ATM Board Framer Loop-Around Test (#1260) on page 560 shows a
diagram of the test.
Figure 27: ATM Board Framer Loop-Around Test (#1260)
TDM bus
(PPN)
ATM
circuit
pack
Tone clock
Tone detector
ATM
framer
looped
Packet
Interface
Packet bus
(PPN)
Note:
PNC mode
iodftone AWF 040699
●
Packet path: the Packet Interface circuit pack sends packet data to the ATM framer
interface, where it is mapped into ATM cells and then looped around internally. The cells
are converted back to packet data after it has been looped. This portion of the test verifies
correct operation of the ATM-EI’s packet-bus interface and a large portion of the ATM-EI's
packet paths. Figure 28: ATM Board Framer Loop-Around Test (#1260) (non-EAA,
Packet Path) on page 561 shows the packet switched signal path for the ATM circuit pack.
●
This test verifies the operation of a large portion of the ATM-EI circuit and packet paths, but
does not verify the optical portion of the lightwave transceiver. If this test passes, the
ATM-EI circuit pack is functioning correctly, but faults can exist in the lightwave transceiver.
If the test fails, the fault can be on the board. After the test results are reported, the ATM
framer is taken out of loopback.
Note:
This test can be run on active or standby ATM-EIs, but it is not allowed if an
ATM-EI is the Expansion Archangel.
560 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Figure 28: ATM Board Framer Loop-Around Test (#1260) (non-EAA, Packet Path)
ATM
circuit
pack
TDM bus
(EPN X)
Tone clock
Tone detector
ATM
framer
looped
PNC mode
Packet bus
(PPN)
ATM
circuit
pack
ATM
circuit
pack
Packet
interface
ATM
switch
PNC mode
ATM
expansion
archangel
PNC mode
Packet bus
(EPN X)
iodfpak AWF 040699
Table 181: ATM Board Framer Loop-Around Test (#1260)
Error
Code
Test
Result
Description / Recommendation
1002
ABRT
The system could not allocate timeslots for the test. The system could be
under heavy traffic conditions or it could have timeslots out of service due
to TDM-BUS errors.
1. If the system has no TDM-BUS errors and is not handling heavy traffic,
retry the command at 1-minute intervals up to 3 times.
1003
ABRT
The system could not allocate a tone receiver for the test. The system
may be oversized for the number of Tone Detectors present, or some Tone
Detectors may be out of service.
1. Verify that at least one Tone Detector resides in this PN. (Even without
a TTR-LEV error, the tested circuit pack’s PN could be missing a Tone
Detector.)
If missing, the test always aborts for this circuit pack, without harming
the system.
Note: A TN2182 Tone-Clock circuit pack must be of vintage B or
newer. If an earlier vintage circuit pack resides in a PN, this test
always aborts with this abort code.
2. Resolve any TONE-PT errors.
3. If neither condition exists, retry the command at 1-minute intervals up
to 3 times.
1 of 5
Issue 1 June 2005
561
Communication Manager Maintenance-Object Repair Procedures
Table 181: ATM Board Framer Loop-Around Test (#1260) (continued)
Error
Code
Test
Result
Description / Recommendation
1015
ABRT
The ATM-EI circuit pack has not been busied out.
1. Busyout the ATM-Expansion Interface circuit pack, then repeat test
board location long .
1031
ABRT
If the ATM Expansion Interface circuit pack is in a PN and is on the active
PNC, this test cannot be executed.
1. If PNC Duplication is enabled, attempt to make the standby PNC active
using reset pnc interchange.
2. If the PNC Interchange is successful, rerun the test.
1033
ABRT
The ATM-EI circuit pack is absent.
1. Use list atm pnc to verify that switch recognizes the circuit pack.
2. Retry the command.
1139
ABRT
The packet bus in the PN where this ATM-EI board resides has a major
alarm against it. This test needs to use the alarmed PN’s packet bus.
1. Resolve any PKT-BUS problems.
2. Retry the command.
1141
ABRT
The Packet Interface circuit pack is out of service.
1. Resolve any PKT-INTF problems.
1394
ABRT
The ATM-EI board is out of service and the test cannot be run. This
condition is due to a change in the ATM-EI board’s ability to communicate
with the ATM switch.
1. Run Test #241. If it does not pass, see repair procedures for
Expansion Interface 2-Way Transmission Test (#241).
1395
ABRT
This test cannot be run on an ATM-EI circuit pack if it is part of the B-side
PNC and duplicated PNC is not enabled.
1. If this test needs to run on this ATM-EI circuit pack, enable PNC
duplication with the change system-parameters duplication
command.
2. Prevent the system from doing a PNC interchange by executing the
set PNC lock command.
3. Repeat this test.
2 of 5
562 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Table 181: ATM Board Framer Loop-Around Test (#1260) (continued)
Error
Code
Test
Result
Description / Recommendation
1407
ABRT
This test cannot be run on an ATM-EI board that is on the active PNC
because it cannot be busied out. This error code indicates that PNC
duplication is enabled.
1. Attempt to perform a PNC interchange with the reset pnc
interchange command.
2. If the PNC interchange is successful, busyout the original
ATM-Expansion Interface circuit pack with the busyout board
location (address of the original ATM-EI board) command.
3. Retry the command.
2000
ABRT
Response to the test was not received in the allowable time period.
1. Retry the command at 1-minute intervals up to 3 times.
2060
ABRT
The link on the packet bus being used to perform the test has failed.
1. Retry the command at 1-minute intervals up to 3 times.
2. If the test continues to abort, resolve any PKT-INTF errors.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 3 times.
2500
ABRT
Internal system error.
1. Retry the command at 1-minute intervals up to 3 times.
1
FAIL
The test did not detect the test tone through the loop-around connection.
Note:
Note:
The packet portion of this test was not run since the circuit
portion failed.
1. Test the active Tone-Clock (test tone-clock location) in the PN
that contains the defective ATM-EI circuit pack to verify that dial tone is
being supplied.
2. If the Tone-Clock is healthy, test the ATM-EI circuit pack (test board
location long).
3. If this test continues to fail, replace the ATM-EI circuit pack or
transceiver.
4. Test the new ATM-EI circuit pack (test board location long).
3 of 5
Issue 1 June 2005
563
Communication Manager Maintenance-Object Repair Procedures
Table 181: ATM Board Framer Loop-Around Test (#1260) (continued)
Error
Code
Test
Result
Description / Recommendation
2
FAIL
The test tone was transmitted and detected correctly, but the correct data
packet was not detected by the Packet Interface circuit pack.
1. Test the Packet Interface circuit pack to verify that it is functioning
properly. If any tests fail, investigate those tests and repair the Packet
Interface circuit pack.
2. If the Packet Interface circuit pack is OK, resolve any DS1C-BD alarms
or errors (if so equipped).
3. Test the ATM-EI circuit pack (test board location long).
4. If this test continues to fail, replace the ATM-EI board.
5. Test the new ATM-EI circuit pack (test board location long).
3
FAIL
The test tone was transmitted correctly, but the returned tone was
distorted.
1. If the Tone-Clock is healthy, test the ATM-EI circuit pack (test board
location long).
2. If this test continues to fail, replace the ATM-EI circuit pack.
3. Test the new ATM-EI circuit pack (test board location long).
4
FAIL
Unable to create loop for TDM path for this test.
1. Retry the command at 1-minute intervals up to 3 times.
2. If this test continues to fail, replace the ATM-EI circuit pack.
3. Test the new ATM-EI circuit pack (test board location long).
5
FAIL
Unable to create loop for packet path for this test.
1. Retry the command at 1-minute intervals up to 3 times.
2. If this test continues to fail, replace the ATM-EI circuit pack.
3. Test the new ATM-EI circuit pack (test board location long).
6
FAIL
A previously-established loop around was not released.
1. Enter reset board location.
2. Retry the command at 1-minute intervals up to 3 times.
3. If this test continues to fail, replace the ATM-EI circuit pack.
4. Test the new ATM-EI circuit pack (test board location long).
4 of 5
564 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Table 181: ATM Board Framer Loop-Around Test (#1260) (continued)
Error
Code
0
Test
Result
Description / Recommendation
PASS
The ATM-EI board is functioning properly, however this test does not verify
that the optical portion of the lightwave transceiver is functioning.
NO
BOARD
No board was detected by the test.
1. Resolve either wrong board (Error 125) or no board (Error 131) issues,
if applicable.
2. Check that the board is properly translated and inserted. If so, check
for hyperactivity (Error 1538). If hyperactive, use reset board
location.
3. Run the test again. If it fails, the NCE chip on board could be bad.
Replace the board and retest.
5 of 5
ATM Board Time Of Day Update (#1261)
This test is nondestructive. The ATM circuit pack requires a reference time to do SDH/SONET
performance monitoring. This test updates the system time to the board and synchronizes the
board with the S8700 Multi-Connect system’s clock during initialization, scheduled
maintenance, and craft long test.
Table 182: ATM Board Time Of Day Update (#1261)
Error
Code
Test
Result
Description / Recommendation
2031
FAIL
The attempt to send the message to the ATM-EI circuit pack was not
successful.
2500
FAIL
Did not send the time-of-day information to the board.
1. Retry the command at 1-minute intervals up to 3 times.
PASS
The ATM-EI circuit pack is successfully updated with system time.
1. If status port-network still indicates that this link is down, it is
possible that one or both of the ATM-EI circuit packs have been busied
out.
2. If the link still does not come up, reset one or both ATM-EI circuit
packs on the link.
1 of 2
Issue 1 June 2005
565
Communication Manager Maintenance-Object Repair Procedures
Table 182: ATM Board Time Of Day Update (#1261) (continued)
Error
Code
Test
Result
Description / Recommendation
0
NO
BOARD
No board detected.
1. Resolve either wrong board (Error 125) or no board (Error 131) issues,
if applicable.
2. Check that the board is properly translated and inserted. If so, check
for hyperactivity (Error 1538). If hyperactive, use reset board
location.
3. Run the test again. If it fails, the circuit pack’s NCE chip could be bad.
Replace the pack and retest.
2 of 2
ATM Board Reset (#1256)
This test is destructive.
If the ATM-EI board is a standby in a PN, the reset is done through the SAKI reset interface. If
the ATM-EI is an Expansion Archangel (active ATM-EI board in the PN) and if the EAL is
present, a special message is sent to the board over the EAL.
Table 183: ATM Board Reset (#1256)
Error
Code
Test
Result
Description / Recommendation
1386
ABRT
No Active EAL to the board. This error applies only if the board under test is
in a PN. Check the error logs for SYS-LINK (System Links) errors against
the PN where the ATM-EI resides, and take appropriate diagnostic action for
the SYS-LINK.
1015
ABRT
This test cannot be run because the ATM-EI circuit pack has not been
busied out.
1. Busyout the ATM circuit pack, then repeat test board location
long.
1407
ABRT
ABORT
1. Perform a PNC Interchange
2. Try to reset the board again.
1 of 2
566 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Table 183: ATM Board Reset (#1256) (continued)
Error
Code
Test
Result
Description / Recommendation
None
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
2. If the test continues to abort escalate the problem.
2000
ABRT
Did not receive the SANITY response in the given time.
1. Wait for 5 minutes and see if board is visible to the system by using
list config all.
2. If the board is visible, run the test again. If same abort code results,
escalate the problem.
3. If the board is not visible to the system with list configuration
all, reseat the board.
4. If the board is still not recognized by the system, replace the board.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
2500
ABRT
Internal system error
1. Try to reset the board again.
1
FAIL
The circuit pack failed to reset.
2
FAIL
The circuit pack failed to restart.
1. Execute command again.
2. If the problem persists, replace the circuit pack.
PASS
The ATM-EI circuit pack is successfully reset.
1. If status port-network still indicates that this link is down, it is
possible that one or both of the ATM-EI circuit packs are busied out.
2. If the links do not come up after reset, review the error logs and take
appropriate diagnostic action.
2 of 2
Issue 1 June 2005
567
Communication Manager Maintenance-Object Repair Procedures
ATM Cross Talk Test (#1298)
This test is nondestructive. The ATM board Cross Talk test verifies that the selected TDM bus
time slot never crosses over to time slots reserved for other connections. The test also checks
for cross connections, where the board talks to time slots other than those specified. Since this
test uses many system resources (TDM time slots, Tone Generator, Tone Detector, and others),
it runs as a part of demand test only.
This test fails if either the TDM programmable logic and/or the interface to the DSP is not
operating properly. Failure of these components can result in 1-way or noisy connections.
Refer to Figure 29: ATM Cross Talk Test #1298 schematic on page 568 for a schematic of this
test.
Note:
Note:
This test takes approximately 12 minutes and applies only to TN2305 and
TN2306 circuit packs.
Figure 29: ATM Cross Talk Test #1298 schematic
TDM bus
(PN X)
Tone detector
iodfatcr AWF 040699
ATM
circuit
pack
DSP Talker
PNC mode
Table 184: ATM Crosstalk Test (#1298)
Error
Code
Test
Result
Description / Recommendation
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1002
ABRT
The system could not allocate time slots for the test. The system could
be under heavy traffic conditions or it could have time slots
out-of-service due to TDM-Bus errors. Refer to TDM-BUS to diagnose
these errors.
1. If the system has no TDM-Bus errors and is not handling heavy
traffic, repeat test at 1-minute intervals up to 5 times.
1 of 2
568 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Table 184: ATM Crosstalk Test (#1298) (continued)
Error
Code
Test
Result
Description / Recommendation
1003
ABRT
The system could not allocate a tone receiver for the test. The system
may be oversized for the number of Tone Detectors present or some
Tone Detectors may be out-of-service.
1. Resolve any TTR-LEV errors in the Error Log.
2. Resolve any TONE-PT errors in the Error Log.
3. If neither condition exists, retry the test at 1-minute intervals up to 5
times.
2000
ABRT
Response to the test was not received within the allowable time period.
1. Retry the command at 1-minute intervals up to 5 times.
2100
ABRT
Could not allocate the necessary system resources to run this test.
1. Retry the command at 1-minute intervals up to 5 times.
1962
ABRT
Every TALKER DSP is busy (an unlikely event).
1. Retry the command at 1-minute intervals up to 3 times.
2302
ABRT
Inconsistent uplink message from the ATM-EI board. This is a very
unlikely event.
1. Retry the command at 1-minute intervals up to 3 times.
2752
ABRT
The circuit pack in this location is not a TN230X.
1–8 None
FAIL
The board is writing to unauthorized TDM time slots. The error code
indicates the number of faulted TALKER DSPs.
1. Retry the command up to 3 times.
2. If the failure persists, replace the circuit pack.
1–8
PASS
The board is not talking to unauthorized time slots on the TDM Bus. The
error code indicates the number of TALKER DSPs that were tested.
2 of 2
Issue 1 June 2005
569
Communication Manager Maintenance-Object Repair Procedures
ATM Board DSP Test (#1293)
This test is nondestructive and is designed to test the board’s interface to the TDM bus and the
functions of all 24 on-board DSPs (Digital Signal Processors). There are three functional types
of DSPs:
●
talkers – put data on the TDM bus
●
listeners – take data off the TDM bus
●
echo cancelers – as implied
Listener and echo cancelers are tightly coupled because firmware allocates sets of DSPs.
Since there are a total of 24 DSPs on the board, there can be up to 8 triplets allocated.
If the test fails for every DSP, a MAJOR alarm is raised against the board. If the test fails for one
or more DSPs, a MINOR alarm is raised. If a DSP is busy, the test for that particular DSP is
considered passed. The test aborts if the system resources (for example, the TDM time slots,
Tone Generator, and others) are not available.
This test applies to TN2305 and TN2306 ATM-EIs, both active and standby, and is run as part of
craft short and long testing, periodic, scheduled, initialization, and error analysis testing. Refer
to Figure 30: ATM Board DSP Test (#1293) on page 570 for a diagram of this loop-around test.
Figure 30: ATM Board DSP Test (#1293)
TDM bus
(PN X)
ATM
circuit
pack
Tone clock
CCMS
CCMS
Tone detector
iodfatmd AWF 040699
DSP listener
DSP echo
DSP talker
Table 185: ATM Board DSP Test (#1293)
Error
Code
Test
Result
Description / Recommendation
1002
ABRT
The system could not allocate time slots for the test. The system could be
under heavy traffic conditions or it could have time slots out of service due
to TDM-BUS errors.
1. If the system has no TDM-BUS errors and is not handling heavy traffic,
retry the command at 1-minute intervals up to 3 times.
1 of 3
570 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-EI (Expansion Interface Circuit Pack)
Table 185: ATM Board DSP Test (#1293) (continued)
Error
Code
Test
Result
Description / Recommendation
1003
ABRT
The system could not allocate a tone receiver for the test. The system may
be oversized for the number of Tone Detectors present, or some Tone
Detectors may be out of service.
1. Verify that at least one Tone Detector resides in this PN. (Even without
a TTR-LEV error, the tested circuit pack’s PN could be missing a Tone
Detector.)
If missing, the test always aborts for this circuit pack, without harming
the system.
2. Resolve any TONE-PT errors.
3. If neither condition exists, retry the command at 1-minute intervals up
to 3 times.
1962
ABRT
Every DSPs is busy (an unlikely event).
1. Retry the command at 1-minute intervals up to 3 times.
2000
ABRT
Response to the test was not received within the allowable time period for
some of the DSPs.
1. If the board is in standby, reset the board and run the test again.
2. Look into the Error Log for Error Type 1218 (bad DSP). If Error Type
1218 is not logged against this board, run the DSP test again and see if
the error persists.
2100
ABRT
Could not allocate the necessary system resources to run this test.
2302
ABRT
Inconsistent uplink message from the ATM-EI board (an unlikely event).
1. Retry the command at 1-minute intervals up to 3 times.
2500
ABRT
Internal system error
2752
ABRT
The circuit pack in this location is not a TN230X.
2 of 3
Issue 1 June 2005
571
Communication Manager Maintenance-Object Repair Procedures
Table 185: ATM Board DSP Test (#1293) (continued)
Error
Code
Test
Result
Description / Recommendation
XYZ
FAIL
A device on the circuit pack is failing. There is at least one bad DSP on the
board. Values are as follows:
●
The X value indicates the number of talker DSPs
●
Y indicates the number of listener DSPs
●
Z indicates the number of Echo Canceler DSPs that have failed the
test.
1. Run the tests for the active Tone-Clock in the PN that contains the
indicted ATM-EI circuit pack to verify that dial-tone is supplied.
2. If the Tone-Clock is healthy, repeat the short test on the ATM-EI board.
3. If this test continues to fail, replace the ATM-EI circuit pack.
XYZ
PASS
The test passed for some or all DSPs depending on XYZ values. XYZ
indicates the number of talker, listener and echo-canceler DSPs for which
the test passed, respectively. In the DSPs that passed the test, the test tone
was correctly detected by the DSP Listener and by tone-detector for the
DSP Talkers on both buses, and the Echo Canceler DSPs are working
properly.
0
NO
BOARD
No board was detected by the test.
1. Check the Error Log for wrong board (Error Type 125) or no board
(Error Type 131). Resolve either of these issues, if applicable.
2. Check that the board is properly translated and inserted. If so, check
for hyperactivity (Error Type 1538). If hyperactive, use reset board
location.
3. Run the test again. If it fails, the circuit pack could be bad. Replace
the circuit pack and retest.
3 of 3
572 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-INTF (TN2305/6)
ATM-INTF (TN2305/6)
S8700 MC
MO Name in Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
ATM-INTF
WRN
test board location
ATM interface board
The system recognizes a TN2305/6 as an ATM interface board (ATM-INTF) unless it has an
assigned personality (add atm pnc or add atm trunk). ATM-INTF does not have an
associated maintenance strategy, although the:
●
list config and change circuit-pack reveal the board
●
test board runs an on-demand Control Channel test
●
reset board resets the board
Table 186 lists circuit packs that are ATM-EI boards if they are administered to provide ATM
port-network connectivity (ATM PNC).
Table 186: ATM-EI circuit packs for ATM PNC
Note:
Circuit Pack
Fiber
Echo
Cancellation
TN2305
Multimode
Yes
TN2306
Single-mode
Yes
Note:
Always replace an ATM-EI circuit pack with the same type.
Error Log Entries and Test-to-Clear Values
Table 187: ATM-INTF Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
23 (a)
0
None
WRN
Off
None
MINOR
On
None
WRN
Off
125 (b)
217 (c)
0
Test-to-Clear Value
Issue 1 June 2005
573
Communication Manager Maintenance-Object Repair Procedures
Notes:
a. Error Type 23: The ATM expansion interface circuit pack is administered through a change
circuit-pack command, but has not been inserted into the system. Insert the circuit
pack.
b. Error Type 125: A wrong circuit pack is located in the slot where this circuit pack is logically
administered. To resolve this problem either remove the wrong circuit pack or insert the
logically-administered circuit pack.
c. Error Type 217: The ATM circuit pack is physically present but has not been given a
personality. Remove the circuit pack or administer it using add atm pnc or add atm
trunk.
System Technical Demanded Tests: Descriptions and Error Codes
Test failure is not logged in the error log.
Order of Investigation
Short Test
Sequence
Long Test
Sequence
X
X
Control Channel Loop Around test (#52)
D/ND
Nondestructive
Control Channel Loop-Around Test
This test queries the circuit pack for its circuit-pack code and vintage, and verifies its records.
Table 188: Test #52: Control Channel Loop-Around
Error
Code
Test
Result
Description / Recommendation
2000
ABRT
The response to the test request was not received within the allowable time
period.
2100
ABRT
The system resources required to this test are not available.
1. Retry the command at 1-minute intervals up to 5 times.
2500
ABRT
Internal system error.
1. Retry the command at 1-minute intervals up to 5 times.
1 of 2
574 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-INTF (TN2305/6)
Table 188: Test #52: Control Channel Loop-Around (continued)
Error
Code
Test
Result
Description / Recommendation
FAIL
The circuit pack failed to return the circuit pack code or vintage.
1. Retry the command up to 5 times.
2. If the problem continues, reset the circuit pack.
3. Retry the command up to 5 times.
Any
PASS
Communication with this circuit pack is successful.
NO
BOARD
This is normal if the test is being executed when:
1. The board is not physically in the system.
2. The system is booting.
Otherwise, there is some inconsistency in the date stored in the system.
1. Verify that the board is physically in the system.
2. Verify that the system is not in the process of booting.
3. Retry the command at 1-minute intervals up to 5 times.
2 of 2
Issue 1 June 2005
575
Communication Manager Maintenance-Object Repair Procedures
ATM-NTWK (ATM Network Error)
S8700 MC
MO Name in Alarm Log
Physical Name in
Error Log1
Alarm
Level
Full Name of MO
ATM-NTWK
ATUUP
WRN
ATM Network Error
ATM-NTWK
location
WRN
ATM Network Error
1. AT indicates it is an ATM switch-related address, UU is the connection number. The connection
number can be converted into a board location with display atm pnc UU, which shows the
translations for the board that reported the ATM network error. P indicates if the ATM-EI board
(reporting the ATM network error) is on the PNC’s A side or the B side. If the system is simplex, only A
is valid.
In an ATM PNC configuration, a proprietary Center Stage Switch (CSS) is replaced by an ATM
network. Because CSS nodes are replaced by the ATM network in the ATM PNC configuration,
SNI boards are no longer needed. In place of the SNI boards, ATM Expansion Interface (EI) or
ATM Circuit Emulation Service (CES) boards are connected to an ATM switch port over a
fiber-optic cable. The ports on the ATM switch are under control of its maintenance software.
Refer to ATM Installation, Upgrades, and Administration using Avaya Communication Manager,
555-233-124, for more information.
An error against ATM-NTWK indicates a problem in the ATM network (including the ATM
switch) that is affecting service quality. These error events are either:
●
Reported by the ATM network to an ATM EI or ATM CES board
●
Detected by either the ATM EI or ATM CES board itself
Since these errors are not related to the ATM EI or ATM CES board, they are not reported
against the ATM-EI or ATM-TRK MO. However, some of these errors invoke alarms that require
action by the system’s maintenance software, while other log-only errors require no action.
Error Codes and Aux Data values
The Cause Code/Error Type information is shown in Table 189. These are the possible errors
that can be logged against the ATM-NTWK MO.
576 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-NTWK (ATM Network Error)
If the ATM-NTWK MO receives more than 6 errors, the most recent are discarded.
Table 189: Error codes and Aux Data values ATM-NTWK
Cause
Code/
Error
Type
Aux
Data
Cause Codes Description
NORMAL EVENTS
0
(a)
Network unreachable
1
(a)
Unallocated (unassigned) number. This cause indicates that the called
party cannot be reached because, although the number is in a valid format,
it is not currently assigned (allocated).
2
(a)
No route to specified transit network. This cause indicates that the
equipment sending this cause has received a request to route the call
through a particular network that it does not recognize, either because the
transit network does not exist or because that particular transit network
does not serve the equipment that is sending this cause. This cause is
supported on a network-dependent basis.
3
(a)
No route to destination. This cause indicates that the called party cannot
be reached because the network through which the call has been routed
does not serve the destination desired. This cause is supported on a
network-dependent basis.
10
(a)
VPCI/VCI unacceptable. This cause indicates that the virtual channel most
recently identified is not acceptable to the sending entity for use in this call.
16
(a)
Normal call clearing. This cause indicates that the call is being cleared
because one of the users involved in the call has requested that the call be
cleared. Under normal situations, the source of this cause is not the
network.
17
(a)
User busy. This cause indicates that the called party is unable to accept
another call because the user busy condition has been encountered. This
cause value can be generated by the called user or by the network.
18
(a)
No user responding. This cause is used when a called party does not
respond to a call establishment message with a connect indication within
the prescribed period of time allocated.
1 of 6
Issue 1 June 2005
577
Communication Manager Maintenance-Object Repair Procedures
Table 189: Error codes and Aux Data values ATM-NTWK (continued)
Cause
Code/
Error
Type
Aux
Data
Cause Codes Description
21
(a)
Call rejected. This cause indicates that the equipment sending this cause
does not wish to accept this call, although it could have accepted the call
because the equipment sending this cause is neither busy nor
incompatible.
Note: If the call was rejected by the far-end ATM-EI or ATM-CES board,
there could also be additional information about this rejection in an ATM-EI
error log entry. Look for an ATM-EI or error with an Error Type between
1104 and 1119 inclusive, with approximately the same time stamp as this
error.
22
(a)
Number changed. This cause is returned to a calling party when the called
party’s number indicated by the calling user is no longer assigned. The new
called party’s number can optionally be included in the diagnostic field. If a
network does not support this capability, cause number 1 “unassigned
(unallocated) number” is used.
23
(a)
User rejects every call with CLIR (calling line identification restriction). This
cause is returned by the called party when the call is offered without calling
party’s number information and the called party requires this information.
27
(a)
Destination out of order. This cause indicates that a user-indicated
destination cannot be reached because a signaling message could not be
delivered to the remote user over the destination’s interface (for example, a
physical-layer or SAAL failure at the remote user, or remote user’s
equipment is off line).
28
(a)
Invalid number format (address incomplete). This cause indicates that the
called user cannot be reached because the called party’s number is not in a
valid format or has insufficient digits.
30
(a)
Response to STATUS ENQUIRY. This cause is included in the STATUS
message when the reason for generating the STATUS message was the
prior receipt of a STATUS ENQUIRY message.
31
(a)
Normal, unspecified. When no more specific cause values apply, this
cause reports a normal event.
32
(a)
DTL transit not-my-node ID
RESOURCE UNAVAILABLE
35
(a)
Requested VPCI/VCI not available. This cause indicates that the requested
VPCI/VCI is not available. This can be caused by mismatched VCI ranges
on different ATM switches.
36
(a)
VPCI/VCI assignment failure
2 of 6
578 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-NTWK (ATM Network Error)
Table 189: Error codes and Aux Data values ATM-NTWK (continued)
Cause
Code/
Error
Type
Aux
Data
Cause Codes Description
37
(a)
User Cell Rate not available
38
(a)
Network out of order. This cause indicates that the network is not
functioning correctly and that the condition is likely to last a relatively long
time. (Immediately retrying the call is unlikely to succeed.)
41
(a)
Temporary failure. This cause indicates that the network is not functioning
correctly, but the condition is unlikely to last long. (Immediately retrying the
call is likely to succeed.)
43
(a)
Access information discarded. This cause indicates that the network could
not deliver access information to the remote user as requested (that is, ATM
adaptation-layer parameters, Broadband low-layer information, Broadband
high-layer information, or sub-address as indicated in the diagnostic).
45
(a)
No VPCI/VCI available. This cause indicates that no appropriate VPCI/VCI
is currently available to handle the call.
47
(a)
Resource unavailable, unspecified. When no more specific cause values
apply, this cause reports a resource-unavailable event.
SERVICE OR OPTION UNAVAILABLE
49
(a)
Quality of Service unavailable. This cause reports that the requested
Quality of Service cannot be provided.
51
(a)
User cell rate not available. This cause reports that the requested ATM
Traffic Descriptor is unobtainable.
57
(a)
Bearer capability not authorized. This cause indicates that a
user-requested bearer capability is implemented by the cause-sending
equipment, but the user is not authorized to use the capability.
58
(a)
Bearer capability not currently available. This cause indicates that the
user-requested bearer capability is implemented by the cause-sending
equipment, but the capability is currently unavailable.
63
(a)
Service or option not available, unspecified. When no more specific cause
values apply, this cause reports an unavailable service or option event.
65
(a)
Bearer capability not implemented. This cause indicates that its sending
equipment does not support the bearer capability requested.
73
(a)
Unsupported combination of traffic parameters. This cause indicates that
the combination of traffic parameters contained in the ATM traffic descriptor
information element (IE) is not supported.
3 of 6
Issue 1 June 2005
579
Communication Manager Maintenance-Object Repair Procedures
Table 189: Error codes and Aux Data values ATM-NTWK (continued)
Cause
Code/
Error
Type
Aux
Data
Cause Codes Description
78
(a)
AAL parameters cannot be supported.
INVALID MESSAGES
81
(a)
Invalid call reference value. This cause indicates that its sending
equipment received a message with a call reference that is currently
inactive on the user-network interface.
82
(a)
Identified channel does not exist. This cause indicates that its sending
equipment received a request to use a channel not activated for the call’s
interface.
88
(a)
Incompatible destination. This cause indicates that its sending equipment
received a request to establish a call with either Broadband low-layer
information, Broadband high-layer information, or other compatibility
attributes that cannot be accommodated.
89
(a)
Invalid endpoint reference value. This cause indicates that its sending
equipment has received a message with an endpoint reference that is
currently idle on the user-network interface.
91
(a)
Invalid transit network selection. This cause indicates that a transit network
identification was received in an incorrect format.
92
(a)
Too many pending add-party requests. This cause indicates a temporary
condition when the calling party sends an add-party message, but the
network rejects the message due to full queues.
93
(a)
AAL parameters cannot be supported. This cause indicates that its sending
equipment received a request to establish a call with ATM adaptation-layer
parameters that cannot be accommodated.
PROTOCOL ERROR
96
(a)
Mandatory information element (IE) is missing. This cause indicates its
sending equipment has received a message with a missing IE.
97
(a)
Message type either non-existent or not implemented. This cause indicates
that its sending equipment received a message with an unrecognized type,
either because the type is undefined, or defined but not implemented by the
cause-sending equipment.
4 of 6
580 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-NTWK (ATM Network Error)
Table 189: Error codes and Aux Data values ATM-NTWK (continued)
Cause
Code/
Error
Type
Aux
Data
Cause Codes Description
99
(a)
Information element (IE) either non-existent or not implemented. This
cause indicates that its sending equipment received a message with an
unrecognized IE, either because the IE’s identifier(s) are undefined, or
defined but not implemented by the cause-sending equipment.
This cause indicates that its sending equipment discarded the IE. However,
the equipment could still process the message since this IE was not
required.
100
(a)
Invalid contents in information element (IE). This cause indicates that its
sending equipment received and implemented an IE. However, one or
more of the IE’s fields are coded in a way that the cause-sending
equipment has not implemented.
101
(a)
Message not compatible with call state. This cause indicates receipt of a
message that is incompatible with the call state.
102
(a)
Recovery on timer expiration. This cause indicates that a timer’s expiration
initiated an error-handling procedure.
104
(a)
Incorrect message length
111
(a)
Protocol error, unspecified. When no more specific cause values apply, this
cause reports a protocol-error event.
5 of 6
Issue 1 June 2005
581
Communication Manager Maintenance-Object Repair Procedures
Table 189: Error codes and Aux Data values ATM-NTWK (continued)
Cause
Code/
Error
Type
Aux
Data
Cause Codes Description
257
to
300 (b)
(b)
ATM Impaired Paths
1. Examine the error log (display errors), atm setup-events log
(list measurements atm svc-setup), and atm pnc-latency
(list measurements atm latency) screens to help diagnose the
problem, although the switch could be operating normally. In this
case, you should consider raising the Activation threshold and/or
increasing the Timeout value on the ATM-RELATED System
Parameters screen. (change system atm).
Use list measurements atm svc-setup to see information
about errors associated with connection numbers.
2. After entering the above command, note the time stamps shown in the
list measurements atm setup-events screen. Execute the
above command periodically and note the time stamps. If the time
stamps have changed for a particular From Conn-To Conn pair, this
indicates there are still setup failures/delays for that connection.
3. After verifying that every associated ATM endpoint is operating
correctly, and if errors are still occurring, contact your local service
provider.
301 (c)
ANY
System wide ATM Impaired Paths.
See the suggestions listed above to trouble shoot these errors.
769 (d)
ATM CLP (Cell Loss Priority) Bit Errors
1025 (e)
ATM Congestion Bit Errors
1281 (f)
ATM Cell Underrun Errors
1537 (g)
ATM Cell Overrun Errors
1793 (h)
ATM Lost Cells
6 of 6
582 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-NTWK (ATM Network Error)
Notes:
a. Aux Data values for Setup and Add Party (XX = port network, YYY = location code). Aux
Data values for WSP Setup (XX = WSP number, YYY = location code). Table 190: Location
codes from Aux Data values on page 583 is a list of UNI 3.1 location codes:
Table 190: Location codes from Aux Data values
Setup
(Location
Code)
Add Party
(Location
Code)
WSP Setup
(location
Code)
0
500
800
User
1
501
801
Private network serving the local user
2
502
802
Public network serving the local user
3
503
803
Transit network
4
504
804
Public network serving the remote user
5
505
805
Private network serving the remote user
7
507
807
International network
10
510
810
Network beyond interworking point
Location Code Meaning
b. Error Types 257 to 300: used to determine the destination PNC connection number of an
ATM Network connection that is experiencing an impaired path. The connection number is
obtained by subtracting 256 from the number that is shown in the Error Type field. See the
following example:
If the Error Type field = 263, subtract 256, which equals 7, the PNC destination
connection number.
The Aux Data field contains the originating and destination PN number (XXYY). Where XX
= the originating PN #, and YY = the destination PN # for example:
1. Aux Data = 302
3 = orig
2 = dest
2. Example Aux Data = 1510
15 = orig
10 = dest
c. Error Type 301 indicates that there is a system wide impaired path network problem.
Note:
Note:
Under certain circumstances network errors can be against the ATM EI board.
Issue 1 June 2005
583
Communication Manager Maintenance-Object Repair Procedures
d. Error Type 769: ATM CLP (Cell Loss Priority) Bit Errors
The ATM cell header has a bit called the cell loss priority (CLP) bit. The bit indicates one of
two states: the cell is eligible for discarding, or it is not. In an ATM configuration, every cell
is transmitted into the ATM network with the CLP bit set to 0 indicating that these cells are
NOT eligible for discarding. Should the system ever receive a cell from the ATM network
with the CLP bit set to 1 (discard eligible), an entity in the ATM network modified the bit
during transit. Generally, an ATM network switch sets the CLP bit to 1 (discard eligible) only
if the cell fails to conform to the cell rate specified in the traffic contract for the VC.
However, Communication Manager cell emissions conform with the VC traffic contract.
Therefore, the presence of a non-conforming cell implies that something else in the ATM
network switch is setting the CLP bit in some cells, the ATM switch can also be policing out
(discarding) cells which do not conform to the traffic contract. This error can occur together
with other errors such as:
“Excessive AAL-5 CRC errors” or
“Excessive LAP-D retransmissions”
These errors affect SVCs with Variable Bit Rate (VBRnt) traffic contracts. VBR SVCs
transport system links such as EAL, PACL, and PRI links. Again, this indicates problems
with cell transmissions in the ATM network.
If cell discard is happening generically in the ATM network, other symptoms can affect the
Constant Bit Rate (CBR) SVCs including audible artifacts in talk paths, failure of modems
over voice lines, and “Cell Underruns” - see note (f).
e. Error Type 1025: ATM Congestion Bit Errors
The ATM cell header has a bit called the congestion bit. In Communication Manager ATM,
every cell is transmitted into the ATM network with the congestion bit set to 0 (congestion
not experienced). Should the system ever receive a cell from the ATM network with the
congestion bit set to 1 (congestion experienced), an entity in the ATM network modified the
bit during transit. It simply indicates that the ATM network is experiencing heavy traffic.
During periods of congestion, the ATM network can choose to discard cells even though
those cells conform to their traffic contracts. Should the ATM network discard cells, errors
such as the following can occur:
“Excessive AAL-5 CRC errors”
“Excessive LAP-D retransmissions”.
These errors affect SVCs with Variable Bit Rate (VBRnt) traffic contracts. VBR SVCs
transport system links such as EAL, PACL, and PRI links. Symptoms that can affect the
Constant Bit Rate (CBR) SVCs include audible artifacts in talk paths, failure of modems
over voice lines, and “cell Underruns” – see note (f).
f. Error Type 1281: ATM Cell Underruns
Communication Manager ATM monitors for cell underrun conditions on SVCs with Constant
Bit Rate (CBR) traffic contracts or on ATM CES trunks. In either case, cells are expected to
arrive at a fixed rate. If cells arrive below that rate, an underrun condition exists. The most
likely cause of cell underruns is a problem with cell transmission through the ATM network.
584 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM-NTWK (ATM Network Error)
Possible symptoms include audible artifacts in talk paths and failure of modems over voice
lines. If cell loss is happening generically in the ATM network, other symptoms like
“excessive AAL-5 CRC errors” or “excessive LAP-D retransmissions” are possible on SVCs
with Variable Bit Rate (VBRnt) traffic contracts. The VBR SVCs transport system links such
as EAL, PACL, and PRI links.
Another ATM board within the system originally generated the arriving cells at the specified
traffic contract rate. In order to have arrived at a lower rate, these cells were either slowed
during transmission or possibly discarded by the ATM network. This indicates problems
with cell transmission in the ATM network. Consult the ATM network vendor. Ask about cell
delay variation, cell discard, and traffic policing.
Cell underruns often happen in conjunction with cell overruns. If both occur, it further indicts
the ATM network.
g. Error Type 1537: ATM Cell Overruns
Communication Manager ATM monitors for cell overrun conditions on SVCs with Constant
Bit Rate (CBR) traffic contracts or on ATM CES trunks. In either case, cells are expected to
arrive at a fixed rate. If cells arrive above that rate, an overrun condition exists. The most
likely cause of cell overruns is a problem with cell transmission through the ATM network.
Both cell underruns and overruns are typical symptoms of cell transmission problems like
cell jitter or delay. The ATM board attempts to compensate somewhat by buffering cells.
However, if the ATM network transmission delays are high, the board could conclude that it
has seen a cell overrun because it has exhausted all of its buffer space.
If cell underruns or both cell underruns and overruns occur, indict the ATM network. Consult
the ATM vendor. Ask about cell delay variation, cell discard, and traffic policing.
Another much less likely cause of cell overruns is that an ATM board is generating cells
above the traffic contract rate. Suppose, a board somehow generates cells too quickly. The
ATM network likely reacts by at least setting the CLP bit in the cells that exceed the traffic
contract (see note (d) for ATM CLP errors). The ATM network can also discard the excess
cells.
If only cell overruns occur, locate the ATM board generating those cells. Execute test
board long. If the board passes, then the ATM network remains the likely cause of
transmission problems. Consult the ATM network vendor. Ask about cell delay variation,
cell discard, and traffic policing.
h. Error Type 1793: ATM lost cells:
The ATM board receiving the CBR cell stream is detecting out-of-sequence AAL1 sequence
numbers, above the defined threshold. This normally indicates that the ATM network has
lost the missing cells. In this case, “lost” could mean that the cells were, for example,
policed out, lost to congestion, or misdirected to another endpoint.
The likely user-visible symptoms of lost cells are missing talk paths or poor voice quality.
Issue 1 June 2005
585
Communication Manager Maintenance-Object Repair Procedures
The “lost cells” error can help you diagnose cell underrun problems. When cell underruns
are accompanied by lost cells errors, the lost cells could have caused the underruns. But if
you have cell under runs without lost cells, it could indicate that the underruns were due to
network jitter instead. It is also possible that network jitter can cause both cell underruns
and lost cells, if the jitter is so severe it causes the cells to violate their traffic contract.
When accompanied by congestion or CLP errors, the congestion or CLP can be causing the
lost cells.
When accompanied by cell overrun errors, the cell overruns can be causing the TN2305 to
discard cells, which in turn can show up as lost cells.
Lost cells without other errors can indicate that cells are being corrupted, especially the
AAL1 sequence number.
In any case, consult your ATM network vendor about possible causes. Look for jitter (cell
delay variation), cell discard, and traffic policing.
586 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM PNC-DUP (ATM PNC Duplication)
ATM PNC-DUP (ATM PNC Duplication)
S8700 MC
MO Name in Alarm Log
Alarm
Level
Initial Command to Run
Full Name of MO
PNC-DUP
NA
status pnc
PNC duplication
The PNC-DUP MO tracks the health of the active and standby PNCs, controls planned and
spontaneous interchanges, and manages related functions such as double call refresh and
unrefresh, antithrashing, and so on. The main responsibility of PNC-DUP is to recover the
system to full service in the event of a fault. In the event of multiple faults, PNC-DUP does its
best to maximize service continuity.
Note:
ATM PNC-DUP behaves differently when the system is running the ATM PNC
feature. While not a separate MO, this discussion explains the unique behavior
of PNC-DUP under the ATM PNC feature.
Note:
In critical-reliability systems, the following components comprising the port-network connectivity
(PNC), are duplicated:
●
ATM-Expansion Interface (ATM-EI) circuit packs in port networks (PNs)
●
Fiber-optic cables connecting the above circuit packs to the ATM Switch Interface Modules
●
ATM Switch
Although not part of the PNC, Tone-Clock circuit packs are also duplicated in each PN. ATM
PNC systems can have up to 64 PNs.
PNC duplication architecture utilizes an active/standby duplication scheme in which one
complete set of PNC components supports call processing, while the duplicate PNC is held in
reserve. All calls on the active PNC are simultaneously set up, or shadowed, on the standby
PNC in order for it to be capable of instantly assuming active status when necessary, allowing
for interchanges without service disruption (in the case of single faults).
PNC duplication does not introduce any additional types of hardware or hardware faults, and
there are no tests associated with the PNC-DUP MO. Instead, its error log entries contain
useful information about the occurrence and causes of interchanges in order to facilitate
diagnosis of problems, which can then be addressed by using the documentation for the
individual MO involved.
Issue 1 June 2005
587
Communication Manager Maintenance-Object Repair Procedures
PNC-DUP Related Commands
Table 191: PNC-DUP Commands on page 588 lists the PNC-DUP related commands and their
output forms are fully described in Maintenance SAT Commands in Maintenance Commands
Reference (03-300191).
Table 191: PNC-DUP Commands
Command
Description
status pnc
Shows information about both PNCs’ operational status,
including state of health, alarms, busyouts and locks.
reset pnc interchange
Initiates a demand PNC interchange. If the standby is healthy
(all-zero state-of-health indexes), there is no effect on service.
Otherwise, calls may be dropped.
set pnc
Locks or unlocks the active PNC, preventing interchanges.
Does not interfere with double call setup.
busyout pnc
Removes the standby PNC from service. See also the
section on busyout of PNC components.
Busyouts and PNC-DUP
Busyout pnc puts the standby PNC in the busyout state. In this condition:
●
Double call set up is turned off.
●
The standby PNC is unrefreshed; existing duplicate call connections are removed.
●
PNC interchanges are prevented.
Upon release, interchanges are re-enabled and a global refresh of double call setup on the
standby is performed.
When PNC duplication is in effect:
●
An active PNC component cannot be busied-out.
●
A standby PNC component can only be busied-out when the standby PNC is first
busied-out.
●
The standby PNC cannot be released unless all standby PNC components are released.
588 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
ATM PNC-DUP (ATM PNC Duplication)
Enabling and Removing PNC Duplication
To Enable PNC Duplication
To enable PNC duplication, perform the following sequence of steps:
1. Enable administration of PNC-DUP on the change system-parameters
customer-options screen.
2. Fully administer duplicate ATM PNC connectivity. Verify by list atm pnc. Or for IP
duplication, go to step three.
3. Fully administer IPSI duplication (ipserver-interface duplication). Verify by using
list ipserver-interface.
4. Activate PNC-DUP through the change system-parameters duplication screen.
This is not allowed if any component of either PNC (A or B) is busied out.
5. The system must insert all connectivity-related components for both standby and active
PNC,