ATT DEFINITY Communications System Generic 3 Instructions Manual

Uniform Dial Plan (UDP)
Issue  3   March 1996
3-1185
nUDPCode — Conversion to AAR with given location c o de, further 
conversion suppressed
nAARCode — Conversion to AAR with given location code,  further 
conversion allowed
nENPCode — Conversion to private network number (via “ENP”  form), route 
to given node number routing
nTemp OOS — Temporarily out of service, give reorder
nIntrcpt — Invalid, give intercept treatment
nblank — This extension code does not apply
Whenever a UDP is used to route a call,...

Feature Descriptions
3-1186Issue  3   March 1996 
If AAR is active on the network, then subnet trunking can be used to insert the 
AAR feature access code on the originating end, or digit insertion may b e used 
to insert it on the incoming end. On the destination switch, AAR conversion is 
administered to convert 222 with 7 digits to an extension by deleting 3 digits and 
inserting a ‘6’. If AAR is not active, then Subnet Trunking must b e used on the 
source switch to delete the XXX and insert the...

Uniform Dial Plan (UDP)
Issue  3   March 1996
3-1187
code, the system translates the PBX code into the administered RNX. (This is in 
reverse for G3r.) If the PBX code indicates that the called extension is on the 
same switch, the call is routed to the local extension. If the PBX c o de indicates 
that the called extension is at another switch within the UDP, AAR uses the 
associated RNX to route the call to the correct switch within the private network. 
(The necessary subset of AAR is provided with...

Feature Descriptions
3-1188Issue  3   March 1996 
For G3i only, it is possible that the first one, two, three, or four digits (PBX code) 
of the 4- or 5-digit extension numb er could be the same as a local extension 
number. In this case, the UDP PBX code overrides the extension number at the 
local switch. Problems can be avoided by assuring that the PBX code does not 
match an extension number.
The list of PBX codes for a switch can contain PBX codes of varying lengths. For 
example, a switch may be...

Uniform Dial Plan (UDP)
Issue  3   March 1996
3-1189
changing of extensions from local to non-local. However, after the dial 
plan is changed to make an extension UDP, nothing can be administered 
with these extensions on the local switch.
nDCS 
UDP is required when DCS is provided. The necessary UDP software is 
provided with the DCS software.
nENP
For G3rV1, G3V2, and later releases, if an extension code is administered 
to use ENP node routing, ENP routes the call to the correct switch. If the 
AAR...

Feature Descriptions
3-1190Issue  3   March 1996 
VDN of Origin Announcement (VOA)
Feature Availability
This feature is available with Generic 3 Version 3 and later releases. The  Call 
Vectoring and VDN of Origin Announcements features must b e optioned.
Feature History
The VDN of Origin Announcements feature was first available in the System 85 
R2V4/Generic 2 releases. In these releases, the feature was known as 
‘‘City-of-Origin’’ and ‘‘Queue-of-Origin’’ announcements.
Description
VDN of Origin...

VDN of Origin Announcement (VOA)
Issue  3   March 1996
3-1191
an alphanumeric  display, no incoming call information is displayed until after the 
VOA message is completed.
After listening to the announcement, the agent can appropriately respond to the 
caller. For exam ple, if a user has two 800 numb ers, one for placing orders and 
one for technical support, they can administer two VDNs to route the calls to the 
same agents. When a call enters the system and is sent to a VDN, the VDN can 
have a VDN...

Feature Descriptions
3-1192Issue  3   March 1996 
nThe agent can hear a unique announcement based on the d ialed number 
identification service (DNIS) received from the service end office or c arrier 
switch. Each DNIS is assigned as the VDN of a vector. The announcement 
associated with the VDN  announces the services asso ciated with the 
DNIS.
NOTE:
The specific announcement associated with the current VDN only 
plays if the “VDN Override” field of the previous VDN is marked ‘‘y’’ 
(yes). If the “ VDN...

VDN of Origin Announcement (VOA)
Issue  3   March 1996
3-1193
The system maintains a separate logical queue for the VDN of Origin 
Announcements when you use the TN750 circuit board  for  integrated 
announcements. If, because of traffic considerations or inoperative equipment, 
the VDN of Origin Announcement cannot be given to the agent within 0 to 1 
second, the system stops an attemp t to p rovide the announcement.
NOTE:
VOA announcements receive higher priority than other announcements on 
the TN750....

Feature Descriptions
3-1194Issue  3   March 1996 
nAgent Call Handling
Answering Options
— Automatic Answer
An ACD agent set u p for Automatic Answer receives zip tone 
instead of ringing. The VDN of Origin Announcement begins 
immediately after the zip tone ends. A non-ACD agent set u p for 
Automatic Answer hears an incoming call ID tone when a call 
comes in. Through the use of a route-to vector step, non-ACD 
agents can receive a VDN of Origin Announcement. The 
announcement begins when the incoming...