AT&T 555-230-520 manual R3 CMS and Bcms Standards, Vector Inflows and Outflows

Interactions Between Call Vectoring/EAS and

BCMS/CMS

R3 CMS and BCMS Standards

The following table illustrates how R3 CMS and BCMS interpret specific VDN flows for the G1/G3 versions of the DEFINITY switch:

Table F-1. R3 CMS and BCMS Standards for Interpreting VDN

Flows (in G1/G3)

Flow Type	Management System	Interpretation
VDN flow in	R3 CMS	Calls that flow into the vector
		from another vector via a route-to
		command.
	BCMS	(Not tracked.)
VDN flow out	R3 CMS	Calls that successfully flow out of
		a vector to another VDN or
		external location via a route-to
		command.
	BCMS	Calls that are advanced to
		another position via a successful
		route-to or messaging split
		command. This can involve
		adjunct routing, calls forwarded,
		calls routed to a VDN, and calls
		picked up by an agent who is not
		in the split for which the call is
		queued by the VDN.
		Calls that are answered by an
		attendant (via a route-to
		command).

NOTE:

(R3 CMS only): If a call that covers to a VDN is originally a call to a measured (nonvector-controlled) VDN, R3 CMS records a VDN flow in for the coverage to the second VDN and a VDN flow out for the first VDN.

Vector Inflows and Outflows

The following section discusses the specific vector flows vis-a-vis R3 CMS.

R3 CMS Standards

Vector flow in pertains to calls that flow into a vector from another vector via a route to or a goto vector command. Vector flow out pertains to calls that successfully flow out of a vector via a route to or a goto vector command.

F-4Issue 4 September 1995