Filter
Top Products
adjunct routing
Issue 4 September 1995
A-19
Feature Interactions
For a call coming in directly to a VDN, the command is treated like a
route-to with
coverage=y
command. However, for a call that is covered to a VDN, the
command is treated like a
route-to with coverage=n
command. A covered call
that is routed by an
adjunct routing
command to a destination that has Call
Forwarding activated is not further redirected (since the call has already been
redirected by coverage).
For Look-Ahead Interflow, the command is considered a neutral vector command
in all cases. However, the command is usually followed by an
announcement
or
wait-time
command, each of which is a call acceptance command. The G3V4
wait-time hearing i-silent
command can be used when a neutral
wait-time
command is required to allow the adjunct to accept or reject the call.
If an
announcement
command follows a failed
adjunct routing
command, the
announcement is interrupted. If the
adjunct routing
command succeeds (that is,
the switch receives a destination from the ASAI adjunct), the announcement
terminates immediately.
CMS Interactions
R3 CMS: Adjunct routing attempts are stored in the ADJATTEMPTS database
item and reported as ‘‘Adjunct Routing Attempts’’ in standard reports. If the call is
queued to a split when the
adjunct routing
command is encountered, the step is
skipped, and no messages are sent to CMS. Accordingly, ‘‘Adjunct Routing
Attempts’’ is not reported for this call.
When a routing response from the adjunct is successfully executed by the
switch, this action is tracked in the ADJROUTED and ADJROUTTIME database
items and shown as ‘‘Adjunct Routing Completions’’ in standard reports.
Additional tracking of the ‘‘Adjunct Routing’’ command varies based on the
destination successfully routed to as follows:
Routed to Station or to Attendant
Database Item Report Heading Notes
OUTFLOWCALLS/
OUTFLOWTIME
Vector Flow Out
INTIME Avg Time In Vector
CONNECTCALLS/
CONNECTTIME
Other Calls Connect answered calls on G3