AvayaŽ Interactive Response · 2004-05-01 · been certified to meet CTR3 Basic Rate Interface...

Avaya� Interactive Response Release 1.2.1 Alarms and log messages

Issue 1.0 Publication Date: June 2004

Federal Communications Commission Statements © 2004, Avaya Inc. All Rights Reserved Part 15: Class A Statement

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.

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.

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

Avaya Fraud Intervention If you suspect that you are being victimized by toll fraud and you need technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1 800 643 2353 for the United States and Canada. For additional support telephone numbers, see the Avaya Web site:

• answered by the called station, • answered by the attendant, or • routed to a recorded announcement that can be administered by the CPE

user. http://www.avaya.com This equipment returns answer-supervision signals on all direct inward dialed (DID) calls forwarded back to the public switched telephone network. Permissible exceptions are:

Select Support >Escalation Management > International Services.

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.

• A call is unanswered. • A busy tone is received. • A reorder tone is received. Canadian Department of Communications (DOC) Interference Information

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

An �outside party� is anyone who is not a corporate employee, agent, subcontractor, or 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.

European Union Declarations of Conformity

Avaya Inc. declares that the switch 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). This equipment has been certified to meet CTR3 Basic Rate Interface (BRI) and CTR4 Primary Rate Interface (PRI) and subsets thereof in CTR12 and CTR13, as applicable.

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)

Copies of these Declarations of Conformity (DoCs) signed by the Vice President of R&D, Avaya Inc., can be obtained by contacting your local sales representative and are available on the following Web site:

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

http://support.avaya.com

Trademarks Avaya, CONVERSANT, and Intuity are registered trademarks of Avaya, Inc. Adobe and Adobe Acrobat are trademarks or registered trademarks of Adobe Systems, Inc. in the United States and in other countries.

Your Responsibility for Your Company's Telecommunications Security U.S. Robotics and Sportster are registered trademarks of 3Com Corporation or its subsidiaries. The final responsibility for securing both this system and its networked

equipment rests with you - an Avaya customer's 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:

Alliance Generation is a registered trademark and NMS Communications, Natural MicroSystems, AG, Natural Access, NaturalFax are trademarks or service marks of NMS Communications Corporation or its subsidiaries. Informix, DB2 are registered trademarks of IBM Corporation. • Installation documents Microsoft, Windows, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

• System administration documents • Security documents • Hardware-/software-based security tools

Netscape is a registered trademark of Netscape Communications Corporation in the United States and other countries. End-users are not entitled to receive from Netscape any support, warranty, or documentation associated with the Netscape product unless they have paid for such support, warranty or documentation. End user can purchase support from Netscape, at http://help.netscape.com.

• 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 Nuance and Nuance Vocalizer are trademarks of of Nuance Communications, Inc. • any other equipment networked to your Avaya products. Oracle is a registered trademark, and Oracle8i, and Oracle9i are trademarks or registered trademarks of Oracle Corporation Sybase is a trademark of Sybase, Inc.

2 Avaya IR R1.2.1 Alarms and log messages

Speechify, OpenSpeech Server, OpenSpeech Recognizer, and OpenVXI are registered trademarks of SpeechWorks International, Inc. Sun, Sun Microsystems, docs.sun.com, Java, Solaris, Sun Blade, and Sun Fire are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and in other countries.

