Lucent Technologies MERLIN LEGEND Release 7.0 Feature Reference page 673

Hide thumbs Also See for MERLIN LEGEND Release 7.0:
Table of Contents

Advertisement

MERLIN LEGEND Communications System Release 7.0
Feature Reference 555-670-110
Features
Remote Access
If a remote caller does not dial a number or feature code before the time-out
period expires, the call goes to the redirect destination programmed for remote
access.
Lines/trunks used for dedicated remote access must not be assigned to ring into a
calling group.
Systems that use Call Accounting System (CAS) track calls by barrier codes.
Touch-tone receivers are needed for remote access to work. For more information
about TTR requirements see
In Release 6.0 and later systems, a remote-access caller who calls into his or her
own local system can reach extensions networked to the local system (non-local
dial plan extensions), just as onsite users of the local system can.
Mode Differences
Hybrid/PBX Mode
Remote access Automatic Callback is available only in Hybrid/PBX mode for calls
made to busy pools.
In Release 6.0 and later systems, networked trunks for use by non-local dial plan
extensions connected to another MERLIN LEGEND Communications System or
to a DEFINITY ECS or DEFINITY ProLogix Solutions systems are available only
in Hybrid/PBX mode.
Feature Interactions
Account Code Entry
Allowed/
Disallowed Lists
''Touch-Tone or Rotary Signaling'' on page
A remote access user cannot enter account codes. If a remote access
user, however, calls an inside extension and the person at that extension
enters an account code, the code overwrites the barrier code number
(01–16) in the ACCOUNT field of the SMDR report.
Allowed and Disallowed Lists are COR items for remote access. When
barrier codes are not used, Allowed and/or Disallowed Lists can be
assigned to lines/trunks systemwide (tie trunks and non-tie trunks are
grouped separately). When barrier codes are used, Allowed and/or
Disallowed Lists can be assigned to individual barrier codes.
Do not assign any Allowed List to a remote access barrier code or to the
default COR for all tie and/or non-tie trunks. When used in conjunction
with toll and local restrictions applied to the barrier code or COR, Allowed
Lists do not work.
Issue 1
April 1999
613
716.

Advertisement

Table of Contents
loading

Table of Contents