Sample Monitoring Script
Following is an example of an ASAI monitoring script that has been developed with the A_Event action.
start:
#This is a sample monitoring script making use of the A_Event action.
#This script would be given, via administration, a “VDN”,
#“ACD”, or “CTL” type designation. This script would be used to
#receive information about monitored calls and pass this
#information to a host. In this type of scenario, the A_Event
#action can be used to receive CONNECT, ABANDON, and END events
#(no ROUTE REQUEST events are received). In this example, a subset of
#the information available in CONNECT events is passed to a host
#via the 3270 interface.
#
#It is assumed here that the Transaction Base Screen for the
#host application is called “connect_data”. This screen is assumed
#to contain fields that are used for transmitting data obtained
#through A_Event. When the host receives the filled screen, it
#responds by sending a different screen, conveniently named
#the “verify” screen. The “verify” screen is then sent back
#with the key, PF3, to obtain the Transaction Base Screen,
#“connect_data”, again.
#
begin_loop:
#
HOST_UP: Event_start:
1.External Action: A_Event Connected_Number: connect_num
Calling_Party_Number: calling_num
Called_Party_Number: called_num
Switch_Data: switch_data
Trunk_Group_Id: trunk_id
Call_Id: call_id
Other_Call_Id: ocall_id
LAI_Display_Info: lai_info
VIS_Data: vis_data
Routing_ID: route_id
Return Field: event_ret
#Check to make sure a CONNECT was received since we don’t care about
#ABANDON’s and END’s in this example application. If a CONNECT
#was not received, go back and get the next event.
#
