ATT DEFINITY Generic 3 Call Vectoring/Expert Agent Instructions Manual

Call Vectoring Commands
A-74Issue  4  September 1995 
For Look-Ahead Interflow, the route-to command can be considered either a call 
acceptance vector command or a neutral vector command. The command is 
considered a call acceptance vector command whenever one of the following is 
true:
nCommand terminates to a valid local destination.
nCommand successfully seizes a non-PRI trunk.
nCommand execution results in a Look-Ahead Interflow call attempt, and 
the call is accepted by the far end switch.
The...

route-to
Issue  4  September 1995
A-75
NOTE:
For c alls that ‘‘route to’’ a s plit or a hunt group and later intraflow to a station 
or t o an att e n d ant , OTHE RCAL LS/ OTHE RTIM E are tracked in the vector 
and in the VDN tables.Routed to Trunk
Database Item Report Heading Notes
OUTF LOW CA LLS / 
OUTF LOW TI MEFlow Out 1st sp lit
Vector Flow Out
VDN Flow Out
DEQUECALLS/ 
DEQ UETI M EDequeued Calls 2nd/3rd splits
Dequeued Avg  Queue Time
INT ER FLOW C ALL S
/  I N TER F L O WT I M EVDN...

Call Vectoring Commands
A-76Issue  4  September 1995 
 
Split calls are also shown in the standard reports  according to the final 
disposition of the call.
Calls that route over an ISDN trunk are Look-Ahead Interflow calls. When a call 
attempts to ‘‘route to’’ an ISDN trunk (Look-Ahead Interflow), the 
LOOKATTEMPTS database item is tracked and reported as ‘‘Look-Ahead 
Interflow Attempts.’’  If the call successfully routes, 
LOOKFLOWCALLS/LOOKFLOWTIME are tracked and reported as ‘‘Look-Ahead 
Interflow...

stop
Issue  4  September 1995
A-77
Stop Command
stop
Purpose
Halts the processing of any su bsequent vector steps.
Syntax
stop
Requirements
Basic Call Vectoring or Call Prompting software must be installed.
Operation
After the sto p command is p rocessed, any calls  already q ueued remain queued, 
and any wait treatment (for example, silence, ringback, music) is continued. On 
the other hand, any calls not queued are dropped under the same scenario.
If a TTR is allocated to the c all, and if the 
stop c...

Call Vectoring Commands
A-78Issue  4  September 1995 
CMS Interactions
R3 CMS:  When the command or the end of the ve ctor is encountered, vector 
INTIME is recorded.  This is reported as ‘‘Avg Time in Vector.’’
R3V4 CMS: VDISCCALLS  d atabase item in the VDN tables pegs call that pass 
all the way through a vector without ever having been queued.
R2 CMS:  Nothing is recorded when the command is encountered. When  the 
disposition (that is, ‘‘answered’’ or ‘‘abandoned’’) of the call is known, VECTIME is...

wait-time
Issue  4  September 1995
A-79
Wait-time Command
wait-time
Purpose
Delays the processing of the next vector step if a specified delay time is included 
in the command’s syntax. Also provides feedback (in the form of silence, 
ringback, or music) to the caller while the call advances in queue. The  G3V4 
Multiple Audio/Music Sources for Vector Delay feature allows a specified audio 
or music source to be selected when a call encounters a 
wait-time command. 
See Multiple Audio or Music Sources on...

Call Vectoring Commands
A-80Issue  4  September 1995 
extension: The valid extension number of an alternate audio/music source
Requirements
Basic Call Vectoring or Call Prompting software must be installed. Also, a 
music-on-hold port must be provid e d for the music treatment. Multiple 
Audio/Music Sources for Vector Delay requires that the “ Vectoring (G3V4 
Enhanced )”  customer option be enabled.
Example
wait-time 224 secs hearing music
wait-time 120 secs hearing 54795 then continue
Operation
The...

wait-time
Issue  4  September 1995
A-81
Feature Interactions
When the command is implemented with music as the treatment, the 
system-wide music-on-hold feature must be administered. Otherwise, the caller 
hears silence. When  Tenant Partitioning is in use the tenant numb er of the active 
VDN determines the system music that is heard.
Feedback continues while a subsequent vector step queues for an 
announcement or for a TTR.
For Look-Ahead Interflow, the command is considered a call acceptance vector...

Criteria for Success/Failure of Call Vectoring 
Command s
Issue  4  September 1995
A-81
Criteria for Success/Failure of Call
Vectoring Commands
The table appearing on the next several p ages summarizes the success and 
failure criteria for various vector c ommands. Before you write or evaluate vectors, 
it is important to understand the information in this ta ble.
NOTE:
If EAS is enabled, ‘‘skill’’ replaces ‘‘split.’’
A 

Call Vectoring Commands
A-82Issue  4  September 1995 
Table A-11. Call Vectoring Command Success/Failure Criteria
Command Success/Failure CriteriaVector Processing 
Disposition
adjunct routingFails if any of the following are true:
nVDN’s COR d oes not permit routing to 
the adjunct-supplied destination.
nTAC/ARS/AAR code is invalid.
nSpecified agent is not logged into the 
specified split for a direct agent call.
nLocal extension is not in the d ialplan.
nInvalid number was dialed.Stop 
wait-time or...