ATT DEFINITY Communications System Generic 3 Instructions Manual

							Extension Number Portability
Issue  3   March 1996
3-727
The ENP Num bering Plan table must be administered to associate the leading 
one or two d i gits of extensions in the ENP subnetwork with a 3-digit ENP code, 
used to construct a 7-digit AAR-like ENP number.
Administering the ENP subnetwork in this manner enables stations to move from 
one node to another within the ENP subnetwork without having to change their 
extensions.
ENP Numb ering Plan administration d e pends on both the UDP customer option 
and on the “Dial Plan Administration” field that asks if the administrator wishes to 
use UDP. If b oth of these fields are not administered to ’y’, then ENP Numbering 
Plan administration is not allowed. If the UDP customer option is not a dministered 
to ’y’, then ‘‘enp-number-plan’’ is not even listed as an option to the a dministrator; 
if UDP is administered to ’y’, then the option is available, b ut the command is 
denied if UDP is not also administered to ’y’ on the Dial Plan form. The  UDP  plan 
length is also administered on the Dial Plan administration form.
All ENP codes specified in the ENP Numb ering Plan should be administered as 
home in AAR Analysis administration, but there is no automatic cross checking to 
verify that ENP codes have been administered correctly in AAR Analysis.
Hardware/Software Requirements
ENP Numb ering Plan does not require any ad d itional hardware or software. 
However, a UDP software license must be acquired. 
						

							Feature Descriptions
3-728Issue  3   March 1996 
Facility Busy Indication
Feature Availability
This feature is available with all Generic 3 releases.
Description
Provides multi-appearance voice terminal users with a visual indication of the 
busy or idle status of an extension number, a trunk group, terminating extension 
group, a hunt group (DDC or UCD group), or any loudspeaker paging zone, 
including all zones.  The Facility Busy Indication button p rovides the voice 
terminal user d irect access to the extension number, trunk group, or paging 
zone.
When the lamp associated with the Facility Busy Indication button is lighted, the 
tracked resourc e is busy.  If the lamp is dark, the resource is idle. If the lamp is 
flashing, the tracked resource is placing a call to the voice terminal with the 
button.
Pressing the Facility Busy Indication button automatically selects an idle call 
appearance and places a call to the resource.
Considerations
With Facility Busy Indication, a user can monitor the busy or idle status of a 
frequently called extension number.  By knowing when the monitored facility is 
busy or idle, the user c an wait until the facility is idle to make a call.  This reduces 
the time spent trying to call busy facilities.
Facility Busy Indication buttons can be administered to track the same resource. 
The maximum parameters for the DEFINITY Communications System Generic 1 
and Generic 3 hardware and software items can be found in the System 
Hardware and Software Capacity Limits tables located throughout the DEFINITY  
documentation set. A new state of the tracked resource (a change from idle to 
busy) is updated within five seconds after the system detects the change.
Extension numbers, trunk group access codes, and Loudspeaker Paging 
Access codes can be stored in a Facility Busy In dication button.  However, an 
access code followed by other numb ers cannot be stored.
It is possible that an incoming call which causes the lamp to flash may g o 
unanswered.  If the lamp represents the status of a trunk group and all trunks in 
the trunk group become busy before the flashing call is answered, the system 
software lights the lamp  steadily to indicate that all trunks are busy. When a trunk 
in that trunk group becomes idle, the system software turns off the busy  
						

							Facility Busy Indication
Issue  3   March 1996
3-729
indication and the lamp goes d ark. Therefore, the lamp flashes, lights steadily, 
and goes out while the call has neither been answered nor dropped.
The Facility Busy Indication cannot monitor the status of the attendant console.
Interactions
None.
Administration
Facility Busy Indication is administered on a per-voice terminal basis by the 
System Manager.  The only administration required is to assign the Facility Busy 
Indication button to a voice terminal or attendant console.
Hardware and Software Requirements
No a d ditional hardware or software is required. 
						

							Feature Descriptions
