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

							Installation
Issue  3  May 1998
1-15
Server Installation on UNIX 
For the CV/LAN, UNIX Platform refers to both Unixware and Solaris x86.
The CV/LAN server can only be installed after CVISDN and CVASAI have been 
installed. 
1. To install the CV/LAN server, type the command:
pkgadd -d diskette1
2. Place the Lucent Technologies CallVisor PC CV/LAN Server disk in the 
appropriate drive and follow the online instructions. Pkgadd displays that 
the package is available to process. Press   to continue the 
installation.
After the installation procedure is complete, the installation program asks you to 
remove the diskette from the disk drive. Shutdown instructions and the message 
Installation of  was successful, are also displayed.
Client Installation on UNIX 
You can install the PC CV/LAN Client package at any time. 
1. Enter the command:
pkgadd -d diskette1
2. Place the PC CV/LAN Client disk in the appropriate drive and follow the 
online instructions.
3.Pkgadd displays that the PC CV/LAN Client package is available to 
process. Press   to continue the installation.
4. After the installation procedure is complete, remove the diskette from the 
disk drive. The message Installation of  was 
successful, is displayed.
Client Installation on Windows NT
1. To install the CV/LAN Client on a Windows NT 4.0 system, insert the Client 
diskette in drive A.
2. Click on the RUN File Menu Item under Program Manager or File Manager, 
type Setup in the dialog box, and press OK. 
3. Follow Setup instructions.
RETURN
RETURN 
						

							Installation
1-16Issue  3  May 1998 
NOTE:
After the Setup is complete, CV/LAN.DLL, the dynamic link library and 
CV/LAN.LIB, the import library, will be installed under a subdirectory called 
Program
.
Running the Sample Application
To run the application on UNIX, the command is itt .
For Windows NT 4.0 system, the command itt  can be run from a 
DOS window. 
						

							Installation
Issue  3  May 1998
1-17
DEFINITY ECS Administration
The DEFINITY ECS BRI line must be administered to establish ASAI connectivity 
between the DEFINITY ECS and the adjunct computer. Use the add station or 
change station command to administer the BRI line. Use the following table as a 
guide.
The Type, XID, Fixed TEI, TEI, MIM Support and CRV Length fields all must have 
the indicated required contents in order to match the built in administration of the 
IPCI board and CallVisor PC ASAI software.
The ISDN protocol stack, specifically the QP module, supports version selection. 
Version 1 (default) corresponds to G3V3, Version 2 corresponds to G3V4 and 
Version 3 corresponds to the DEFINITY ECS Release 6. For Release 6
3, the 
default also is 3. To find out which software version is on the DEFINITY ECS, use 
the list conf soft command. The Software Version is displayed on the Memory 
Resident: line.
3. The default is 3 which supports Release 5 and 6.
Table 1-1. Field Name and Requirements
Field Name Required/Optional Contents
Extension: R System dial plan sequence
Type: R ASAI
Port: R Port connecting to ASAI line
Name: O Your name or handle
XID: R y
Fixed TEI: R y
TEI: R 3
MIM Support: R n
CRV Length: R 2
Event Minimization R n 
						

							Installation
1-18Issue  3  May 1998 
Configuration
This section assumes that you have read the installation steps in this document.
NOTE:
The Network Support Utilities (NSU) package must be installed before you 
can install the CallVisor software packages.
The NSU package contains the streams utilities, header files, libraries and other 
files that are needed to add streams modules to the UNIX system kernel.
Upgrading Software
The upgrade procedure consists of removing the existing packages and installing 
the new packages as described in ‘‘DEFINITY ECS Administration’’ on page 1-17 
of this chapter. Upgrade the system when no one else is using the computer.
You must supply the configuration information as part of the upgrade procedure.
NOTE:
Before beginning the upgrade, copy or print the current configuration 
parameters for future reference.These parameters can be found in the files 
/usr/adm/asai/asai_parms and /usr/adm/isdn/ipci_parms.
1. Log in as root. Bring the computer to single-user mode and then run state 1 
by entering the command:
shutdown -iS -y -g120
2. Press Ctrl-d to proceed and enter 1 for the selected run state.
3. Remove the CallVisor PC software by entering the commands:
pkgrm cvasai and pkgrm cvisdn 
4. Now install the new version. Configure the software as described in the 
‘‘Configuring and Reconfiguring Software’’ on page 1-19 of this chapter.
Removing Software
To remove software, enter the command:
           pkgrm cvasai
and
pkgrm cvisdn
and
pkgrm cvesai 
						

							Installation
