Home > Lucent Technologies > Communications System > Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual

Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual

    Download as PDF Print this page Share this page

    Have a look at the manual Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.

    Page
    of 458
    							OA&M
    Issue  3  May 1998
    2-31
    admin stream. After processing the received data, this program then waits for 
    more data from the admin stream.
    The admin and signal stream files are always kept open by ipci_admin.
    Messages
    All of the following messages in the asai_log file are identified by a time stamp 
    and the phrase ipci_admin:
    nStatus Messages — Two status messages are written to the asai_log 
    file /usr/adm/asai/asai_log(4)by ipci_admin. One message 
    indicates the beginning of the ipci_admin program. The other message 
    indicates the successful setup of each signal stream.
    nError Messages — If ipci_admin encounters a nonrecoverable error 
    situation, an error message is sent to the console if it cannot be logged, 
    otherwise, the message is sent to the log file.
    nPCI Driver Status Messages — For every status message received 
    from the IPCI driver, a corresponding formatted message is written to the 
    asai_log file.
    !CAUTION:
    The ipci_admin daemon should never be killed with a kill -9;
    a kill (-15) should be used to allow the daemon to clean up the 
    semaphores and message queues prior to exiting. If the semaphores 
    or message queues become locked or hung, they can be freed using 
    the ipcs(1) UNIX utility.
    Exit Codes
    This program, if it exits, will exit with a code of 1. Since this program is meant to 
    be run as a daemon process, the exit code probably does not carry any great 
    significance.
    Files
    /dev/isdn/ipci/admin
    /dev/isdn/ipci/signal
    /usr/adm/asai/asai_log
    /usr/adm/asai/log_msgs 
    						
    							OA&M
    2-32Issue  3  May 1998 
    See Also
    admin(7)
    asai_log(4)
    ipci(4)
    log_msgs(4)
    signal(7)
    link_restart(1)
    link_status(1) 
    						
    							OA&M
    Issue  3  May 1998
    2-33
    ipci_off(1)
    Name
    ipci_off — Put specified IPCI board offline
    Synopsis
     ipci_off [n]
    Description
    This command is used to place board n offline. (The value of n can be 1, 2, 3
     or 4.) When this is done, no new instances of communication between the UNIX 
    ASAI adjunct and the ECS can be started. After executing this command, the 
    board cannot be used for any signaling requests. To place it back online, it must 
    be pumped using ipci_on.
    Exit Codes
    If an error is encountered or if the board is already offline, 1 is returned as the exit 
    code. Otherwise, 0 is returned.
    Notes
    When a board has reached the offline state, it cannot be used for any signaling 
    requests. To place it back online, it must be pumped.
    Files
    /dev/isdn/ipci/command
    See Also
    command(7)
    ipci_on(1)
    ipci_stat(1) 
    						
    							OA&M
    2-34Issue  3  May 1998 
    ipci_on(1)
    Name
    ipci_on— Pump Software to IPCI Board(s)
    Synopsis
     ipci_on [n]
    Description
    ISDN software is placed on the IPCI board(s) and that software is initialized. The 
    board is then considered to be 
    online.
    If a value of n is specified, only that board is addressed. If no value of 
    n is 
    specified, the software is sent to all IPCI boards and all IPCI boards are placed 
    into the
     online state.
    If n is used, its value will be 1, 2, 3 or 4. Board numbers are assigned to the 
    physical boards when the system administrator installs the software.
    Operation
    First, /usr/adm/isdn/boot.bin (the bootstrap loader) is copied to the stream 
    file /dev/isdn/ipci/ command. When this has been done successfully, the 
    IPCI streams device driver starts running this program on the board(s). Then 
    /usr/adm/isdn/pcisdn.bin, the ISDN program, is copied. When this has 
    been completed successfully, the pcisdn.bin program is started on the 
    board(s) by the IPCI streams device driver. Then, the software on the boards is 
    initialized.
    Messages
    All of the following messages written by ipci_on are identified by a date and 
    time stamp followed by the program name ipci_on:
    nError Messages — If an error is encountered, a message is written to 
    stderr and a copy of the same message is written to the log 
    /usr/adm/asai/asai_log(4)file.
    nStatus Messages — Two status messages are written to the asai_log 
    file. One message indicates the beginning of the pumping. The other 
    message indicates the ending of the pumping.
    Exit Codes
    For success, 0 is returned. If an error is detected, 1 is returned. 
    						
    							OA&M
    Issue  3  May 1998
    2-35
    Notes
    This program is executed at boot time for all IPCI boards. It can be executed any 
    other time for a board(s) that has successfully been placed offline. ipci_off 
    should be used to take the board offline.
    Files
    /usr/adm/asai/asai_log
    /usr/adm/isdn/boot.bin
    /usr/adm/isdn/pcisdn.bin
    /dev/isdn/ipci/command
    See Also
    asai_log(4)
    boot.bin(4)
    command(7)
    ipci(4)
    ipci_off(1)
    pcisdn.bin(4) 
    						
    							OA&M
    2-36Issue  3  May 1998 
    ipci_stat(1)
    Name
    ipci_stat — Print Status of IPCI Board(s)
    Synopsis
    ipci_stat [n]
    Description
    If n is specified, a status report is printed for only that board. Otherwise, a status 
    report is given for all boards. The report is printed to stdout.
    For each board, four items are printed:
    line_control
    Normally, the adjunct computer (UNIX ASAI adjunct) should be in control of the 
    interface between the ISDN phone and the ECS. When this is the case, pc is 
    printed. If the adjunct software is not in control of this interface, phone is printed.
    Line control is determined by the status of relays on the IPCI board. When they 
    are 
    energized, the phone and the ECS are connected by the pc software. When 
    the relays are not 
    energized, the phone and the ECS are directly connected by a 
    metallic connection.
    switch_connection
    The connection to the ECS is either active or not 
    active.
    switch_tei
    The board LAPD Terminal Endpoint Identifier (TEI) is printed as a decimal number 
    and will not be greater than 127.
    link_status
    Indicates the status, up or down, of both levels 1 and 2.
    Files
    /dev/isdn/ipci/command
    See Also
    command(7) 
    						
    							OA&M
    Issue  3  May 1998
    2-37
    ipci_test(1)
    Name
    ipci_test — Test an IPCI Board
    Synopsis
     ipci_test[n]
    Description
    IPCI board n is tested.
    Operation
    If the board is online, nondestructive (loop back) online tests are done. If the 
    board is offline, board memory tests are done.
    Return Value
    For success, 0 is returned. If an error is detected, 1 is returned.
    Output
    The online/offline status is printed on stdout followed by the results of the test. 
    Errors are printed on stderr.
    Files
    /dev/isdn/ipci/command
    /usr/adm/isdn/boot.bin
    See Also
    boot.bin(4)
    command(7)
    ipci_off(1)
    ipci_on(1)
    ipci_stat(1) 
    						
    							OA&M
    2-38Issue  3  May 1998 
    ipci_ver(1)
    Name
    ipci_ver — Print ipci product and software version information
    Synopsis
    ipci_ver
    Description
    Ipci product information is printed to stdout. This includes the name, date and 
    version of the pumpware, the ipci product and the device driver as well as the 
    board identification number.
    Exit Codes
    If there are no errors, the exit code is 0. Otherwise, the exit code is set to 1 to 
    indicate an error. 
    						
    							OA&M
    Issue  3  May 1998
    2-39
    isdn_alarm(1)
    Name
    isdn_alarm — Turn on or off isdn_bri maintenance alarming
    Synopsis
    isdn_alarm — a|d [-b1...-b4] [-t0...-tn] [-e] [-?] 
    Description
    isdn_alarm uses the suspend and resume routines to turn on or off the 
    isdn_bri alarms that are sent from the ECS.
    -a
    Activates alarming
    -d
    Deactivates alarming
    -b
    Specifies the board, where =1...4, is sent the message
    -t
    Sets the time-out to 
    n seconds, where =0...n ; the default is -t3
    -e
    Displays the exit codes list shown below
    -?
    Displays the terse help message 
    						
    							OA&M
    2-40Issue  3  May 1998 
    Exit Codes
    If isdn_alarm fails, one of the following exit codes is returned:
     0 =  The alarm condition was changed per request
    -1 =  Failure due to inadequate memory
    -2 =  Open stream failure
    -3 =  Failure to send message to board
    -4 =  Failure to receive messages from board
    -5 =  Time-out while waiting to receive a message
    -6 =  Layer 1 is down (could not attempt reset)
    -7 =  Layer 2 failed to recover from reset
    -8 =  State machine transitioning, try again 
    						
    All Lucent Technologies manuals Comments (0)

    Related Manuals for Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual