ATT DEFINITY Generic 3 Call Vectoring/Expert Agent Instructions Manual

Call Vectoring Commands
A-14Issue  4 September 1994 
Command Directory
The manual p a ge directory in this section lists and discusses all of the 
commands used within Call Vectoring.  For each command presented, the 
following is provided:  purpose, syntax, valid entries, requirements, an example, 
description of the command’s operation,  answer supervision considerations, 
feature interactions, and CMS/BCMS interactions.  The following points 
concerning the appearance of the command line are in...

adjunct routing
Issue  4  September 1995
A-15
Adjunct Routing Command
adjunct routing
Purpose
Causes a message to be sent to an adjunct requesting routing instructions.
Syntax
adjunct routing link < extension>
Valid Entries
Valid ASAI-BRI link extension number
Requirements
Basic  Call Vectoring and ASAI software must be installed. Also, an ISDN-BRI p ort 
is required, and the port must be connected to an ASAI host.
Example
adjunct routing link 765
Operation
The adjunct routing command provides a means...

Call Vectoring Commands
A-16Issue  4  September 1995 
nCalling number information.  DNIS number provided by ISDN-PR I 
facilities, or by the administered destination for other trunk facilities. If the 
call originates from a local switch extension, this extension is the numb er 
dialed (after d i git translation).
nCalled number.  Originally called extension (if a call is forwarded to a 
VDN), or the first VDN through which the call was routed (if the c all was not 
forward ed to the VDN).
nRouting VDN....

adjunct routing
Issue  4  September 1995
A-17
NOTE:
Actually, other than to another goto step, the first step to which a goto step 
is usually designed to branch is a nontreatment step (that is, a step 
containing a command other than a 
wait-time or an announcement 
command). Thus, the skipping of a treatment step according to the 
scenario described just before this note rarely occurs.
On the other hand, if the 
goto ste p fails, the switch skips any announcement or 
wait-time step that imme diately...

Call Vectoring Commands
A-18Issue  4  September 1995 
Finally, note that the adjunct can also decide to not route a call by rejecting (that 
is, negatively acknowledging) the route request sent by the switch.  Upon 
receiving a route request rejection, the switch terminates the 
announcement or 
wait-time step that is being executed for the call and then continues with the next 
vector step.
When the switch receives a call route (destination) from the ASAI adjunct, the 
switch first validates the route...

adjunct routing
Issue  4  September 1995
A-19
Feature Interactions
For a call c oming 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...

Call Vectoring Commands
A-20Issue  4  September 1995 
Split calls are also shown in the standard reports based on the final disposition of 
the call.
The presence of the command in a vector enables the calls serviced by the 
vector to be vector-directed. When such a call is answered by an agent, the call 
is tracked as ACDCALLS/ANSTI ME ,  a n d  i t is rep ort e d  as ‘ ‘A C D Calls,’’ ‘‘Split 
ACD Calls,’’ and ‘‘Avg Speed Ans.’’
A call abandoned after the command routes the call to a station or an...

adjunct routing
Issue  4  September 1995
A-21
Calls that route to a sp lit are tracked as INFLOW and are reported as  ‘‘Flow In.’’  
Calls that route to a trunk are tracked as ROUTED CAL LS/ ROUTEDTIME.  
However, these calls are not shown on standard reports.
BCMS Interactions
If the command advances a call to another position (that is, ASAI routing is 
successful), the call is tracked as “outflow” in the VDN Re port. 

Call Vectoring Commands
A-22Issue  4  September 1995 
Announcement Command
announcement
Purpose
Provides the caller with a recorded announcement.
Syntax
announcement < extension>
Valid Entries
Valid announcement extension numb er
Requirements
Basic Call Vectoring or Call Prompting software must be installed. Also, 
integrated b oard, aux trunk or analog (T&R or Lineside DS1) announcement 
equipment must be installed. Finally, the announcements themselves need to be 
administered and recorded. See...

adjunct routing
Issue  4  September 1995
A-23
If the announcement’s queue is currently full, the call retries the announcement 
step every five seconds and for an indefinite period of time before any new 
vector steps are processed.
The 
announcement command step is skipped, and vector processing continues 
at the next vector step, whenever any of the following conditions exist:
nRequested announcement is busied out, not available, or not 
administered.
nIntegrated board is not installed.
nExternal aux...