Tutorial
2-12 Issue 4 September 1995
Figure 2-8. Checking Queue Capacity
A check of split 5 is implemented by the
goto step
command in Step 1. In this
example, 21 slots are assigned to split 5 (that is, the queue length for split 5 is
21
). Accordingly, the
goto step
command tests whether the split contains more
than 20 calls via the condition
if calls-queued in split 5 > 20 pri l
. If this test is
successful, control is passed to the
busy
command in Step 10. The
busy
command gives the caller a busy signal and eventually causes the call to drop.
On the other hand, if 20 or fewer calls at a medium priority are already queued to
the main split when Step 1 executes, the
queue-to main split
command in Step 2
queues the call, and vector processing continues at Step 3.
NOTE:
Instead of providing the caller with a busy tone if the
queue-to main split
step cannot queue the call, we can queue the call to another split that is
designed to serve as a backup split. To do this, we can change the step
parameter for the
goto step
command from 10 to 6 (so that the command
reads
goto Step 6.....
). In such a case, control is passed from Step 1 to the
check-backup split
step (Step 6). Inasmuch as this queuing step is
included within a continuous loop of steps (Steps 6 through 9), continuous
attempts to queue the call are now made (if necessary).
Page 1 of 1
CALL VECTOR
Number: 27 Name: base
Basic?y EAS?n G3V4 Enhanced?n ANI/II-Digits?n ASAI Routing?n
Prompting?n LAI?n G3V4 Adv Route?n
01 goto step 10 if calls-queued in split 5 pri l > 20
02 queue-to main split 5 pri l
03 wait-time 10 seconds hearing ringback
04 announcement 2771
05 wait-time 10 seconds hearing music
06 check-backup split 7 pri m if calls-queued < 5
07 wait-time 60 seconds hearing music
08 announcement 2881
09 goto step 6 if unconditionally
10 busy
11 _______________