Purpose

The stop command halts the processing of any subsequent vector steps.

Syntax

stop

For information about unexpected results, see Troubleshooting vectors.

Requirements

No special requirements.

Operation

A vector stops processing when:

• A vector step includes a stop command

• The last step vector step is processed

• 10,000 vector steps have been processed

The stop command halts the processing of any subsequent vector steps. After the stop command is processed, any calls that are already queued remain queued, and any wait treatment is continued. Wait treatments include silence, ringback, system music, or alternate audio or music source.

The following example shows a vector that uses a stop command:

Stopping vector processing

1. goto step 6 if calls-queued in split 21 pri m > 10
2. queue-to split 21 pri m
3. announcement 4000
4. wait-time 30 seconds hearing ringback
5. stop
6. busy

In the above example, if the stop command is reached, the caller remains in queue at split 21 and continues to hear a ringback. Further vector processing is stopped and does not continue to step 6. Therefore, callers connected to split 21 do no hear a busy signal.