Lucent Technologies MERLIN LEGEND Release 6.1 Feature Reference page 638

MERLIN LEGEND Communications System Release 6.1
Feature Reference 555-661-110
Features
Remote Access
Feature Interactions
Account Code Entry
Allowed/
Disallowed Lists
Authorization Code
Automatic Route
Selection
Callback
Caller ID
Conference
Digital Data Calls
Display
A remote access user cannot enter account codes. However, if a remote
access user 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.
In Release 6.0 and later systems (Hybrid/PBX mode only), for private
trunks that will be used by remote networked users to access network
trunks via ARS, default COR programming is used. Disallowed Lists
should be programmed appropriately (all tie and/or all non-tie) for these
trunks. Allowed Lists should not be used.
A caller cannot enter an authorization code on a remote access call.
Remote access users can make calls by using ARS. Dial into the system,
enter a barrier code if one is required, and dial the ARS code while
listening to system dial tone. FRLs can be assigned to restrict the routes
that remote callers can use. When barrier codes are not used, an FRL is
assigned to all lines/trunks (tie trunks and non-tie trunks are grouped
separately) and cannot be assigned to individual lines/trunks. When
barrier codes are used, FRLs are assigned to individual barrier codes.
The steps above are not used by networked non-local users making ARS
calls into your system, even though your system treats these calls as
remote access calls. Instead, a caller dials the ARS call normally, as they
would any other ARS call.
If the system is programmed for remote access, remote access users can
use Callback. (The factory setting for Automatic Callback is off, but you
can enable this feature in Hybrid/PBX mode only for remote access
callers.) The user cannot hang up but must wait on the line until the
extension or pool is available.
If a remote access call comes in on a loop-start line with Caller ID (via a
jack on an 800 GS/LS-ID module), caller information is recorded by
SMDR. Caller ID information is not retrieved on remote access
lines/trunks unless LS-ID Delay is programmed for the line/trunk, because
the calls are answered too quickly.
An inside user can initiate a conference with the callers involved in a
remote access call by selecting the active remote access line/trunk.
Data calls cannot be made into lines programmed for remote access.
Calls received through remote access show standard call information for
outside calls, including the caller's number if an ISDN/PRI service or
Caller ID is available. If a remote access call is sent to coverage because
an invalid number has been dialed, an MLX display telephone user who
receives the call sees
4 0
.
Issue 1
August 1998
Page 589