ATT AUDIX Voice Power Release 2.1.1 Guide

Error Messages
Introduction to System Messages
System messages are logged automatically in an error log when problems
or potential problems occur within the AUDIX Voice Power system. The
System Manager can access the error log by selecting Event Log
Report from the System Report menu. Use the procedures Viewing the
Event Log Report and Using the Explain Command in Chapter 5 to read
the Event Log Report.
NOTE:
The Event Log Report is designed to be used by support
personnel. Many of the errors, regardless...

Appendix B: Error Messages
Messages call attention to the following types of conditions:
n   Software failures
n    Hardware failures at the board level
n    Diagnostic test results (when initiated by the error tracker software)
n   Alarm conditions
n   System restart conditions
Sometimes, messages require corrective action. The urgency of the
message is specified with one of the following definitions in the message:
n
n
Critical means that the error is interrupting service, so immediate
action is...

Appendix B: Error Messages
n
nMaintenance (MTC) Process—runs temporary diagnostics—
messages 700-799
Data Base Initialization (DBINIT)—messages 1700-1799
Tip/Ring Interface Process (TRIP)—messages 2000-2099
User Applications (APP)—messages 5000 and up
n
n
—
—
—
—Voice Mail Database Interface Process (DlP2)—messages
5000-5099
Message Delivery Process (DIP21 )-messages 5000-5099
Administration Process—messages 5100-5149
DCP Communication Process (DlP27)—messages
5150-5199
Reports Process (DlP3)—messages...

Appendix B:  Error Messages
System Message Format
In this section, the system messages are listed in a slightly different
format than they are written to the errors file. The messages listed here
include additional information to help you understand the message and
take the proper corrective action.
The system messages in this section begin with a message identification
(msg_id) number. Following the msg_id number is the message
mnemonic. The mnemonic is useful when identifying an error message to...

Appendix B:  Error Messages
The following is a sample message:
CRITICAL 40 instances of 904 (CS_C_FUSE) by 15:31
The first, tenth, twentieth, fortieth, eightieth, and so on messages are
written to the errors file. A message that occurs a large number of times
indicates a significant problem that should be dealt with as soon as
possible.
The following example illustrates the format of a typical system message
as listed in this section. In the example, the msg_id is 311. The mnemonic
is 
INITASH and the...

Appendix B: Error Messages
System Message Listings
The messages are arranged in numerical order by msg_ids. They are
organized in subgroups according to the software process that outputs the
message. Each message appears in bold type.
Following each message is a short explanation of the message and the
recommended corrective action. A similar explanation appears when you
use the explain command. If no corrective action is provided, the message
is either informational or is corrected automatically by the...

Appendix B: Error Messages
109 (VROP_GSEMA), MAJOR
Cannot Get VROPQ Semaphore To Lock It
An administrative command could not access a control semaphore. The
failure of the command is not serious, but the failure indicates major
interprocess communication failures in the system are likely to follow
soon.
n     Try stopping the system and then restarting it. If this is
unsuccessful, a reboot of the processor will correct the problem.
110 (VROP_LSEMA), MAJOR
Cannot Lock VROPQ Semaphore But It Should Be...

Appendix B: Error Messages
Transaction State Machine (TSM) Process
401 (TSM_RCV), CRITICAL
TSM: Cannot Receive Msg: ret = , errno = 
TSM failed to receive a message from another process. The value of the
errno indicates the reason for the error.
n    Contact your AT&T Field Service Representative for assistance.
402 (TSM_SND), CRITICAL
TSM: Cannot Send Msg to : ret= 
errno =  mcont = 
TSM failed to send a message to another process. The value of the errno
indicates the reason for the error.
n    Contact...

Appendix B:  Error Messages
405 (TSM_NOSLOT), MAJOR
TSM: No Slot Available for Script 
n     Contact your AT&T Field Service Representative for assistance.
406 (TSM_NOSCRIPT), MAJOR
TSM: Cannot Find Script ; errno = 
TSM failed to open the specified script file. This occurs if the script file
does not exist. The value of the errno indicates the cause of the error.
n    Ensure that the script file (.T file) is in directory /vs/trans.
n    Script needs to be assigned.
n    Look up the value of errno in...

Appendix B: Error Messages
409 (TSM_MTSCRIPT), MAJOR
TSM: No Data in Script 
The specified script has no instructions.
n       Reload the application software if the error persists.
410 (TSM_SHMFAIL), CRITICAL
TSM: Shared Memory failure: , errno 
TSM failed to attach a shared memory segment. This error can only be
seen at initialization. The errno indicates the reason for the error.
n    Contact your AT&T Field Service Representative for assistance.
411 (TSM_PC_FAIL), MAJOR
TSM: Script on Channel...