Technical Support To report problems or to request assistance setting up and using your system, contact the Avaya Technical Services Organization (TSO). The telephone number for support in the United States is 1-800-242-2121. For additional support telephone numbers: • Visit the Avaya Support Centre Web site (http://support.avaya.com). • Select Escalation Management > International Services. 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 Avaya Support Centre Web site http://support.avaya.com.

Ordering Information: Avaya Publications Center Voice: +1 207 866 6701

+1 800 457 1764 (Toll-free, U.S. and Canada only) Fax: +1 207 626 7269

+1 800 457 1764 (Toll-free, U.S. and Canada only) Write: Globalware Solutions

200 Ward Hill Avenue Haverhill, MA 01835 USA Attention: Avaya Account Manager

Web: http://www.avayadocs.com E-mail: [email protected]

Acknowledgment This document was written by the CRM Information Development group.

Issue 1.0 June 2004 3

http://support.avaya.com/

http://support.avaya.com/

Contents

Alarms and log messages ...................................................................................................11

ADMIN alarms and log messages.................................................................................11 ADMIN001 (ADMIN_MSG) .........................................................................................11 ADMIN002 (WEBADM_MSG).....................................................................................12

ALERT alarms and log messages.................................................................................12 ALERT001 (AL_LVL_CHG) ........................................................................................13 ALERT002 (AL_RESET_STATS) ...............................................................................13 ALERT003 (AL_INVALID_THRESHOLD) ..................................................................13 ALERT004 (AL_BAD_THRESH_RULES) ..................................................................14 ALERT005 (AL_THRESHOLDS_CREATED).............................................................14 ALERT006 (AL_THRESHOLDS_CHANGED) ............................................................15 ALERT007 (AL_ALERTER_CMD)..............................................................................15 ALERT008 (AL_ACTIVE)............................................................................................15 ALERT009 (AL_RETIRED).........................................................................................16 ALERT010 (AL_RETIRE_ALARM) .............................................................................16 ALERT012 (AL_THRESHDESC_READ)....................................................................16 ALERT013 (AL_ACTION_CMD).................................................................................17 ALERT014 (AL_DIAL_OUT) .......................................................................................17 ALERT015 (HIGH_TEMP_ALARM)............................................................................17 ALERT016 (FAN_ALARM) .........................................................................................18

ASAI alarms and log messages ....................................................................................18 ASAI001 (A_LINKDWN_PL) .......................................................................................19 ASAI002 (A_LINKDWN_LL) .......................................................................................19 ASAI006 (A_LINKDWN_OK) ......................................................................................20 ASAI008 (A_DSCRIPT_TERM) ..................................................................................20 ASAI010 (A_LOGFAIL_WREST)................................................................................21 ASAI011 (A_LOGFAIL_NOSWR) ...............................................................................21 ASAI012 (A_LOGFAIL_EXACD) ................................................................................22 ASAI013 (A_LOGFAIL_TRBSY).................................................................................22 ASAI015 (A_LOGFAIL_SWOVL)................................................................................23 ASAI016 (A_LOGFAIL_UNKNW) ...............................................................................24 ASAI017 (A_ENFAIL_VCBSY) ...................................................................................24 ASAI018 (A_ENFAIL_INITG)......................................................................................25 ASAI019 (A_ENFAIL_NONEX)...................................................................................26 ASAI020 (A_ENFAIL_SWLMT) ..................................................................................26 ASAI021 (A_ENFAIL_ARMON) ..................................................................................26 ASAI022 (A_ENFAIL_ACVCS) ...................................................................................27 ASAI023 (A_ENFAIL_SWOVL) ..................................................................................27 ASAI024 (A_ENFAIL_UNKNW)..................................................................................28 ASAI025 (A_RESTART) .............................................................................................28 ASAI026 (A_NOEVRP)...............................................................................................28


Contents

ASAI027 (A_PROT_ERR) ..........................................................................................29 ASAI028 (A_LOGIN_OK)............................................................................................29 ASAI029 (A_ENREQ_OK)..........................................................................................30 ASAI030 (A_UNK_RET) .............................................................................................30 ASAI031 (A_UNK_CTL)..............................................................................................31 ASAI032 (A_DSC_MSGS)..........................................................................................31

AVB alarms and log messages .....................................................................................32 AVB001 (AVB_COPYRIGHT).....................................................................................32 AVB002 (AVB_PARSE_ERROR)...............................................................................32 AVB003 (AVB_ERROR) .............................................................................................33 AVB004 (AVG_PLATFORM) ......................................................................................33 AVB005 (AVB_MISSINGURL)....................................................................................34 AVB006 (AVB_EXCEPTION) .....................................................................................34 AVB007 (AVB_BADGRAMMAR) ................................................................................35 AVB008 (AVB_BADINPUTRETURN) .........................................................................35 AVB009 (AVB_BADRECORD) ...................................................................................36 AVB010 (AVB_BADPROMPT) ...................................................................................36 AVB011 (AVB_BADPROPERTY) ...............................................................................36 AVB012 (AVB_SEMANTICERROR)...........................................................................37 AVB013 (AVB_LOG) ..................................................................................................37

BKRST alarms and log messages ................................................................................38 BKRST001 (BKDONE) ...............................................................................................38 BKRST002 (BKBADNFSMNT) ...................................................................................38 BKRST003 (BKBADDIR) ............................................................................................38 BKRST004 (BKCANCEL) ...........................................................................................39 BKRST005 (BKWRITEFAIL).......................................................................................39 BKRST007 (BKSTARTED).........................................................................................40 BKRST008 (BKFAILED) .............................................................................................40 BKRST010 (BKNOSPACE) ........................................................................................41 BKRST011 (BKREMDONE) .......................................................................................41 BKRST012 (BKREMFAIL) ..........................................................................................42 BKRST013 (RSTDONE) .............................................................................................42 BKRST014 (RSTFAIL)................................................................................................42

BRDG alarms and log messages..................................................................................43 BRDG001 (BRDG_MSGRCV)....................................................................................43 BRDG002 (BRDG_MSGSND) ...................................................................................43 BRDG003 (BRDG_SYSTBL) ......................................................................................44 BRDG004 (BRDG_NOMEM)......................................................................................44 BRDG005 (BRDG_NOCHAN) ....................................................................................45

CDH alarms and log messages ....................................................................................46 CDH005 (CDHSUM)...................................................................................................46 CDH006 (CCASUM) ...................................................................................................47 CDH007 (CDHSUM)...................................................................................................47 CDH008 (CDHDEL) ....................................................................................................48 CDH009 (CCADEL) ....................................................................................................48 CDH012 (CDH_UPL_FAILED.....................................................................................49


Contents

CDH015 (CDH_NO_PARM) .......................................................................................49 CGEN alarms and log messages..................................................................................50

CGEN001 (UNEXPMSG)............................................................................................50 CGEN002 (CGEN_SYSTBL) ......................................................................................51 CGEN003 (CGEN_NOMSGQ) ...................................................................................52 CGEN004 (CGEN_MSGRCV) ....................................................................................52 CGEN005 (CGEN_MSGSND) ....................................................................................52 CGEN006 (CGEN_INIT) .............................................................................................53 CGEN007 (CGEN_NOMEM) ......................................................................................54 CGEN008 (CGEN_NOTR)..........................................................................................55 CGEN009 (CGEN_NOSP)..........................................................................................55 CGEN010 (CGEN_NOT1) ..........................................................................................56 CGEN011 (CGEN_TRFAIL) .......................................................................................56 CGEN012 (CGEN_TRERR) .......................................................................................56 CGEN013 (CGEN_SPFAIL) .......................................................................................57 CGEN015 (CGEN_T1FAIL) ........................................................................................57 CGEN016 (CGEN_T1ERR) ........................................................................................58 CGEN017 (CGEN_NOSAVE).....................................................................................58 CGEN018 (CGEN_TRHWFAIL) .................................................................................58 CGEN020 (CGEN_NOSERVE) ..................................................................................59 CGEN021 (CGEN_NOCHAN) ....................................................................................59 CGEN022 (CGEN_NORESTRICT) ............................................................................60 CGEN023 (CGEN_DEFOWN)....................................................................................61 CGEN024 (CGEN_EXECFAIL) ..................................................................................61 CGEN025 (CGEN_REGFORMAT).............................................................................62 CGEN026 (CGEN_NOIDLE) ......................................................................................63 CGEN029 (CGEN_CHANBUSY)................................................................................63 CGEN030 (CGEN_CHANSNORM) ............................................................................63 CGEN031 (CGEN_SETGRP) .....................................................................................64 CGEN032 (CGEN_FORMAT).....................................................................................64 CGEN035 (CGEN_LBOLT) ........................................................................................65 CGEN036 (CGEN_RTUINFO)....................................................................................65 CGEN040 (CGEN_INVALID_CFG) ............................................................................66 CGEN043 (CGEN_MIRROR_ERROR) ......................................................................66

CHRIN alarms and log messages.................................................................................66 CHRIN001 (CI_NORESET) ........................................................................................67 CHRIN002 (CI_ASAIOPEN) .......................................................................................67

CTI DIP log messages ..................................................................................................67 CTI005 (CTI_GENERIC).............................................................................................68 CTI008 (CTI_NO_QKEY)............................................................................................69

DB alarms and log messages .......................................................................................69 DB003 (DB MSGRCV)................................................................................................69 DB004 (DB_SQL_EX).................................................................................................70 DB005 (DB_GENERIC) ..............................................................................................70 DB006 (DB_PORT_IN_USE)......................................................................................71 DB007 (DB_PORT_UNAVAIL) ...................................................................................71


Contents

DB008 (DB_LOST_CONN).........................................................................................72 DB009 (DB_NEW_PORT) ..........................................................................................73 DB010 (DB_INFO)......................................................................................................73

DIP alarms and log messages ......................................................................................73 DIP001 (VS_BUG)......................................................................................................74 DIP002 (SCRIPT_ERR)..............................................................................................74

DSKMG alarms and log messages ...............................................................................74 DSKMG001 (DSKMSG_SYSFL) ................................................................................75 DSKMG002 (DSKMSG_RSV) ....................................................................................75

FXAUD alarms and log messages ................................................................................76 FXAUD002 (NOT_INITSF) .........................................................................................76

FXMON alarms and messages .....................................................................................77 FXMON004 (NOT_INITSF).........................................................................................77 FXMON011 (NOTFINDLOG)......................................................................................77 FXMON035 (FXINITGROUPFAIL) .............................................................................77 FXMON039 (FXRTUPROBLEM)................................................................................78

GEN alarms and log messages ....................................................................................79 GEN001 (SYSERR)....................................................................................................79 GEN002 (SYSMSG) ...................................................................................................79 GEN020 (LG_NUMARGS)..........................................................................................80 GEN022 (LG_BADCMD) ............................................................................................80 GEN050 (LG_CHG_VALUE) ......................................................................................80

HOST alarms and messages ........................................................................................81 HOST001 (HOST_NORESP) .....................................................................................81 HOST002 (HOST_EXPSCR)......................................................................................82 HOST003 (HOST_RESET).........................................................................................82 HOST004 (HOST_FAILACT)......................................................................................83 HOST005 (HOST_NOPOLL) ......................................................................................85 HOST006 (HOST_UNKNOWN)..................................................................................86 HOST007 (HOST_WRITE) .........................................................................................86 HOST008 (HOST_OFFSYNC) ...................................................................................87 HOST009 (HOST_LOGIN) .........................................................................................88 HOST010 (HOST_DEFINE) .......................................................................................88 HOST011 (HOST_HELPER) ......................................................................................89 HOST012 (HOST_SESSION).....................................................................................89 HOST013 (HOST_DOWN) .........................................................................................90 HOST014 (HOST_UP)................................................................................................91 HOST015 (HOST_HIBERNATE) ................................................................................92 HOST016 (HOST_BRDOPEN)...................................................................................92 HOST017 (HOST_INRECOV) ....................................................................................93 HOST018 (HOST_OUTRECOV) ................................................................................94

INIT alarms and log messages .....................................................................................94 INIT001 (INIT_NODBFILE) .........................................................................................94 INIT005 (INIT_CANT_SAVE)......................................................................................95 INIT008 (INIT_AUTOCLEAN) .....................................................................................95


Contents

INIT009 (INIT_MANUALREN) ....................................................................................96 LOG alarms and log messages.....................................................................................96

LOG001 (LG_START_LOG).......................................................................................96 LOG002 (LG_END_LOG) ...........................................................................................97 LOG006 (LG_GL_INVALID_MSG) .............................................................................97 LOG007 (LG_LOGDAEMON).....................................................................................98

MTC alarms and log messages ....................................................................................99 MTC002 (MTC_STATE_EVENT) ...............................................................................99 MTC003 (MTC_STATE_ALARM) ...............................................................................99 MTC004 (MTC_DIAG_START) ................................................................................100 MTC005 (MTC_DIAG_PASS)...................................................................................100 MTC006 (MTC_DIAG_FAIL).....................................................................................100 MTC007 (MTC_REQ_FAIL)......................................................................................101 MTC009 (MTC_LOAD_FAIL)....................................................................................101 MTC017 (MTC_RESPAWN).....................................................................................102

NMS alarms and log messages ..................................................................................102 NMS001 (NMS_INTERNAL_ERROR)......................................................................102 NMS002 (NMS_GENERIC_ERROR) .......................................................................103 NMS004 (NMS_API_FAIL) .......................................................................................103 NMS003 (NMS_OBJECT_FAIL)...............................................................................103 NMS005 (NMS_TRUNK_EVENT) ............................................................................104 NMS007 (NMS_BOARD_CONFIG)..........................................................................105

PROXY alarms and log messages..............................................................................106 PROXY001 (PX_BROKEN_SOCKET) .....................................................................106 PROXY002 (PX_SERVER_FILE_ERROR)..............................................................107 PROXY003 (PX_SYS_MUTEX_FAILURE) ..............................................................107 PROXY004 (PSYS_VSYS_QKEY_ERROR)............................................................108 PROXY005 (PX_MAINT_STATE_CHANGE) ...........................................................108 PROXY006 (PX_SYS_THREAD_ERROR) ..............................................................109 PROXY007 (PX_SERVER_OOS) ............................................................................109 PROXY008 (PX_SEND_FAILURE) ..........................................................................110 PROXY009 (PX_UNRECOGNIZED_MESSAGE) ....................................................110 PROXY010 (PX_ALL_SRV_PORTS_OOS) .............................................................111 PROXY011 (PX_GENERAL_FAILURE)...................................................................111 PROXY012 (PX_RTU_FAILURE).............................................................................112 PROXY013 (PX_SRV_TIMEOUT)............................................................................112

RECOG alarms and log messages .............................................................................112 RECOG001 (RECOG_MSGRCV) ............................................................................113 RECOG002 (MSG_SEND) .......................................................................................113 RECOG004 (RECOG_GRAMERR)..........................................................................113

SYS alarms and log messages ...................................................................................114 SYS001-SYS157 ......................................................................................................114

THRESH alarms and log messages............................................................................114 THRESH001 (THRESH_INFO) ................................................................................114 THRESH002 [THRESH_MINOR] ............................................................................115


Contents

THRESH003 [THRESH_MAJOR].............................................................................116 THRESH004 [THRESH_CRITICAL] .........................................................................116

TRACE alarms and log messages ..............................................................................117 TRACE001 (TRACE_GEN) ......................................................................................117

TSM alarms and log messages...................................................................................117 TSM002 (TSM_LOADSCR) ......................................................................................117 TSM003 (SPBUSY) ..................................................................................................118 TSM004 (TSM_SPUNAVAIL) ...................................................................................119 TSM008 (TSM_RTU_BUSY) ....................................................................................120 TSM009 (NO_RTU) ..................................................................................................120 TSM010 (TSM_QFLUSH).........................................................................................121 TSM012 (TSM_NOEXTFUNC) .................................................................................121 TSM013 (TSM_NOPROG) .......................................................................................121

TTS alarms and log messages ...................................................................................122 TTS002 (TTS_BADFILE) ..........................................................................................122 TTS003 (TTS_TRACE).............................................................................................123 TTS004 (TTS_NOTINIT)...........................................................................................123 TTS005 (TTS_MSGFAIL) .........................................................................................124 TTS006 (TTS_CONNFAIL).......................................................................................124 TTS007 (TTS_STATECHARGED) ...........................................................................125 TTS008 (TTS_NORESOURCE) ...............................................................................125 TTS009 (TTS_MGRFAIL) .........................................................................................126 TTS010 (TTS_ADDFAIL)..........................................................................................126

UNIX alarms and log messages..................................................................................127 UNIX001 (UNIX_NOTICE)........................................................................................127 UNIX002 (UNIX_WARNING) ....................................................................................127 UNIX003 (UNIX_TROUBLE) ....................................................................................128 UNIX004 (UNIX_CRITICAL) .....................................................................................128 UNIX005 (UNIX_INFO).............................................................................................128 UNIX006 (UNIX_ERROR) ........................................................................................129

VOIP alarms and log messages..................................................................................129 VOIP001 (VOIP_ENABLED_CALL_PROC) .............................................................130 VOIP002 (VOIP_DISABLED_CALL_PROC) ............................................................130 VOIP003 (VOIP_CONFIG_ERROR) ........................................................................131 VOIP004 (VOIP_NETWORK_ERROR) ....................................................................131 VOIP005 (VOIP_REMOTE_ERROR).......................................................................132 VOIP006 (VOIP_MEDIA_ERROR) ...........................................................................133 VOIP007 (VOIP_OAM_ERROR) ..............................................................................133 VOIP008 (VOIP_SIGNAL_ERROR) .........................................................................133 VOIP009 (VOIP CALL_ERROR) ..............................................................................134 VOIP010 (VOIP_CALL_FORCE_CLEARED)...........................................................135

VROP alarms and log messages ................................................................................136 VROP011 (VROP_NBUFS] ......................................................................................136 VROP014 (VROP_FSFAIL) ......................................................................................136 VROP018 (VROP_MALLOC) ...................................................................................137


Contents

Index ....................................................................................................................................138


Alarms and log messages

When the Avaya IR system has problems or errors, it generates a system message. System messages are used to alert you to problems, potential problems, or a change in the state of the system. These messages are collected in the Message Log Report screen of the Web Administration tool.

You administer the destination, threshold, and priority of each message individually using the Message administration screens of the Web Administration tool.

Alarms and log messages generally describe the actions to take regarding these system-reported troubles. If the action requires you to contact your remote maintenance service center, this means one of the following:

• If you are a field technician supporting a customer per a maintenance agreement or a time and material charge basis, you are the remote maintenance service representative. If the problem is more serious than you can handle, contact the next level of support or Avaya for assistance.

• If you are a support person assisting an end customer, you are the remote maintenance service representative. If you cannot solve the problem, contact the Technical Support Center (TSC) at 1-800-242-2121 for assistance.

• If you are a customer, contact the TSC at the number shown above.

ADMIN alarms and log messages ADMIN messages track voice system administration tasks.

ADMIN001 (ADMIN_MSG)

Alarm level

None.



Description

This message informs you that administrative command of interest has been issued. The message body shows:

• The process and login ID that invoked the command

• The full text of the command

• The result, if possible

Action

If the body of the message says to look for a disposition message, check for a subsequent ADMIN001 message with the same process ID, login ID, and command text.

ADMIN002 (WEBADM_MSG)

Alarm level

None.

Description

This message shows a command run from web administration. The message body shows the:

• Login ID of the user who is logged into web administration and invoked the command

• The process java and process ID.

• Full text of the command

Action

None.

ALERT alarms and log messages The Avaya IR system generates ALERT alarms and log messages to:

• Report the workings of the Alerter process

• Identify when threshold levels are reached


ALERT alarms and log messages

ALERT001 (AL_LVL_CHG)

Alarm level

None.

Description

This message indicates a threshold level change for the included message. The action taken by the Alerter when a threshold change occurs is defined by how the message is configured. Check the Message Administration screen (Configuration Management > Message Administration) to view the how the message is set up.

Action

No corrective action is necessary.

ALERT002 (AL_RESET_STATS)

Alarm level

None.

Description

The Alerter has received a command to reset its statistics.

Action


ALERT003 (AL_INVALID_THRESHOLD)

Alarm level

None.

Description

The Alerter has received a command to print or reset an invalid threshold. The cause is that an invalid threshold was entered by a user at the Alerter command interface.



Action


ALERT004 (AL_BAD_THRESH_RULES)

Alarm level

None.

Description

The Alerter failed to convert the indicated threshold rules file to Alerter thresholds for voice system messages. Thresholding for voice system messages will not function.

Note: If no thresholds were specified, this message can be ignored.

Repair procedure

To restore thresholding:

1. Restore the identified thresholds rules file, using a system backup.

2. If no valid backup exists, reinstall the system software.

ALERT005 (AL_THRESHOLDS_CREATED)

Alarm level

None.

Description

The Alerter created the indicated number of message thresholds from the thresholds rules file.

Action




ALERT006 (AL_THRESHOLDS_CHANGED)

Alarm level

None.

Description

The Alerter updated message thresholds from the threshold rules file.

Action


ALERT007 (AL_ALERTER_CMD)

Alarm level

None.

Description

The Alerter has received the command indicated by the message.

Action


ALERT008 (AL_ACTIVE)

Alarm level

None.

Description

The Alert is active.



Action


ALERT009 (AL_RETIRED)

Alarm level

None.

Description

The Alert is retired.

Action


ALERT010 (AL_RETIRE_ALARM)

Alarm level

None.

Description

The alarm identified by the Alert has been retired.

Action


ALERT012 (AL_THRESHDESC_READ)

Alarm level

None.

Description

The threshold description was read successfully by the Alerter.



Action


ALERT013 (AL_ACTION_CMD)

Alarm level

None.

Description

The action in the command specified by the Alerter has been taken.

Action

Take action based on the cited command and your requirements.

ALERT014 (AL_DIAL_OUT)

Alarm level

None.

Description

An informational message was generated by the Alerter.

Action


ALERT015 (HIGH_TEMP_ALARM)

Alarm level

Major.



Description

This alarm indicates an overheating problem in the system. It occurs when the CPU temperature exceeds the value in the Maximum Allowable Temperature field in the Dialout parameters screen of Web Administration. The default value is 55 degrees Centigrade.

Action

The message displays the current CPU temperature and the limit.

1. Make sure the limit is not less than 55 degrees Centigrade.

2. If the limit is less than 55 degrees Centigrade, set it higher. If not, shut down the machine until the source of the overheating problem can be determined.

ALERT016 (FAN_ALARM)

Alarm level

Major.

Description

This alarm indicates that one of the fans in the system is not operating at full capacity. An overheating problem could occur.

Action

Shut down system and have the fans repaired.

ASAI alarms and log messages The Avaya IR system generates Adjunct Switch Application Interface (ASAI) alarms and log messages to report workings of ASAI links including problems with connections that support the feature.


ASAI alarms and log messages

ASAI001 (A_LINKDWN_PL)

Alarm level

Critical.

Description

The ASAI physical link has gone down. All ASAI-provided services will not function until the link has been re-established.

Repair procedure

Note: If message ASAI025 on page 28 follows this message, no corrective action is necessary.

To correct the problem and remove the alarm:

1. Contact your remote maintenance service center for assistance.

2. Check the ASAI link wiring between the Avaya IR system and the PBX for proper connection.

3. Go to the ASAI Parameters screen (Feature Packages > ASAI Administration > Parameters) and make sure that the:

― Status in the CONNECT Event field is connected

― Correct ID is selected in the Node ID field

4. Make sure that another Avaya IR system is not using the same node ID.

ASAI002 (A_LINKDWN_LL)

Alarm level

Critical.

Description

The ASAI physical link is up, but the ASAI environment cannot be set. All ASAI-provided services will not function until the link has been re-established.




Repair procedure:



2. Check with your PBX administrator to ensure that the ASAI port on the PBX has been administered with Fixed TEI=y and TEI=3.

3. Go to the ASAI Parameters screen (Feature Packages > ASAI Administration > Parameters) and make sure that the:

― Status in the CONNECT Event field is connected

― Correct ID is selected in the Node ID field

4. Make sure that another Avaya IR system is not using the same NODE_ID.

ASAI006 (A_LINKDWN_OK)

Alarm level

None.

Description

The ASAI link should be up and running.

Repair procedure


ASAI008 (A_DSCRIPT_TERM)

Alarm

Major.



Description

The data-only voice response application running on the specified virtual channel has stopped abruptly. This may indicate a problem with the service assigned to the domain. All ASAI messages related to that domain are lost.

Repair procedure

No immediate action is necessary, as the application will restart automatically. Make sure the application has restarted.

ASAI010 (A_LOGFAIL_WREST)

Alarm level

Major.

Description

The IR system agent on the specified channel could not be logged in. As a result, Automatic Call Distribution (ACD) will not route calls to this channel. The extension assigned to the channel on the IR system is incorrect.

Repair procedure



2. Correct the extension assigned to the specified channel.

3. Consult your PBX administrator to verify that the channel extension is a member of the ACD split.

ASAI011 (A_LOGFAIL_NOSWR)

Alarm level

Major.



Description

The IR system agent on the specified channel could not be logged in. As a result, the ACD will not route calls to this channel. The login request cannot be executed due to lack of switch resources.

Repair procedure

If message ASAI028 on page 29 follows this message, no corrective action is necessary. Otherwise, consult your PBX administrator.

ASAI012 (A_LOGFAIL_EXACD)

Alarm level

Major.

Description

The IR system agent on the specified channel could not be logged in. As a result, Automatic Call Distribution (ACD) will not route calls to this channel. The problem is that the extension assigned to the specified channel on the IR system is not a member of the ACD split.

Repair procedure

Have the PBX administrator add the extension to the ACD split.

ASAI013 (A_LOGFAIL_TRBSY)

Alarm level

Major.

Description

The IR system agent on the specified channel could not be logged in. As a result, Automatic Call Distribution (ACD) will not route calls to this channel.

The specified extension currently has an active call.



Repair procedure




2. Log the channel out.

3. Retry the login request.

ASAI015 (A_LOGFAIL_SWOVL)

Alarm level

Critical.

Description

The IR system agent on the specified channel could not be logged in. As a result, Automatic Call Distribution (ACD) will not route calls to this channel.

Switching equipment congestion exists. The switch is not accepting the request at this time because of processor overload.

Repair procedure


To correct the problem:


2. Suggest that the adjunct or user retry the request later.

3. If the problem persists, consult your PBX administrator.



ASAI016 (A_LOGFAIL_UNKNW)

Alarm level

Major.

Description

The IR system agent on the specified channel could not be logged in due to an unknown error. As a result, Automatic Call Distribution (ACD) will not route calls to this channel.

Repair procedure




2. Suggest that the adjunct or user retry the request later.

3. If the problem persists, consult your PBX administrator.

ASAI017 (A_ENFAIL_VCBSY)

Alarm level

Critical.

Description

The ASAI domain with the specified extension cannot be activated. Information about the call placed to this domain will not be reported to the service assigned to this domain. Either the virtual channels are unavailable or they are all busy.


Repair procedure

Caution: This repair procedure requires you to stop the voice system. Stopping the voice



system ends call processing. Stop the voice system at times of little or no call activity, or re-route calls to agents or to another IR system.



2. Stop the voice system.

3. Edit the file /vs/data/irAPI.rc:

a) If a VCHANS=32 entry exists, change the number 32 to 40.

b) If a VCHANS entry does not exist, add the line VCHANS=32.

4. Start the voice system.

ASAI018 (A_ENFAIL_INITG)

Alarm level

Major.

Description

The ASAI domain with the specified extension cannot be activated. Information about the call placed to this domain will not be reported to the service assigned to this domain. The domain is in an initialization state.


Repair procedure



2. Verify that the correct service has been assigned to the specified domain by taking these actions:

a) Disable the domain.

b) Enable the domain.



ASAI019 (A_ENFAIL_NONEX)

Alarm level

Major.

Description

The ASAI domain with the specified extension cannot be activated. Information about the call placed to this domain will not be reported to the service assigned to this domain. The extension corresponding to the specified ASAI domain is non-existent on the PBX.

Repair procedure

Consult your PBX administrator to add the specified domain to the PBX.

ASAI020 (A_ENFAIL_SWLMT)

Alarm level

Major.

Description

The ASAI domain with the specified extension cannot be activated. Information about the call placed to this domain will not be reported to the service assigned to this domain. The switch limit for the maximum number of monitored domains has been exceeded.

Repair procedure

If message ASAI029 on page 30 for the same domain follows this message, no corrective action is necessary. Otherwise, consult your PBX administrator.

ASAI021 (A_ENFAIL_ARMON)

Alarm level

Major.



Description

The ASAI domain with the specified extension cannot be activated. Information about the call placed to this domain will not be reported to the service assigned to this domain. The specified ASAI domain is already monitored by another adjunct.

Repair procedure

If message ASAI029 on page 30 follows this message for the same domain, no corrective action is necessary. Otherwise, the adjunct that monitors the domain has to disable the domain before the voice system can monitor it.

ASAI022 (A_ENFAIL_ACVCS)

Alarm level

Major.

Description

The ASAI domain with the specified extension cannot be activated. Information about the call placed to this domain will not be reported to the service assigned to this domain. The specified ASAI domain may be either an adjunct- or vector-controlled split.

Repair procedure

If message ASAI029 on page 30 follows this message for the same domain, no corrective action is necessary. Otherwise, consult your PBX administrator to make sure that the domain extension is neither an adjunct-controlled nor a vector-controlled split.

ASAI023 (A_ENFAIL_SWOVL)

Alarm level

Critical.

Description

The ASAI domain with the specified extension cannot be activated. Information about the call placed to this domain will not be reported to the service assigned to this domain. Switching equipment congestion exists. The switch is not accepting the request at this time because of processor overload.



