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

							Installation
Issue  3  May 1998
1-5
For Release 61, the default also is 3. See the ‘‘DEFINITY ECS 
Administration’’ on page 1-17 of this chapter for more information how to 
get the DEFINITY ECS Software Version. Enter the correct number or 
press   for the default. 
NOTE:
Most of the features (except for new Event Reports) will be provided to the 
applications regardless of whether link version 1, version 2 or version 3 is 
selected. The TSC may have to activate a number of new ASAI features. 
ASAI version control is used to allow applications to work even though 
certain protocol features may not be totally upward compatible. The 
approach used by the DEFINITY ECS is that new ASAI messages that were 
unsolicited by the adjunct are under version control, but those messages 
which were requested by the adjunct are not. For example, the G3V4 Event 
Reports (Login and Call Originated) would not be sent if the adjunct had 
negotiated a version 1 (G3V3) link, but the adjunct could request the new 
Send DTMF Signals feature on G3V4 even under link version 1. This way, 
the adjunct can still have access to the new functionality without being 
concerned about receiving unexpected ASAI messages.
In CallVisor, QP_HIGHERVER_OK and QP_LOWERVER_OK have been 
changed to QP_HIGHERVER and QP_LOWERVER, respectively. The 
former represents boolean values used to allow or disallow support for other 
link versions. They now represent a list of versions supported by the adjunct. 
When necessary, the CallVisor PC administration can limit the versions at 
which the protocol will run to meet their application’s needs. Three kernel 
tunables are used to negotiate the ASAI link version:
* QP_DESIRED_VER - the preferred version
* QP_HIGHERVER - the highest allowed version
* QP_LOWERVER - the lowest allowed version
The version will be negotiated to the first acceptable one in the list. First try 
qp_ver, then qp_high, then qp_high-1.... and finally qp_low. If the ECS or 
CV/PC does not support version control, it will be negotiated as though the 
list contained only the lowest version, that is, 1. If the version negotiation 
fails, there will be no error message and the link will not come up. This can 
be diagnosed by running isdn_trace and seeing restarts (08 02 00 00 46
79 ...). No restart acks (08 02 80 00 4E 79 ...) will be run.
10. The installation procedure asks to enter the highest allowed version.
QP_HIGHERVER is provided to specify the highest version. Enter a 
version number or press  for the default.
11. The installation procedure asks to enter the lowest allowed version.
QP_LOWERVER is provided to specify the lowest version. Enter a version 
number or press  for the default.
1. The default is 3 which supports Release 5 and 6.
RETURN
RETURN
RETURN 
						

							Installation
1-6Issue  3  May 1998 
NOTE:
These values are set on a per-adjunct (PC) basis, not on a per-link basis. If 
the adjunct is to be connected to both a G3V3 link and a G3V4 link it would 
be advisable to select 1 for QP_LOWERVER
 and 2 for QP_HIGHERVER. 
Also, 2 should be selected for QP_DESIRED_VER. Version 3 corresponds 
to the DEFINITY ECS Release 6. For Release 6
2, the default also is 3. So 
for Release 6, QP_HIGHERVER and QP_DESIRED_VER should be 
set to 3.
12. The installation procedure asks you to remove the diskette from the disk 
drive and displays shutdown instructions. The message Installation 
of  was successful is also displayed.
If you are not installing the optional CallVisor PC LAN GATEWAY package, 
skip to Step 18.
NOTE:
Install CallVisor PC LAN Gateway package before the installation of 
CallVisor PC LAN. If CallVisor PC LAN Gateway package is not installed 
first, it will take longer to come up. If it is done hours later, the DLG may 
hang and will need reboot.
13. Verify that the hostname and IP address of the ASAI MAPD board(s) for 
each CallVisor LAN link destination are in the /etc/hosts file on the 
adjunct PC. If they are not, then add them now.
NOTE:
If your LAN installation uses a Domain Name Service such as NIS instead
of /etc/hosts for host name resolution,
 The Network Administrator’s 
Guide manual for your operating system should be consulted for information 
on how to add hostnames and IP addresses.
14. Place the (optional) CallVisor PC LAN GATEWAY product disk in the 
appropriate drive and enter the command pkgadd -d diskette1 and follow 
the online instructions.
15. The installation script will ask you to enter the number of LAN links you 
wish to install, enter one number from 1 to 4, the default is 1.
16. For each LAN link entered in the previous step, the installation script will 
ask you to provide a valid host name for the LAN link destination. This will 
be the host name(s) of the MAPD(s) added to /etc/hosts in Step 13. 
The default is DEFINITY ECS.
NOTE:
The installation script will attempt to verify the hostname of each LAN 
destination entered in the previous step and print a warning message if it 
cannot. Installation will proceed regardless of the outcome.
2. The default is 3 which supports Release 5 and 6. 
						

							Installation
