ATT DEFINITY Generic 3 Call Vectoring/Expert Agent Instructions Manual

Looping Examp les
Issue  4 September 1995
M-5
The example in Figure M-5 a d ds a delay so that the lookahead interflow attempt 
occurs only every 10 seconds.
Figure M-5. Example Vector with Improved Performance
The example in Figure M-6 increases performance even more by increasing the 
d elay between lookahead interflow attempts to 30 se conds.
Figure M-6. Another Example Vector with Improved Performance
Table M-2 c ompares the relative processing cost of the three examples by 
looking at the a...

Improving Performance
M-6Issue  4 September 1995 
Check Backup 
Recommendation: When using check-backup commands to queue a call to 
backup splits, ensure that an adequate amount of time has elasped before 
checking the b ackup splits again. 
NOTE:
With the introduction of the ‘Expected Time Wait Time’ feature in Generic 3 
Version 4, the style of programming used in this example is no longer 
relevant. The  best a p proach is to use the ‘Expected Time Wait’ feature to 
locate the most appropriate split...

Looping Examp les
Issue  4 September 1995
M-7
Since the agent availability status may not be likely to change every 10 seconds, 
it may make sense to increase the wait time to 30 seconds, as shown in the 
example in Figure M-9.
Figure M-9. Another Example Vector with Improved Performance
Table M-2 compares the relative processing cost of the three examples by 
looking at the approximate number of vector steps executed while processing 
the call. Assumption is that the announcement is 5 seconds long.
When...

Improving Performance
M-8Issue  4 September 1995 
Other Examples
After Business Hours
Recommendation: Test to see if the d estination resourc es are available (such as 
during business hours) before queuing.
The example in Figure M-10 q ueues calls to a hunt group regardless of the time 
of the call. When the call is made after b usiness hours, the announcement is 
repeated until the caller hangs up.
Figure M-10. Example Vector 
The example in Figure M-11 tests for business hours before queuing the call....

Other Examples
Issue  4 September 1995
M-9
Lookahead Interflows
Recommendation: When  using  a  lookahead interflow, first test to see if the 
receiving office is open for business.
The scenario is a sending switch in Los Angeles, with office hours from 8:00 AM 
to 5:00PM (8:00-17:00) PST and the receiving switch is in New York, with office 
hours from 8:00 AM to 5:00PM EST (5:00-14:00 PST).  There is a 3 hour d ifference 
between the two switches. 
The example in Figure M-12 routes calls to the New York...

Improving Performance
M-10Issue  4 Septemb er 1995 
The example in Figure M-14 can b e used if you have Generic 3 Version 4 
Advanced Routing  optioned. In this case, the ‘Expected Wait Time’ feature may 
be used to determine whether it is worthwhile placing a lookahead interflow call 
attemp t.
Figure M-14. Another Example Vector with Improved Performance
There is little reason to attempt an interflow if the call will be answered quickly at 
the main switch. For the exam ples in Figure M-13 and Figure...

Relative Processing Cost of Vector Command s
Issue  4 September 1995
M-11
Relative Processing Cost of Vector 
Commands
Some vector commands use more p rocessing resources than others. Table M-4 
and Table M-5 show the relative processing costs of specific vector commands 
for Generic 3 Version 4i/v/vs and Generic 3 Version 4r respectively. Whenever 
possible, use the lower cost vector commands. This will minimize your 
performance costs and upgrade your performance.
Table M-4. Relative Processing Cost of...

Improving Performance
M-12Issue  4 Septemb er 1995 
Table M-5. Relative Processing Cost of Vector Commands for 
Generic 3 Version 4r
relative 
performance
 cost vector command
medium adjunct routing
medium c heck-backup
medium c ollect digits 
medium c onverse 
medium g oto vector (table comparison) 
medium messaging 
medium queue-to 
medium route-to 
low announcement 
low b usy
low d isconnect
low g oto step 
low g oto vector 
low sto p
low wait-time 

Issue  4   Septemb er 1995N-1 
N
Call Vectoring System Parameters
G3iV1.1 and G3V2 System Parameters
1. The total of VDN, Station, and Login ID extensions cannot exceed 25,000.
2,000 for G3rV3
7,084 for G3rV3 for Simultaneous 3-way Conf. Calls
Table N-1. Maximum System Parameters for Call Vectoring/EAS 
for G3V2
ITEMG3iV1.1-
286G3vsV2 
ABP/PBPG3sV2 
ABP/PBPG3iV2-
386 G3rV2
Call Vectoring
Multiple Splits per Call 3NA/3 NA/3 3 3
Priority Levels 4 NA/4 NA/4 4 4
Recorded Announcement 128 NA/128 NA/128 128...

Call Vectoring System Parameters
N-2Issue  4   September 1995 
G3V3 System Parameters
1.The total of VDN, Station, an d Log in ID extensions cannot exceed 25,000.
2,000 for G3rV3
7,084 for G3rV3 for Simultaneous 3-way Conf. Calls
2. Measured limits depend on the CMS release used.
Table N-2. Maximum System Parameters for Call Vectoring/EAS 
for G3V3
ITEMG3vsV3 
ABP/PBPG3sV3 
ABP/PBP G3iV3 G3rV3
Call Vectoring
Max. Skills a Call Can Simultaneously
Queue toNA/3 NA/3 3 3
Priority Levels NA/4 NA/4 4 4...