3-730Issue  3   March 1996 
Facility Restriction Levels (FRLs) and
Traveling Class Marks (TCMs)
Feature Availability
Facility Restriction Levels (FRLs) are available with all Generic 3 releases; 
Traveling Class Marks is an optional feature available with all Generic 3 releases 
(except G3vs/G3s ABP) when Private Network Access (PNA) software is 
purchased. Traveling Class Marks are not available with G3vs/G3s ABP.
Description
Provides u p to eight levels of restriction for users of the AAR and/or ARS features.
FRLs and TCMs provide a method of allowing certain calls to specific users, 
while denying the same calls to other users. For example, certain users may be 
allowed to use Central Office trunks to other corporate locations while other users 
may b e restricted to the less expensive private network lines.
FRLs and TCMs are transparent to the user.  Appropriate values are 
predetermined and programmed into the system.  Dialing procedures are 
unaffected.
Call routing for each call is determined by the dialed Area Code and/or office 
code (either p u blic or private network) or by the administered dial string. 
Translation on the first three or six d i gits of the called number yields Routing 
Patterns. More than one translation can point to the same pattern. A blank entry 
provides intercept treatment and is used for unassigned private network office 
codes. Each Routing Pattern contains up to six routing preferences (16 for G3r).  
Each preference includes the following information:
nTrunk Group Number
nMinimum FRL required to access the trunk group
No sp ecific routing order is required.
Each facility, such as a trunk or voice terminal, capable of originating a call also 
has an associated FRL.  Whether a given call is allowed or not depends on two 
things:  compatibility between FRLs and availability of an idle trunk.
Compati bility is determined by a comparison of the minimum FRL associated 
with the trunk group and the originating-side FRL.  Either can have a value of 
zero through seven. Access to the associated trunk group is permitted if the 
originating-side FRL is greater than or e qual to the minimum FRL. Note that lower 
originating-side FRLs can access fewer routing preferences, whereas lower 
minimum FRLs permit  greater access.  Stated another way, a 0 originating-side 
FRL is the most restricted and a 7 is the least restricted.  A 0 minimum FRL is the  
						

							Facility Restriction Levels (FRLs) and Traveling Class 
Marks (TCMs)
Issue  3   March 1996
3-731
least restrictive, and a 7 is the most restrictive (when a p plied to the routing 
pattern’s FRL). Comp atibility checking begins with the first-c hoice route (the first 
one in the pattern).  Assuming access is permitted, availability is checked; that 
is, is there an i dle trunk in the group?  If so, the call continues.  If not, 
compati bility is checked on the next routing preference.
If the compatibility check fails on the first-choice route, the intercept tone 
continues.
NOTE:
Intercept is not received unless all p ossible routes are inaccessible.
If the compatibility check fails on the second or subsequent routing preference, 
or if all accessible trunk groups are busy, the call may queue on the first choice 
trunk group or first compatible trunk group. (See the Ringback Queuin g feature 
for d etails.)
If the trunk group selected for a call is an intertandem tie trunk group, then a TCM 
is outpulsed as the last digit.  A TCM is equivalent to the originating-side FRL. At 
the next tandem switch,  compatibility and availability checking are done, as 
before.  In this case, the FRL assigned to the incoming intertandem tie trunk 
group is used as the originating-side FRL (to compare with the TCM). If it is 
sufficient, then the call continues and no comparison on the TCM and the 
outgoing trunks TCM is made. If it is not sufficient, then the TCM is compared 
with the outgoing trunk’s FRL to see if the call is allowed to continue. However, if 
this fails to yield a route and if the TCM is higher than the tie trunk FRL, then the 
TCM is used in another attempt to comp lete the call.
Call Originating Facilities
At a switch serving as the call origination point, any of the following can be the 
originator of an ARS or AAR  call:
nVoice terminal
nRemote Access user
nAttendant
nIncoming tie trunk group from a subtending location
nData terminal c a pable of Keyboard Dialing
At a tandem switch, either of the following can b e the originator of an ARS or AAR 
call:
nIncoming Intertandem tie trunk group
nIncoming Access tie trunk g roup — links a remote main switch to a 
tandem switch
Each of these facilities is assigned an FRL via an associated COR, either directly 
or indirectly. 
						

							Feature Descriptions