Issue  3  May 1998
1-19
pkgrm command removes all package-created and installed files, along with 
directories created when the package was installed.
When you execute pkgrm cvasai, all files in the /usr/adm/asai directory, 
along with all other files belonging to the ASAI package, are removed.
Also, for isdn package, when you execute pkgrm cvasai, all files in the 
/usr/adm/isdn directory, along with all other files belonging to the ASAI 
package, are removed.
All ASAI header files installed in /usr/include/asai and ISDN/IPCI headers 
for the ISDN package in the /usr/include/isdn directory are removed. The 
directories are removed only if they are empty.
NOTE:
If you have local header files or other files in these directories, they will not 
be removed and neither will the directory.
The pkgrm procedure will build a new UNIX kernel. When this is completed, a 
message will be displayed requesting to reboot the system. After both packages 
have been removed, execute the command
shutdown -i6 -y -g0
to reboot the system.
Configuring and Reconfiguring Software 
The initial part of the installation and upgrade procedure consists of configuring 
the software. You must enter the information when prompted by the software. See 
the ‘‘Configuration’’ on page 1-18 of this chapter for more details. For the ISDN 
package, you must enter the number of IPCI boards to be installed or those 
already installed, the IRQ number, the PC memory addresses as well as the 
matching version parameters. Refer to the table below for default IPCI values:
Table 1-2. Default IPCI Configuration Values
ISDN board # IRQ/IVN PC memory address
1 2 d0000
2 2 d4000
3 2 d8000
4 2 dc000 
						

							Installation
1-20Issue  3  May 1998 
Note that regardless of the number of ISDN boards installed in the computer, the 
same IRQ/IVN number is used. Matching Versions Requirement for the ISDN 
protocol stack, specifically for the QP module, must be done correctly or the ASAI 
link will not come up. Three new tunable parameters are provided to allow 
selecting the desired version and allowable alternatives. QP_DESIRED is set to 
the desired version. Version 1 corresponds to G3V3, Version 2 corresponds to 
G3V4 and Version 3 corresponds to the DEFINITY ECS Release 6. For Release 
6
4, the default also is 3. QP_HIGHERVER and QP_LOWERVER are provided to 
allow higher version and/or lower version operation.
The tunable parameters are located in /etc/conf/cf.d/stune. The defaults 
are:
QP_DESIRED_VER is set to 3 (Release 6)
QP_HIGHERVER is set to 3 to allow higher (later) versions
QP_LOWERVER is set to 1 to allow lower (earlier) versions
If you have to reconfigure your adjunct computer system (to change the version, 
for example), do so when no one else is using the adjunct.
To change the values, edit the /etc/conf/cf.d/stune file. Follow the 
standard tuning procedures and rebuild the kernel, then reboot the system. 
Execute the command
shutdown -i6 -y -g0
to reboot the system.
If the version parameters are incompatible with the ECS version, the BRI link will 
not start up. The QP module will log this error to the system console and the crash 
buffer.
For the ASAI package, you must enter the number of ASAI nodes/IPCI boards 
installed: 1, 2, 3, or 4 (if that information is not available at the time of installation).  
If the ISDN package was installed first, this information is available to the ASAI 
package.
If only one IPCI board was configured for the ISDN package, the following 
message is displayed:
Configuring  for 1 ASAI Nodes.
Reconfiguring the packages requires you to reinstall the ISDN and ASAI software.
If you have to reconfigure your adjunct computer system (to add a board, for 
example), do so when no one else is using the adjunct.
4. The default is 3 which supports Release 5 and 6. 
						

							Installation
Issue  3  May 1998
1-21
NOTE:
Make sure that you save a copy of the current configuration parameters for 
future reference.
Memory Considerations
This section introduces a number of concepts that assume practical experience 
with administration of the ASAI applications package. The material presented 
here is discussed in detail in Chapter 1, “ASAI and Capability Groups” of 
DEFINITY Enterprise Communications Server Release 6 CallVisor ASAI 
Technical Reference.
ASAI services are broken down into functional sets called capability groups. 
Capability groups enable the adjunct to communicate and control the DEFINITY 
ECS. Central to the idea of capability groups and ASAI in general is the concept of 
an association.
An association is a channel of communication between the adjunct and the 
DEFINITY ECS that is used for messaging purposes. An association begins with 
initiating capabilities, controlling capabilities manipulate messages during an 
association and terminating capabilities end an association.
An adjunct or more specifically, each BRI board installed on an adjunct, can 
manage many active associations at one time and each association must be 
tracked by the CallVisor ASAI software drivers. Tracking consumes adjunct 
memory that must be reserved for the CallVisor drivers (148 bytes are required to 
track a single association).
The amount of memory to be reserved is specified by the NCLID (number of 
cluster ids) environment variable. NCLID effectively limits the number of active 
ASAI associations that are allowed to run on each BRI board. It is important to 
note that the NCLID specifies the maximum number of associations that may run 
on each BRI board, not the maximum number for all boards combined.
The NCLID default is 2048. This should be sufficient for the majority of 
applications using ASAI. However, if the adjunct processor has a limited amount 
of memory, or if the ASAI application is controlling a large number of stations or 
calls, the NCLID will need to be adjusted. In any case, the NCLID value should 
always be set to conform to your system’s specific operational needs.
The default of 2048 specifies that each BRI board installed be limited to 2048 
active associations and that approximately 296K of adjunct memory be reserved 
on behalf of each board (2048 x 148 bytes per association = 296K). If four boards 
are installed, a total of approximately 4 x 296K will be reserved for tracking their 
combined associations.
Note that with four boards installed, if the adjunct has four megabytes of memory 
or fewer, system performance will suffer greatly. In this case, it is recommended 
that one or more boards be removed, or that the NCLID be lowered. Lowering the  
						

							Installation
