Call #3) Arriving call already under ICM script control, and the script requested to be run does not exist (for a state table application)

For example, a call that has been routed to this VRU from another VRU so that a particular script can be run. The ICM instructs the VRU to run a particular script that cannot be found by the VRU. The VRU then decides to end the call.

Figure 1. Arriving call already under ICM script control, and the script requested to be run does not exist (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 Request_Instruction is passed to the gateway and Run_Script_Request received back. When the script cannot be found the state table issues Dialog_Failure_Conf_Send with a status of E_INVALID_SCRIPT. The state table then disconnects, and issues Release_DialogueID.