Lucent Technologies Whats New In DEFINITY Enterprise Communications Server Release 8.2 Manual

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
New Switch and Adjunct Support 
45 General Telephony Enhancements - Global 
1
—Default: n
— Error: invalid entry, press help.
Attendant Vectoring
Attendant Call Vectoring is a stand alone feature that is supported on a single 
switch environment with or without CAS. Attendant Call Vectoring permits unique 
treatment for each of the attendant-seeking calls according to a number of factors, 
as defined by the Vector Directory Numbers for each functionality, so as to provide 
a highly flexible approach for managing incoming calls to an attendant on a 
DEFINITY switch.
Terminology and Acronyms
Table 2. Terms and Acronyms
Term Meaning
BSR Best Service Routing
CAS Centralized Attendant Service
IAS Inter-PBX Attendant Service
RLT Release Link Trunk
TAAS Trunk Answer Any Station
TN Tenant Number. Tenant numbers are assigned to all endpoints in the system 
and indicates which tenant partition the endpoint belongs to. If tenant 
partitioning is not administered the system has only one “universal” tenant 
partition and all endpoint TN numbers are defaulted to 1.
VDN Vector Directory Number 
						

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
New Switch and Adjunct Support 
46 General Telephony Enhancements - Global 
1
Attendant Group Calls
Attendant group calls are calls directed to an attendant group; calls to an 
individual attendant (via the assigned extension) are not considered attendant 
group calls. Calls begin as or become attendant group under the following 
conditions:
1
nCall to Listed Directory Number (LDN)
nAttendant group in coverage path
nAttendant control of trunk group access
nAttendant return calls
nAttendant serial calls
nCalls forwarded to attendant group
nControlled Restriction
nDialed attendant access code
nEmergency access (dialed FAC or off hook timeout)
nVIP Wakeup
nDID/Tie/ISDN intercept treatment
nDID time-out due to Unanswered DID Call Timer expiry
nDID busy treatment
nCall Park time-out
nCall Transfer time-out
nSecurity Violation Notification (SVN)
nMultifrequency signaling with attendant group as terminating destination
nCDR buffer full with attendant group as Call Record Handling Option
nTrunk incoming destination is attendant group
nTrunk group night service destination is attendant group
nHunt group night service destination is attendant group
nAutomatic Circuit Assurance (ACA) referral calls
nVDN routes to the attendant access code
Attendant group calls terminate to the attendant group associated with a particular 
party’s tenant number (TN). When tenant partitioning is not administered, the 
system can have only one “universal” tenant partition and attendant group in 
which attendants can be members. Any attempt to assign an attendant to an 
1. Multimed ia d ata c alls c an also b e sent to an attend ant g roup , but only voic e is b eing  
sup ported  for R8 attendant vec toring. Data c alls were not orig inally sup p orted  for b asic  
vec toring  and  supp ort is still inc omplete. Since there is no need  to p rovid e this 
func tionality, MMCH c alls will be b locked from attend ant vectoring .  
						

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
New Switch and Adjunct Support 
47 General Telephony Enhancements - Global 
1
attendant group other than 1 is denied. All endpoints in the system are defaulted 
to TN 1 which by default belongs to attendant group 1. Any attempt to assign TN 
numbers other than 1 is also denied. So, attendant group calls will always 
terminate to attendant group 1. For example, station 2000 is assigned TN 1 so 
when the attendant access code is dialed from station 2000, the call terminates to 
attendant group 1.
When tenant partitioning is administered, attendants can be assigned to multiple 
attendant groups and endpoints can be assigned TN numbers for any of the 
tenant partitions. The TN is associated with an attendant group via the tenant 
form. So, tenant partitions 1 and 2 can be associated with separate attendant 
groups or the same attendant group. Attendant group calls still terminate to the 
attendant group assigned to a party’s TN. For example, station 2000 is assigned 
TN 1 which is associated with attendant group 1. Station 3000 is assigned TN 2 
which is associated with attendant group 2. When the attendant access code is 
dialed from station 2000, the call terminates to attendant group 1 and when dialed 
from station 3000, terminates to attendant group 2. This is a flexible method of 
assigning multiple tenant partitions to be controlled by one attendant group or 
assigning each tenant partition a separate attendant group.
Call Vectoring
Call vectoring provides a highly flexible approach to managing calls. It consists of 
three basic components:
1. A Vector Directory Number (VDN)
2. Vectors
3. Vector commands
The VDN is an extension which can be directly dialed or administered as a 
destination (e.g., last point in a coverage path, night service destination, etc.). 
Each VDN is assigned a vector in which call handling procedures are 
programmed using vector commands. Once the call goes to a vector, the call’s 
routing and treatment are determined by the commands in the vector.
Attendant Vectoring
A new customer option for attendant vectoring will be added and will not be 
available if RLT CAS is turned on. So, this feature will be available in non-
distributed attendant environments and distributed attendant environments for IAS 
and QSIG CAS. When the new option is on, attendant vectoring will be available 
for customers to program how they want their attendant group calls processed. 
This feature will be based upon and use existing call vectoring and attendant 
administration. 
Just as TN assignment currently determines which attendant group calls are 
terminated to, the TN assignment will also determine which VDN the calls are 
redirected to (i.e., a VDN field will be added for each tenant partition). If a VDN is 
administered, attendant group calls will be redirected to the VDN rather than the 
attendant group. If a VDN is not assigned calls will terminated to the associated  
						

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
New Switch and Adjunct Support 
48 General Telephony Enhancements - Global 
1
attendant group as they currently do. How Definity determines which party’s TN to 
use in call scenarios will remain unchanged by attendant vectoring. The VDN for 
the selected TN will apply. For example, the selected TN for calls covered to an 
attendant group, is the called user’s
, not the calling user’s, TN. When tenant 
partitioning is not administered, the system can have only one partition and 
attendant group. All attendant group calls are directed to attendant group 1. The 
form to administer TN associations is not accessible so system-wide console 
assignments apply. To follow the existing principals of this administration, the 
attendant vectoring VDN assignment will appear on the Console Parameters form 
when partitioning is turned off. When it is turned on, the field will be removed from 
the console form and the contents will be automatically copied to TN 1.
To associate VDNs and vectors for attendant vectoring, a new field will be added 
to both the VDN and the call vectoring forms to indicate attendant vectoring. 
When attendant vectoring is indicated for VDNs and vectors, all call center 
associated fields will be removed (Skills, BSR, etc.). There will be no restrictions 
applied to attendant and non-attendant vectoring. For example, an attendant VDN 
can point to a non-attendant vector and vice versa. The same is true for vector 
commands. For example, an attendant VDN which points to an attendant vector 
can have a vector step which routes to another VDN which is a non-attendant 
VDN. In this case, the call will be removed from queue and treated as though it 
had just entering vector processing rather than a continuation from one VDN to 
another. The reverse will also be true if non-attendant VDNs get subsequently 
routed to attendant VDNs. The following commands will be provided for attendant 
vectoring:
nAnnouncement 
nbusy
ndisconnect after announcement 
ngoto step  if time-of-day is  : to  
:
ngoto step  if 
ngoto vector  if time-of-day is  : to  
:
ngoto vector  if 
nqueue-to attd-group
nqueue-to attendant 
nqueue-to hunt-group  pri 
nroute-to number  with cov  if 1
nwait-time  secs hearing 
1. In this c ase, unconditional is not a c hoice, it is the only option 
						

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
New Switch and Adjunct Support 
49 General Telephony Enhancements - Global 
1
nwait-time  secs hearing  then 
nstop
If attendant vectoring results in putting a call in the attendant queue, it will be 
placed in queue with the priority as administered on the console parameter form. 
There will be no changes made to the attendant priority queue for attendant 
vectoring. Note that even when partitioning is turned on and multiple attendant 
groups exist, all queues have the same priority assignments. Priority queue 
administration also applies for calls to an individual attendant (via the assigned 
extension).
If attendant vectoring results in putting a call in the hunt group queue, it will be 
placed in queue with the indicated priority. To use this command, the hunt group 
must be vector controlled.
Until some mechanism is provided for customers to apply vector commands or 
specialized administration to specific types of attendant group calls, the following 
will not be redirected to the attendant VDN:
nEmergency Access - these calls will still be sent directly to the attendant 
group. However, an attendant vectoring VDN can be assigned as the 
emergency access redirection extension.
nAttendant return calls - these calls will still be sent to the original attendant 
if available or placed into the attendant group queue if no attendants are 
available.
nSerial calls - as with return calls, serial calls will still be returned to the 
original attendant if available and placed in queue if no attendants are 
available.
nVIP Wakeup calls - these reminder calls will still be sent directly to the 
attendant group.
nCall Park time-out - these calls result in a conference (caller, principal, and 
attendant) and call vectoring does not allow conferenced calls to be 
vectored.
nCall Transfer time-out - these calls are controlled by the attendant return 
call timer and are processed as though they had been attendant extended 
calls (i.e., actual attendant return calls). It is unclear when or why this 
functionality was introduced, but the design will not be changed in order to 
allow the calls to be vectored.
One of the main reasons for providing attendant vectoring is to allow attendant 
group calls to be routed anywhere when the system is in night service. For R8, 
there will be no additional night service functionality provided for attendant 
vectoring. The desired night service routing can be provided using the existing 
night station service in conjunction with attendant vectoring. All existing night 
service rules will remain in place (e.g., night console service supersedes night 
station service which supersedes TAAS). Attendant group calls will not be  
						

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
New Switch and Adjunct Support 
50 General Telephony Enhancements - Global 
1
redirected to attendant vectoring when the system is in night service unless a 
night console is available. Otherwise, they will continue to be redirected to the 
applicable night service processing. In order to achieve attendant vectoring for 
calls when the system is in night service without a night console, the night station 
service extensions must be attendant vectoring VDN extensions.
Attendant VDN
The fact that VDN extensions can be dialed directly or calls can be transferred to 
VDN extensions will remain unchanged for attendant VDNs.
Currently, VDN extensions can be assigned to:
nHunt Group night destination - An attendant vectoring VDN can be 
assigned as a hunt group’s night destination. Calls to that hunt group when 
it is in night service will be redirected to the VDN and attendant vectoring 
will apply. Note that hunt group night service does not apply if the hunt 
group is vector controlled. When 
vector? is y, the night service destination 
field is removed from the form. In order for a hunt group to be available in 
vectoring for the 
queue-to hunt-group command, the hunt group must be 
vector controlled. So, the hunt group in the 
route-to command could be in 
night service and the call would then terminate to the indicated night 
service destination.
nLDN and trunk night destination - One or all trunk groups can be placed 
into night service and an attendant vectoring VDN can be assigned as the 
group’s night service destination. If a night destination is assigned for LDN 
calls, it will over-ride (for LDN calls) the trunk group’s night destination. 
Either of these destinations can be an attendant vectoring VDN. However, if 
tenant partitioning is administered and the trunk group night service 
destination is the attendant group, the call will be redirected to the VDN 
associated with the trunk group’s TN. If, instead, the night service 
destination is explicitly assigned to a particular attendant vectoring VDN, it 
may or may not be the VDN that would have resulted had the night 
destination been the attendant group.
nTenant night destination - For tenant partitioning, each par tition can be 
assigned a night destination. When tenant partitioning is turned off, local 
attendant group calls are sent to the LDN night destination. When 
partitioning is turned on, local attendant seeking calls are sent to the 
partition’s night destination.
nTrunk group incoming destination - The incoming destination can be an 
attendant vectoring VDN except for RLT trunk groups. As in trunk group 
night service, an assigned incoming destination to an attendant vector 
could result in the call being sent to a different VDN than if the destination 
had been assigned to the attendant group.
nLast coverage point in a coverage path - Attendant VDNs can be assigned 
as a coverage point.
nAbbreviated dialing lists - Attendant VDNs can be assigned to abbreviated 
dialing lists. 
						

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
New Switch and Adjunct Support 
51 General Telephony Enhancements - Global 
1
nEmergency access redirection - An attendant VDN can be assigned to 
emergency access redirection. When the attendant’s emergency queue 
over-flows or when the attendant group is in night service, all emergency 
calls will be redirected to this VDN. Careful thought should be given to 
routing these calls off-switch.
nQSIG CAS number for attendant group calls - An attendant VDN can be 
assigned to this number which determines where attendant group calls at a 
QSIG Branch are processed. This will allow local vectoring at a Branch 
prior to routing the calls to the Main or elsewhere.
nAuxiliary data for the following button assignments - In keeping with 
existing procedures, attendant VDNs will not be denied as auxiliary button 
data for:
nFacility busy indication - visual indication of busy or idle status for 
the associated extension
nManual message waiting indication - light a message waiting lamp 
on the station associated with the button 
nManual signaling - rings the station associated with the button
nRemote message waiting indicator - message waiting status lamp 
automatically lights when a LWC message has been stored in the 
system for the associated extension
Attendant Routing Examples
The following examples outline how the Attendant Vectoring commands can be 
used to route calls in an attendant environment. For these examples, consider the 
following vectors and vector administration.
Assume the following attendant vectors (tenant partitioning is turned on):
Table 3. Attendant Vectoring Vectors
VDN 1999
vector 1VDN 2999
vector 2VDN 3999
vector 3
1. goto step 6 if time-of-day is 
all 12:00 to 13:00
2. queue-to attd-group
3. goto step 7 if queue-fail
4. wait 999 secs hearing music
5. busy
6. route-to number 4000 with 
cov y if unconditionally
7. route-to number 
93035381000 with cov y if 
unconditionally1. queue-to attd-group
2. goto step 6 if queue-fail
3. announcement 9000
4. wait 999 seconds hearing music
5. disconnect after announcement 
9001
6. queue-to hunt-group 1
7. goto step10 if queue-fail
8.wait 999 secs hearing ringback
9. busy
10. route-to number 93035381000
with cov y if unconditionally1. goto step 7 if time-of-day is all 
    12:00 to 13:00
