AT&T 555-230-520 manual Service Observing, Call Interflow

Basic Call Vectoring

The following vectors illustrate how interflow is used:

VDN (extension=1000	name=‘‘Billing Service’’ vector=55)
Vector 55:

1.announcement 3001

2.goto step 8 if oldest call-wait in split 1 pri l > 120

3.goto step 8 if calls-queued in split 1 pri l > 10

4.queue-to main split 1 pri t

5.wait-time 50 seconds hearing music

6.announcement 3002

7.goto step 5 if unconditionally

8.route-to number 2020 with cov n if unconditionally

VDN (extension=2020 name=‘‘Message Service’’ vector=100)

Vector 100:

1.announcement 3900 (‘‘We’re sorry, all our

agents are busy. Please leave a message. Thank you.’’)

2.messaging split 18 for extension 3000

3.disconnect after announcement 2505(‘‘We cannot

take a message at this time. Please call back tomorrow.’’)

Figure 4-13. Call Interflow

In the first vector, a branch is made to Step 8 from Step 2 if the condition in the latter step (oldest call-wait in split 1 > 120 seconds) is true. If the condition is false, a branch is made to Step 9 from Step 3 if the condition in the latter step (calls-queued in split 1 > 10) is true. If that condition is also false, the call is queued (Step 4), and a wait-announcement loop becomes effective (Steps 5 through 7).

If a successful branch to Step 8 is made from Step 2, the route-to number command is executed. The destination number (2020) in this particular command is a VDN. Accordingly, vector processing terminates in the first vector and begins at the first step of the second vector, to which the VDN points.

Once processing control is passed to the second vector, the caller is provided with the appropriate announcement (Step l). Thereafter, upon execution of the messaging split command in Step 2, the system attempts to either queue the call to the message service split or else terminate the call to a message service agent or to an AUDIX voice port. If one of these attempts succeeds, the caller may leave a message. If none of the attempts succeed, the command fails, and vector processing continues at the next vector command (usually an announcement explaining that the necessary connection could not be made).

Service Observing

Vector initiated Service Observing is available with G3V4 and later releases. For a complete description of Service Observing see the DEFINITY Communications System Generic 3 Feature Description, 555-230-204.

4-16Issue 4 September 1995