Filter
Top Products
Call Vectoring Commands
A-42 Issue 4 September 1995
■ Interflow
Since a
converse-on
step can place calls only to hunt groups that are
vector-controlled, and since the activation of Call Forwarding for a
vector-controlled hunt group is blocked, calls placed by a
converse-on
step to a hunt group cannot interflow.
■ Intraflow
Since a
converse-on
step can place calls only to hunt groups that are
vector-controlled (that is, without coverage paths), intraflow is not
possible.
■ Live Agents
Although not recommended, the switch does not prevent a
converse-on
step from delivering a call to a group of live agents. To the agent, the call
looks like any other ACD call. However, certain features, such as call
transfer, conference, and supervisor assist are denied.
The answering agent can display any digits collected prior to executing
the
converse-on
step by using the ‘‘callr-info’’ button.
■ Look-Ahead Interflow
If a call placed by a
converse-on
vector step is answered by a VRU, or if
such a call queues to a split (skill) on the receiving switch while a
Look-Ahead Interflow call attempt is outstanding, the Look-Ahead
Interflow call attempt is accepted.
A
converse-on
step that fails is neutral.
■ Message Center
The
converse-on
step may deliver calls to message hunt groups. Such
calls are treated as direct calls to the message.
If a call is forwarded to a VDN and then delivered to a message split by a
converse-on
step, the call is treated as a redirected call.
■ Multiple Split (Skill) Queuing
A call can be queued to three different splits (skills) and then to a
converse split (skill) as a result of a
converse-on
step.
■ Music on Hold
During the data return phase of a
converse-on
step, the caller is
temporarily placed on hold. Music on hold, if administered, is suppressed.
■ Non-Vector Controlled Splits (Skills)
A
converse-on
step may not place a call to a nonvector-controlled split
(skill).
■ Priority Queuing
The queue priority of a call placed by a
converse-on
step is administrable
on the vector step.