1-22Issue  3  May 1998 
NCLID reduces both the number of active associations and the amount of adjunct 
memory reserved for each board.
For instance, setting the NCLID to 1024 reduces the number of active 
associations per board to 1024 and cuts the amount of reserved memory per 
board to 148K (1024 x 148). Alternately, setting the NCLID to 512 reduces the 
number of active associations per board to 512 and cuts the amount of reserved 
memory per board to 74K (512 x 148). These settings are not likely to impact the 
performance of most applications.
Certain ASAI applications may require the NCLID to be increased above the 
default of 2048. If the ASAI application is using one ASAI link to control a large 
number of calls on a R5r, the NCLID may need to be increased. There is, 
however, a practical limit to which the NCLID value may be raised. Appendix B 
“ASAI and Release 6 Requirements” of 
DEFINITY ECS Release 6 CallVisor ASAI 
Technical Reference
 discusses the capacity requirements and constraints for the 
DEFINITY ECS Release 6 in detail.
For example, Table B-1 of that appendix lists all the R5r systemwide ASAI limits 
for the maximum number of domain-control station associations as 6000. 
However, setting the NCLID to a value between the default (2048) and the 
maximum (9600), (for example 5000), will not always guarantee that 5000 active 
ASAI associations can be supported.
Despite the fact that the 
theoretical maximum number of domain-control station 
associations is 6000, the 
actual maximum number of associations is limited by the 
availability of a variety of other system resources.
For this reason, you must consider several factors when setting the NCLID in the 
hope of maximizing performance. The amount of memory available on the adjunct 
processor, as well as the number of BRI boards installed, greatly affect system 
capabilities.
It must also be noted that the capacity requirements and constraints on the 
DEFINITY ECS Release 6, apply equally to all ASAI links. If an application uses 
more than one ASAI link or if other ASAI applications are connected to the same 
DEFINITY ECS, the maximum number of associations per link will be lower than 
normal. This will also affect the 
actual maximum number of associations that can 
be realized.
Set NCLID using the idtune(1M) command. Follow the procedures outlined in 
UNIX System V/386 Release 4 System Administrator’s Guide for rebuilding the 
kernel. Any NCLID between 64 and 9600 will work, provided that sufficient adjunct 
memory is available. Setting the NCLID to a value outside this range is not 
supported.  
						

							Installation
Issue  3  May 1998
1-23
Starting Up the System
System start-up for CallVisor PC ASAI is automatic. When you boot the adjunct, 
the asai_admin daemon is started. asai_admin completes the protocol stack 
and begins the process of message writing to the asai_log. If there is an 
existing log, it is moved to old_asai_log.
The asai_log contains messages about the start-up process. The sample below 
shows typical log entries for a successful start-up.
910318165042:asai_admin: ASAI administration daemon has started.
910318165042:asai_admin: Push of FEL onto /dev/isdn/ipci/signal01 succeeded.
910318165042:asai_admin: Link of /dev/asai/asai file with /dev/isdn/ipci/signal.
910318165042:asai_admin: l01 succeeded.
910318165042:asai_admin: ASAI stack setup was successful.
Matching Versions Requirement for the ISDN protocol stack, specifically the
QP module, must be done correctly or the ASAI link will not come up. Three 
tunable parameters are provided to allow selecting the desired version and 
allowable alternatives. QP_DESIRED_VER is set to the desired version. 
Version 1 corresponds to G3V3, Version 2 corresponds to G3V4 and Version 3 
corresponds to the DEFINITY ECS Release 6
5. 
5. The default is 3 which supports Release 5 and 6. 
						

							Installation
1-24Issue  3  May 1998