Repair procedure

If message ASAI029 on page 30 follows this message for the same domain, no corrective action is necessary. Otherwise, consult your PBX administrator.

ASAI024 (A_ENFAIL_UNKNW)

Alarm level

Major.

Description

The ASAI domain with the specified extension cannot be activated due to an unknown error. Information about the call placed to this domain will not be reported to the service assigned to this domain.

Repair procedure

If message ASAI029 on page 30 follows this message for the same domain, no corrective action is necessary. Otherwise, consult your PBX administrator.

ASAI025 (A_RESTART)

Alarm level

None.

Description

The ASAI link has been established. All ASAI-provided services will start to function now.

Repair procedure


ASAI026 (A_NOEVRP)

Alarm level

Major.



Description

The service assigned to the voice system agent on the specified channel requested call information from the ASAI feature that was not available. The call information about the call that is terminated to the specified channel has not arrived yet.

Repair procedure


1. Verify that the ACD split with the service voice system has been administered and is in service.

2. Verify that the PBX extension-to-channel assignments have been correctly administered.

ASAI027 (A_PROT_ERR)

Alarm level

Minor.

Description

ASAI protocol errors have been detected. An occasional report does not indicate a serious problem.

Repair procedure

Check the integrity of the cabling of the ASAI link.

ASAI028 (A_LOGIN_OK)

Alarm level

None.

Description

The voice system agent on the specified channel has been logged in. The ACD will start routing calls to this channel.

Repair procedure




ASAI029 (A_ENREQ_OK)

Alarm level

None.

Description

The ASAI-administered domain with the specific extension is activated now. The CTI feature will not function.

Repair procedure


ASAI030 (A_UNK_RET)

Alarm level

Major.

Description

Unexpected routing messages for which there is no administered RTE domain have been received over the ASAI link. If an administered domain were available, event messages would have been sent to the assigned service. Since no service is available, the voice system discards the messages. The error message in the log indicates how many messages were discarded over a one minute period.

Repair procedure


1. Check with your PBX administrator to verify that the PBX has been correctly administered.

2. Go to the Add ASAI Domain screen (Feature Packages > ASAI Administration > Domains >Add ASAI Domain) and add an RTE domain with the specified extension.

3. Go to the Enable ASAI Domain screen (Feature Packages > ASAI Administration > Domains >Enable ASAI Domain) and enable the RTE domain you added.



ASAI031 (A_UNK_CTL)

Alarm level

Minor.

Description

Unknown messages for which there is no administered CTL domain are received over the ASAI link. If an administered domain were available, event messages would have been sent to the assigned service. Since no service is available, the voice system discards the messages. The error message in the log indicates how many messages were discarded over a one minute period. This does not indicate a serious problem.

Repair procedure

No corrective action is necessary. However, to prevent these messages from appearing:

1. Go to the Add ASAI Domain screen (Feature Packages > ASAI Administration > Domains >Add ASAI Domain) and add a CTL domain with the specified extension.

2. Go to the Enable ASAI Domain screen (Feature Packages > ASAI Administration > Domains >Enable ASAI Domain) and enable the CTL domain you added.

ASAI032 (A_DSC_MSGS)

Alarm level

Major.

Description

The voice system has discarded messages that were received over the ASAI link for the specified domain. This is because the messages were not processed fast enough by the specified ASAI application. The ASAI application is not fully functional. Calls are not being processed.

Repair procedure


1. Display ASAI domains (Feature Packages > ASAI Administration > Domains > Display > Display Domains) to verify that the correct service has been assigned to the specified domain.



2. If the correct service is not assigned to the domain, go to the Change ASAI Domains screen (Feature Packages > ASAI Administration > Domains > Change Domain) and make the required assignment.

3. If the problem persists, contact the ASAI application developer for further assistance.

There may be an error in the ASAI application specified in the message.

AVB alarms and log messages The Avaya IR system generates AVB alarms and log messages to report problems with the Avaya VoiceXML Browser (AVB) software feature.

AVB001 (AVB_COPYRIGHT)

Alarm level

None.

Description

Copyright notices.

Repair procedure


AVB002 (AVB_PARSE_ERROR)

Alarm level

Major.

Description

VoiceXML parse error: %s<<type,S>>, where type contains further information.

Repair procedure

Based on information in type from above, make the appropriate corrections to the VoiceXML document. For information about creating VoiceXML applications, see the Avaya IVR Designer Help for VXML Applications.


AVB alarms and log messages

AVB003 (AVB_ERROR)

Alarm level

Major

Description

ERROR: %s<<type,S>>, where type contains further details.

Repair procedure


1. Based on the information in type, make appropriate changes to the VoiceXML document.

For information about creating VoiceXML applications, see the Avaya IVR Designer Help for VXML Applications.

2. If the message indicates badfetch, check the name in the URL attribute and verify that Web connection is established.

AVB004 (AVG_PLATFORM)

Alarm level

Major

Description

Platform error: %s<<type,S>>, where type contains further details.

Repair procedure

Caution: This repair procedure requires you to stop the voice system. Stopping the voice system ends call processing. Stop the voice system at times of little or no call activity, or re-route calls to agents or to another IR system.


1. Stop and start the voice system.



2. If the problem persists, reboot the system.

AVB005 (AVB_MISSINGURL)

Alarm level

Major.

Description

No initial URL %s<<type,S>>.

Repair procedure


1. Verify that applDispatch.vxml file is in /vs/data/vxml.

2. Verify that the testClient.vxmlURL parameter in /vs/data/vxml/default.cfg contains the correct location for the applDispatch.vxml file.

3. Verify that the applDispatch.vxml file is free of errors.

AVB006 (AVB_EXCEPTION)

Alarm level

Major.

Description

Exception in document %s<<type,S>> reason %s<<type,S>>.

Repair procedure

Review the VoiceXML document for errors based on information provided in the error message. For information about creating VoiceXML applications, see the Avaya IVR Designer Help for VXML Applications.



AVB007 (AVB_BADGRAMMAR)

Alarm level

Minor.

Description

Bad grammar: %s<<type,S>>.

Repair procedure

Review the grammar in the VoiceXML document for errors.

To find grammar problems:

1. Log in as root.

2. At the command prompt, enter sproxyadm -r all -D 5 to increase the debug level for the speech proxy.

For more information about the srproxyadm command, see sproxyadm command.

3. Run a trace command with the process specified as ASRPROXYMGR.

For more information about the trace command, see trace command.

4. Reproduce the problem, review the trace command output, and look for grammar errors (search for PROXY).

AVB008 (AVB_BADINPUTRETURN)

Alarm level

Major.

Description

Message in Recognition interface, Unable to process answer: %s<<type,S>>.

Repair procedure


1. Look for further speech recognition errors.

2. Verify the connection between the IR system and the speech recognition server.



AVB009 (AVB_BADRECORD)

Alarm level

Major

Description

Record failed: %s<<type,S>>.

Repair procedure

Contact your field support representative.

AVB010 (AVB_BADPROMPT)

Alarm level

Major.

Description

Prompt failed: %s<<type,S>>.

Repair procedure

1. Look for TTS alarms and log messages on page 122 and take action based on your findings.

2. If no TTS alarms and messages appear, or if suggested repair procedures do not resolve the problem, verify the connection between the IR system and the speech recognition server.

AVB011 (AVB_BADPROPERTY)

Alarm level

Minor.



Description

Invalid <property>: %s<<type,S>>.

Repair procedure

Review the VoiceXML document for errors. For information about creating VoiceXML applications, see the Avaya IVR Designer Help for VXML Applications.

AVB012 (AVB_SEMANTICERROR)

Alarm level

Minor.

Description

Semantic error: %s<<type,S>>.

Repair procedure

Review the VoiceXML document for errors. Pay particular attention to javascript statements. For information about creating VoiceXML applications, see the Avaya IVR Designer Help for VXML Applications.

AVB013 (AVB_LOG)

Alarm level

None.

Description

A VoiceXML script has used the <log> element to place a message into the system event log.

Action

None.



BKRST alarms and log messages BKRST alarms and messages report events and problems with system backup and restore processes. For example, a backup may have started, failed, or gone to a bad directory.

BKRST001 (BKDONE)

Alarm level

None.

Description

The backup process is complete.

Action

No action is necessary.

BKRST002 (BKBADNFSMNT)

Alarm level

None.

Description

The mount directory provided for backups is not usable because it is either not mounted or not an NFS directory. The backup process will not be completed.

Repair procedure

Make sure that the specified directory is an NFS directory and that it is mounted.

BKRST003 (BKBADDIR)

Alarm level

None.


BKRST alarms and log messages

Description

The mount directory provided for backups is not mounted, and the backup process cannot change to the required directory. The backup process will not be completed.

Repair procedure

Make sure that the mount point specified directory is mounted, and that you can use the cd command to change to the mount directory.

BKRST004 (BKCANCEL)

Alarm level

None.

Description

The identified backup process has been cancelled.

Action

No action is required.

BKRST005 (BKWRITEFAIL)

Alarm level

None.

Description

The backup process cannot write to the mount point.

Repair procedure

Make the mount directory writable by ensuring that it is:

• An NFS directory



• Mounted

• Accessible through the LAN

BKRST007 (BKSTARTED)

Alarm level

None.

Description

The specified backup process has started.

Action

No action is necessary.

BKRST008 (BKFAILED)

Alarm level

Major.

Description

The specified backup process failed. Backup processes can fail for a variety of reasons.

Repair procedure

To resolve the problem:

1. Go to the Message Log Report screen (Reports > Message Log Report) and check for messages such as BKBADNFSMNT, BKBADDIR, and BKWRITEFAIL.

2. Take action based any messages that you find and the related repair procedures.

3. If no messages identify the problem, determine whether the ulimit on the backup NFS system is adequate.


BKRST alarms and log messages

a) Check on whether an archive file was created.

b) If an archive file was created, compare the size of that file to the ulimit.

c) If the archive file is equal in size to the ulimit, increase the ulimit.

BKRST010 (BKNOSPACE)

Alarm level

None.

Description

There is not enough space on the backup mount point to complete the backup.

Repair procedure

Free up space or direct backup processes to another mount point.

BKRST011 (BKREMDONE)

Alarm level

None.

Description

A backup archive has been successfully deleted.

Action

None.



BKRST012 (BKREMFAIL)

Alarm level

None.

Description

The deletion procedure for a backup archive failed.

Repair procedure

Make sure that the directory for the deletion was specified correctly.

BKRST013 (RSTDONE)

Alarm level

None.

Description

Avaya IR system records have been restored from an archive.

Action

None.

BKRST014 (RSTFAIL)

Alarm level

None.


BRDG alarms and log messages

Description

Restoration of files from archive failed.

Repair procedure

Make sure that the correct directory is specified for the archive.

BRDG alarms and log messages The Avaya IR system generates BRDG alarms and log messages to report various failures of the Call Bridge feature. Bridging is controlled by the xferdip command and processes.

BRDG001 (BRDG_MSGRCV)

Alarm level

Major.

Description

The Call Bridge feature failed to communicate with the voice system during call processing. The application is unable to bridge calls. The xferdip process cannot receive the message required to start the call transfer.

Repair procedure


Stop and start the voice system. If the problem does not clear, contact your Avaya support representative.

BRDG002 (BRDG_MSGSND)

Alarm level

Major.



Description

The Call Bridge feature failed to communicate with the voice system during call processing. The application is unable to bridge calls because xferdip process cannot send the message required to start the call transfer.

Repair procedure



BRDG003 (BRDG_SYSTBL)

Alarm level

Major.

Description

The xferdip process cannot attach to shared system memory. The application is unable to bridge calls.

Repair procedure



BRDG004 (BRDG_NOMEM)

Alarm level

Major.


BRDG alarms and log messages

Description

The xferdip process cannot allocate the memory required to start the call transfer. The application is unable to bridge calls.

Repair procedure

Stop and start the voice system. If the problem does not clear, contact your Avaya support representative. If messages appear frequently, the IR system may be overloaded, degrading system performance.

BRDG005 (BRDG_NOCHAN)

Alarm level

Minor.

Description

The xferdip process cannot find an available channel. The Call Bridge feature failed to find an available channel in the equipment group specified in the message. The application may not be able to complete the call bridge. The impact may be significant if the message occurs more frequently than the currently set threshold limit. In that case, you will see a threshold message similar to the following:

*C THR004 The first threshold level for BRDG_NOCHAN exceeded. 10 messages have been generated in the last 5 minutes.

The limits and message priority shown above reflect the default values for this threshold message.

Repair procedure


1. Go to the Display Equipment screen (Configuration Management > Voice Equipment > Display Equipment).

2. Verify that all channels:

― Are assigned to the equipment group specified by the voice response application bridge instruction.

― Assigned to the specified equipment group are in service.



3. If necessary, go to the Channels to Groups screen (Configuration Management > Voice Equipment > Channels to Groups) and make corrections to the assignment of equipment groups.

4. Determine if all the channels assigned in the specified equipment group are often busy:

a) To view system operations, type sysmon page_number and press Enter.

page_number specifies the number of pages you want to view.

b) Observe system operations long enough to assess the level of business for channels in the equipment group.

5. If all channels assigned to the equipment group are often busy, go to the Channels to Groups screen (Configuration Management > Voice Equipment > Channels to Groups) and assign another equipment group to the channels to increase capacity.

6. If busy channels are not an issue, make another bridging request through the xferdip process after a channel is available.

CDH alarms and log messages CDH alarms and log messages report events and problems associated with processes related to building Call Data Handling reports.

CDH005 (CDHSUM)

Alarm level

Major.

Description

The IR system cannot summarize CDH records. There is no impact on call processing, but CDH reports will not be built.

Possible reasons for the failure are:

• A CDH DIP is not configured in the /vs/data/ldbdip.rc file.

• The connection to the remote database failed.

• An SQL exception occurred.


CDH alarms and log messages

Repair procedure


1. Make sure that the CDH DIP is configured in the ldbdip.rc file.

2. If the CDH DIP is configured correctly, check the connection to the remote database.

3. If the connection to the remote database is operating and the application for the database is ORACLE, go the Message Log Report screen (Reports > Message Log Report), and check for messages regarding SQL exceptions.

4. If SQL exceptions have occurred, take action to correct them.

When an SQL exception occurs, the text of the message about the event specifies the action to take.

Any SQL exception reported during execution of cdhsum will be logged. You can use the logCat command to read the compressed files.

5. If the above actions do not resolve the problem, contact your Avaya support representative for assistance.

CDH006 (CCASUM)

Alarm level

Major.

Description

The IR system cannot summarize CCA records. There is no impact on call processing, but CDH reports will not be built.

Repair procedure

Same as CDH005 on page 46.

CDH007 (CDHSUM)

Alarm level

Major.



Description

The IR system cannot summarize traffic records. There is no impact on call processing, but CDH reports will not be built.

Repair procedure


CDH008 (CDHDEL)

Alarm level

Major.

Description

The IR system cannot delete Call Data Handling (CDH) records from the database. There is no impact on call processing, but CDH reports will not be built.

Repair procedure


CDH009 (CCADEL)

Alarm level

Major.

Description

The IR system cannot delete Call Classification Analysis (CCA) records from the database. There is no impact on call processing, but CDH reports will not be built.

Repair procedure



CDH alarms and log messages

CDH012 (CDH_UPL_FAILED

Alarm level

Major.

Description

The upload of the call data records failed. There is no impact on call processing, but CDH reports will not be built.

Repair procedure


CDH015 (CDH_NO_PARM)

Alarm level

Major.

Description

The IR cannot read the CDH parameters. There is no impact on call processing, but CDH reports will not be built.

The CDH DIP may not be configured in the /vs/data/ldbdip.rc file, or a java exception may have occurred when the /vs/data/ldbdip.rc file was read.

Repair procedure

If CDH is configured, use the logCat command to check the log for a java exception error. Then contact your Avaya support representative for assistance.



CGEN alarms and log messages The Avaya IR system generates CGEN alarms and log messages to report problems with internal voice processes, generally serious problems that greatly reduce function of the system.

CGEN001 (UNEXPMSG)

Alarm level

Minor.

Description

An internal voice system process received an unexpected message from the process identified in this message. The message has been ignored.

Repair procedure



1. Identify the source of the unexpected message.

This information is in the generated message.

2. If the source of the unexpected message is an application data interface process (DIP), contact the application developer.

3. If the source of the unexpected message is not a DIP, stop and start the voice system.

4. If the problem persists, confirm that all installed system software packages are compatible with the installed version of the IR system software package.

5. Remove any software package that is incompatible and install the proper version.


CGEN alarms and log messages

CGEN002 (CGEN_SYSTBL)

Alarm level

Major.

Description

The voice system table named in the message is corrupted or cannot be accessed by the source of the message. System functionality is severely impaired.

Repair procedure



1. Go to the Feature Licensing screen (Configuration Management > Feature Licensing) and make sure that the number of channels installed on the Avaya IR system is a legal configuration.

If the number of assigned channels exceeds the licensed number, system functions may be affected. If you have exceeded the number of licensed channels, you will need to contact your Avaya support representative to purchase more channels.

2. If the number of assigned channels is within parameters, check the name of the voice system table (table_name).

3. If table_name is devtbl, take these actions

a) Stop the voice system.

