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

							Testing
Issue  3  May 1998
10-3
Executing the ITT Program 
The following instructions assume that the installation steps have been completed 
successfully for the CallVisor PC ISDN, ASAI and ITT packages. Run asai_test 
to verify that the link(s) are working between the adjunct and the ECS.
The program, asai_test, sends an ASAI heartbeat and waits for a reply on 
each administered link. asai_test reports success if a positive acknowledgment 
is received.
The command, mkclid, creates cluster id, file descriptor and input/output files 
used by the script files. These files are created with the users login id and shell 
umask file permissions.
Enter the following commands:
cd /usr/adm/asai_itt
The ECS sends a heartbeat to the adjunct every two minutes and, after doing that 
three times with no response, tears down and then restarts the link. During this 
time C_ABORTS are sent to the adjunct. Scripts can be run without the
C_ABORTS appearing by running the asai_hb command. Refer to the manual 
page for more information about the asai_hb command.
Enter the following command for link 1:
nohup /usr/bin/asai_hb 1 &
The following command line illustrates how to execute the ITT:
Figure 10-2. Execution of the ASAI integration test tool
Here scriptfile represents the name of the main script file to be interpreted by 
the ITT.
itt scriptfile 
						

							Testing
10-4Issue  3  May 1998 
Scripts 
This section describes the format of script and capability-info files.
The script test file is an ASCII file (created using a text editor) that tells the test 
tool which functions to execute and gives it the information that will allow it to 
gather the proper information to execute that function.
Test script files can have embedded comments, but these must appear on lines by 
themselves. Comment lines should start with a 
sharp (#) symbol, followed by a 
space and then the comments. Comment lines will appear in the trace but will not 
be interpreted by the test tool.
 Figure 10-3 shows embedded comments:
Figure 10-3. Script File — Comments
#
#      Copyright (c) 1996 Lucent Technologies
#        All Rights Reserved 
#
#      THIS IS UNPUBLISHED PROPRIETARY SOURCE CODE OF Lucent Technologies
#      The copyright notice above does not allow for any   
#      actual or intended publication of such source code.
#
#
# FILE Name:test.event
#    AUTHOR:Robert Hutchison
#   PURPOSE:this script tests the event notification features
# of the ASAI library.
# 
						

							Testing
Issue  3  May 1998
10-5
Each command (noncomment) line in the test script file contains the following 
parts:
stall 
This script command temporarily stops the test tool and gives instructions to the 
person running the test. This command can be used in demos, where you want to 
stop and tell about what is happening, or to give the operator instructions like “pick 
up extension 1600” or “dial 1601 from extension 1600.” These instructions permit 
the operator to test functionality such as event reports.
The format for a stall command:
stall instructions
instructions tells the operator what to do. When these instructions are printed 
on the screen, the operator is prompted to press the   key. library function name The name of the ASAI library function to be 
executed; (for example, asai_open is 
used to open communication with the ASAI 
stack and, the ECS).
return value filename The name of a file where the return value 
of the function is to be stored. This is 
especially important for the asai_open 
call because we need to save its return 
value to be used as input to subsequent 
calls. If the return value is to be ignored, a 
reference to /dev/null will be sufficient 
to throw away its value.
capability-specific argumentsOther arguments on the command line are 
function specific and are described in detail 
with the particular command.
RETURN 
						

							Testing
10-6Issue  3  May 1998 
asai_open 
This script command causes the asai_open() library function to be executed.  
Its command line is as follows:
asai_open return_filename asai_special_file flags node_id server_num server_type
The arguments to asai_open are as follows:
return_filenameThe filename of the file where the return value of the 
asai_open (a file descriptor) will be stored. The value 
will be put in the file in ASCII so that it will be editable 
as necessary.
This file will probably be passed to subsequent 
commands wishing to refer to this stream (file 
descriptor).
asai_special_fileThe filename of the ASAI provider (usually 
/dev/asai/asai), or the machine name in the case 
of CV/LAN.
flagsThe numeric value of flags to be forwarded to
asai_open().
node_idA character string referring to the node being opened.  
In the default environment (where the administrator 
uses the suggested values on IPCI installation), this 
would be signal01.
server_numInforms the ASAI library software of the number of 
services that this open (if successful) will serve. If this 
open does not intend to serve anything, then both this 
and the next fields should be ignored.
server_typeInforms the ASAI library software of the service type 
that this open (if successful) will serve. If this open 
intends to serve more than one type of service, then 
each server_type should be separated by a blank 
and the server_num should match the number of 
service types that you entered here. 
						

							Testing
Issue  3  May 1998
10-7
After the asai_open(), the node id will automatically be set by the test tool 
through asai_set_env() using the node id specified on the command
asai_open command line. An example of an asai_open command line follows:
asai_open fd_file /dev/asai/asai 0 signal01 1 C_RT_SER
Here /dev/asai/asai is the pathname of the ASAI provider, 0 denotes the 
open flags passed to the open, signal01 represents the node name (or special 
file name of the ISDN connection to the ECS), 1 indicates that this open (if 
successful) will serve one type of service, and C_RT_SER is the service type 
(routing an incoming call). 
						

							Testing
10-8Issue  3  May 1998 
asai_close 
This script command tells the integration test tool to close an open stream through 
the asai_close() library function. The format of the command line is as follows:
asai_close close_ret fd_value
This command expects two arguments:
close_retThe name of a file where the return value from the 
asai_close() will be stored. If the return value is not needed 
or desired, then /dev/null would be sufficient.
fd_valueThe name of the file that contains the file descriptor that we 
want to close. It would probably be the return value file of the 
asai_open command line. 
						

							Testing
Issue  3  May 1998
10-9
asai_send 
Requests the integration test tool to use the supplied information to issue an 
asai_send() library function call. Its format is as follows:
asai_send send_ret fd_file CAPABILITY CAP_Type clid_file cap_info
This command line expects six arguments described as follows:
Three examples are provided in the following three subsections. send_retThe name of a file where the return value from the
 asai_send() will be stored.
fd_file The name of the file where the file descriptor is stored. This file 
was probably created as the return-value file of the asai_open 
command line.
CAPABILITY A character string that describes the capability being requested.  
The value corresponds to the capability names listed in the 
asaiDefs.h header file.
CAP_TypeA character string describing the type of capability. Possible 
values are:
C_REQUEST
C_POS_ACK
C_NEG_ACK
clid_fileThe name of the file that contains the cluster identification 
number for this send. This is an ASCII file that can be created 
through an editor and may or may not contain a terminating 
newline character.
cap_infoA file that contains capability-specific information. If this 
argument is omitted and the capability needs other information 
from the user, it will prompt him or her for that information. If this 
filename is specified but the file does not exist, the function will 
use its interactive mode, ask the questions, and record the 
users responses in the specified file. If the filename is specified 
and the file exists, the information contained therein will be used 
as the detailed information for the capability.
The format of this file is capability-specific. It will, therefore, be 
described with the individual capabilities. 
						

							Testing
10-10Issue  3  May 1998 
Heartbeat Request — C_HB_REQ 
This capability requires no additional information. The cap_info argument to the 
asai_send command line is ignored if it is there.
Set Value Request — C_SV_REQ 
This capability allows the user to either:
— Turn on or off a message waiting lamp for a particular phone 
or
— Send a Flexible Billing rate change request. If used in the interactive mode, 
the conversation might look as follows:
Figure 10-4. Set Value Request 
Here the emboldened values represent values that the user typed in. If recorded 
in a file (to be used later in regression tests), it would be stored as follows:
sv_common.sv_item = 131
sv_mwi_val.mwi_type = 144
sv_mwi_val.clled_num = 5767162
Note that although the symbols were used in the interactive mode, the actual 
values are stored in the cap_info file. The asaidefs.h header file stores 
symbolic values and their associated definitions.
     field name: sv_common.sv_item
symbolic values: C_SV_MWI
     C_SV_FLEX
   enter choice: C_SV_MWI
--- message waiting indicator ---
     field name: sv_mwi_val.mwi_type
symbolic values: C_MWI_ON
   C_MWI_OFF
   enter choice: C_MWI_ON
     field name: sv_mwi_val.clled_num
    enter value: 5767162 
						

							Testing
Issue  3  May 1998
10-11
NOTE:
Due to the changes in t_sv_req for the addition of Flexible Billing Set 
Val ue capability, all previous ITT set value request input scripts will have to 
be updated with sv.common.sv_item as the first line in the file. This was 
optional prior to this release of CallVisor.
Event Notification Request — C_EN_REQ 
This capability allows the user to ask the ECS to send event reports for a specified 
domain or vector directory number. In its interactive mode, the interaction for 
sending this capability looks like:
Figure 10-5. Event Notification Request
The test tool prints the information as it extracts it from the command line:
asai_send send_ret fd_value C_EN_REQ C_REQUEST cl_id en_parms
and then prompts the user for the proper capability-specific values. It then stores 
the answers in the file en_parms (the last argument on the command line) as 
follows:
en_common.domain_type = 129
acd_grp_info.acd_group = 2015551212
Note that although the symbol C_ACD_GROUP was used in the interactive mode, 
the actual value was stored in the file.
 
--- EVENT NOTIFICATION REQUEST ---
        asai_common.capability = 23
        asai_common.primitive_type = 0
        asai_common.cluster_id = 10
       field name: en_common.domain_type
  symbolic values: C_ACD_GROUP
                   C_CALL_VECTOR
     enter choice: C_ACD_GROUP
       field name: acd_grp_info.acd_group
      enter value: 2015551212 
						

							Testing
10-12Issue  3  May 1998 
asai_rcv 
This script command allows the user to receive messages from the ASAI provider 
(that is, the ECS). The script command line’s format is as follows:
asai_rcv rcv_ret fd_file CAP CAP_Type clid_fn [ output  expected  timer]
The command line expects six, seven, or eight arguments described as follows:
rcv_retThe name of the file where the return value from the
asai_rcv() will be stored. If the return value is not 
important, you can specify /dev/null.
fd_fileThe name of a file that contains the file descriptor value. It 
should probably be the same file that kept the return value 
from the call to asai_open().
CAPThe symbolic name of the capability that you expect to 
receive. If it is not important which capability is to be 
received, then a value of * will tell the test tool to skip its 
validity checking of this field.
CAP_TypeThe value of capability type (also known as 
primitive_type) is taken from the expected file.
clid_fnThe name of a file where the cluster identifier will be stored. If 
this information is not needed later, a file name /dev/null 
can be specified.
outputThe name of a file where the output of the asai_rcv() will 
be stored. It will be an ASCII file consisting of name-value 
pairs. See capability-specific sections of this document for 
more detailed information on these files. If the output 
parameter is omitted, the information received from the ASAI 
provider will only be printed on the screen and will not be 
stored in any file.
expectedAn optional field contains the file name that contains 
name-value pairs that tell the test tool what you expect to 
receive from the library. These name-value pairs must be in 
the same order and are formatted like the output file 
described previously. The test tool will compare these 
name-value pairs against the name-value pairs received from 
the library. If a single capability description match is not found 
in the ‘‘expected” file, an exception is printed. If multiple 
description matches exist and a value cannot be found, an 
exception is printed. If there is no “expected” file, enter NULL 
and the test tool will ignore the ‘‘expected” field.
timerA default timer of 120 seconds will cause the test tool to exit 
with an Alarm call message displayed. To change the 
default value enter an integer value.