3-732Issue  3   March 1996 
Voice terminals and all incoming tie trunk groups use the FRL contained within 
the assigned COR.  Attendants use the FRL contained within the COR assigned 
to the attendant group for extended calls. If Individual Attendant Access is 
assigned, the individual attendant’s COR FRL is used. Data terminals use the 
FRL contained within the COR assigned to the associated data module.
The Remote Access feature can be accessed via a DID trunk group, tie trunk 
group, dedicated central office trunk group, 800 Service trunk group, and/or 
dedicated foreign exchange trunk group. In the absence of a Remote Access 
Barrier Code, the applicable FRL is contained in the COR assigned to the trunk 
group. If a Barrier Code is required on Remote Access calls, the a p plicable FRL 
is the Remote Ac cess default entry (none) contained in the COR assigned to the 
Barrier Code.
Call Terminating Facilities
Any of the following trunk types can serve as the termination point for an ARS or 
AAR call:
nTie trunk — excluding RLTs, but including CCSA and EPSCS Access 
trunks
nWA TS
nCO
nFX
nIS D N - PR I
Each of these outgoing trunk groups has an assigned COR that c ontains an FRL.  
However, this FRL is never used.  Terminating-side FRLs are assigned in the 
Routing Pattern, not to the outg oing trunk group.
Considerations
FRLs p rovide the means to restrict certain users from placing selected calls while 
allowing other users to place the same calls.
Originating-side FRLs are assigned via the COR of the originating-side facility, 
such as an incoming tie trunk group or voice terminal.  If an FRL is not assigned, 
the system assumes an FRL of 0 for all originating facilities except the attendant 
group.  An FRL of 7 is assumed for the attendant group.
A COR is also assigned to each trunk group.  If the COR specifies an FRL, the 
FRL is ignored. The minimum FRL specified in the Routing Pattern is the only FRL 
used on the terminating side of the call.
On attendant-extend e d calls, the attendant group FRL is used rather than the 
FRL of the calling party. 
						

							Facility Restriction Levels (FRLs) and Traveling Class 
Marks (TCMs)
Issue  3   March 1996
3-733
Interactions
nARS and AAR
FRLs apply only on ARS and AAR calls (including UDP).
nAuthorization Codes
Authorizations Codes can be used to raise a user’s FRL.
nCDR Account Codes
If CDR 15-digit  account  codes are used, the “FRL”  field in the CDR record 
is overwritten.
nIntercept Treatment
The TCM used to pass on the originating facility’s FRL is sent by ISDN 
facilities in the SETUP  message.
Administration
FRLs are assigned by the System Manager as a part of ARS and/or AAR 
administration.  Originating FRLs are assigned on a per-COR basis. Terminating 
FRLs are assigned on a per-Routing Pattern basis.  TCMs do not require 
assignment.
Assignment Guidelines
If there will b e users within the system who are not allowed to make outside calls, 
use some value other than 0 as the value for the first-choice trunk group.  By 
assigning these users an FRL of 0, none of the trunk groups can be accessed 
(since all trunk group FRLs are greater than 0). Such calls are d enied.
Each Routing Pattern must be individually constructed.  The same trunk group 
can be used in more than one pattern.  The associated FRL is assigned within 
the pattern and is not associated with the trunk group itself.  The same trunk 
group can have a different FRL in a different p attern.
Be consistent in FRL assignments.  Do not use a range of 0 through 5 in one 
pattern and a range of 2 through 7 in another pattern if all users can access the 
first-choice route.  Admittedly, the trunk group with an FRL of 2 may be more 
expensive than the trunk group with an FRL of 0, but there is no real reason to 
assign a 2 to a trunk group that everyone can access.  For ease of assignments, 
always use a 0 for such a trunk group.
There should be a COR established for each FRL used in a Routing Pattern. The 
appropriate COR is then assigned to the users who can access the routes 
restricte d by the FRL value.  For example, a mid dle executive mi ght b e able to 
access all routes with an FRL of 5 or lower, whereas the president can access all 
routes.  In this case, the executive is assigned a COR with an FRL of 5 and the 
president is assigned a COR with an FRL of 7. 
						

							Feature Descriptions
