Home > ATT > Communications System > ATT AUDIX Voice Power Release 2.1.1 Guide

ATT AUDIX Voice Power Release 2.1.1 Guide

    Download as PDF Print this page Share this page

    Have a look at the manual ATT AUDIX Voice Power Release 2.1.1 Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 164 ATT manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.

    							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 of severity, are really
    events encountered by the software. It is necessary to contact an
    AT&T Field Service Representative only if there is a perceived
    problem with AUDIX Voice Power.
    When an error message is read from the Event Log Report, refer to the
    System Message Listings in this section to determine the action you
    should take. If the action requires you to contact a field service
    representative, this means to call the appropriate customer support center
    for your telephone system. For the name of the center and the telephone
    number, contact your AT&T Account Team or AT&T Authorized Dealer, or
    consult the Switch Notes for your telephone system.
    B-1 
    						
    							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 essential.
    Major means that this is a potentially serious problem and should
    be fixed soon even though it is not interrupting service at this
    moment.
    Informational means that no immediate action is necessary, but
    you should be aware of the system’s condition.
    Status means that this is not an error and no action is necessary.
    n
    n
    This is to inform you of a change of state within the system.
    The messages are divided into subgroups according to the software
    process which outputs the messages:
    n
    n
    nSpeech Processing Library (SPPLIB)—messages 100-299
    Transaction State Machine (TSM) Process—controls transactions
    via script execution and commands—messages 400-499
    Voice Response Output Process (VROP)—manages speech
    database and downloads speech data to the IVP4 voice response
    unit (VRU)—messages 500-599
    Error Tracker (ET) Process—provides error history— messages
    600-699
    n
    B-2 
    						
    							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 5200-5249
    Outcalling Data Interface Process (DIP31)—messages
    5250-5299
    Fax Data Interface Process (DlP25)—messages 5300-534
    Switch Information Data Interface Process
    (DlP24)—messages 5400-5499
    —
    —
    —
    —
    B-3 
    						
    							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
    service representatives. If the message pertains to a hardware unit, the
    mnemonic is followed by the unit type in parentheses.
    The message priority level (critical, major, informational, and status)
    follows the mnemonic. The actual content of the message is shown on the
    second line. It is followed by a brief description.
    Any variable fields within the message are shown enclosed within angle
    brackets () and appear as actual strings or integers on the screen or
    printer.
    When a system message is generated for the first time within an hour, it
    has the following format:
       
    The following is a sample message:
    CRITICAL 904 (CS_C_FUSE) Cabinet Fuse Blown 15:30
    If a system message is generated repeatedly within a short time (typically,
    within a few minutes), the following message format is used to avoid
    flooding the errors file with duplicate messages:
       
    —
    
    B-4 
    						
    							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 associated hardware device is TR. The message
    priority is 
    MAJOR. This means some corrective action is required. The
    description of the error message follows for the TR . In this
    string, the  signifies the board number.
    311 (INITASH) (TR) , MAJOR
    Initialization Error on Channel:  TR:
    
    B-5 
    						
    							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 system.
    Some of the corrective actions must be performed by a System
    Administrator or a field service representative. These messages are
    identified whenever possible.
    Speech Processing Library (SPPLIB)
    108 (SPP_NOSAVE), MAJOR
    Cannot Save Shared Memory () During  To Disk
    The system is attempting to save recent changes entered into the
    configuration. The update was not completed successfully.
    n     Check the permissions on the directories and files in the path
    /gendb/shmem/*.
    n     Ensure that the root file system is not out of free space.
    n     Possible damaged file system (use fsck when the system is at
    single-user level).
    n     Possible disk or disk controller problems.
    B-6 
    						
    							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 Available
    An administrative command was unable to lock a semaphore that was
    allocated to it. 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.
    B-7 
    						
    							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 your AT&T Field Service Representative for assistance.
    403 (TSM_ASS), MAJOR
    TSM: Cannot get script name for channel : ret= 
    TSM was unable to find the specified script corresponding to a channel.
    n     Return to the Voice Equipment window to check that a service is
    assigned to the channel.
    404 (TSM_TRAN), MAJOR
    TSM: Cannot load script  for channel 
    TSM failed to load the specified script from disk. This message occurs if
    TSM encountered an error while opening or reading the script file.
    n  Reload application software if error persists. Ensure that:
    — The assembled script file (.T file) is in directory /vs/trans.
    — The assembled script file (.T file) is in the proper format, that
    is, it is the output produced by the tas assembler.
    B-8 
    						
    							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 Intro(2), Introduction to Section 2 in
    the UNIX Programmer Reference Manual.
    407 (TSM_BADSCRIPT), MAJOR
    TSM: Script  has Bad Format
    The format of the script file (.T file) is invalid. This can occur if the file is
    not the output of the tas assembler.
    n     Ensure that the script file (.T file) is the output of the tas assembler.
    n    Reload the application software if the error persists.
    408 (TSM_SCRD), MAJOR
    TSM: Read Error on Script 
    A read error occurred while TSM was reading the script file from disk.
    n     Hang up the telephone and try again several times.
    n     You have UNIX system disk problems. Reboot the system, then
    reload the software.
    B-9 
    						
    							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  Failing PC at Instruction
    
    The program counter (PC) value is invalid. The PC value is too small or
    too large. This may be caused by an invalid location or the program size
    has exceeded the maximum allowable limit.
    n    Contact the provider of the application software that includes the
    script assigned to < Channel >.
    412 (TSM_TSTART), MAJOR
    TSM: Cannot Start Transaction on channel : 
    The script was loaded into memory, but cannot start execution because
    the initial PC value is incorrect.
    B-10 
    						
    All ATT manuals Comments (0)

    Related Manuals for ATT AUDIX Voice Power Release 2.1.1 Guide