Call #1) Arriving call not under ICM script control (for a state table application)

For example, a call that is arriving at a VRU directly from a public network where, firstly, the VRU registers its interest in particular variables, then, the ICM instructs the VRU to run a particular script that is completed successfully before the call in ended.

Figure 1. Arriving call not under ICM script control (for a state table application)
This graphic is arranged in three blocks representing, from left to right, state table, custom server, and peripheral gateway. Server activity is shown as arrows labeled with function names and joining to state table or gateway as appropriate. In this call, after the usual Create_DialogueID and Register_Variables actions, the function New_Call is passed to the gateway and Run_Script-Request received back. After the script is successfully run, the state table sends a Run_Script-Result, disconnects, and issues Release_DialogueID.