ATT DEFINITY Generic 3 Call Vectoring/Expert Agent Instructions Manual

							Criteria for Success/Failure of Call Vectoring 
Command s
Issue  4  September 1995
A-83
check-backup splitFails if any of the following are true:
nVector conditional is false.
nSplit’s queue is full.
nSplit is not vector-c ontrolled.
nCall is already queued at the sp ecified 
p riority to the specified split.
nCall is already queued to three 
d ifferent sp lits.Continue vector 
processing with the 
next sequential step.
Otherwise:
Succeeds, and the call is terminated to an 
agent.Exit vector 
processing, and 
pass control to call 
processing.
Succeeds, and the call is queued or 
requeued in the specified split at the 
specified priority.Continue vector 
processing with the 
next sequential step.
collect digitsFails if any of the following are true:
nCall originates from an outside caller 
who is not using a touch-tone 
telephone.Call Prom pting timer 
takes effect, 
command times out, 
and vector 
processing 
continues at the next 
vector step.
nNo TTR is in the system, or the TTR 
q ueue is full.Continue vector 
processing at the 
next step.
nCaller enters fewer digits than the 
maximum specified.Call Prom pting timer 
takes effect, 
command is 
terminated, and any 
digits collected prior 
to the timeout are 
available for 
subsequent 
processing.
Otherwise, succeeds.Continue vector 
processing at the 
next step.
Table A-11. Call Vectoring Command Success/Failure Criteria
Command Success/Failure CriteriaVector Processing 
Disposition 
						

							Call Vectoring Commands
A-84Issue  4  September 1995 
converse-on splitFails if any of the following are true:
nConverse split q ueue is full.
nConverse split is not vector-controlled.
nAuto-available sp lit is in effect, and all 
a gents are logg e d out by Redirection 
on No Answer (RONA).Continue vector 
processing with the 
next sequential step.
Otherwise: Succeeds, call is delivered to 
the converse split, and (if administered) 
d i gits are outpulsed to the VRU. The caller 
is connected to the VRU, the voice 
response sc ript is executed, and (if 
necessary) digits are outp ulsed to the 
switch.Continue vector 
processing with the 
next sequential step.
disconnectAlways succeeds. Play the 
announcement (if 
specified).  Then 
drop the call.
goto stepFails if the step condition is not met. Continue vector 
processing with the 
next sequential step.
Succeeds if the step condition is met. Continue vector 
processing with the 
destination step.
goto vectorFails if the step condition is not met. Continue vector 
processing with the 
next sequential step.
Succeeds if the step condition is met. Continue vector 
processing with the 
first nonblank step of 
the destination 
vector.
Table A-11. Call Vectoring Command Success/Failure Criteria
Command Success/Failure CriteriaVector Processing 
Disposition 
						

							Criteria for Success/Failure of Call Vectoring 
Command s
Issue  4  September 1995
A-85
messaging splitFails if any of the following are true:
nSpecified split is not an AUDIX split or 
a Message Server Adjunct (MSA) 
s plit.
nSpecified extension is invalid.
nMessaging split queue is full.
nMessaging split is not vector 
c ontrolled and has no working agents 
(none logged in or all in AUX work 
mode).
nCommunications link with the 
messaging adjunct is inaccessible.Continue vector 
processing with the 
next sequential step.
Otherwise, succeeds.Terminate ve ctor 
processing.
Table A-11. Call Vectoring Command Success/Failure Criteria
Command Success/Failure CriteriaVector Processing 
Disposition 
						

							Call Vectoring Commands
A-86Issue  4  September 1995 
NOTE:
Complete o perational details for the route-to commands are provided in 
Ap pendix G.
queue-to main splitFails if any of the following are true:
nSplit’s queue is full.
nSplit is not vector-c ontrolled.
nCall is already queued at the s pecified 
p riority to the specified split.
nCall is already queued to three 
d ifferent sp lits.Continue vector 
processing with the 
next sequential step.
Otherwise:
Succeeds, and the call is terminated to an 
agent.Exit vector 
processing, and 
pass control to call 
processing.
Succeeds, and the call is queued or 
requeued in the specified split at the 
specified priority.Continue vector 
processing with the 
next sequential step.
stopAlways succeeds.Exit vector 
processing.  Control 
is passed to normal 
call processing.  Any 
queuing or treatment 
in effect remains in 
effect.  Call is 
dropped if not 
queued.
wait-timeAlways succeeds.Connect the sp ecified 
treatment and pass 
control to the delay 
timer. Any fee d back 
is continued until 
other feedback is 
provided.
Table A-11. Call Vectoring Command Success/Failure Criteria
Command Success/Failure CriteriaVector Processing 
Disposition 
						

							Issue  4 September 1995B-1 