b) Move the devtbl to another area.

For example, type mv /vs/shmem/devtbl.old and press Enter.

c) Start the voice system.

Warning: This procedure causes all system configuration information, such as switch administration and service assignments, to be lost. When the voice system is restarted, the system configuration uses the default settings.

4. If table_name is anything other than devtbl, take these actions:



a) Stop the voice system.

b) Start the voice system.

5. If the problem persists, reboot the operating system.

CGEN003 (CGEN_NOMSGQ)

Alarm level

Critical.

Description

An internal voice system process cannot communicate with other internal voice system processes. System functionality is severely impaired.

Repair procedure

Reboot the operating system.

CGEN004 (CGEN_MSGRCV)

Alarm level

Critical.

Description

An internal voice system process cannot communicate with other internal voice system processes. System functionality is severely impaired.

Repair procedure

Reboot the operating system.

CGEN005 (CGEN_MSGSND)

Alarm level

Critical.



Description

The voice system cannot communicate with the specified process. System functionality is severely impaired. If the reason given for this message is EAGAIN, an interprocess communication message queue capacity across all processes on the voice system is being exceeded. When this happens, all processes may have trouble communicating with one another. The process listed in the message may or may not be the process that caused the problem. If the receiving process (the process which failed to get the message) is not handling incoming messages often enough, it may be the only process affected.

Repair procedure

• If the receiving process listed is a voice response application DIP, test the voice response application to determine why the process is getting behind in reading its message queue.

• If the receiving process is a voice system process (for example, VROP, MTC, TSM, etc.) then it is more likely that all processes are having trouble communicating, and call handling will be severely impaired until the problem is resolved.

• To gather data about this problem for later analysis, take these actions:

a) Type cd /usr/install and press Enter.

b) Type sar > sar.out and press Enter.

c) Type ps -ef > ps.out and press Enter.

d) Type ipcs -qop > ipcs.out and press Enter.

e) Reboot the operating system.

• If the reason for the message is EAGAIN, and you have recently added hardware to the system, check the circuit card to ensure that the card recently added has a unique index. For example, make sure that there are not two cards that have the same switch setting.

• If the problem persists, follow the trouble escalation procedure and inform personnel that you have collected the data listed in steps a-e above.

CGEN006 (CGEN_INIT)

Alarm level

Critical.



Description

A system process has trouble initializing. Voice operations may be impaired or may not function at all.

Repair procedure

Contact your Avaya support representative.

CGEN007 (CGEN_NOMEM)

Alarm level

Critical.

Description

The voice system failed to allocate memory internally for data. System functionality is severely impaired.

Repair procedure





3. If the problem still persists, contact field support as needed and take action based on the situation:

― If the message reports that space for a file /vs/trans/script.D could not be allocated, then there may be a large number of script.D files in /vs/trans. Remove any script.D files that are no longer needed and ensure that the script.D files that are needed have not been corrupted.

― If the error message was reported by CDH, type /vs/bin/newscript and press Enter. This command causes the Call Data Handling function to re-read all the /vs/trans/script.D files.



― If the error was reported by one of the reporting programs (cddrot or cdrpt), rerun the report.

― If the error persists, the IR system may be making excessive demands on memory, or there may be a process memory leak that requires examination. Check memory resources.

CGEN008 (CGEN_NOTR)

Alarm level

Major.

Description

The voice system failed to open a required card driver. System cards are unusable.

Repair procedure

• If this problem occurs because a driver was purposely removed and you do not wish to reinstall it, renumber the voice channels.

• If the problem persists, contact field support.

CGEN009 (CGEN_NOSP)

Alarm level

Major.

Description

The voice system failed to open or attach a card driver. System cards are unusable.

Repair procedure

Contact your field support representative.



CGEN010 (CGEN_NOT1)

Alarm level

Major.

Description

The voice system failed to open a card driver. System cards are unusable.

Repair procedure

Same as CGEN008 on page 55.

CGEN011 (CGEN_TRFAIL)

Alarm level

Critical.

Description

The voice system failed to perform the indicated function on the voice channel or card specified. System functionality is severely impaired.

Repair procedure


CGEN012 (CGEN_TRERR)

Alarm level

Major.

Description

The voice system failed to perform the indicated function on the voice channel or card specified. Functionality is impaired.



Repair procedure


CGEN013 (CGEN_SPFAIL)

Alarm level

Major.

Description

The voice system failed to perform the indicated function on the card specified. System functionality is severely impaired.

Repair procedure


1. If any feature packages have been removed from the system recently, verify that any related cards and functions have been unassigned from the application.

If feature packages are not unassigned, the card that handled the functions may come up in the BROKEN state.

2. Make any required changes in feature package assignment.

3. If the card remains in the BROKEN state, try to restore the card or contact your Avaya support representative.

CGEN015 (CGEN_T1FAIL)

Alarm level

Critical.

Description

The voice system failed to perform the indicated function on the voice channel or card specified. System functionality is severely impaired.

Repair procedure




CGEN016 (CGEN_T1ERR)

Alarm level

Major.

Description

The voice system failed to perform the indicated function on the voice channel or card specified. Card functionality is impaired.

Repair procedure


CGEN017 (CGEN_NOSAVE)

Alarm level

Major.

Description

The system was unable to save configuration changes made by the user (for example, voice response application assignments to a channel, or card remove/restores) on disk. Shared memory updates will be lost when system is rebooted. Call processing is not affected until then.

Repair procedure


1. Reboot the operating system.

2. If the problem persists, restore the system from backup files.

CGEN018 (CGEN_TRHWFAIL)

Alarm level

Major.



Description

A hardware failure has been detected on the voice channel or circuit card specified. Card functionality is impaired.

Repair procedure


CGEN020 (CGEN_NOSERVE)

Alarm level

Critical.

Description

An incoming call has not been processed because no service was assigned to the specified channel or the dialed number identification service (DNIS).

Repair procedure


1. Determine how calls on the channel indicated by the message should be routed to services.

Calls can be routed based on channel number or DNIS.

2. If calls should be routed based on channel number, assign the appropriate services (voice response application) to the channel.

3. If calls should be routed based on DNIS, assign DNIS service to the channel.

CGEN021 (CGEN_NOCHAN)

Alarm level

Critical.

Description

An internal software error occurred when describing channel characteristics to the Resource Manager. The identified channel is unusable.



Repair procedure



1. If the error is EINVAL, take these actions:

a) Go to the Feature Licensing screen (Configuration Management > Feature Licensing) and make sure that the number of cards installed is a legal configuration.

If too many channels are configured, the EINVAL error may occur.

b) Renumber the voice channels.

2. If the problem persists, or if the error is not EINVAL, stop and start the voice system.

3. If the problem still persists, reboot the operating system.

4. Contact your Avaya support representative if rebooting does not resolve the problem.

CGEN022 (CGEN_NORESTRICT)

Alarm level

Minor.

Description

The voice system failed to reset the restriction list for a channel. System functionality may be impaired if applications are assigning resource restrictions to channels (irRestrictResource(3irAPI)).

Repair procedure



1. Make sure AD or the customized default owner is run as root.



2. If AD or the customized default owner is run as root, stop and start the voice system.


4. If the problem still persists, contact your remote maintenance service center.

CGEN023 (CGEN_DEFOWN)

Alarm level

Major.

Description

A channel was returned to the default owner because of an abrupt exit of the prior channel owner. This message may indicate an IRAPI application failed to release (irDeinit(3irAPI)) prior to exit (2) or an IRAPI application core dump. Any outstanding activities on the channel are cancelled and the channel is made available to take new calls.

If a transient IRAPI process does not wait for an IRE_DEINIT_DONE event before exiting, a CGEN023 alarm will be generated. The IRAPI process must call (void) irSetEvent(cid, IRE_DEINIT_DONE, IRF_NOTIFY); to the IRE_DEINIT_DONE event to be generated.

Repair procedure


CGEN024 (CGEN_EXECFAIL)

Alarm level

Critical.

Description

The voice system service provided by the identified process has failed to start up. The result is that an incoming call has not been processed.

Repair procedure

Caution: This repair procedure requires you to stop the voice system. Stopping the voice



system ends call processing. Stop the voice system at times of little or no call activity, or re-route calls to agents or to another IR system.


1. If the messages indicate that the process is a permanent process, take these actions:

a) Type ps -ef and press Enter to determine whether the process is running.

b) If the process is running, type ls -l process and press Enter to check that the identified process exists and that it is executable.

c) If the process is executable, make sure that the service assigned to the channel is a valid by entering display service.

d) If the service is on the list, it is a valid service.

e) If the service is not on the list, reassign the service.

2. If the messages indicate that the process is a not a permanent process, take these actions.

a) Stop and start the voice system.

b) If the problem persists, make sure that the process is correctly entered in the /etc/inittab file.

CGEN025 (CGEN_REGFORMAT)

Alarm level

Critical.

Description

A voice system service registration file has a bad format or is the wrong version. The service corresponding to this registration file may be started incorrectly and, therefore, not function properly.

Repair procedure

• If the service indicated in the message is a TSM service, verify and install the service.

• If the service indicated in the message is not a TSM service, the registration file should be rebuilt by typing defService service where service is the service specified in the message.



CGEN026 (CGEN_NOIDLE)

Alarm level

None.

Description

Timeout on attempt to idle channel.

Repair procedure

No corrective action is immediately necessary. Automatic recovery occurs within 60 seconds.

If this event occurs frequently, or if resources are under-utilized, which will be reported by other messages, then stop and start the voice system.

CGEN029 (CGEN_CHANBUSY)

Alarm level

Minor.

Description

In-service channels occupancy off high water mark.

Repair procedure


CGEN030 (CGEN_CHANSNORM)

Alarm level

None.



Description

The voice system detected that the occupancy of the in-service channels is below the high water mark.

Repair procedure


CGEN031 (CGEN_SETGRP)

Alarm level

Major.

Description

An internal software error occurred when describing an equipment group to the Resource Manager. Applications that use the equipment group identified in the message may not function correctly.

Repair procedure





3. If the problem still persists, see the Avaya IVR Designer Help for TAS Applications or the Avaya IVR Designer Help for VXML Applications help for more information about the specific error listed in the reason text.

CGEN032 (CGEN_FORMAT)

Alarm level

Critical.



Description

A voice system file is corrupted and cannot be accessed by the internal voice system process that describes channel and card characteristics to the Resource Manager. Circuit card resources cannot be accessed. Functions provided by cards are not available. Voice coding and playback are not available for systems that require an NMS card for these services.

Repair procedure


CGEN035 (CGEN_LBOLT)

Alarm level

Major.

Description

A reboot of the system should be scheduled to occur within the number of days specified. Otherwise, an automatic reboot will occur. By manually performing the reboot, it may be possible to reduce the impact service caused by the reboot.

Repair procedure

Reboot the system at a time of low system activity.

CGEN036 (CGEN_RTUINFO)

Alarm level

None.

Description

The voice system detected the indicated Feature Licensing values for the function.

Repair procedure




CGEN040 (CGEN_INVALID_CFG)

Alarm level

Critical.

Description

The voice system detected an invalid configuration. System functionality is impaired.

Repair procedure


CGEN043 (CGEN_MIRROR_ERROR)

Alarm level

Major

Description

The system has found disk mirroring problems that could not be fixed. The alarm message indicates which disk has failed.

Repair procedure

Check the error log at /vs/mirror/elog. If one of the hard disk drives has failed, replace the drive.

CHRIN alarms and log messages CHRIN alarms and log messages report events and problems with Avaya IR system db_init processes, which initialize and activate the trace facility. Data interface processes (DIPs) call db_init once at the start to set up the trace mechanism provided by the system.


CTI DIP log messages

CHRIN001 (CI_NORESET)

Alarm level

Critical.

Description

The dbinit process is unable to initialize with the Resource Manager.

Repair procedure

Reboot the Avaya IR system. If rebooting does not clear the problem, contact your Avaya support representative.

CHRIN002 (CI_ASAIOPEN)

Alarm level

Major.

Description

The dbinit process cannot open the asai table. ASAI connections may experience problems, or may not work at all.

Repair procedure

Reboot the Avaya IR system. If rebooting does not clear the problem, contact your Avaya support representative.

CTI DIP log messages The CTI DIP writes error messages into the Message Log report.



CTI005 (CTI_GENERIC)

Alarm level

None.

Description

All CTI exceptions are logged using this message type. The message text at the end is usually self-explanatory. Typical messages and suggested repair procedures are shown in the table that follows.

Messages Recommended Actions CTI_LOST_CONN � Lost connection to JtapiServer

or

Error while trying to write to socket

JtapiServer is the java process which communicates with the telephony server.

Run ps �ef|grep ctidip, two processes should get listed.

1.ctidip, 2.java �cp� -Dpname=ctidip

If process 2 is not running, run /vs/java/run_cti from the command line.

ProvShutdownEvent raised for provider

The network connection between the Avaya IR and Tserver is down.

Verify the following:

• Tserver in question is powered up • Tserver and Avaya IR are both connected

to the network • Service is running on the CVCT server

(check Telephony Services Controller) • Try to ping the server

ProvInServiceEvent raised for provider

No action is required. The Telephony Server was successfully connected to.

Extension does not belong to this provider

The extension does not exist in the Telephony Server database. Use Telephony Services Admin and add the extension to the security database.

Action

Take action based on the message text. If the text is not clear to you, contact your Avaya support representative.


DB alarms and log messages

CTI008 (CTI_NO_QKEY)

Alarm level

None.

Description

The CTI DIP process could not obtain a required system resource (qkey). The CTI DIP process will not complete. The message text and suggested repair procedures are shown in the table that follows.

Messages Recommended Actions Cannot get Qkey for ctidip Check if this problem occurs

after restarting the voice system. Run the top command to check whether there is enough free memory.

Try to run /vs/bin/vrs/ctidip from the command line. If this runs without any error messages, the next time you restart the voice system, the ctidip will start correctly.

Repair procedure

If the recommended actions do not clear the problem, contact your Avaya support representative.

DB alarms and log messages DB alarms and log messages report events and problems with remote databases.

DB003 (DB MSGRCV)

Alarm level

Major.



Description

The Call Data Handler (CDH) failed to communicate to the voice system. The traffic data may not be recorded correctly. There is no impact on call processing.

Repair procedure

Reboot the system.

DB004 (DB_SQL_EX)

Alarm level

None.

Description

All SQL exceptions are logged using this type of message. The text at the end of the message provides an explanation of the exception.

Repair procedure

If the explanatory text is not clear to you, contact your Avaya support representative.

DB005 (DB_GENERIC)

Alarm level

None.

Description

All java exceptions are logged using this type of message. The text at the end of the message provides an explanation of the exception.

Repair procedure

If the explanatory text is not clear to you, contact your Avaya support representative.


DB alarms and log messages

DB006 (DB_PORT_IN_USE)

Alarm level

None.

Description

The administered port is already in use.

Repair procedure

No action required.

DB007 (DB_PORT_UNAVAIL)

Alarm level

None.

Description

None of the ports in the range administered for JDBCDIP processes are available for use. (The port range includes the administered ports and an additional five ports.)

Repair procedure


1. Type netstat-a | grep portn and press Enter to determine whether other processes are using the administered port range.

n represents the port number.

If the identified port is not in use, there will be no output in response to the command.

2. If other processes are using the administered port range, go to the JDBC Administration - Edit screen (Configuration Management > JDBC Administration - Main > select desired DIP) and reassign an unassigned port to the process.

3. Return to the JDBC Administration - Main screen and select Restart to restart the DIP.

Note: If the IR system consistently experiences problems with unavailable ports, contact your Avaya support representative for assistance.



DB008 (DB_LOST_CONN)

Alarm level

Major.

Description

The JDBC feature controls interactions with remote databases. This message indicates that the JDBCDIP process has lost its connection to the JDBCSERVER process.

Repair procedure


1. To check for a java process, type ps-ef|grep ais number and press Enter for each DB DIP.

