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

							OA&M
Issue  3  May 1998
2-51
link_change(1)
Name
/usr/bin/link_change — Change the destination of LAN GATEWAY links
Synopsis
link_change -n  -h  -i 
Description
link_change is a shell script which is used to change the host destination of a 
LAN GATEWAY link.
 -n  and either -a  or -i  must be 
specified.
link_change will verify the PC’s ability to communicate over the LAN with the 
specified host or IP address (via ping) and print a warning if it is unable to do so, 
but will make the change anyway. After the verification of the host or IP address, 
link_change sends a message to the administration daemon to restart the 
specified LAN link and attempts to connect to the new destination. The user is 
prompted if communication with the administration daemon is not possible. 
link_change updates the LAN parameters file with new destination and exits.
link_change can only be invoked by the super-user.
link_change cannot be used to add or delete LAN GATEWAY link; the link to be 
changed must exist in the current configuration. Links may only be added or 
deleted during the ISDN/LAN GATEWAY installation process.
See Also
lan_change(1)
lan_stat(1) 
						

							OA&M
2-52Issue  3  May 1998 
link_offline(1)
Name
/usr/bin/link_offline — Take down LAN GATEWAY connection
Synopsis
 link_offline -1
Description
The link_offline command sends a message to the LAN GATEWAY 
administration daemon requesting the specified link(s) be put offline. Both TLI and 
TCP connectivity are broken and the retry strategy will be disabled. Any LAN link 
put offline will not be put back online until a lan_restart request has been 
made or the PC is rebooted.
The -1 options makes the request for all LAN GATEWAY links.
See Also
link_restart(1)
link_status(1) 
						

							OA&M
Issue  3  May 1998
2-53
link_restart(1)
Name
/usr/bin/link_restart — Take down the LAN GATEWAY connection and 
restart it
Synopsis
 link_restart  -1
Description
The link_restart command sends a message to the LAN GATEWAY 
administration daemon requesting the specified link(s) be taken offline and then 
immediately reestablished. Both TLI and TCP connectivity are broken.
The -1 option makes the request for all LAN GATEWAY links.
See Also
link_offline(7)
link_status(1)
lan_stat(1) 
						

							OA&M
2-54Issue  3  May 1998 
link_status(1)
Name
/usr/bin/link_status — Print Status of IPCI Link(s) and LAN GATEWAY 
links
Synopsis
 link_status[-n] LinkNo [-a]
Description
If -n link No is specified, a status report is printed for only that link. Otherwise, 
a status report is given for all administered links. The report is printed to stdout. 
link_status is a shell script that determines if a specified link belongs to an 
IPCI group or a LAN GATEWAY group and (via the appropriate OA&M call) prints 
the status of the link(s).
If -
a is specified, a long version of the status for LAN GATEWAY links is 
generated.
See the manual page for lan_stat(1) for more details on the LAN GATEWAY 
link status.
See Also
isdn_trace(1) 
ipci_stat(1) 
						

							OA&M
Issue  3  May 1998
2-55
log_msgs(4)
Name
log_msgs — UNIX ASAI adjunct Log Message File
Description
This file contains an explanation of certain status or error indications received by 
ipci_admin (1) from the IPCI device driver as it monitors the admin stream. 
Where applicable, it also contains remedial action information for the system 
administrator. Each status or error number is unique.
The information in this file is used by ipci_admin(1). All characters in this file 
are printable ASCII characters. This file resides in the /usr/adm/asai directory.
There are two types of lines in this file: 1) comment lines and 2) message lines.
A comment line has “#” as its first character. It is followed by zero or more ASCII 
characters that are followed by a new-line character. A comment line may contain 
a maximum of 61 characters. This limit includes the “#” of character and the 
new-line character. “Blank” comment lines can be used to provide relief between 
successive messages.
A message for a particular status or error number may consist of one or more 
message lines. The format of a message line is:

“number” is the status or error number. It is a field of six characters with the 
number right justified. The number consists of digits only and is padded to the left 
with either blanks or zeroes.
 is from 0 to 53 ASCII characters.
Subsequent message lines of the same message contain the same status/error 
number also. The messages in the file must be in ascending status/error number 
order.
Files
/usr/adm/isdn/log_msgs
See Also
ipci_admin(1)
asai_log(4) 
						

							OA&M
