The VRU script returns control to vector processing on Communication Manager by simply hanging up the line. In cases where no data is returned to Communication Manager, control is returned by executing the quit command. In cases where data is returned, control is returned when the VRU hangs up on completion of the VRU data return operation.

The last set of digits collected before the converse-on split step is executed is still available and can be displayed by an answering agent on the non converse split by using the callr-info button.

A VRU script can be programmed to continue running after hanging up the voice line. This after-call work is usually very short and can involve either a final message to a host or a final update to a local database. For the scenario, the VRU port is still associated with the running script even though there is no longer a voice connection.

From Communication Manager point of view, the agent is available for the next call. If a call is delivered to this port, the VRU does not answer the call until the previous script has completed. As long as the VRU script’s after call work is short in duration, this poses no significant problem for the VRI feature. However, high volume VRI applications with lengthy ACW periods must be prevented, especially if such periods are so lengthy approaching the administered time out period on Communication Manager for the RONA feature. In such a case, RONA treats the VRU ports as faulty and starts taking the ports out of service.