Issue  3  May 1998
1-7
17. The installation script will verify system requirements and complete the 
installation. If error messages occur, follow the instructions provided by the 
messages. Otherwise, the message Installation of  was 
successful is displayed.
18. Place the CallVisor PC ASAI product disk in the appropriate drive and 
follow the online instructions.
Pkgadd displays that the CallVisor PC ASAI package is available to 
process. Press  to continue the installation.
19. After several minutes the installation procedure displays the number of 
ASAI nodes that the package is configuring. If this information is not 
available, the installation procedure asks you to enter the number of ASAI 
nodes. This is the combined total number of IPCI boards that are already 
installed or that are going to be installed and the number of LAN links being 
installed on the machine. The default is 1. Enter the correct number
(1 to 8) or press   for the default.
20. After the installation procedure rebuilds the kernel, the installation program 
asks you to remove the diskette from the disk drive and shutdown 
instructions are displayed. The message Installation of  
was successful is also displayed.
nIf this is an upgrade, enter the command:
shutdown -i6 -y -g0
and return to Step 19 and proceed.
nIf hardware is to be installed, enter the command:
shutdown -i0 -y -g0
When the screen message reboot the computer now appears, shut 
off the power.
21. If no ISDN links were installed, proceed to Step 27.
With the power shut off, install the IPCI board by completing the Steps 2 
and 3 listed in Chapter 3 of 
PC/ISDN Platform Installation and Reference 
manual.
Do not do Step 4 or any subsequent steps listed in PC/ISDN Platform 
Installation and Reference
.
In Step 3, you do not have to connect either a headset or a voice terminal 
(phone). You must use a terminating resistor to connect the LINE 
connector to the wall jack going to the DEFINITY ECS BRI line. 
NOTE:
Most ISDN voice terminals require power to operate. This may involve 
additional equipment depending on the wire installation and equipment in 
your building. Consult your DEFINITY ECS administrator or 
telecommunications consultant for additional information.
Do not turn the power on yet.
RETURN
RETURN 
						

							Installation
1-8Issue  3  May 1998 
If you can see the LED with the cover on the computer, you may put the 
cover on. Otherwise, leave the cover off until instructed to put it back on 
after all the software is installed and the LED has confirmed the basic 
sanity of the IPCI board. If in doubt, leave the cover off.
22. If IRQ 3 was chosen, disable the COM2 port. Most 386/486-class 
computers have COM1 and COM2 on the motherboard. If this is the case, 
use the CMOS configuration utility to disable COM2 according to your 
computer user manual.
If you do not have COM2 on the motherboard, check to see if you have an 
expansion board that provides COM2. If you do, disable it according to the 
manufacturer’s documentation.
23. Power up the computer.
The UNIX system should come up. If it does, proceed to the next step.
If it does not, reboot again. When the message Booting the UNIX 
system appears, press the space bar. When the system asks which 
file to boot from? Enter the command:
/stand/unixold
The system now boots using the kernel that was copied in the earlier step. 
Call the CallVisor PC helpline number at 1 732 957-5725 for assistance 
before proceeding.
24. At the login prompt, log in as root.
25. Observe the LED on the IPCI board. This LED will normally begin to flash 
within 90 seconds after you log in. If it does not flash, call the CallVisor PC 
helpline number at 1 732 957-5725.
A flashing LED means the board hardware and software are operating 
correctly.
26. Be sure that the DEFINITY ECS administration has been completed and 
the BRI line is connected to the LINE connector on the IPCI board.
27. Enter the command:
asai_test
This tests the connection from the adjunct to the DEFINITY ECS and 
verifies that the administration is correct. All boards and connections (ISDN 
and LAN) are tested. If the test passes, a success report is displayed.
The QP module logs link startup failures to both the system consoles and 
the crash buffer. If the QP module has failed, it is probably because of the 
DEFINITY ECS and adjunct version incompatibility. If QP messages are 
seen on the console, correct the parameters as described in the 
‘‘Configuring and Reconfiguring Software’’ on page 1-19 of this chapter. 
Use crash (1m) to examine the crash buffer.
For more link details, see ‘‘asai_test(1)’’ in Chapter 2, ‘‘OA&M.’’ 
						

							Installation