3-734Issue  3   March 1996 
Remote Access users can access the system’s features and services the same 
as an on-premises user. FRL assignment is via Remote Access Barrier Codes. 
Up to 10 Barrier Codes, each with its own COR (and FRL) can be assigned.  
Although the COR defines other restrictions, 10 Barrier Codes are enough to also 
provide a range of FRL assignments. Assignment of Barrier Code FRLs is the 
same as if the user were on-premises. The  simplest way to assign these FRLs is 
to duplicate the on-premises FRLs, then merely relate the a ppropriate Barrier 
Code to those that will be using Remote Access.
Hardware and Software Requirements
No a d ditional hardware is required.   The optional Private Network  A c cess or 
ARS software is required.  
						

							Facility Test Calls (with Security Measures)
Issue  3   March 1996
3-735
Facility Test Calls (with Security 
Measures)
Feature Availability
This feature is available with all Generic 3 releases. Logoff Notification is 
available with G3V4 and later releases.
Description
Provides a voice terminal user with the capability of making test calls to access 
specific trunks, DTMF receivers, time slots, and system tones.  The test call is 
used to make sure the facility is operating properly.  A local voice terminal user 
can make a test call by dialing an access code. AT&T remote maintenance 
personnel may also use this feature to make test calls.
Four types of Facility Test Calls can be made:
nTrunk test call
Accesses specific tie or CO trunks. DID trunks cannot be accessed.
A user’s Class of Restriction must be a dministered with the Facility Access 
Trunk Test option in order for the user to make trunk test calls.
nDTMF receiver test call
Accesses and tests the DTMF receivers located on a Tone Detector or 
Call Classifier/Tone Detection circuit pack.
nTime slot test call
Connects the voice terminal user to a specific time slot located on the 
Time Division Multiplex buses or out-of-service time slots.
nSystem tone test call
Connects the voice terminal user to a specific system tone.
For detailed instructions for making test calls, see Chapter 5 of 
D EFI NIT Y 
Communications System G3i/s/vs Maintenance
, 555-204-105, DEFINITY 
Communications System G3r Maintenance
, 555-230-105, DEFINITY 
Communications System Generic 1 and Generic 3 Voice Terminal O perations
, 
555-230-701, or 
DEFI NI TY Com munications System Generic 1 and Generic 3 
Console O peration
, 555-230-700. 
						

							Feature Descriptions
3-736Issue  3   March 1996 
Security Measures
To help secure this feature from unauthorized use the following steps can be 
taken:
nRemove the code when not in use.
nChange the code from the factory default.
nSecure record s of the c o de.
nUse COR to restrict which users can use the access code.
Logoff Notification, available with G3V4 and later releases, can be set to notify 
the system administrator at logoff that the Facility Test Calls feature is still 
enabled. Notification guards against inadvertently leaving the Facility Test Calls 
feature active. It can also alert the system administrator to unauthorized feature 
activation.
Consult the 
BCSystems Security Handbook, 555-025-600, for additional steps to 
secure your system.
Considerations
If a user has a problem with a specific system facility, Facility Test Calls can be 
used to test that facility for proper operation.
A DTMF voice terminal must be used to make test calls.
NOTE:
AT&T has designed the Facility Test Calls feature incorporated in this 
product that, when properly administered by the customer, will enable the 
customer to minimize the ability of unauthorized persons to gain access to 
the network. It is the c ustomer’s responsibility to take the appropriate steps 
to properly implement the features, evaluate and administer the various 
restriction levels, protect access codes and distribute them only to 
individuals who have been advised of the sensitive nature of the access 
information. Each authorized user should be instructed concerning the 
proper use and handling of access codes.
In rare instances, unauthorized individuals make connections to the 
telecommunications network through use of test call features. In such 
events, applicable tariffs require that the customer pay all network charg es 
for traffic. AT&T cannot be responsible for such charges, and will not make 
any allowance or give any credit for charges that result from unauthorized 
access.