number stands for the number of the DIP.

2. If the IR system displays a java process, no further action is necessary.

3. If the IR system does not display a java process, test the connection to the database with one of the following methods:

― Use the dbconfig command line tool.

― Go to the JDBC Administration - Edit screen (Configuration Management > JDBC Administration - Main > select the desired DIP) and click Test.

4. If the connection passes the test, take these actions:

a) Type tail -f /vs/java/jdbc.err and press Enter to tail the /vs/java/jdbc.err file.

b) Look for any exceptions.

c) Contact your Avaya support representative to share information and receive assistance.

5. If the connection does not pass the test, troubleshoot the connection.


DIP alarms and log messages

DB009 (DB_NEW_PORT)

Alarm level

None.

Description

The administered port for the database DIP is not available, so the DIP is using the next administered port.

Action

No action required.

DB010 (DB_INFO)

Alarm level

None.

Description

This message is an informational message regarding database dip status, such as database dip connection status.

Repair procedure

No corrective action is necessary. See Administering the JDBC database interface for more information.

DIP alarms and log messages The Avaya IR system generates Data Interface Process (DIP) alarms and log messages to report DIP process failures.



DIP001 (VS_BUG)

Alarm level

None.

Description

Error in software.

Repair procedure

When this error is logged, the Message Log Report screen contains additional text indicating the nature of the problem. Examples include the following:

DCDIP: VS startup failed

DCDIP: Cannot attach shared memory

This alarm occurs when there is an internal software error. Go to the Message Log Report screen (Reports > Message Log Report) and check messages. Then contact your remote maintenance service center for assistance.

DIP002 (SCRIPT_ERR)

Alarm level

Major

Description

Error in voice response application.

Repair procedure

Contact the person responsible for developing voice response applications.

DSKMG alarms and log messages The Avaya IR system generates DSKMG alarms and log messages to report file access failures that affect speech or data operations.


DSKMG alarms and log messages

DSKMG001 (DSKMSG_SYSFL)

Alarm level

Major.

Description

The indicated file cannot be accessed for the reason specified in the message. Applications that need to reserve speech files may fail.

Repair procedure

To resolve the problem, take action based on the message:

• If the reason field indicates that the file or directory cannot be created, take the following actions:

a) At the system prompt, type df -v and press Enter to see if the speech file system is out of space.

b) Note the resulting message.

c) If the free space is less than three percent, contact your remote maintenance service center.

• If the reason field indicated a failure on a library call, make sure that the IRAPI libraries libirAPIt.so and libirEXT.so exist in the /usr/lib directory.

The Introduction to the IRAPI section of this online help contains important information about a change to the IRAPI library that may affect IRAPI applications.

• If the reason field indicates a system call failure, reboot the system.

DSKMG002 (DSKMSG_RSV)

Alarm level

Major.

Description

The indicated file cannot be reserved or accessed for the reason specified in the message. Applications requiring recording to the file will be incomplete.



Repair procedure


• If the reason field indicates that the file or directory cannot be created, check to see if the speech file system is out of space:

a) At the system prompt, type df -v and press Enter.

b) Note the resulting message.

c) If the free space in /voice1 is less than three percent, contact your remote maintenance service center.

d) If there is space on the device, remove files to free up the inodes.

The problem may be that there are no inodes left on the system.

• If the reason field indicated a failure on a library call, make sure the IRAPI libraries libirAPIt.so and libirEXT.so exist in the /usr/lib directory.

• he Introduction to the IRAPI section of this online help contains important information about a change to the IRAPI library that may affect IRAPI applications.

• If the reason field indicates a system call failure, reboot the system.

FXAUD alarms and log messages The Avaya IR system generates FXAUD alarms and log messages to report messages and problems with FAX on Audix.

FXAUD002 (NOT_INITSF)

Alarm level

None.

Description

An error occurred initializing the softFax process, and the FAX operation will not work. The reason is identified in the message.

Repair procedure

Contact your remote maintenance service center for assistance.


FXMON alarms and messages

FXMON alarms and messages The Avaya IR system generates FXMON alarms and log messages to report fax maintenance updates and alarms.

FXMON004 (NOT_INITSF)

Alarm level

None.

Description

The FAX maintenance process could not initialize softFAX.

Repair procedure

Contact your remote maintenance service center for assistance.

FXMON011 (NOTFINDLOG)

Alarm level

Minor.

Description

The FAX maintenance process cannot open the designated file for the outstanding FAX operation.

Repair procedure

Verify the existence of the file.

FXMON035 (FXINITGROUPFAIL)

Alarm level

None.



Description

The system was unable to place a call in a given group for the reason specified in the message.

Repair procedure



1. Go to the Display Equipment screen (Configuration Management > Voice Equipment > Display Equipment) to verify that the group listed in the message exists and has some channels in it.

2. If the group does not have channels in it, assign channels to the equipment group.

3. If the problem persists, stop and start the voice system.

4. If the problem still persists, contact your Avaya support representative.

FXMON039 (FXRTUPROBLEM)

Alarm level

None.

Description

The necessary resources to handle the FAX could not be allocated.

Repair procedure


1. Go to the Feature Licensing screen (Configuration Management > Feature Licensing) and verify that the number of right-to-use (RTU) FAX licenses is sufficient.

2. If you require additional FAX licenses, contact your Avaya support representative to purchase them.

3. If licenses are not an issue, go to the Display Equipment screen (Configuration Management > Voice Equipment > Display Equipment) to determine whether:

― The card that handles FAXes is in service.


GEN alarms and log messages

― Channels are in service

― FAX service is assigned to the channel or channels.

4. If FAX service is not assigned to the channel or channels, assign it.

5. If the channels or the card are not in service, try to restore them or contact your Avaya support representative.

GEN alarms and log messages The Avaya IR system generates GEN alarms and log messages to report updates and problems with internal voice system processes.

GEN001 (SYSERR)

Alarm level

None.

Description

An internal voice system process has encountered a general error described in the message text. System functionality is impaired.

Repair procedure


GEN002 (SYSMSG)

Alarm level

None.

Description

An internal voice system process has logged general status information with this message.

Repair procedure




GEN020 (LG_NUMARGS)

Alarm level

None.

Description

An internal voice system process has received a command with the incorrect number of arguments. The source of the message is Alerter, which indicates that a user command was issued with incorrect arguments. The command has been ignored.

Repair procedure


GEN022 (LG_BADCMD)

Alarm level

None.

Description

An internal voice system process has received a command that it does not recognize. If the source of the command is the Alerter, the message indicates that a user command was badly formed or unrecognized by the Alerter. The command has been ignored.

Repair procedure


GEN050 (LG_CHG_VALUE)

Alarm level

None.


HOST alarms and messages

Description

An internal voice system process has received a command to change one of its internal parameters. The name of the parameter and its old and new values are printed in the message.

Repair procedure


HOST alarms and messages The Avaya IR system generates HOST alarms and log messages to report problems communicating with a host system.

HOST001 (HOST_NORESP)

Alarm level

Major.

Description

The application cannot reach the host to get data for the call. One of these problems exists:

• There is a mismatch between the IR system configuration for the host and the actual host configuration.

• The host connection is down, or the host is down.

• The host has not responded within the Initial Timeout specified in the application for a Send Host Screen action.

Repair procedure


• Ensure that the host connection is operating and that the IR system host configuration agrees with the actual host configuration.

• Evaluate connections between the IR system and the host.

A noisy connection may cause the host to retransmit screens excessively, resulting in slow response times from the host. Or, the connection may need to be upgraded.



• Check the timeout values in the application. See the Avaya IVR Designer Help for TAS Applications or the Avaya IVR Designer Help for VXML Applications for more information.

HOST002 (HOST_EXPSCR)

Alarm level

None.

Description

The applications cannot get correct data for the call. The host has sent an unexpected screen within the Unrecognized Screen Timeout specified in the application for a Get Host Screen action.

For some applications, unexpected screens are part of the normal flow of the application and can be ignored. However, for other applications, this might show that either the application is not recognizing the screen sent by the host or the host is taking too long to respond with the expected screen.

Repair procedure

For many applications, no corrective action is necessary. If the message persists, check the logic in the voice response application. See the Avaya IVR Designer Help for TAS Applications or the Avaya IVR Designer Help for VXML Applications for more information.

HOST003 (HOST_RESET)

Alarm level

Critical.

Description

The application cannot access the host to get data for calls. One of these problems exists:

• There is a mismatch between the IR voice system and the actual host configuration.

• The host is down, or the connection to the host is down.

• The application running on the host (for example, CICS or TSO) is down.



• There is a logic problem in the host application.

Repair procedure

To restore the connection to the host:

1. Check configuration settings and network conditions:

― Check that configuration settings in both systems are correct and make any required changes.

― Check with your LAN administrator to ensure that the connection between the host and the IR system is operating, and that the host is not down.

2. Reset the connection with the host:

a) Type stop_hi and press Enter to stop the host.

b) Type start_hi and press Enter to restart the host.

3. Free a session of the card by typing hfree session_number and pressing Enter.

session number represents the session you want to free.

4. The system displays a message saying whether the hfree command succeeded or failed.

5. Type sb_te session_numbers and press Enter to start the 3270 Terminal Emulation software.

The Terminal Emulator (TE) displays the current screen of the LU. The 3270 status line appears at the bottom of the screen to inform you whether or not the host is active. Refer to documentation for your host system for more information about 3270 screens and status lines.

If the problem is with the application, check and re-check screen definitions, make corrections, and test the application as needed. See the Avaya IVR Designer Help for TAS Applications or the Avaya IVR Designer Help for VXML Applications for more information.

HOST004 (HOST_FAILACT)

Alarm level

Major.

Description

The application cannot access the host to get data for the call. One of these problems exists:



• The keyboard is locked.

• The session is owned by someone else.

• The configuration of the host on the IR system is incorrect, or the configuration of the IR system on the host is incorrect.

• The host connection is down, or the host itself is down.

Repair procedure


1. If the keyboard is locked or you cannot access the host, take these actions:

a) Free a session of the card by typing hfree session_number and pressing Enter.

The system displays a message saying whether the hfree command succeeded or failed.

b) Type sb_te session_numbers and press Enter.

You are asked to press Enter to display the screen currently in use by the sessions.

c) Press the key configured as the 3270 reset key to unlock the keyboard.

It is likely that the application assigned to that session at one point sent a screen at an inappropriate time, causing the host to lock the keyboard.

2. If communication with the host is not restored, take the following actions:



3. If the session is owned by someone else, type ps ef and press Enter.

The system checks if another program, like the terminal emulator or file transfer program, is using the session.

4. If another program or programs are using the session, take these actions:

a) Terminate the program that is using the session.

b) Reassign the application to the session by typing hassign session_number and pressing Enter.

5. Make sure that the session has been configured for a host Licensed Unit (LU).



HOST005 (HOST_NOPOLL)

Alarm level

Major.

Description

The application cannot access the host on the specified session to get data for the call. The host has stopped polling or checking the voice system. One of these problems exists:

• Host sessions are recovering or logging in.

• There is a mismatch between the voice and host configurations.

• The host is down or the host connection is down.

Repair procedure


1. Go to the Message Log Report screen (Reports > Message Log Report) and check for a HOST017 on page 93 message.

2. If no HOST17 message appears in the Message Log Report screen, type hstatus and press Enter to determine if the sessions are recovering or logging in.

3. If the sessions are recovering or logging in, wait until this process is complete.

No additional steps are necessary.

4. If the sessions are not recovering or logging in, wait until a HOST017 message appears in the message log, and then reset the host connection:

a) Type stop_hi and press Enter to stop the host.

b) Type start_hi and press Enter to restart the host.

5. If the problem persists, type hfree session_number and press Enter to free the specified session of the card.

The system displays a message reporting the success or failure of the hfree command.

6. Type sb_te session_numbers and press Enter.

The Terminal Emulator (TE) displays the current screen of the Licensed Unit (LU). The 3270 status line appears at the bottom of the screen to inform you whether or not the host is active.

7. If the host connection is not restored, check configuration settings and network conditions:





HOST006 (HOST_UNKNOWN)

Alarm level

Critical.

Description

The applications cannot access the host to get data for calls. There is no cable, dialup, or session connection to the host.

Repair procedure


• Check that configuration settings in both systems are correct and make any required changes.

• Check with your LAN administrator to ensure that the connection between the host and the IR system is operating, and that the host is not down.

HOST007 (HOST_WRITE)

Alarm level

Major.

Description

The application cannot send a screen of data to the host to get data for the call. The application either tried to send the wrong screen or to write onto a protected field on the screen.

Repair procedure




1. Type hspy session_ number and press Enter to display the screen currently in use by the session.

You are asked to press Enter again. The application may have tried to send a different screen or tried to write into a protected field.

2. Correct the host application by taking the following actions:

a) Redefine the logic of the application to either send the correct screen or not write to the protected field.

b) Re-verify and reinstall the host application.

3. Type hfree session_number and press Enter to free the specified session.

A message appears, reporting the success or failure of the hfree command.

4. Type sb_te session_numbers and press Enter to move from the current screen back to the login base screen using the proper screens and keys.

You are asked to press Enter again to display the screen currently in use by the sessions.

5. If the session does not respond to your input, check the terminal emulator status line indicator at the bottom of the display.

The Terminal Emulator (TE) displays the current screen of the LU. The 3270 status line appears at the bottom of the screen to inform you whether or not the host is active.

6. Type hassign application_name to session_number and press Enter to reassign the application back to the session.

A message appears, reporting the success or failure of the hassign command.

7. If the problem persists, type sb_trace session_number and press Enter.

The system displays a message reporting the success or failure of the sb_trace command.

HOST008 (HOST_OFFSYNC)

Alarm level

Major.

Description

The application cannot access the host to get data for the call. The application wants to send a screen when the host has not yet responded to a previous send of another screen.



Repair procedure

Check the logic of the application. See the Avaya IVR Designer Help for TAS Applications or the Avaya IVR Designer Help for VXML Applications for more information.

HOST009 (HOST_LOGIN)

Alarm level

Major.

Description

The application cannot access the host to get data for the call. The application failed to log in. The specified session could not attempt to log in to the host because all the login IDs and passwords are being used by other sessions.

Repair procedure

Either add more login IDs and passwords to the application, or do not use any more sessions than are available through existing login IDs and passwords. See the Avaya IVR Designer Help for TAS Applications or the Avaya IVR Designer Help for VXML Applications for more information.

HOST010 (HOST_DEFINE)

Alarm level

Critical.

Description

The application will not run because it is incomplete or improperly defined.

Repair procedure

Check the logic of the application. See the Avaya IVR Designer Help for TAS Applications or the Avaya IVR Designer Help for VXML Applications for more information.



HOST011 (HOST_HELPER)

Alarm level

Major.

Description

The application cannot access the host to get data for the call. The application depends on the HELPER DIP to identify fields on the screens.

Repair procedure




2. If the problem persists, check the logic of the application.

See the Avaya IVR Designer Help for TAS Applications or the Avaya IVR Designer Help for VXML Applications for more information.

HOST012 (HOST_SESSION)

Alarm level

Major.

Description

The application cannot access the host to get data for the call. Either not enough sessions have been assigned to the application, or some sessions assigned to the application are not logged in to take calls.

Repair procedure




1. Enter hstatus with the appropriate argument (application_name, session_number, range, or all) to verify that there are as many sessions defined as there are voice channels assigned to the application.

2. Enter hstatus with the appropriate argument (application_name, session_number, range, or all) to verify that the application has enough sessions logged in and ready to handle calls.

3. If the voice response application is not assigned to the Licensed Unit (LU), assign as many sessions as needed by entering hassign application_name to session_number.

The system displays a message that reports the success or failure of the hassign command.

4. If a LU is assigned to application but in the logged-out state, enter hlogin session_number to log in logged-out sessions.

5. Enter hstatus with the appropriate argument (application_name,session_number,range, or all) to determine if some sessions are in the recovery state.

Sessions may be put into the recovery state due to faulty logic in the host application.

If some sessions are in recovery, check the logic of the host application. See the Avaya IVR Designer Help for TAS Applications or the Avaya IVR Designer Help for VXML Applications for more information.

HOST013 (HOST_DOWN)

Alarm level

Major.

Description

The application cannot access the host to get data for the call. One of these problems exists:

• The voice system was stopped before all sessions were logged out.


• The connection to the host is down, or the host is down.

• There is a logic problem in the host application.

Repair procedures

If the voice system was stopped before all sessions logged out, take these actions:



1. Enter hfree followed by the appropriate argument (application, session_number, range, or all) to free all sessions assigned to the application or the card.