B
Call Vectoring Management
Introduction
Call Vectoring management involves a number of different considerations and 
tasks.  This a p pendix d esc ribes these considerations/tasks. Specifically, the 
following topics are discussed:
nCall Vectoring feature requirements
nUpgrading to a Call Vectoring environment
nChanging the vector
nTesting the vector
Implementation Requirements for the
Call Vectoring Features
The tables appearing on the next several p a ges indicate the forms and the 
hardware required for implementing each of the Call Vectoring features.  Details 
on completing the forms can be found in the 
DE FI NITY  Co mm unications System 
Generic 3 Implementation
, 555-230-653. 
						

							Call Vectoring Management
B-2Issue  4 September 1995 
NOTE:
The Basic Call Vectoring and/or Call Promp ting  option(s) must be enabled 
on the System-Parameters Customer-Options form before the associated 
forms and the fields on the forms can be administered.
Table B-1. Basic Call Vectoring Requirements
FeatureForm(s) Hardware
Basic Call 
Vectoring
nVector Directory Number 
Form
nHunt Group Form
nCall Vector Form
nFeature Related System 
Parameters FormAnnouncement capabilities 
require either:
nTN750 Integrated 
Announcement circuit 
p ac k(s), or
nExternal announcement 
facility (analog 
announcements). Also, each 
analog announcement 
requires a p ort on a TN742, 
TN746B, or TN769 Analog 
Line circ uit pack.
NOTE: International 
e quivalents for these circuit 
packs include the following:
nTN467, TN468B 
(Australia and United 
Kingdom)
nTN479 (Japan)
nTN2135 (Italy)
nTN2144 (Netherlands)
nTN2149 (Belgium) 
						

							Imp lementation Re quirements for the Call Vectoring 
Features
Issue  4 Septemb er 1995
B-3
NOTE:
The TN750 Integrated Announcement circuit pack provides 16 ports for 
listening to announcements. On each port in G3i, there can be five 
listeners, while in G3r, there can be 255 listeners. Theoretically, then, 80 
callers in G3i and 4080 callers in G3r can be listening to announcements 
on an integrated board at one time.  The recording time provided is either 
4:16 or 8:32, depending on the sampling rate emp loyed (16K or 32K). An 
external announcement off an analog port can have only five simultaneous 
listeners in G3i and 128 simultaneous listeners in G3r. G3V4 and later 
releases provide for the installation of multiple TN750C Integrated 
Announcement circuit packs. Up to 5 boards can be installed in the G3i 
and 10 boards in the G3r. See “Recorded Announcements” in the
 
DEFINITY Communications System Generic 3 Feature Desc ription
, 555-
230-204 for more details.
Table B-2. Call Prompting Requirements
FeatureForm(s) Hardware
Call 
Promp ting
nVector Directory Number 
Form
nHunt Group Form
nCall Vector Form
nVector Routing Tables 
Forms (G3V4 Enhanced)Announcement capabilities 
require either:
nTN750 Integrated 
Announcement circuit 
p ac k(s), or
nExternal announcement 
facility (analog 
announcements). Each 
analog announcement 
requires a p ort on a TN742, 
TN746B, or TN769 Analog 
Line circ uit pack.
NOTE: International 
e quivalents for these circuit 
packs include the following:
nTN467, TN468B 
(Australia and United 
Kingdom)
nTN479 (Japan)
nTN2135 (Italy)
nTN2144 (Netherlands)
nTN2149 (Belgium) 
						

							Call Vectoring Management
