Forced Account Code Entry; Ars Facility Restriction Level - Lucent Technologies MERLIN LEGEND Release 5.0 System Planning Manual

MERLIN LEGEND Communications System Release 5.0
System Planning 555-650-112
5 Data Communications
Assigning Features to Data Stations

Forced Account Code Entry

The Forced Account Code Entry feature is used for billing or for tracking data calls
by requiring data extension users to enter account codes (1 to 16 digits) for
outside calls. Assign this feature to data stations so that you can associate
outgoing data calls with specific client accounts.
NOTE: NOTE: NOTE:
Account codes cannot be used to track incoming calls to data stations.
Planning Form Instructions
To record your decisions, use the Optional Features section of Data Form 1a or
1b for each data station. Under the Forced Account Code Entry heading, do one
of the following:
If the user must enter an account code for outgoing calls, check the Yes
box.
If you do not want the feature assigned to the data station, check the No
box (the factory setting).

ARS Facility Restriction Level

Use these instructions only if the system is operating in Hybrid/PBX mode.
If the system uses ARS for data calls, you can assign a Facility Restriction Level
(FRL) to each data station. This value (from 0 to 6) corresponds to the FRL
assigned to each route and is used to restrict data users from access to specific
routes. Before restricting a data station, review the values assigned to each route.
To restrict a data station from specific routes, assign an FRL value lower than the
route's lowest value. (Values equal to or greater than the route's values allow data
extension users to access those routes.) A value of 0 is the most restrictive, and a
value of 6 is the least restrictive. The factory setting is 3.
For example, to give an modem data station unlimited use of any ARS route,
assign a value of 6. If you have ISDN terminal adapter data stations, assign a
value of 0 to prevent users from inadvertently using ARS to select an analog line
for outside data calls.
5
5
Issue 1
June 1997
Page 5-39