2-56Issue  3  May 1998 
pcisdn.bin(4)
Name
pcisdn.bin — IPCI Board ISDN Program File
Description
This program file is downloaded to the IPCI board by ipci_on(1).
Files
/usr/adm/isdn/pcisdn.bin
See Also
ipci_on(1)
boot.bin(4) 
						

							OA&M
Issue  3  May 1998
2-57
signal(7)
Name
signal — IPCI and LAN GATEWAY Device Driver Communication Files
Description
The signal devices allow direct communication between a Lucent Technologies 
application program and the ECS.
There is a one-to-one correspondence between each signal stream and the IPCI 
board it serves or, in the case of LAN GATEWAY, between the signal stream and 
the MAPD. Hence, signal01 corresponds to board 1, etc.
Note the path difference for LAN GATEWAY links. LAN GATEWAY links reside in 
the directory /dev/esai/signal0-8.
Notes
These files will have the same major device number as the admin(7) and 
command(7) files. Their minor device number will be 1, 2, 3 or 4 depending on the 
board number.
The names of these files are shown below.
Files
/dev/isdn/ipci/signal01
/dev/isdn/ipci/signal02
/dev/isdn/ipci/signal03
/dev/isdn/ipci/signal04
/dev/esai/signal0[1-8]
See Also
ipci_admin(1)
admin(7)
command(7)
cmd(7) 
						

							OA&M
2-58Issue  3  May 1998 
CV/LAN Administration
OA&M changes for client and server    
It is mandatory for the client and server both to connect to the same TCP/IP port.  
In order to meet this requirement, for the UNIX platforms in /etc/services file 
and for Windows NT platform in 
C:
tdir
1\system32\drivers\etc\services file, the following line must 
be administered: 
       CV/LAN     XXXX/tcp   # Callvisor LAN service
9999 is an unused/unreserved TCP port name.
1. ntdir is the Windows NT System directory where NT has been installed, for example, winnt 4.0.  
						

							Issue  3  May 19983-1
3
Introduction to ASAI
This chapter is an overview of ASAI — what it does and how it works. Its purpose 
is to provide enough general information to design an application. Specific 
information, in the form of manual pages for the ASAI functions and capabilities, 
can be found in Chapter 8, ‘‘ASAI Capability Primitives’’ and Chapter 9, 
‘‘Programming Manual Pages.’’ Coding examples appear throughout Chapter 4, 
‘‘ASAI Library Functions.’’
The Adjunct-Switch Application Interface (ASAI) is an open standard interface that 
permits an application running on an adjunct computer to access telephony 
services provided by the ECS. Lucent Technologies’ CallVisor Switch-Adjunct 
Application Interface Platform for the UNIX system provides connectivity between 
an adjunct and the DEFINITY ECS via the ISDN personal computer interface 
(IPCI). 
The ASAI library, a dynamic C library of functions and capabilities, provides an 
application programmer with easy access to the IPCI so that his or her application 
program can utilize the DEFINITY ECS services or features. The ASAI library also 
allows the ECS to access services provided by the adjunct, such as Routing and 
Heartbeat.
The ASAI library provides a set of standard capabilities for performing the 
following tasks:
nManaging active calls to which the adjunct is not a party (called “third party 
calls”); for example, transferring a call or putting a call on hold
nQuerying or setting values of various indicators maintained by the
ECS — for example, setting on the message-waiting indicator
nActivating or deactivating a number of the ECS features — for example, 
call forwarding or send all calls
nRouting incoming and outgoing calls 
						

							Introduction to ASAI
3-2Issue  3  May 1998 
nTesting a communication path to ensure that the ASAI link is operating
nTerminating (aborting) calls when necessary
nReading event reports to provide a complete audit trail of all of these 
activities
Each group of capabilities is called an Application Service Element or ASE.
Capabilities are the building blocks of ASAI. They are sent from the adjunct to the 
ECS or received by the adjunct from the ECS. The exchange of capabilities is 
managed by the ASAI library functions asai_send() and asai_rcv().
Library functions perform another very important task: controlling the 
communication path across which capabilities are exchanged. The functions 
asai_open(),asai_set_env(),asai_get_env(), and asai_close() are 
used to establish and terminate a communication path.
In addition, asai_errval() provides error information to be used in 
error-handling routines.