Filter
Top Products
BCMS/CMS Tracking in a Call Vectoring Environment
Issue 4 September 1995
F-11
1. Call comes into a VDN whose vector queues the call to splits 1, 2 and 3.
2. Vector executes a
route-to VDN
step.
3. Call is then queued to splits 4, 5 and 6.
4. Call is answered in split 5.
Here’s the tracking table for this scenario:
Comments:
■ R3 CMS:
Outflow
is tracked in split 1 because this split is the
original
primary split, and the call is dequeued from this split via a
route-to VDN
step.
Dequeue
is tracked in splits 2, 3, and 6 because the call is
dequeued from each of these splits without being answered in any one of
them.
Outflow
is tracked in split 4 because this split becomes the
new
primary split after the
route-to VDN
step is executed, and the call is
subsequently dequeued from this split by being answered in another split
(split 5) to which the call is also queued. Finally,
inflow
is tracked in split 5
because the call is answered in this split, and the split is not the primary
split.
■ BCMS: Follows the same scheme as R3 CMS except for the
dequeue
tracking.
■ R2 CMS:
Outflow
is tracked in splits 1, 2, 3, 4, and 6 because the call is
dequeued from these splits without being answered in any one of them.
Inflow
is tracked in split 4 because this split is the first one to which the call
is requeued after the
route to
command is executed.
Call Answered after a Route To Split. The following scenario involves a call
answered after it is routed to a split via a
route-to digits
or
messaging split
command. The scenario is as follows:
1. Call comes into a VDN whose vector queues the call to splits 1, 2 and 3.
2. Vector executes a
route-to digits
(or
messaging split
) step.
Table F-7. Tracking for Call Answered by Non-Primary Split
after Route to VDN
Split Tracking
123456
R3 CMS outflow dequeue dequeue outflow inflow
answer
dequeue
BCMS outflow outflow inflow
answer
R2 CMS outflow outflow outflow inflow
outflow
answer outflow