2. Enter sb_te session_numbers to use the terminal emulator on all of the recovering sessions and manually move the sessions to the Login Base screen with the screens and keys.

The current screen on the sessions is displayed.

3. Use the hassign command to reassign the application to all the sessions and verify that all sessions become logged in.

If the application is down, take these actions:

1. Enter hfree session_number to free a session of the card.


2. Enter sb_te session_numbers.


If the problem persists:



If the problem still persists, check the logic in the voice response application. See the Avaya IVR Designer Help for TAS Applications or the Avaya IVR Designer Help for VXML Applications for more information.

HOST014 (HOST_UP)

Alarm level

None.

Description

At least one session has recovered and is now logged in for the application to take a call.



Repair procedure


HOST015 (HOST_HIBERNATE)

Alarm level

Critical.

Description

The applications cannot access the host to get data for calls. The HOST Data Interface Process (DIP) has stopped handling calls. This is normal when the voice system is stopped, and in this case the message can be ignored. If the voice system is still running, the message might indicate internal problems in the HOST DIP.

Repair procedure



1. If the voice system is running, enter hstatus all to determine if the HOST DIP is running.

If all sessions are shown as not available, the HOST DIP is not running.

2. If the HOST DIP is not running, stop and start the voice system.

HOST016 (HOST_BRDOPEN)

Alarm level

Critical.

Description

The system cannot communicate with the host. This shows that the HOST DIP cannot open any host licensed units (LUs). This problem occurs when the host connection is stuck in an



inactive state. This problem is typically caused by an error between the voice system and the host, such as a dropped host connection, power hit on the voice system, and so forth.

Repair procedure


1. Shut down the operating system.

2. Reboot the operating system.

HOST017 (HOST_INRECOV)

Alarm level

Major.

Description

The session assigned to the application is not available to handle calls. It will continue to retry the login, recover sequences, or do both, as specified in the application. One of the following problems exists:

• The connection to the host is down.


• There is a logic problem in the application.

Repair procedure

If the application is down, take these actions:

1. Type hfree session_number and press Enter to free a session of the card.


2. Type sb_te session_numbers and press Enter.


If the problem persists:





If the problem still persists, check the logic in the voice response application. See the Avaya IVR Designer Help for TAS Applications or the Avaya IVR Designer Help for VXML Applications for more information.

HOST018 (HOST_OUTRECOV)

Alarm level

None.

Description

The session assigned to the application is now available to handle calls.

Repair procedure


INIT alarms and log messages The Avaya IR system generates INIT alarms and log messages to report updates and problems with the software processes that administer the circuit cards.

INIT001 (INIT_NODBFILE)

Alarm level

Critical.

Description

The system configuration from the previous operation of the voice system is completely lost. All administered values are set to their default states. Administrative action is required to assign services to channels and put channels in the INSERV state. Card functions must be specified in order for the system to operate under any configuration other than the default settings.

No calls can be processed until the system has been re-administered.


INIT alarms and log messages

Repair procedure

This alarm requires remote maintenance center intervention.

INIT005 (INIT_CANT_SAVE)

Alarm level

Major.

Description

The IR system cannot save system configuration data to hard disk.

CAUTION: If the voice system is stopped and started at this point, some or all of the voice system administered values may be lost.

Repair procedure

This alarm requires remote maintenance center intervention. Contact your Avaya support representative.

INIT008 (INIT_AUTOCLEAN)

Alarm level

None.

Description

Channels have been renumbered as a result of a change in hardware.

Note: This alarm occurs when a card in the system has been replaced by another card of the same class, but of a different name or running at a different rate. Therefore an automatic renumber of the cards has occurred and the new card has default settings.

Repair procedure

The new circuit card may need to be re-administered if the default settings, protocols, or functions are not appropriate.



INIT009 (INIT_MANUALREN)

Alarm level

Minor.

Description

A change in configuration was detected. An automatic renumbering was not completed because the manual renumber option is set. A renumbering of channels should be done as soon as possible.

Note: The system displays this alarm only when your remote maintenance center activates it.

Repair procedure

Renumber the voice channels.

LOG alarms and log messages The Avaya IR system generates LOG alarms and log messages to report updates from the logger process. Most of these messages do not require action.

LOG001 (LG_START_LOG)

Alarm level

None.

Description

The voice system logger has started a new message log file.

Repair procedure



LOG alarms and log messages

LOG002 (LG_END_LOG)

Alarm level

None.

Description

The voice system logger has closed one message log file and is starting a new message log file.

Repair procedure


LOG006 (LG_GL_INVALID_MSG)

Alarm level

None.

Description

The voice system logger has been asked to log a message type which is invalid and which it cannot expand into a readable form for the Message Log Report screen. Alarm level is based on the priority of the message ID passed to the Logger.

Repair procedure


1. Identify the source of the unexpected message.

The name of the source should be part of the compressed message format of the invalid message.

2. If the source of the unexpected message is a voice response application data interface process (DIP), review the application for problems.

3. If the source of the unexpected message is not a DIP, determine whether all installed voice system software packages are compatible with the installed version of the system software.

4. Remove any software package that is incompatible and install the proper version.



LOG007 (LG_LOGDAEMON)

Alarm level

None.

Description

This message can have different values for the string1 and string2 fields. The description, effect statement, and the corresponding repair procedure differ for each of the values. Alarm level is based on the priority of the message ID passed to the Logger. Use the following list of messages to determine the proper description and effect statement and repair procedure for the LOG007 message you have encountered.

Message Description Repair Procedure

logDaemon: Exiting upon request:

Logger has received a command to exit.


logDaemon: msgrc=1, errno NOT EINTR:

Logger cannot communicate with other internal voice system processes. Logger functionality is severely impaired.

Reboot the system.

LOG007 logDaemon: PID <pid> <msg>.:

Logger has been started or reinitialized. This message is in each log file maintained by the Logger.


LOG007 logDaemon: REINITIALIZED.:

The voice system message Logger has received a command to reinitialize.


LOG007 logDaemon: Unable to open: <command>.:

The voice system message Logger is unable to execute the UNIX command indicated by the message. Logger functionality is impaired.

• Make sure the UNIX command file being executed by the Logger exists and is executable.

• If necessary, restore the missing or corrupted UNIX command file indicated in the message from a system backup.

• If no valid backup copy exists reinstall the Avaya IR system software.


MTC alarms and log messages

MTC alarms and log messages The Avaya IR system generates MTC alarms and log messages to report state and problems with the circuit cards and bus.

MTC002 (MTC_STATE_EVENT)

Alarm level

None.

Description

The identified card has had a state transition. The card state has been changed to BROKEN. Applications dependent on the card will not function.

Repair procedure

Contact your Avaya support representative or try to restore the card.

MTC003 (MTC_STATE_ALARM)

Alarm level

None.

Description

The identified card has had a state transition. The card state has been changed to BROKEN. Applications dependent on the card will not function.

Repair procedure




MTC004 (MTC_DIAG_START)

Alarm level

None.

Description

Diagnostic tests have been started on the identified card.

Repair procedure


MTC005 (MTC_DIAG_PASS)

Alarm level

None.

Description

The identified card has successfully passed all diagnostic tests performed.

Repair procedure


MTC006 (MTC_DIAG_FAIL)

Alarm level

Major.

Description

The identified card has failed one or more diagnostic tests. The card state has been changed to BROKEN. Applications dependent on this card will not function.


MTC alarms and log messages

Repair procedure


MTC007 (MTC_REQ_FAIL)

Alarm level

Critical.

Description

An internal software error occurred when requesting a resource from, or releasing a resource to the Resource Manager. The request could not be processed. The identified card or channel is not available.

Note: If the reason is User requested abort, an abort of a remove or restore request for a card or channel was initiated while the request was still being processed. The state of the card or channel may not be accurate.

Repair procedure

Contact your Avaya support representative for assistance.

MTC009 (MTC_LOAD_FAIL)

Alarm level

Major.

Description

An error occurred loading the card in the message. Applications dependent on this card may not function. Call processing may be impaired.

Repair procedure


Issue 1.0 June 2004 101


MTC017 (MTC_RESPAWN)

Alarm level

Major.

Description

The maintenance process (mtc) has respawned and has attempted to leave channels and cards in the appropriate state. However some cards, channels, or both may not be available.

Repair procedure


NMS alarms and log messages NMS alarms and messages report events related to NMS cards for systems containing those cards.

NMS001 (NMS_INTERNAL_ERROR)

Alarm level

Major.

Description

A general internal software error has occurred in NMSIP. This includes operating system related API failures, system utility failures, and so on.

Repair procedure

This is an internal software error for which there is no repair. Contact your Avaya support representative with the log message and relevant additional information, such as the application that was involved and the type of channel protocol in use.


NMS alarms and log messages

NMS002 (NMS_GENERIC_ERROR)

Alarm level

Major.

Description

A general processing error has occurred in NMSIP. This can be the result of protocol errors, configuration errors, and other types of problems. The log message should indicate the error type and a possible solution.

Repair procedure

Review the text of the log message to determine the actual severity. If the log message is not clear to you, or the suggested solution does not work, contact your Avaya support representative. Provide any relevant additional information that you can obtain, such as the application involved and the type of channel.

NMS004 (NMS_API_FAIL)

Alarm level

Major.

Description

A software error has occurred in NMSIP as a result of an NMS API request failure of a NMS asynchronous response EVENT. Errors of this type are generally serious.

Repair procedure

Review the text of the log message to determine the actual severity. If the log message is not clear to you, or the suggested solution does not work, contact your Avaya support representative. Provide any relevant additional information that you can obtain, such as the application involved and the type of channel.

NMS003 (NMS_OBJECT_FAIL)

Alarm level

Major.

Issue 1.0 June 2004 103


Description

An internal software error has occurred in NMSIP. The Object identified is in error.

Repair procedure

This is an internal software error for which there is no repair. Contact your Avaya support representative with the log message and relevant additional information, such as the application that was involved and the type of channel protocol in use.

NMS005 (NMS_TRUNK_EVENT)

Alarm level

Major.

Description

Trunk-specific activity, such as a trunk going up or coming down.

Repair procedure


1. Review the text of the log message to identify the event.

2. If the event is related to a trunk or trunks coming up, no further action is required.

3. If the event is related to a trunk or trunks going down, take these actions:

a) Check the physical trunk or trunk for loose connections.

b) Verify that the switch at the far end is operating properly.

c) Ensure that the physical trunk is configured correctly both on the switch and on the <mav_prod_name_> system.

d) Type trunkmon-b <trunk number> and press Enter to determine the exact condition of the trunk.

4. If you cannot resolve the problem by troubleshooting the trunk, contact your Avaya support representative and provide information like the following:

― Alarms received

― Application involved


NMS alarms and log messages

― Type of channel protocol in use

― Type of board

― Type of switch

NMS007 (NMS_BOARD_CONFIG)

Alarm level

Major.

Description

The configuration file has failed to configure the NMS board.

Repair procedure


1. To gather more information on the problem, type examine/vs/data/diagnose/diagBrd <board number> and press Enter.

2. Type nms display card = card number and press Enter.

Review the configuration information for accuracy and completeness.

3. Make any required corrections to the NMS board configuration settings.

4. If the configuration settings are correct, contact your Avaya support representative and provide relevant information, such as:

― Alarms received

― Application involved

― Type of channel protocol in use

― Type of board

― Type of switch

Issue 1.0 June 2004 105


PROXY alarms and log messages The Avaya IR system generates PROXY alarms and log messages to report the most serious alarms related to speech or DPR proxy operations.

PROXY001 (PX_BROKEN_SOCKET)

Alarm level

Minor.

Description

There is a problem with connectivity between the speech recognition or DPR proxy and the specified port on the recognition server.

Repair procedure


1. Go to the Speech Server Status screen (Feature Packages > Speech and DPR Administration > Display Status > Speech Server Status) to verify the current state of the specified server or port.

You also may use the sproxyadm command.

2. If the state of the port or server is BROKEN, verify that the recognition server is still running.

3. If the recognition server is running, check connections to the recognition server.

4. If there is a problem with the port or server, go to the Change Speech Server State screen (Feature Packages > Speech and DPR Administration > Administration > Change Speech State > Change Speech Server State) to change the state of server.

Again, you may use the sproxyadm command.

5. If the problem persists, restart the recognition server and change the state of the server once more, as in step 4.

6. If the problem still persists, contact your field support representative.


PROXY alarms and log messages

PROXY002 (PX_SERVER_FILE_ERROR)

Alarm level

Critical.

Description

The specified configuration file is missing. This could be a result of improper configuration of the system or accidental removal of the file.

Repair procedure


1. Restore the configuration file from a backup file.

2. If there is no backup file, administer the Natural Language Speech Recognition or DPR feature again.

PROXY003 (PX_SYS_MUTEX_FAILURE)

Alarm level

Major.

Description

The speech recognition or DPR proxy is not able to initialize mutex due to system error.

Repair procedure




2. If the problem persists, contact your field support representative.

Issue 1.0 June 2004 107


PROXY004 (PSYS_VSYS_QKEY_ERROR)

Alarm level

Critical.

Description

The system was unable to get message Qkey for the specified Recognition Type.

Repair procedure





PROXY005 (PX_MAINT_STATE_CHANGE)

Alarm level

Minor.

Description

The maintenance state of the specified recognition type, server, or port has changed. The system displays this message when any of the following events occurs:

• A PROXY01 or PROXY13 message was received.

• The voice system was started and the speech recognition or DPR proxy was initialized.

• A user requested the maintenance state change.

Repair procedure

See the repair procedure for PROXY001.



PROXY006 (PX_SYS_THREAD_ERROR)

Alarm level

Major.

Description

The speech recognition or DPR proxy is not able to initialize a thread due to a system error.

Repair procedure





PROXY007 (PX_SERVER_OOS)

Alarm level

Minor.

Description

All ports of the specified server are offline. If this is not a result of a change state request from a user, you need to resolve the problem.

Repair procedure


1. Go to the Speech Server Status screen (Feature Packages > Speech and DPR Administration > Display Status > Display Speech Proxy Status > Speech Server Status) to verify that the recognition server is still running.


2. If the recognition server is running, check the connection to the recognition server.

Issue 1.0 June 2004 109


3. If there is no problem with the LAN, go to the Change Speech Server State screen (Feature Packages > Speech and DPR Administration > Administration > Change Speech State > Change Speech Server State) to change the state of recognition server.


PROXY008 (PX_SEND_FAILURE)

Alarm level

Minor.

Description

The speech recognition or DPR proxy is unable to send a message to another component in the system.

Repair procedure





PROXY009 (PX_UNRECOGNIZED_MESSAGE)

Alarm level

None.

Description

The speech recognition or DPR proxy received an unexpected message from another component in the system.



Repair procedure

No action necessary.

PROXY010 (PX_ALL_SRV_PORTS_OOS)

Alarm level

Major.

Description

All ports of the specified server are offline. This is a result of a change state request from a user.

Repair procedure


PROXY011 (PX_GENERAL_FAILURE)

Alarm level

Minor.

Description

The speech recognition or DPR proxy experienced a general failure that might cause problems with the results of speech or dial pulse recognition.

Repair procedure

• If the reason field of the error specifies a problem with getting system resources, stop the voice system and start it again.

• If the problem persists, contact your field support representative.

Issue 1.0 June 2004 111


PROXY012 (PX_RTU_FAILURE)

Alarm level

Critical.

Description

The application is not able to get enough Right-to-Use licenses (RTUs) to continue operations.

Repair procedure

1. Check the Feature Licensing (Configuration Management > Feature Licensing) screen to identify the RTUs available.

2. Contact your Avaya support representative to purchase more RTUs.

PROXY013 (PX_SRV_TIMEOUT)

Alarm level

Minor.

Description

The speech recognition or DPR proxy is not able to get a response from the specified server on the specified port.

Repair procedure

See the repair procedure for PROXY001.

RECOG alarms and log messages The Avaya IR system generates RECOG alarms and log messages to report operational updates and problems related to speech recognition.


RECOG alarms and log messages

RECOG001 (RECOG_MSGRCV)

Alarm level

Major.

Description

The speech recognition feature failed to communicate with the voice system during call processing. Applications using the speech recognition feature will fail.

Repair procedure

Reboot the system.

RECOG002 (MSG_SEND)

Alarm level

Major.

Description

The speech recognition feature failed to communicate with the voice system during call processing. Applications using the speech recognition feature will fail.

Repair procedure

Reboot the system.

RECOG004 (RECOG_GRAMERR)

Alarm level

Minor.

Description

