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

Here you can view all the pages of manual Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual. The Lucent Technologies manuals for Communications System are available online for free. You can easily download all the documents as PDF.

Page 71

OA&M
Issue  3  May 1998
2-21
asai_ver(1)
Name
asai_ver — Print ASAI product and software version information
Synopsis
asai_ver
Description
ASAI product information is printed to stdout. This includes the name, date and 
version of the ASAI product.
Exit Codes
If there are no errors, the exit code is 0. Otherwise, the exit code is set to 1 to 
indicate an error.
Files
/usr/adm/asai/asai.Name
/usr/adm/asai/asai.Date
See Also
asai.Date(4)
asai.Name(4) 

Page 72

OA&M
2-22Issue  3  May 1998 
boot.bin(4)
Name
boot.bin — IPCI Board Bootstrap Loader Program File
Description
This data file, containing the IPCI Bootstrap Loader Program, is downloaded to 
the IPCI board by ipci_on. When this program is started, it is used to load the 
ISDN software onto the board.
Files
/usr/adm/isdn/boot.bin
See Also
ipci_on(1)
pcisdn.bin(4) 

Page 73

OA&M
Issue  3  May 1998
2-23
cmd(7)
Name
cmd(7) — LAN GATEWAY Streams Module Communication File
Description
The cmd file allows communication between certain OA&M commands and the 
LAN GATEWAY streams module.
This device is meant to be used by OA&M delivered commands and not by 
customer commands.
NOTE:
This file has the same major device number as the LAN GATEWAY 
admin(7) and the signal(7) files.
Files
/dev/esai/cmd
See Also
admin(7)
signal(7) 

Page 74

OA&M
2-24Issue  3  May 1998 
command(7)
Name
command — IPCI Streams Device Driver Communication File
Description
The command file allows communication between certain OA&M commands and 
the IPCI streams device driver. The IPCI streams device driver communicates 
with the IPCI board and with software on the board.
This device is meant to be used by OA&M delivered commands and not by 
customer commands.
Notes
This file has the same major device number as admin(7) and the signal(7) files.
Files...

Page 75

OA&M
Issue  3  May 1998
2-25
esai_alarm(1)
Name
esai_alarm — Turn on or off isdn_bri maintenance alarming
Synopsis
 esai_alarm -a|d [-b1...-b8] [-t0...-tn] [-e] [-?] 
Description
esai_alarm
Uses the suspend and resume routines to turn on or off the ASAI BRI port alarms 
associated with the link specified.
-a
Activates alarming
-d
Deactivates alarming
-b
Specifies the link, where =1...8, has sent the message 
-t
Sets the time-out to n seconds, where =0...n. Default is -t3
-e
Displays the exit codes list...

Page 76

OA&M
2-26Issue  3  May 1998 
Exit Codes
If esai_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 link
-4 =  Failure to receive messages from link
-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 

Page 77

OA&M
Issue  3  May 1998
2-27
esai_trace(1)
Name
esai_trace — Trace LAN Gateway (ESAI) ASAI messages
Synopsis
esai_trace
Description
esai_trace is a general-purpose diagnostic tool. Its output is the actual ASAI 
message traffic to and from the ASAI-E LAN Gateway board. The message trace 
has the following general format:
       
The following table explains the format.
Received messages (those coming from the ECS) usually have uplink in the 
function field.
Transmitted messages (those going to the ASAI-E...

Page 78

OA&M
2-28Issue  3  May 1998 
The function name is separated from the starting byte number by a slash ( / ).
The starting-byte number indicates the byte number of the beginning (left most) 
byte of the hex field. The first line of a message has a byte number of 0. The 
second line has a number greater than zero (usually 12) and so forth for each 
additional line of the same message. The next message will have a byte number 
of 0 for the first line.
The diagnostic field indicates the purpose of the entry....

Page 79

OA&M
Issue  3  May 1998
2-29
ipci(4)
Name
ipci — Pump and start administration for all IPCI boards
Synopsis
ipci
Description
ipci is a shell script that starts the ipci administration daemon process, 
ipci_admin (1) located in /etc/idrc.d.
Operation
The ASAI program is executed once per machine boot in the multiuser init level 
 of 2. The name of the log file (asai_log) is changed to old_asai_log. The 
administration daemon [asai_admin(1)] is then started. When this is done, the 
standard error device is...

Page 80

OA&M
2-30Issue  3  May 1998 
ipci_admin(1)
Name
ipci_admin — Administer admin and signal files
Synopsis
ipci_admin
Description
 ipci_admin sets up the protocol stack for signal device files and logs messages 
received from the admin(7) stream.
Operation
The ipci_admin program is executed once per machine boot. It is started by the 
ipci(4) script and becomes a daemon process.
This program has two tasks.
nTo add the necessary module(s) into the signal(7) streams that carry ISDN 
D channel signaling or...
Start reading Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual

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

All Lucent Technologies manuals