Lucent Technologies MERLIN LEGEND Release 7.0 Feature Reference page 674

MERLIN LEGEND Communications System Release 7.0
Feature Reference 555-670-110
Features
Remote Access
Allowed/
Disallowed Lists
Authorization Code
Automatic Route
Selection
Callback
Caller ID
Conference
Digital Data Calls
Display
Forward and
Follow Me
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. They 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 just 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.
Calling Party Number 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 service or Caller ID
is available. If you have Caller ID service and a Release 7.0 or later
system, the caller's name also can be viewed. If a remote access call is
sent to coverage because an invalid number has been dialed, an MLX or
ETR display telephone user who receives the call sees Cover DISA#?
on Page 1. Page 2 of the display shows the Calling Party Number or
Calling Party Name.
You can set up forwarding of calls to extensions or outside telephone
numbers through remote access, as long as the system manager has
enabled Remote Call Forwarding. To do so, call into the system on a line/
trunk that is programmed for remote access. If a barrier code is required,
the remote access dial tone (stutter tone) sounds. Enter the barrier code.
Once you have correctly entered the barrier code (or if barrier codes are
not required), the system dial tone sounds.
Issue 1
April 1999
614