Issue  3  May 1998
1-9
If the test fails, check the version parameters and consult the DEFINITY 
ECS administrator. If the test fails for LAN type links, proceed to Step 30.
If the DEFINITY ECS is properly administered and the wiring checks out, 
call the CallVisor PC helpline number at 1 732 957-5725.
28. Shut down the computer. Enter the command:
shutdown -i0 -y -g0
Switch off power and install the cover.
29. Power up the computer.
30. At the login prompt, log in as root and give the IPCI board one minute to 
come up. Recheck connectivity to the DEFINITY ECS using the asai_test 
command.
If the test fails, consult the DEFINITY ECS administrator. If the DEFINITY 
ECS is properly administered and the wiring checks out but the test still 
fails, call the CallVisor PC helpline number at 1 732 957-5725.
If the connectivity fails for LAN type links, use the link_status(1) 
command to obtain the current status of LAN link(s).
If the status is other than Talking, use the ping command to verify 
connectivity to the host; for example, /usr/sbin/ping hostname 
where hostname is the hostname of the MAPD administered in Step 13.
If the ping command returns an affirmative response yet asai_test fails, 
check the /usr/adm/isdn/lan_parms file for typographical errors. If 
there are none, verify that the MAPD administration is correct by following 
the procedures in the 
DEFINITY ECS CallVisor ASAI DEFINITY LAN 
Gateway over MAPD Installation, Administration, and Maintenance, 
for 
your operating system
.
If the ping command returns a negative response, either the ASAI MAPD 
is not properly configured, not connected to the LAN or there may be other 
LAN problems (for example, LAN administration or routing). Consult the 
DEFINITY ECS CallVisor ASAI DEFINITY LAN Gateway over MAPD 
Installation, Administration, and Maintenance 
and the Network 
Administrators’ Manual
 for these types of problems.
If the DEFINITY ECS and ASAI MAPD are properly administered and the 
LAN checks out, call the CallVisor PC helpline number at 
1 732 957-5725.
If the connectivity test succeeds, you have demonstrated the compatibility 
of the computing platform and the CallVisor PC package.
Congratulations, you have successfully installed the CallVisor PC package.
NOTE:
The kernel environment variable which is the number of cluster ids (NCLID) 
sets the amount of memory to be reserved. NCLID effectively limits the 
number of active ASAI associations that are allowed to run on each BRI 
board or LAN GATEWAY link. NCLID has a default value of 2048 if only  
						

							Installation
1-10Issue  3  May 1998 
ISDN links are installed and a default value of 1024 if any LAN GATEWAY 
links are installed. This should be sufficient for the majority of applications 
using ASAI.
However, if the adjunct processor has a limited amount of memory or if a 
running ASAI application is controlling a large number of stations or calls, 
NCLID may need to be changed. In any case, NCLID should be set to 
conform to your system’s specific operational needs. For more details, see 
‘‘Configuration’’ on page 1-18 of this chapter.
You can install the CallVisor PC ITT package at any time. Enter the 
command:
pkgadd -d diskette1
Place the CallVisor PC ITT product disk in the appropriate drive and follow 
the online instructions.
Pkgadd displays that the CallVisor PC ITT package is available to process. 
Press  to continue installation.
After the installation procedure is complete, remove the diskette from the 
disk drive. The message Installation of  was 
successful is displayed.
RETURN 
						

							Installation
Issue  3  May 1998
1-11
CV/LAN Product Description 
CV/LAN allows application software running on UnixWare, Solaris x86, SPARC 
Solaris™, or Windows NT 4.0 to access the DEFINITY ECS CallVisor ASAI 
features across a TCP/IP LAN in a client-server arrangement. 
The server runs on the CallVisor PC or the Multi-Application Platform for 
DEFINITY (MAPD). The CallVisor PC and CV/LAN applications use the same 
library and differ slightly in only one API call. For further information see Chapter 
6, ‘‘CV/LAN Programming.’’
The following Figure 1-1 shows how the applications run on the CallVisor PC 
server and connect to the DEFINITY ECS through the DEFINITY LAN Gateway 
ethernet interface, or through an ISDN-BRI interface.
Figure 1-1. CallVisor PC Adjunct-Server Configuration
DEFINITY ECS
ISDN BRI
ASAI Link
MAPD (DLG)*
TN801 (3 slots)
* MAPD Board Running the DEFINITY LAN Gateway Application† UnixWare or Solaris X86
CallVisor
Protocol
Stack
ASAI Tunnel ProtocolCallVisor PC
†
TCP/IP
TN556 BRIAPP 
						

							Installation
