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 401

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...

Page 402

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...

Page 403

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...

Page 404

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...

Page 405

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...

Page 406

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...

Page 407

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...

Page 408

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...

Page 409

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...

Page 410

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...
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