In a voice response application, an invalid wholeword grammar or subword wordlist number was used by the getdig instruction. The IR system did not recognize the structure.

Issue 1.0 June 2004 113


Repair procedure


1. Check the application to ensure that the getdig() instruction is using a valid WholeWord grammar or subword wordlist number.

2. If the problem persists, reinstall the speech recognition languages or the subword vocabulary.

SYS alarms and log messages SYS log messages report normal events that are the results of system calls.

SYS001-SYS157

A large number of messages report normal events related to system processes. Although the reported events do not cause alarms, you may find the information they provide helpful when you are troubleshooting.

THRESH alarms and log messages The Avaya IR system generates THRESH alarms and log messages to report messages that indicate that a particular threshold was exceeded. You can set up thresholds through the Message Administration screens.

THRESH001 (THRESH_INFO)

Alarm level

None.

Description

This is a threshold message. Threshold messages:

• Indicate that too many messages of a particular type are being generated

• May indicate an escalation of priority


THRESH alarms and log messages

Here is an example of a typical threshold message:

THRESH001 -- -- -- The first threshold level for LG_MSGNAME exceeded. 100 messages have been generated in the last 1 hour.

The message mnemonic in this example is LG_MSGNAME. The message text gives the currently set threshold limits for the message.

Repair procedure


1. Review the text of the threshold message to identify the message mnemonic and the number of messages generated.

2. Type explain mnemonic and press Enter, if necessary.

3. Note the message ID that appears in the header of the Explain output.

4. Take action based on your findings.

THRESH002 [THRESH_MINOR]

Alarm level

Minor.

Description







Repair procedure

Same as THRESH001 on page 114.

Issue 1.0 June 2004 115


THRESH003 [THRESH_MAJOR]

Alarm level

Major.

Description







Repair procedure


THRESH004 [THRESH_CRITICAL]

Alarm level

Critical.

Description






TRACE alarms and log messages



Repair procedure


TRACE alarms and log messages The Avaya IR system generates TRACE alarms and log messages during diagnostic tests.

TRACE001 (TRACE_GEN)

Alarm level

None.

Description

Descriptive trace messages appear in log files when Avaya support services run diagnostic tests on the Avaya IR system.

Action


TSM alarms and log messages The Avaya IR system generates TSM alarms and log messages to report problems with voice operations.

TSM002 (TSM_LOADSCR)

Alarm level

Critical.

Issue 1.0 June 2004 117


Description

The voice system has tried to load a voice response application file that is missing or corrupted. The channel number contained in the message provides information about call processing:

• If the message contains a channel number of 1, any incoming calls using the voice response application will not be processed. Attempts by a DIP to run the application with a soft seizure request will also fail. (The soft_szr command sends a message to the Transaction State Machine (TSM) process requesting that a script be started on a channel.)

• If the message contains a channel number greater than 1, an attempt to process a call or a soft seizure request with the application has failed on the channel indicated.

Repair procedure

To investigate the problem:

1. Verify that the voice response application name in the system message is valid.

2. If the name is not valid, then determine the following:

― Is another application attempting to execute the invalid application using the exec instruction?

― Is an IRAPI application attempting to use irExecp () to execute an invalid script name?

3. Check the logic of the application.

See the Avaya IVR Designer Help for TAS Applications or the Avaya IVR Designer Help for VXML Applications for more information.

TSM003 (SPBUSY)

Alarm level

Minor

Description

The service running on the indicated channel was unable to perform the specified function because the card was overloaded. This is a temporary condition and will be relieved when the demand decreases. Call processing on the channel has been degraded.

The impact may be significant if the message occurs more frequently than the currently set threshold limit. In that case, you will see a threshold message similar to the following:


TSM alarms and log messages

** THR003 -- -- -- The first threshold level for TSM_SPBUSY exceeded. 10 messages have been generated in the last 1 minute.

The threshold limits and message priority shown above reflect the default values for this message.

Repair procedure


1. If you have multiple NMS cards on your system, go to the Display Equipment screen (Configuration Management > Voice Equipment > Display Equipment) to determine whether a card has gone out of service.

2. If a card is out of service, try to restore the card or contact your Avaya support representative for assistance.

3. If all cards are in service, check system resources and reduce the load on the IR system, if necessary.

TSM004 (TSM_SPUNAVAIL)

Alarm level

Critical.

Description

The service running on the indicated channel was unable to perform the specified function. There are not a sufficient number of cards in service that perform the identified function. Call processing has been degraded or inhibited completely on all channels needing the function.

Note: A Text-to-Speech (TTS) error may be logged even if PTTS is not activated. In this case, the TTS portion of the message can be ignored.

Repair procedure

See the repair procedure for TSM003 on page 118.

Issue 1.0 June 2004 119


TSM008 (TSM_RTU_BUSY)

Alarm level

Minor

Description

The service running on the indicated channel was unable to perform the specified function because a Feature License was overloaded. This is a temporary condition resulting from the dynamic nature of license allocation on the system. This condition will be relieved when the system's demand for this Feature License decreases.

The impact may be significant if the message occurs more frequently than the currently set threshold limit. In that case, you will see a threshold message similar to the following:

** THR003 The first threshold level for TSM_SPBUSY exceeded. 10 messages have been generated in the last 1 minute.

The threshold limits and message priority shown above reflect the default values for this message.

Repair procedure

It may be useful to purchase a Feature License for a larger number of simultaneous users of this feature to avoid degraded service. Contact your service representative to purchase more feature licenses.

TSM009 (NO_RTU)

Alarm level

Major.

Description

The service running on the indicated channel was unable to perform the specified function because no Feature License has been purchased for an optional feature.

Repair procedure

It will be necessary to purchase a Feature License for the optional feature in order for this service to perform as designed. Contact your service representative to purchase more feature licenses.


TSM alarms and log messages

TSM010 (TSM_QFLUSH)

Alarm level

None.

Description

The TSM speech queue has been force-flushed.

Action

No action required.

TSM012 (TSM_NOEXTFUNC)

Alarm level

Major.

Description

A voice response application called an extend function with an invalid extension function ID. An extend TAS instruction that executes C language functions on behalf of a TAS-based voice response application has an error.

Repair procedure

Contact the person or firm responsible for development of voice response applications. Advise them to make sure that irVADynSwitchAdd is called with the integer value corresponding to the argument passed to the extend instruction. See the Avaya IVR Designer Help for TAS Applications for more information.

TSM013 (TSM_NOPROG)

Alarm level

None.

Issue 1.0 June 2004 121


Description

TSM received an event when no program was running on the channel.

Action

No action required.

TTS alarms and log messages The Avaya IR system generates TTS alarms and log messages to report problems with the Proxy Text-to-Speech (PTTS) feature.

TTS002 (TTS_BADFILE)

Alarm level

Major.

Description

The Proxy Text-to-Speech (PTTS) feature failed to access the text file indicated during call processing. Applications requiring access to this file will be incomplete.

Repair procedure


1. Verify that the voice response application refers to the correct text file name.

2. Verify that the text file is in existence in the correct directory.

3. If the application refers to the correct text file, restore the text file or files from backup files.

4. If no backup files are available, re-create the text file.



TTS alarms and log messages

TTS003 (TTS_TRACE)

Alarm level

None

Description

General trace.

Repair procedure

Contact your Avaya support representative if the warning persists.

TTS004 (TTS_NOTINIT)

Alarm level

Major.

Description

The Proxy Text-to-Speech (PTTS) feature failed to initialize a resource.

Repair procedure



1. Go to the Text-to-Speech Configuration screen (Feature Packages > Speech and DPR Administration > Administration > Text-to-Speech Configuration) to check the configurations.


2. If the text-to-speech configuration is incorrect, go to the appropriate configuration screen and make any required changes.



Issue 1.0 June 2004 123


TTS005 (TTS_MSGFAIL)

Alarm level

Major.

Description

The Proxy Text-to-Speech (PTTS) feature failed to communicate with the voice system during call processing. Applications using the feature to read from a text file will fail.

Repair procedure





TTS006 (TTS_CONNFAIL)

Alarm level

Major.

Description

The Proxy Text-to-Speech communications have a TCP/IP error.

Repair procedure


1. Check the configuration and status of the speech server.


TTS alarms and log messages

2. If speech server disconnection is not the cause of the problem, stop and start the voice system.

TTS007 (TTS_STATECHARGED)

Alarm level

Minor.

Description

The Proxy Text-to-Speech (PTTS) state is changed.

Repair procedure

No action required if operations are not affected.

TTS008 (TTS_NORESOURCE)

Alarm level

Major.

Description

Proxy Text-to-Speech (PTTS) server has all ports busy, so there is no resource available to handle the request.

Repair procedure



1. Administer the Proxy Text-to-Speech (PTTS) server to support more connections.

2. Using the sproxyadmin command, administer the IR system to support the increased number of connections on the PTTS server.

Issue 1.0 June 2004 125


3. If the problem persists, or if no additional connections are available, stop and start the voice system.

4. If the problem still persists, consider upgrading connections, upgrading the Proxy Text-to-Speech server, or upgrading both.

TTS009 (TTS_MGRFAIL)

Alarm level

Major.

Description

The Proxy Text-to-Speech (PTTS) application failed to create the TTS proxy manager.

Repair procedure



1. Go to the Text-to-Speech Configuration screen (Feature Packages > Speech and DPR Administration > Administration > Text-to-Speech Configuration > Display Text-to-Speech Configuration) to check the configurations.


2. If the configuration is incorrect, go to the Text-to-Speech Configuration screen and make the required changes.


TTS010 (TTS_ADDFAIL)

Alarm level

Major.


UNIX alarms and log messages

Description

The Text-to-Speech (PTTS) application failed to add the TTS proxy.

Repair procedure

See the repair procedure for TTS009 on page 126.

UNIX alarms and log messages The Avaya IR system generates UNIX alarms and log messages to report problems with the UNIX operating system.

UNIX001 (UNIX_NOTICE)

Alarm level

None.

Description

These are normal messages issued by the UNIX operating system from time to time.

Action

No action required.

UNIX002 (UNIX_WARNING)

Alarm level

Minor.

Description

These are warning messages issued by the UNIX operating system.

Action

No action is required until a higher severity message is issued.

Issue 1.0 June 2004 127


UNIX003 (UNIX_TROUBLE)

Alarm level

Major.

Description

These messages report problems experienced by the UNIX operating system.

Repair procedure

Take action based on the text of the message. Contact your Avaya support representative, if necessary.

UNIX004 (UNIX_CRITICAL)

Alarm level

Critical.

Description

The UNIX operating system is experiencing a very serious problem.

Repair procedure

Contact your Avaya support representative immediately.

UNIX005 (UNIX_INFO)

Alarm level

None.

Description

These are normal messages issued by the UNIX operating system from time to time.


VOIP alarms and log messages

Action


UNIX006 (UNIX_ERROR)

Alarm level

Minor.

Description

Warning messages issued by the UNIX operating system.

Action

No action is required until a higher severity is issued.

VOIP alarms and log messages VoIP alarms and messages report events related to VoIP operations. When troubleshooting problems with packet connectivity, the components of concern are the:

• DEFINITY or MultiVantage system

• IP network where the Avaya IR is located

• VoIP subsystem portion of the Avaya IR system

Troubleshooting of the VoIP subsystem is based on events and alarms. If a VOIP_ENABLED_CALL_PROC event appears in the Message Log Report, and is not followed by any other events or alarms from the VoIP subsystem, then the VoIP subsystem is operating correctly. All other VoIP events and alarms result from a problem with the VoIP subsystem, or its connection to the IP network. Events and alarms identify the problem and explain what triggered the event or alarm. The topics in this section provide further information, including repair procedures.

Issue 1.0 June 2004 129


VOIP001 (VOIP_ENABLED_CALL_PROC)

Alarm level

None.

Description

The VoIP subsystem is processing calls under normal conditions.

Action

No action required.

VOIP002 (VOIP_DISABLED_CALL_PROC)

Alarm level

Major.

Description

The VoIP subsystem is not processing calls.

Repair procedure


1. Check for other VOIP messages and alarms, such as VOIP_CONFIG_ERROR, to determine the cause of the problem.

2. Take action based on your findings.

3. Contact your Avaya support representative, if necessary.



VOIP003 (VOIP_CONFIG_ERROR)

Alarm level

Major.

Description

A VoIP configuration parameter is incorrect. The text of the message identifies the incorrect parameter. The VoIP subsystem is probably not processing calls.

Repair procedure

To resolve the problem, go to the Change VoIP Parameters screen (Configuration management > Switch interfaces >Voice over IP > Change Parameters > Change VoIP Parameters) and correct the parameter.

VOIP004 (VOIP_NETWORK_ERROR)

Alarm level

Major.

Description

The VoIP subsystem is not processing calls because it cannot access the packet network (LAN).

Repair procedure


1. Check the Solaris network configuration on the Avaya IR system and make any required corrections.

2. Check the network configuration on the MultiVantage system and make any required corrections.

See your MultiVantage documentation for more information.

3. Make sure that the Avaya IR system and the MultiVantage system can access the network and communicate with each other.

4. Contact your Avaya support representative, if necessary.

Issue 1.0 June 2004 131


VOIP005 (VOIP_REMOTE_ERROR)

Alarm level

Major.

Description

The VoIP subsystem is not processing calls because there is a problem with remote equipment, a gateway, or a gatekeeper.

Repair procedure


1. Go to the Assign VoIP Card screen (Configuration Management > Switch interfaces > Voice over IP > Assign VoIP Card) and check the entry in the Gatekeeper IP Address field.

The gatekeeper is the DEFINITY or MultiVantage system that interacts with the VoIP subsystem. The IP address on the Assign VoIP Card screen should be correct and match the IP address for the DEFINITY or MultiVantage system in Solaris.

2. If the gatekeeper IP address is not correct, make the required corrections:

― If necessary, revise the gatekeeper IP address on the Assign VoIP Card screen.

― If necessary, revise the gatekeeper IP address in Solaris, or work with your network administrator to make the change.

3. If the gatekeeper address is correct on the Assign VoIP Card screen and in Solaris, determine whether LAN or switch problems are causing the error:

― Contact your network administrator to inquire about LAN problems.

― Contact your PBX administrator to inquire about switch problems.

4. If no problems exist with the LAN or the switch, attempt to clear the error by removing and restoring the VoIP card.

Removing the card with the remove command may put it into the MANOOS (manually out of service) state. Once the card is in the MANOOS state, you can restore it to the INSERV (in service) state with the restore command.

5. If the VoIP card is not restored, contact your Avaya support representative.



VOIP006 (VOIP_MEDIA_ERROR)

Alarm level

Minor.

Description

There is a problem with the media path for a particular call. If multiple media error events appear in the Message Log Report screen, the network is probably congested, or a device on the network is probably not forwarding UDP packets fast enough.

Repair procedure

Work with your LAN administrator to resolve the problem.

VOIP007 (VOIP_OAM_ERROR)

Alarm level

Major.

Description

A problem occurred when the IR system attempted to process an administrative, operations, or maintenance request. As a result, card and channels operations may not be working. Operations, Administration and Maintenance (OAM) errors occur when there is a serious problem with the IR system, not just the VoIP subsystem.

Repair procedure

Contact your Avaya support representative immediately.

VOIP008 (VOIP_SIGNAL_ERROR)

Alarm level

Minor.

Issue 1.0 June 2004 133


Description

There is an overall signaling problem, or a signaling problem with a call. The VoIP subsystem may not be processing calls.

Repair procedure


1. Make sure that the Avaya IR configuration for VoIP matches the configuration on DEFINITY or MultiVantage.

2. Make any required corrections.

3. Attempt to remove and restore the card.

VOIP009 (VOIP CALL_ERROR)

Alarm level

Minor.

Description

An error occurred when a call was processed. No free channel is available to accept the call.

Repair procedure

To resolve the problem, take action according to the situation:

• Repeated messages of this type are a strong indication that the IR system is overloaded. More VoIP channels are required, or you may need to better manage the performance of the IR system.

• You must have RTU licenses for at least one channel to use the feature. Go to the Display VoIP Parameters screen (Switch Interfaces > Voice over IP > Display VoIP Parameters) and check the number of VoIP channels configured. Make sure that you have adequate licenses for these channels. You may need to change the configuration or purchase additional licenses.



VOIP010 (VOIP_CALL_FORCE_CLEARED)

Alarm level

None.

Description

A call has been force-cleared (terminated) by the VoIP subsystem. Causes of call force-clearing are:

― Voice system shutdown (the most frequent cause)

― VOIP errors such as VOIP_CALL_ERROR on page 134, VOIP_MEDIA_ERROR on page 133 and VOIP003 (VOIP_CONFIG_ERROR) on page 131.