2. queue-to attd-group
3. goto step 7 if queue-fail
4. announcement 9000
5. wait 15 seconds hearing music
6. goto step 4 if unconditionally
7. queue-to attendant 6000
8. goto step 10 if queue-fail
9. wait 999 secs hearing ringback
10. route-to number 93035381000
with cov y if unconditionally 
						

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
New Switch and Adjunct Support 
52 General Telephony Enhancements - Global 
1
Administration is as follows:
a. All stations are assigned TN 1 which is associated with attendant group 1, 
VDN 1999, and music source 1
b. All trunk groups are assigned TN 2 which is associated with attendant 
group 1, VDN 2999, and music source 2
c. All VDNs are assigned TN 3 which is associated with attendant group 2, 
VDN 3999, and music source 3
d. Extension 4000 is assigned to a hunt group 1
e. Extension 6000 is assigned to an attendant console for direct access
Local Attendant Group Access Code
When a station dials the attendant access code, the call is redirected to vector 1. If 
it is lunch time, the call is sent to a hunt group and vector processing terminates. If 
it is not lunch time, the call is sent to attendant group 1. If an attendant is available, 
the call is terminated to the attendant and vector processing terminates. 
Otherwise, the call will be queued to the attendant group and the caller hears 
music from the music source assigned to TN 1 until an attendant answers the call. 
If the call cannot be queued, it is routed to a remote location with coverage and 
vector processing terminates. If the call is unanswered after 999 seconds in the 
attendant queue, the caller hears busy and vector processing terminates.
NOTE:
The route-to command leaves vector processing as soon as the call is 
successfully routed. So, in the example above, if it is lunch time the call will 
route to the hunt group and all hunt group processing will then apply. If the 
group is assigned a queue and the call can be queued, it will be. If not, and 
coverage criteria is met, the call will follow the hunt group’s coverage path. If 
the hunt group is in night service, the call will go to the hunt group’s night 
service destination. If the route-to command had indicated coverage “n”, the 
hunt groups coverage path would not have been followed and vector step 7 
would apply.
Incoming Trunk Calls to Attendant Group
When a call is received on a trunk which has the attendant group assigned as the 
incoming destination or the call is addressed to the attendant group, the call is 
redirected to vector 2. The call is then sent to attendant group 1. If an attendant is 
available, the call is terminated to the attendant and vector processing terminates. 
Otherwise, the call will be queued to the attendant group and the caller will hear 
the announcement followed by music from the music source assigned to TN 2. If 
the call is unanswered after 999 seconds in the attendant queue, the caller is 
dropped after hearing an announcement and vector processing terminates. If 
queueing to the attendant fails, the call is queued to hunt group 1. If a member is 
available to take the call, it will be terminated to the member and vector 
processing terminates. If a member is not available and the call can be queued, it 
will be and the caller will hear ringback until a member answers. If the call is  
						

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
New Switch and Adjunct Support 
53 General Telephony Enhancements - Global 
1
unanswered after 999 seconds in the hunt group queue, the caller hears busy and 
vector processing terminates. If the call cannot be queued, the call will be routed 
to the remote location and vector processing will terminate. 
NOTE:
The main difference from scenario 1 is queueing the call to the hunt group 
rather than routing the call there. In this scenario, the call will not follow the 
hunt group’s coverage path or night service destination.
Incoming LDN Calls
When a call is received for an LDN, the call is redirected to vector 3. If it is lunch 
time, the call is sent to attendant 6000. If the attendant is available, the call is 
answered and vector processing terminates. If the attendant is not available the 
call is placed into queue and the caller hears ringback until the attendant answers 
the call. If the call is unanswered after 999 seconds in the attendant’s queue, the 
call is sent to the remote location and vector processing terminates. If the call 
cannot be placed in attendant 6000’s queue, the call is routed to a remote location 
and vector processing terminates. If it is not lunch time, the call is sent to 
attendant group 2. If an attendant is available, the call is terminated to the 
attendant and vector processing terminates. Otherwise, the call will be queued to 
the attendant group and the caller will hear an announcement followed by music 
(from the music source assigned to TN 3) every 15 seconds. If the call cannot be 
queued, it is sent to attendant 6000.
NOTE:
Vector 3 attempts to queue the call to attendant 6000. A route-to command 
could have been used also, but care should be taken since an attendant 
cannot be assigned a coverage path. 
QSIG CAS
This example shows how you can use Attendant Vectoring with CAS.
CAS BRANCH
Suppose the customer would like to always play an announcement at a QSIG 
CAS branch before routing the call to the QSIG CAS main. An attendant VDN 
(assume 1000) would need to be administered in the QSIG CAS Number field at 
the branch instead of the number to the QSIG CAS main’s attendant access code 
(assume 303-538-0 with AAR access code 9). The following vector would play an 
announcement and then route the call to the QSIG CAS main. 
						

							What’s New in DEFINITY ECS
