Filter
Top Products
converse-on split (skill)
Issue 4 September 1995
A-45
■ VDN Override
If a call that accesses multiple VDNs encounters a
converse-on
step
passing ‘‘vdn,’’ normal override rules determine which VDN number is
outpulsed to the VRU.
■ VDN Reports
For call tracking in CMS and BCMS VDN reports, a
converse-on
step is
treated like an
announcement
step. A call is considered ‘‘answered’’ when
it is answered by a nonconverse split (skill) but never when it is answered
by a converse split (skill).
■ Vector-controlled Splits (Skills)
A
converse-on
step may place a call to a split (skill) only if that split (skill)
is administered as a vector-controlled split (skill).
CMS Interactions
CMS tracks calls placed by a
converse-on
step to a CMS-measured split (skill).
converse-on
vector steps may be administered from R3 CMS and later releases.
Since with the
converse-on
step it is now possible for a call to be ‘‘answered’’ in
more than one split (skill), trunk totals no longer match split (skill) totals. However,
VDN totals and trunk totals will match.
For call tracking in CMS VDN reports, a
converse-on
step is treated like an
announcement
step. A call is considered ‘‘answered’’ when it is answered by a
nonconverse split (skill) but never when it is answered by a converse split (skill).
BCMS Interactions
BCMS tracks calls placed by a
converse-on
step to a BCMS-measured split
(skill). Since with the
converse-on
step it is now possible for a call to be
‘‘answered’’ in more than one split (skill), trunk totals may no longer match split
totals. However, VDN totals and trunk totals will match.
For call tracking in BCMS VDN reports, a
converse-on
step is treated like an
announcement
step. A call is considered ‘‘answered’’ when it is answered by a
nonconverse split (skill) but never when it is answered by a converse split (skill).