Filter
Top Products
MERLIN LEGEND Communications System Release 6.0
System Programming
555-660-111
Issue 1
February 1998
Common Administrative Procedures
Page 4-339Remote Access Features
4
Remote Access over Networked Tandem PRI
and Tie Trunks 4
In Release 6.0 and later systems, Hybrid/PBX mode only, an ARS call originating
at a remote, networked communications system can arrive on a networked tie or
PRI trunk of the local system and receive remote-access treatment automatically.
This operation allows callers on one system to use lines on another system
speedily and transparently when optimal cost efficiency dictates the need for lines
connected to a different switch in the organization’s private network (in prior
systems and for calls over other remote access trunks, it is necessary to make an
explicit remote-access call, enter a barrier code, and finally use ARS).
To permit this operation, both the local and remote systems must be programmed
using ARS and remote access options. If two or more different system managers
administer the networked systems, they should work together to coordinate their
efforts.
Local Users Calling out on Networked Lines 4
To implement this operation on a local system where callers will use the
networked lines on a
remote
system, use the procedures outlined in the section,
“Automatic Route Selection” on page –363
.
Remote Users Calling out on Local Lines 4
When your system is networked with a remote system, you can set up your
system so that remote users can use public switched network trunks connected to
your control unit for cost-efficient calling. Your system treats such calls as remote
access calls, but the networked user does not enter a barrier code. Instead, the
system applies default restrictions that apply to all tie and/or all non-tie trunks, as
described later in this topic. These restrictions do not affect other remote-access
trunks that are programmed for use with barrier codes
Calling restrictions should be imposed at the remote originating switch using ARS
and extension FRLs as necessary. In addition, it is unnecessary to assign tandem
trunks for remote access. It is easiest if networked systems that share outside
facilities also use the same ARS access code (9, for example).
To implement this operation on a local system where callers on a remote
networked system will use the
local
trunks connected to your MERLIN LEGEND
Communications System control unit, use the procedures in this chapter as
outlined below. The relevant topics provide additional details.
1. It is not necessary to assign private networked trunks for remote access.
Callback for non-local trunk-to-trunk tandem calls does not work. Automatic
Callback can be used at the local system when all private networked trunks
are busy.