Filter
Top Products
BCMS/CMS Tracking in a Call Vectoring Environment
Issue 4 September 1995
F-7
Also, when multiple split queuing is involved, R2 CMS tracks an
outflow
in those
splits to which the call queues and from which it eventually dequeues without
being answered there. In effect, then, R2 CMS tracks an outflow in the same
situations where R3 CMS tracks a dequeue.
Examples of Split Flow Tracking
The following sections provide some examples of tracking in R3 CMS, R2 CMS,
and BCMS. Each section first presents a scenario of Call Vectoring events. The
scenario is then followed by a table in which the tracking for the various splits
involved is recorded. Following each ‘‘tracking table,’’ an explanation of the
tracking procedure is provided.
The scenarios presented include the following:
■ Call answered by a primary split
■ Call answered by a nonprimary split
■ Call abandoned
■ Call answered by a primary split after a route to VDN
■ Call answered by a nonprimary split after a route to VDN
■ Call answered after a route to split
NOTE:
Inflows, outflows, and dequeues are not tracked for splits administered by
the
converse on split
command. However, if a call is answered both by a
converse split and (subsequently) by a nonconverse split, an ‘‘answer’’ is
tracked for each split. However, a call is really considered ‘‘answered’’ only
when it is answered by a nonconverse split. Therefore, traffic
measurements for converse splits should be used only to measure
converse split traffic and not to calculate the total number of calls.
Call Answered by a Primary Split. The following scenario involves a call
answered by the primary split. The scenario is as follows:
1. Call comes into a VDN whose vector queues the call to splits 1, 2 and 3.
2. Call is answered in split 1.