1-12Issue  3  May 1998 
The following Figure 1-2 shows how CallVisor PC is configured as a CV/LAN 
server. Applications can run on all the connected CV/LAN clients. Connectivity to 
the DEFINITY ECS is provided through the CallVisor PC server over either a 
DEFINITY LAN Gateway Interface, or an ISDN-BRI interface. The CV/LAN clients 
do not communicate directly with the ECS.
Figure 1-2. CallVisor PC as a CV/LAN server
MAPD
(DLG)*
TN801 (3 slots)
DEFINITY ECS
ISDN BRI
ASAI Link
SPARC
SolarisTCP/IPTCP/IP
TCP/IP
TCP/IP
TCP/IP CV/LAN 
Solaris X86
CV/LAN
UnixWare
Client
CV/LAN
Windows NT 4.0
Client Client
Client
* MAPD Board Running the DEFINITY LAN Gateway Application† UnixWare or Solaris X86
CallVisor
Protocol
Stack
CV/LAN
Server
ASAI Tunnel Protocol
CallVisor PC†
CV/LAN  TCP/IP
TN556 BRI
CV/LAN Protocol 
						

							Installation
Issue  3  May 1998
1-13
The following Figure 1-3 shows that ASAI client application communication is 
done directly through TCP/IP to the MAPD running CV/LAN server software (PEC 
1273-CVL). It does not involve any CallVisor PC server.
Figure 1-3.CallVisor PC Configuration — CV/LAN to MAPD
CV/LAN client is supported over the following platforms: UnixWare 2.1.2 and later; 
Solaris x86, SPARC Solaris versions 2.4, 2.5, 2.5.1, and Windows NT 4.0. The 
CV/LAN server is supported on Unixware 2.1.2 and later, as well as Solaris x86.
DEFINITY ECS
SPARC
SolarisTCP/IP
TCP/IP
TCP/IP
TCP/IP CV/LAN 
Solaris X86
CV/LAN
UnixWare
Client
CV/LAN
Windows NT 4.0
Client Client
Client
MAPD
* MAPD Board Running the CV/LAN server software
CV/LAN CV/LAN Protocol
(CV/LAN)*
TN801 (3 slots) 
						

							Installation
1-14Issue  3  May 1998 
System Configuration
Each client communicates with the server through any Ethernet interface card 
supporting Unixware versions 2.1.2, and later; Solaris x86, SPARC Solaris 
versions 2.4, 2.5, 2.5.1, as well as Windows NT 4.0. Application software on the 
clients has access to the full range of ASAI features supported by the CallVisor 
PC ASAI interface.
The CV/LAN server runs on UnixWare 2.1.2 and later, and Solaris x86 operating 
systems; it requires the CallVisor PC ASAI library package. The interface card 
between the server and the DEFINITY ECS may consist of the PC/ISDN-BRI card 
or the DEFINITY ECS LAN Gateway card. The server communicates with clients 
over the LAN through any Ethernet interface card supporting Unixware or Solaris 
x86.
Software Configuration
The CallVisor PC ASAI library must also be installed on the client side. Client 
administration specifies a “well known address” to access a server. In addition to 
UNIX, the server must be running the CallVisor PC ASAI library package and 
CV/LAN server software.
System Operation and Limits
Client applications use the CV/PC ASAI library to establish communication with a 
server. This process is nearly identical to that used with the CallVisor PC ASAI 
library (server addresses must be specified by the client; this is not required in the 
PC ASAI library). Once a connection is established, the applications use library 
routines asai_send() and asai_rcv() to send and receive ASAI messages. 
The server routes the messages to and from the proper DEFINITY ECS. The 
format of the messages matches exactly those used with the CallVisor PC/ASAI 
library. Except for minor changes in the communication establishment, 
asai_open expects that the applications developed with the CallVisor PC/ASAI 
library will run unchanged over the LAN.
Certain configuration limits are inherited from the CallVisor PC ASAI library or   
the DEFINITY ECS ASAI limits. In particular, only one client can provide routing or 
maintenance (heartbeat) service, per link for an ECS. ASAI limits for the number 
of active monitors, etc., supported by a single ECS, are not changed by the 
CV/LAN implementation.