B-4Issue  4 September 1995 
NOTE:
The Basic Call Vectoring and/or Call Promp ting  option(s) must be enabled 
on the System-Parameters Customer-Options form before the associated 
forms and the fields on the forms can be administered.
NOTE:
G3V4 or a later release is required for G3V4 Enhanced Vectoring. The 
following options must be enabled on the System-Parameters Customer-
O ptions form before G3V4 Enhanced Vectoring capabilities can be used: 
Basic Call Vectoring and/or Call Promp ting option(s); and “ Vectoring (G3V4 
Enhanced).”
NOTE:
G3V4 or a later release is required for Ad vanced Vector Routing. The 
following options must be enabled on the System-Parameters Customer-
O ptions form before Advanced Vector Routing conditionals can be 
programmed in a vector step: Basic Call Vectoring and/or Call Promp ting 
option(s); “Vectoring (G3V4 Enhanced)”; and “Vectoring (G3V4 Advanced 
Routing).”
Table B-3. G3V4 Enhanced Vectoring Requirements
FeatureForm(s) Hardware
G3V4 
Enhanced
Vectoring
nVector Directory Number 
Form
nHunt Group Form
nCall Vector FormRequires no hardware in a ddition 
to that required for Basic Call 
Vectoring.
Table B-4. Advanced Vector Routing Requirements
FeatureForm(s) Hardware
Advanced
 Vector 
Routin g
nVector Directory Number 
Form
nHunt Group Form
nCall Vector FormRequires no hardware in a ddition 
to that required for Basic Call 
Vectoring. 
						

							Imp lementation Re quirements for the Call Vectoring 
Features
Issue  4 Septemb er 1995
B-5
NOTE:
G3V4 or a later release is required for ANI/II-Digits Routing. The following 
options must be enabled on the System-Parameters Customer-Options 
form: Basic Call Vectoring  and/or Call Prompting  option(s);  “Vectoring 
(G3V4 Enhanced)”; and “Vectoring (ANI/II-Digits Routing).”
NOTE:
The Look-Ahead Interflow, ISDN-PRI, Basic Call Vectoring and (usually) 
private network access options must b e enabled on the System-
Parameters Customer-Options form.
Table B-5. ANI/II-Digits Requirements
FeatureForm(s) Hardware
ANI/II-
Digits 
Routin g
nVector Directory Number 
Form
nHunt Group Form
nCall Vector Form
nTrunk Group Forms
nVector Routing Tables 
FormsRequires no hardware in addition 
to that required for Basic Call 
Vectoring.
Table B-6. Look-Ahead Interflow Requirements
FeatureForm(s) Hardware
Look-
Ahead 
Interflow
nTrunk Group Form 
(ISDN-PRI)
nCPN Prefix Table FormExisting ISDN-PRI hardware can 
b e used for Look-Ahead Interflow 
ISDN-PRI connectivity to the 
receiving switch. Interc onnecting 
facilities must b e ISDN-PRI with 
no interworking (that is, call 
connections that use both ISDN-
PRI and non-ISDN-PRI facilities 
to complete) for the full 
c a pabilities of the feature to be 
o perational.  Look-Ahead 
Interflow calls that interwork may 
interflow successfully, b ut the 
a bility to do so on an intelligent 
b asis will be lost as will the Look-
ahead DNIS information. 
						

							Call Vectoring Management
B-6Issue  4 September 1995 
NOTE:
Both the sending switch and the receiving switch must have the Basic Call 
Vectoring and the Look-Ahead Interflow features active. In ad dition, Look-
Ahead Interflow calls can c onnect ISDN-PRI switch-to-switch using private, 
p u blic, or SDN facilities.
NOTE:
The Basic Call Vectoring options must be enabled on the System-
Parameters Customer-Options form.
NOTE:
The ACD, ASAI Interface, and ASAI Capability Groups must be enabled on 
the system.
NOTE:
The Packet Bus option (G3r only) must b e enabled on the Maintenance-
Related System Parameters form before associated ISDN-BRI forms and 
fields can be administered.
NOTE:
Direct Agent Calls (DACs) remain in queue for the agent if the agent does 
not have c all coverage.  Otherwise, DACs follow the agent’s c overage path 
after the no answer time interval expires.
Table B-7. Adjunct Routing Requirements
FeatureForm(s) Hardware
Adjunct 
Routin g
nHunt Groups
nClass of Restriction (for 
Direct Agent Calls)
nCall Vector
nStation
nStation (ISDN-BRI-ASAI)A TN556  ISDN-BRI  circuit  pack 
and a TN778 p a cket control must 
b e in place. The latter provides 
p acket bus control. Also, an 
adjunct/host processor must be 
in p lace to receive the request 
and select the route. A TN2198 
two-wire BRI port circuit pack 
can be used in place of the 
TN556. In this case, an NT1 is 
also required.