Vector processing with goto steps in an ASAI link or application failure condition

Last Updated : Sep 08, 2012 |

Processing rules for a vector that includes more than one adjunct routing link command and has an ASAI link or application failure condition in effect summarized as follows:

  • An announcement or wait time treatment is skipped when one of the following conditions is true:

    • The treatment step follows immediately after a failed adjunct routing link command.

    • The treatment step is the first non-goto step that follows a goto step that succeeds. In this context, a goto step is treated as a success when the specified goto condition is true and the call branches from the goto step to the treatment step.

    • The treatment step is the first non-goto step that follows a failed goto step. In this context, a goto step is treated as a failure when the specified goto condition is true, the call fails to branch and control proceeds to the treatment, which is the next step listed in the vector sequence.

Note:

The treatment step is skipped even when a failed goto step that precedes the treatment is, in turn, preceded by more than one successful goto steps.

The rules listed for vector processing under ASAI link or application failure conditions are illustrated in the following examples.

Example 1 - Vector processing with goto steps in an ASAI link or application failure condition

VDN (extension=1040  name=‘‘Ad Route’’  vector=40)
Vector 40
 1. adjunct routing link 10  [link/application is down]
 2. wait-time 10 seconds hearing ringback [step is skipped]
 3. adjunct routing link 20 [link/application is down]
 4. goto step 7 if available-agents in split 20 < 1 [step executes and condition is false]
 5. wait-time 10 seconds hearing ringback [step is skipped]
 6. goto vector 50 @step 1 if unconditionally  [step executes, go to vector 50]
 7. goto step 10 if calls-queued in split 20 pri l > 50
 8. announcement 4001
 9. goto vector 50 @step 1 if unconditionally
10. route-to number 6000 with cov n if unconditionally
   VDN (extension=6000  name=‘‘Message’’  vector=60)

Based on the scenario presented in the example shown above, the following vector processing events occur:

Step 1 fails: In the example, the adjunct link or application is out of service. The adjunct routing link command in step 1 fails.

Step 2 is skipped: Because the wait-time command in step 2 immediately follows an adjunct routing link command whose adjunct link is out of service, the wait-time step is skipped.

Step 3 fails: For purposes of this example, step 3 contains another adjunct routing link command whose adjunct link is out of service. The step fails and control is passed to the goto step command in step 4.

Step 4 executes: A goto step that immediately follows a failed adjunct routing link command is always executed. In this example, the command fails to branch because there is a minimum of one available agent in split 20.

Step 5 is skipped: The wait-time step that follows the unsuccessful goto step (step 4) is skipped, because in an ASAI link failure condition, the first non-goto step to be processed after the first successful first goto step is always skipped if the step is either an announcement or a wait-time step. Control is passed to the goto vector command in step 6.

Step 6 executes: Step 6 routes the call to vector 50 (not shown), which is designed to queue the call and provide standard call treatment.

In the next example, the goto step succeeds when the specified condition is true, that is, no agents are available in split 20, and control is passed to step 7, where another goto step determines whether there are more than 50 calls in split 20. If the condition is true, step 7 succeeds and control is sent to step 10, where the route-to number command sends the call to vector 60.

The example processing events are described as follows:

Example 2 - Vector processing with goto steps in an ASAI link or application failure condition

VDN (extension=1040  name=‘‘Ad Route’’  vector=40)
Vector 40
 1. adjunct routing link 10 [link/application is down]
 2. wait-time 10 seconds hearing ringback [step is skipped]
 3. adjunct routing link 20 [link/application is down]
 4. goto step 7 if available-agents in split 20 < 1 [step executes and condition is true]
 5. wait-time 10 seconds hearing ringback
 6. goto vector 50 if unconditionally
 7. goto step 10 if calls-queued in split 20 pri l > 50 [step executes and condition is true]
 8. announcement 4001
 9. goto vector 50 if unconditionally
10. route-to number 6000 with cov n if unconditionally [step executes unconditionally]

VDN (extension=6000  name=‘‘Message’’  vector=60)
Vector 60 

1. announcement 4000 [We’re sorry. We are still unable to connect you to an agent. If you would like to leave a 
   message, please do so after the tone.]
2. wait-time 6 seconds hearing silence
3. messaging split 18 for extension 1500
4. announcement 4010 [We’re sorry. We are unable to connect you to our voice mail. If you would like to try to 
   leave a message again, please do so after the tone. Otherwise, call back weekdays between  8:00 A.M. and 5:00 P.M.]
5. goto step 2 if unconditionally

Based on the scenario presented in the example, the following vector processing events occur:

Step 1 fails: For purposes of this example, the adjunct link or application is out of service. The adjunct routing link command in step 1 fails.

Step 2 is skipped: Because the wait-time command in step 2 immediately follows an adjunct routing link command whose adjunct link is out of service, the wait-time step is skipped.

Step 3 fails: For purposes of this example, step 3 contains another adjunct routing link command whose adjunct link or application is also out of service. The step fails and control is passed to the goto step command in step 4.

Step 4 executes: A goto step that follows a failed adjunct routing link command is always executed. In this example, the command succeeds and branches to step 7, because no agents are available in split 20.

Step 7 executes: Again, a goto step that follows a failed adjunct routing link command is always executed. In this example, the command branches unconditionally to vector 60

Step 10 executes: In this example, step 10 (route-to number) is the first non-goto step immediately preceded by more than one goto step in an ASAI link fail condition. The step executes, because the step is not an announcement or wait time command.

Vector 60: Step 1 executes: The first step in this vector is an announcement command. In this example, this is the first step in the processing sequence to be either an announcement or wait-time step. However, this step is not skipped, since the step is not the first non-go to step in the processing sequence. Instead, step 10 in vector 40 (a route-to number step) is the first non-goto step.