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
Have a look at the manual Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
![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...](http://img.usermanuals.tech/thumb/3002/85233/w64_definity-ecs-r6-callvisor-pc-asai-installation-and-reference_d-409.png "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...")
Testing Issue 3 May 1998 10-13 Heartbeat Confirmation — C_HB_CONF This message is received from the ECS confirming a heartbeat request. Its output looks like the following: : Figure 10-6. Heartbeat Confirmation Message The contents of the output file look like the following: Figure 10-7. Heartbeat Confirmation Output --- HEARTBEAT CONFIRMATION --- asai_common->capability = 24 asai_common->primitive_type = 1 asai_common->cluster_id = 10 asai_common.capability = 24 asai_common.primitive_type = 1 asai_common.cluster_id = 10
Testing 10-14Issue 3 May 1998 Set Value Confirmation — C_SV_CONF This message confirms a set value request. Its screen output resembles the following: Figure 10-8. Set Value Confirmation Message --- SET VALUE CONFIRMATION --- asai_common->capability = 31 asai_common->primitive_type = 1 asai_common->cluster_id = 10
Testing Issue 3 May 1998 10-15 Event Report — C_EN_REP This message contains event reports sent to the adjunct (PC) by the ECS. Incoming Call Event Report The following event report is generated when an external caller places a call to an ASAI-controlled domain. : Figure 10-9. Incoming Call Event Report For explanations of each field’s meaning, see Chapter 9, ‘‘Programming Manual Pages.’’ --- EVENT REPORT --- asai_common->capability = 22 asai_common->primitive_type = 0 asai_common->cluster_id = 10 erep_common.event_name = 11 --- INCOM_CAL REPORT --- incall_list.clling_num = 5767907 incall_list.clled_num = 1234567890 incall_list.trk.direct = 0 incall_list.trk.reserved = 0 incall_list.domain_type = 1 incall_list.val_length = 10 incall_list.domain_val = 1234567890 incall_list.leng_udata = 23 incall_list.udata_type = 5 incall_list.incomg_udata = display stuff goes here incall_list.priority_level = 3 incall_list.interflow_type = 2 incall_list.hour = 0 incall_list.minute = 0 incall_list.second = 0 incall_list.dnis_chars =
Testing 10-16Issue 3 May 1998 Figure 10-10. Call Alerting Figure 10-11. Connected Report Figure 10-12. Drop Report --- EVENT REPORT --- asai_common->capability = 22 asai_common->primitive_type = 0 asai_common->cluster_id = 10 ev_rpt_ptr->erep_common.event_name = 0 --- ALERTING REPORT --- ev_rpt_ptr->alert_list.connect_num = 1234567890 ev_rpt_ptr->alert_list.clling_num = 1234567890 ev_rpt_ptr->alert_list.dial_num = 1234567890 --- EVENT REPORT --- asai_common->capability = 22 asai_common->primitive_type = 0 asai_common->cluster_id = 10 ev_rpt_ptr->erep_common.event_name = 1 --- CONNECTED REPORT --- ev_rpt_ptr->connect_list.connect_num = 1234567890 ev_rpt_ptr->connect_list.clled_num = 1234567890 --- EVENT REPORT --- asai_common->capability = 22 asai_common->primitive_type = 0 asai_common->cluster_id = 10 ev_rpt_ptr->erep_common.event_name = 4 --- DROP REPORT --- ev_rpt_ptr->drop_list.drop_cause = 25 ev_rpt_ptr->drop_list.drop_type = 1 ev_rpt_ptr->drop_list.droped_num = 1234567890
Testing Issue 3 May 1998 10-17 Figure 10-13. Call End Report --- EVENT REPORT --- asai_common->capability = 22 asai_common->primitive_type = 0 asai_common->cluster_id = 10 ev_rpt_ptr->erep_common.event_name = 12 --- CALLEND REPORT --- ev_rpt_ptr->calend_list.calend_cause = 25
Testing 10-18Issue 3 May 1998 Manual Pages The following manual pages describe the utilities available to test the tool for the programmers. close_dialog_out(3) Name close_dialog_out Synopsis close_dialog_out() Description Closes the temporary dialog-recording file opened by open_dialog_out. It knows the FILE pointer used for the file because the open function stored it in a static variable. Return Value Returns SUCCESS or causes the program to exit with a status of 16.
Testing Issue 3 May 1998 10-19 get_long(3) Name get_long Synopsis long get_long( fieldname, cap_info ) char *fieldname; struct cap_info *cap_info; Description Obtains the current value of the specified field from the capability information structure if that value is of type long. The cap_info argument can either be the address of the start of the table or the address of the proper entry itself. Return Value Returns the long value requested or exits with a status of 19 if the value stored in the table is not a long. This indicates that the capability information structure was incorrectly set up.
Testing 10-20Issue 3 May 1998 get_string(3) Name get_string Synopsis char *get_string( fieldname, cap_info ) char *fieldname; struct cap_info *cap_info; Description Obtains the current value of the specified field from the capability information structure if that value is a string. The cap_info argument can either be the address of the start of the table or the address of the proper entry itself. Return Value Returns the pointer to the string requested or exits the program with a status of 20 if the value stored in the table is not a string. This indicates that the capability information structure was incorrectly set up.
Testing Issue 3 May 1998 10-21 open_dialog_out(3) Name open_dialog_out Synopsis open_dialog_out(filename) char *filename; Description Opens the file whose name is pointed to by its argument. If unsuccessful, it causes the program to exit with a value of 15. It stores the FILE pointer in a static variable, allowing append_dialog() and close_dialog_out() to access the file directly. Return Value Returns the defined value of SUCCESS.
Testing 10-22Issue 3 May 1998 parse(3) Name parse Synopsis int parse( prim, nid, clid, batch_ans, ans_len, ans_filename ) long *prim; char *nid; long *clid; char *batch_ans; int ans_len; char *ans_filename; Description Parses the remainder of a script file command line and returns the operation mode of the function based on the information on the command line. It stores the various information elements in the variables (and arrays) whose addresses are supplied to the function. The meanings of its arguments are defined in the following table: Table 10-1. Argument Types and Descriptions ARGUMENT TYPE MEANING prim long * address of long where primitive type is stored nid char * address of char array where node id is copied clid long * address of long where clid is stored batch_ans char ** address of table of pointers to character strings where batch answers will be stored ans_len int length of previous table ans_filename char * address of char array where batch answers may be written if we are in INTERACTIVE mode