Lucent Technologies MERLIN LEGEND Release 6.1 Feature Reference page 632

MERLIN LEGEND Communications System Release 6.1
Feature Reference 555-661-110
Features
Remote Access
Local Dial Plan. If a remote access caller dials the system on a DID, E&M,
PRI B-channel with dial-plan routing, T1-emulated tie line, or T1-emulated
DID trunk, the caller can be connected without entering the remote access
code separately. Instead, the remote access code is part of the telephone
number dialed by the caller and is routed automatically by the system as a
remote access call. If the dialed telephone number does not include the
remote access number or the line/trunk is not programmed for routing by
dial plan, the call is treated as a normal incoming call and remote access is
not available.
Non-Local Dial Plan (Release 6.0 and later systems, Hybrid/PBX mode).
Intersystem calls between extensions on networked systems are not
remote access calls. However, the remote access code for a non-local
system can be included in the non-local dial plan, so that users from one
system can reach another networked system more economically via
remote access for changing forwarding or for system maintenance. The
remote access codes of networked systems must be unique and
unambiguous with respect to the other numbers in the local and non-local
plans. The receiving system applies restrictions, and barrier codes should
be required.
When a call is received for an unassigned number on a dial plan-routed PRI
facility, a DID trunk, a dial-in tie trunk, or a line/trunk programmed for shared
remote access and Night Service is activated, the call is redirected to the QCC
queue, a calling group, or an extension, depending on how the destination of calls
to unassigned numbers is programmed. The factory setting specifies the primary
operator as the destination.
When a call is received for an unassigned number on a private network facility, the
caller hears a fast busy or warble tone, depending on the type of facility the call
arrived on.
NOTE:
In Release 6.0 and later systems (Hybrid/PBX mode), a remote access
user from one system can reach Remote Access on a networked remote
system by using a DID trunk, tandem trunk, a PRI B-channel with dial-plan
routing, T1-emulated DID trunk, or dial-in tie trunk. The remote system
applies any restrictions. The remote access codes for each system must
be unique and unambiguous. The default COR settings that control this
access should require barrier codes.
Table 40 summarizes the ways that remote access is made available to callers,
depending upon the type of line/trunk and the routing used on that line/trunk.
Issue 1
August 1998
Page 583