Repair procedure

Go to the Message Log Report screen (Reports > Message Log Report) and take action based on your findings:

• If force-clearing is occurring during shutdown, minimize the impact of shutdown on call processing by:

― Allowing more time for active calls to end. You can specify a wait time of up to 600 seconds before the voice system stops.

― Conducting shutdown during times when calls are not being handled or call activity is low.

― Using the sysmon command to monitor voice operations while the system is shutting down.

• If you find multiple instances of VOIP_CALL_ERROR or VOIP_MEDIA_ERROR messages, reduce the overload on the IR system or the network. See VOIP_CALL_ERROR on page 134 and VOIP_MEDIA_ERROR on page 133 for more information.

• If you find a VOIP_CONFIG_ERROR message, correct the configuration. See VOIP_CONFIG_ERROR on page 131 for more information.

Issue 1.0 June 2004 135


VROP alarms and log messages The Avaya IR system generates VROP alarms and log messages to report problems with voice response operations.

VROP011 (VROP_NBUFS]

Alarm level

Critical.

Description

VROP_TNG could not acquire sufficient shared memory for speech buffers.

Repair procedure

Reboot the system.

VROP014 (VROP_FSFAIL)

Alarm level

Critical.

Description

VROP_TNG failed to access the speech file indicated during processing. Voice response applications requiring access to this file will be incomplete.

Repair procedure


1. Make sure that the voice response application refers to the correct speech file name.

2. Make sure that the required speech file exists and has the correct access permission.

3. If the application is correct in its references and the speech file is accessible, restore the speech file or files from backup files.

4. If the backup files are not available, recreate the speech file.


VROP alarms and log messages

VROP018 (VROP_MALLOC)

Alarm level

Critical.

Description

The system has failed to play or code a phrase. This is likely to recur until the problem has been resolved.

Repair procedure




2. If the problems does not resolve, contact your Avaya support representative.

Issue 1.0 June 2004 137

AVB alarms and log messages � 32 AVB001 (AVB_COPYRIGHT) � 32 AVB002 (AVB_PARSE_ERROR) � 32 Index AVB003 (AVB_ERROR) � 33 AVB004 (AVG_PLATFORM) � 33 AVB005 (AVB_MISSINGURL) � 34 AVB006 (AVB_EXCEPTION) � 34 AVB007 (AVB_BADGRAMMAR) � 35 AVB008 (AVB_BADINPUTRETURN) � 35 AVB009 (AVB_BADRECORD) � 36 A AVB010 (AVB_BADPROMPT) � 36 AVB011 (AVB_BADPROPERTY) � 36 ADMIN alarms and log messages � 11 AVB012 (AVB_SEMANTICERROR) � 37 ADMIN001 (ADMIN_MSG) � 11 AVB013 (AVB_LOG) � 37 ADMIN002 (WEBADM_MSG) � 12

Alarms and log messages � 11 B ALERT alarms and log messages � 12 ALERT001 (AL_LVL_CHG) � 13 BKRST alarms and log messages � 38 ALERT002 (AL_RESET_STATS) � 13 BKRST001 (BKDONE) � 38 ALERT003 (AL_INVALID_THRESHOLD) � 13 BKRST002 (BKBADNFSMNT) � 38 ALERT004 (AL_BAD_THRESH_RULES) � 14 BKRST003 (BKBADDIR) � 38 ALERT005 (AL_THRESHOLDS_CREATED) � 14 BKRST004 (BKCANCEL) � 39 ALERT006 (AL_THRESHOLDS_CHANGED) � 15 BKRST005 (BKWRITEFAIL) � 39 ALERT007 (AL_ALERTER_CMD) � 15 BKRST007 (BKSTARTED) � 40 ALERT008 (AL_ACTIVE) � 15 BKRST008 (BKFAILED) � 40 ALERT009 (AL_RETIRED) � 16 BKRST010 (BKNOSPACE) � 41 ALERT010 (AL_RETIRE_ALARM) � 16 BKRST011 (BKREMDONE) � 41 ALERT012 (AL_THRESHDESC_READ) � 16 BKRST012 (BKREMFAIL) � 42 ALERT013 (AL_ACTION_CMD) � 17 BKRST013 (RSTDONE) � 42 ALERT014 (AL_DIAL_OUT) � 17 BKRST014 (RSTFAIL) � 42 ALERT015 (HIGH_TEMP_ALARM) � 17 BRDG alarms and log messages � 43 ALERT016 (FAN_ALARM) � 18 BRDG001 (BRDG_MSGRCV) � 43 ASAI alarms and log messages � 18 BRDG002 (BRDG_MSGSND) � 43 ASAI001 (A_LINKDWN_PL) � 19 BRDG003 (BRDG_SYSTBL) � 44 ASAI002 (A_LINKDWN_LL) � 19 BRDG004 (BRDG_NOMEM) � 44 ASAI006 (A_LINKDWN_OK) � 20 BRDG005 (BRDG_NOCHAN) � 45 ASAI008 (A_DSCRIPT_TERM) � 20

C ASAI010 (A_LOGFAIL_WREST) � 21 ASAI011 (A_LOGFAIL_NOSWR) � 21

CDH alarms and log messages � 46 ASAI012 (A_LOGFAIL_EXACD) � 22 CDH005 (CDHSUM) � 46, 47, 48, 49 ASAI013 (A_LOGFAIL_TRBSY) � 22 CDH006 (CCASUM) � 47 ASAI015 (A_LOGFAIL_SWOVL) � 23 CDH007 (CDHSUM) � 47 ASAI016 (A_LOGFAIL_UNKNW) � 24 CDH008 (CDHDEL) � 48 ASAI017 (A_ENFAIL_VCBSY) � 24 CDH009 (CCADEL) � 48 ASAI018 (A_ENFAIL_INITG) � 25 CDH012 (CDH_UPL_FAILED � 49 ASAI019 (A_ENFAIL_NONEX) � 26 CDH015 (CDH_NO_PARM) � 49 ASAI020 (A_ENFAIL_SWLMT) � 26 CGEN alarms and log messages � 50 ASAI021 (A_ENFAIL_ARMON) � 26 CGEN001 (UNEXPMSG) � 50 ASAI022 (A_ENFAIL_ACVCS) � 27 CGEN002 (CGEN_SYSTBL) � 51 ASAI023 (A_ENFAIL_SWOVL) � 27 CGEN003 (CGEN_NOMSGQ) � 52 ASAI024 (A_ENFAIL_UNKNW) � 28 CGEN004 (CGEN_MSGRCV) � 52 ASAI025 (A_RESTART) � 19, 20, 28 CGEN005 (CGEN_MSGSND) � 52 ASAI026 (A_NOEVRP) � 28 CGEN006 (CGEN_INIT) � 53 ASAI027 (A_PROT_ERR) � 29 CGEN007 (CGEN_NOMEM) � 54 ASAI028 (A_LOGIN_OK) � 22, 23, 24, 29 CGEN008 (CGEN_NOTR) � 55, 56 ASAI029 (A_ENREQ_OK) � 24, 25, 26, 27, 28, 30 CGEN009 (CGEN_NOSP) � 55 ASAI030 (A_UNK_RET) � 30 CGEN010 (CGEN_NOT1) � 56 ASAI031 (A_UNK_CTL) � 31 CGEN011 (CGEN_TRFAIL) � 56 ASAI032 (A_DSC_MSGS) � 31 CGEN012 (CGEN_TRERR) � 56

Issue 1.0 June 2004 138

VROP alarms and log messages

CGEN013 (CGEN_SPFAIL) � 57 GEN020 (LG_NUMARGS) � 80 CGEN015 (CGEN_T1FAIL) � 57 GEN022 (LG_BADCMD) � 80 CGEN016 (CGEN_T1ERR) � 58 GEN050 (LG_CHG_VALUE) � 80 CGEN017 (CGEN_NOSAVE) � 58

H CGEN018 (CGEN_TRHWFAIL) � 58 CGEN020 (CGEN_NOSERVE) � 59 HOST alarms and messages � 81 CGEN021 (CGEN_NOCHAN) � 59 HOST001 (HOST_NORESP) � 81 CGEN022 (CGEN_NORESTRICT) � 60 HOST002 (HOST_EXPSCR) � 82 CGEN023 (CGEN_DEFOWN) � 61 HOST003 (HOST_RESET) � 82 CGEN024 (CGEN_EXECFAIL) � 61 HOST004 (HOST_FAILACT) � 83 CGEN025 (CGEN_REGFORMAT) � 62 HOST005 (HOST_NOPOLL) � 85 CGEN026 (CGEN_NOIDLE) � 63 HOST006 (HOST_UNKNOWN) � 86 CGEN029 (CGEN_CHANBUSY) � 63 HOST007 (HOST_WRITE) � 86 CGEN030 (CGEN_CHANSNORM) � 63 HOST008 (HOST_OFFSYNC) � 87 CGEN031 (CGEN_SETGRP) � 64 HOST009 (HOST_LOGIN) � 88 CGEN032 (CGEN_FORMAT) � 64 HOST010 (HOST_DEFINE) � 88 CGEN035 (CGEN_LBOLT) � 65 HOST011 (HOST_HELPER) � 89 CGEN036 (CGEN_RTUINFO) � 65 HOST012 (HOST_SESSION) � 89 CGEN040 (CGEN_INVALID_CFG) � 66 HOST013 (HOST_DOWN) � 90 CGEN043 (CGEN_MIRROR_ERROR) � 66 HOST014 (HOST_UP) � 91 CHRIN alarms and log messages � 66 HOST015 (HOST_HIBERNATE) � 92 CHRIN001 (CI_NORESET) � 67 HOST016 (HOST_BRDOPEN) � 92 CHRIN002 (CI_ASAIOPEN) � 67 HOST017 (HOST_INRECOV) � 85, 93 CTI DIP log messages � 67 HOST018 (HOST_OUTRECOV) � 94 CTI005 (CTI_GENERIC) � 68 CTI008 (CTI_NO_QKEY) � 69 I D INIT alarms and log messages � 94

INIT001 (INIT_NODBFILE) � 94 DB alarms and log messages � 69 INIT005 (INIT_CANT_SAVE) � 95 DB003 (DB MSGRCV) � 69 INIT008 (INIT_AUTOCLEAN) � 95 DB004 (DB_SQL_EX) � 70 INIT009 (INIT_MANUALREN) � 96 DB005 (DB_GENERIC) � 70 DB006 (DB_PORT_IN_USE) � 71 L DB007 (DB_PORT_UNAVAIL) � 71

LOG alarms and log messages � 96 DB008 (DB_LOST_CONN) � 72 LOG001 (LG_START_LOG) � 96 DB009 (DB_NEW_PORT) � 73 LOG002 (LG_END_LOG) � 97 DB010 (DB_INFO) � 73 LOG006 (LG_GL_INVALID_MSG) � 97 DIP alarms and log messages � 73 LOG007 (LG_LOGDAEMON) � 98 DIP001 (VS_BUG) � 74

DIP002 (SCRIPT_ERR) � 74 M DSKMG alarms and log messages � 74

DSKMG001 (DSKMSG_SYSFL) � 75 MTC alarms and log messages � 99 DSKMG002 (DSKMSG_RSV) � 75 MTC002 (MTC_STATE_EVENT) � 99 MTC003 (MTC_STATE_ALARM) � 99 F MTC004 (MTC_DIAG_START) � 100 MTC005 (MTC_DIAG_PASS) � 100 FXAUD alarms and log messages � 76 MTC006 (MTC_DIAG_FAIL) � 100 FXAUD002 (NOT_INITSF) � 76 MTC007 (MTC_REQ_FAIL) � 101 FXMON alarms and messages � 77 MTC009 (MTC_LOAD_FAIL) � 101 FXMON004 (NOT_INITSF) � 77 MTC017 (MTC_RESPAWN) � 102 FXMON011 (NOTFINDLOG) � 77

FXMON035 (FXINITGROUPFAIL) � 77 N FXMON039 (FXRTUPROBLEM) � 78

NMS alarms and log messages � 102 G NMS001 (NMS_INTERNAL_ERROR) � 102 NMS002 (NMS_GENERIC_ERROR) � 103 GEN alarms and log messages � 79 NMS003 (NMS_OBJECT_FAIL) � 103 GEN001 (SYSERR) � 79 NMS004 (NMS_API_FAIL) � 103 GEN002 (SYSMSG) � 79

Issue 1.0 June 2004 139

Index


NMS005 (NMS_TRUNK_EVENT) � 104 NMS007 (NMS_BOARD_CONFIG) � 105

P PROXY alarms and log messages � 106 PROXY001 (PX_BROKEN_SOCKET) � 106 PROXY002 (PX_SERVER_FILE_ERROR) � 107 PROXY003 (PX_SYS_MUTEX_FAILURE) � 107 PROXY004 (PSYS_VSYS_QKEY_ERROR) � 108 PROXY005 (PX_MAINT_STATE_CHANGE) � 108 PROXY006 (PX_SYS_THREAD_ERROR) � 109 PROXY007 (PX_SERVER_OOS) � 109 PROXY008 (PX_SEND_FAILURE) � 110 PROXY009 (PX_UNRECOGNIZED_MESSAGE) � 110 PROXY010 (PX_ALL_SRV_PORTS_OOS) � 111 PROXY011 (PX_GENERAL_FAILURE) � 111 PROXY012 (PX_RTU_FAILURE) � 112 PROXY013 (PX_SRV_TIMEOUT) � 112

R RECOG alarms and log messages � 112 RECOG001 (RECOG_MSGRCV) � 113 RECOG002 (MSG_SEND) � 113 RECOG004 (RECOG_GRAMERR) � 113

S SYS alarms and log messages � 114 SYS001-SYS157 � 114

T THRESH alarms and log messages � 114 THRESH001 (THRESH_INFO) � 114, 115, 116, 117 THRESH002 [THRESH_MINOR] � 115 THRESH003 [THRESH_MAJOR] � 116 THRESH004 [THRESH_CRITICAL] � 116 TRACE alarms and log messages � 117 TRACE001 (TRACE_GEN) � 117 TSM alarms and log messages � 117 TSM002 (TSM_LOADSCR) � 117 TSM003 (SPBUSY) � 118, 119 TSM004 (TSM_SPUNAVAIL) � 119 TSM008 (TSM_RTU_BUSY) � 120 TSM009 (NO_RTU) � 120 TSM010 (TSM_QFLUSH) � 121 TSM012 (TSM_NOEXTFUNC) � 121 TSM013 (TSM_NOPROG) � 121 TTS alarms and log messages � 36, 122 TTS002 (TTS_BADFILE) � 122 TTS003 (TTS_TRACE) � 123 TTS004 (TTS_NOTINIT) � 123 TTS005 (TTS_MSGFAIL) � 124 TTS006 (TTS_CONNFAIL) � 124 TTS007 (TTS_STATECHARGED) � 125 TTS008 (TTS_NORESOURCE) � 125 TTS009 (TTS_MGRFAIL) � 126, 127 TTS010 (TTS_ADDFAIL) � 126

U UNIX alarms and log messages � 127 UNIX001 (UNIX_NOTICE) � 127 UNIX002 (UNIX_WARNING) � 127 UNIX003 (UNIX_TROUBLE) � 128 UNIX004 (UNIX_CRITICAL) � 128 UNIX005 (UNIX_INFO) � 128 UNIX006 (UNIX_ERROR) � 129

V VOIP alarms and log messages � 129 VOIP001 (VOIP_ENABLED_CALL_PROC) � 130 VOIP002 (VOIP_DISABLED_CALL_PROC) � 130 VOIP003 (VOIP_CONFIG_ERROR) � 131, 135 VOIP004 (VOIP_NETWORK_ERROR) � 131 VOIP005 (VOIP_REMOTE_ERROR) � 132 VOIP006 (VOIP_MEDIA_ERROR) � 133, 135 VOIP007 (VOIP_OAM_ERROR) � 133 VOIP008 (VOIP_SIGNAL_ERROR) � 133 VOIP009 (VOIP CALL_ERROR) � 134, 135 VOIP010 (VOIP_CALL_FORCE_CLEARED) � 135 VROP alarms and log messages � 136 VROP011 (VROP_NBUFS] � 136 VROP014 (VROP_FSFAIL) � 136 VROP018 (VROP_MALLOC) � 137

AvayaŽ Interactive Response · 2004-05-01 · been certified to meet CTR3 Basic Rate Interface...

Documents

Transcript of AvayaŽ Interactive Response · 2004-05-01 · been certified to meet CTR3 Basic Rate Interface...