Call interflow example
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 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 [All our agents are busy. Please leave a message.
]
2. messaging split 18 for extension 3000
3. disconnect after announcement 2505 [Please call back tomorrow.
]
In the example, vector 55 provides a series of initial vector steps that test the queue status for split 1. Based on the outcome of the tests, the call is connected to split 1 or vector processing branches to step 8.
In step 8 a route-to number command specifies extension number 2020, which is a VDN assigned to vector 100. When the route-to number command is executed, vector processing in vector 55 terminates, the call is removed from the split 1 queue and vector processing continues with step 1 in vector 100.
When control is passed to the second vector, step 1 provides the caller with an appropriate announcement and then step 2 executes a messaging split command that attempts to queue the call to the message service split or else terminate the call to either a message service agent or AUDIX voice port. If either of the attempts succeeds, the caller can leave a message. If none of the attempts succeed, the command fails and vector processing continues at the next vector step.
Tip:
Use an announcement to inform the caller that the messaging connection was unsuccessful.