ATT DEFINITY Generic 3 Call Vectoring/Expert Agent Instructions Manual

Enabling the Vector Disconnect Timer
Issue  4 Septemb er 1995
B-7
Enabling the Vector Disconnect Timer
Call Vectoring makes available a Vector Disconnect Timer, which can be set for 
any amount of time between 1 and 240 minutes inclusive.  The timer is enabled 
by selecting the timer field in the Feature-Related System-Parameters form. The 
timer is started when vector processing is started. Once the timer runs out, the 
call is dropped. The timer is canceled when vector processing terminates.
Enabling...

Call Vectoring Management
B-8Issue  4 September 1995 
In testing the vector, you should not consider the entire vector at once.  Rather, 
you should first figuratively divide the vector into portions, then test each of these 
portions until the entire vector is tested.
After the new vector is thoroughly tested, the vector should be brought into 
service by changing the VDN to point to the new vector.
The set of following g uidelines is intend e d to serve as a general procedure for 
changing and testing...

Issue  4 Septemb er 1995C-1 
C
Considerations for the Call Vectoring 
Features
Introduction
This a p pendix contains several lists of considerations you should bear in mind 
when using the Call Vectoring features.  These considerations are intended to 
help you g et the highest degree of productivity from Call Vectoring.
NOTE:
If EAS is optioned, ‘‘skill’’ replaces ‘‘split.’’
Basic Call Vectoring Considerations
The following are considerations you should keep in mind when working with 
Basic Call...

Considerations for the Call Vectoring Features
C-2Issue  4 Septemb er 1995 
nCalls should not b e queued to an unstaffed split (unless this is intended by 
the customer) without some alternate treatment.
nInterflow calls should not b e p ermitted to interflow back and forth between 
a remote switch vector and a local switch.  This process could cause a 
single call to use up all available trunks.
nAfter an announcement is provided, the audible feedback (such as music) 
should be re-attached.
nFor...

Look-Ahead Interflow Considerations
Issue  4 September 1995
C-3
is being implemented via a route-to d i gits command, the route-to d igits 
command fails, and vector processing continues at the next ste p, which 
should be a default treatment.
nIt may be prudent to take steps in case a route-to attendant command 
fails, such as providing a disconnect announcement.
nFrom time to time, all of the system’s touch-tone receivers might b e in use.  
As a result, you should avoid starting your main vector with...

Considerations for the Call Vectoring Features
C-4Issue  4 Septemb er 1995 
nIt is perfectly acceptable for a vector to route a call over an ISDN-PRI 
facility to a destination that is not a VDN. In such a case, the sending 
switch treats the call like a Look-Ahead Interflow call. Generic ISDN 
processing at the receiving switch causes the call to be accepted.  The 
DNIS name is i gnored.
nIf a Look-Ahead Interflow call terminates to a VDN on a receiving switch 
where the Look-Ahead Interflow option is...

VDN Return Destination Considerations
Issue  4 September 1995
C-5
VDN Return Destination 
Considerations
The VDN Return Destination feature allows an incoming trunk c all to be placed 
back in vector processing after all parties, except the originator, drop. This 
feature is activated through switch administration of the VDN form. It is an 
optional system feature, and as such, it must be optioned on the System-
Parameters/Customer-Options form.
A new field added to the VDN form will allow the user to...

Considerations for the Call Vectoring Features
C-6Issue  4 Septemb er 1995 
taken by the adjunct is to drop one party on the call, the switch will drop 
the other party as well and clear the call (it cannot retain a call with only 
one party, if there is no Return Destination for further processing).*
User Scenario — Remote Access with Host
Provided Security
A customer may use the VDN Return Destination feature to provide a more 
flexible remote access feature together with host based call security. The...

VDN Return Destination Considerations
Issue  4 September 1995
C-7
If the host security is not passed, the host will route the call to an appropriate 
alternate destination (e.g., announcement with security violation message) and 
log the invalid call attempt.
If the host is not available, the call will be disconnected after an announcement 
(vector step 7 above).
After the called destination d isconnects from the call, the caller can remain on 
the line to be connected to the Return Destination. A sample...

Considerations for the Call Vectoring Features
C-8Issue  4 Septemb er 1995 
User Scenario — Saving in Trunk Facilities
Between Call Centers
A customer can also use VDN Return Destination to return a call to a local agent 
after the call is transferred to a remote destination (call). This will eliminate the 
need for the remote a gent to transfer the caller back to a local agent and will 
save in switch trunk facilities, since each time the call is transferred back to a 
local agent an additional trunk is...