Release 8.2 Job Aid  555-233-754  Issue 1
April 2000
New Switch and Adjunct Support 
54 General Telephony Enhancements - Global 
1
CAS MAIN
Calls from a QSIG branch are sent to the main with the main’s attendant access 
code as the destination address so these calls are automatically attendant group 
calls. The VDN to which these calls get redirected will depend on the TN of the 
incoming trunk.
Night Station Service 
This example shows how you can make use of the Attendant Vectoring features 
for night service.
Administration is as follows:
a. Trunk group 1 is assigned TN 2 which is associated with attendant group 1, 
and night destination 4999
b. Trunk group 2 is assigned TN 1 which is associated with attendant group 2, 
and night destination 5999
c. Extension 6000 is assigned to a station
d. System night service is on
When a non-DID call comes in on trunk group 1, the call is redirected to VDN 
4999 which routes it to a remote location.
When a non-DID call comes in on trunk group 2, the call is redirected to VDN 
5999 which routes it to station 6000. If station 6000 is unavailable, the call will not 
Table 4. QSIG CAS Vector
VDN 1000
vector 1
1. announcement 9000
2. route-to number 93035380 with 
cov y if unconditionally
Table 5. Night Station Service Vectors
VDN 4999
vector 4VDN 5999
vector 5
1. route-to number 93035381000 with cov y if 
unconditionally1. route to number 6000 with cov n if uncondi-
tionally
2. route-to number 93035381000 with cov y if 
unconditionally