Lucent Technologies MERLIN LEGEND Release 6.0 Network Reference Manual page 63

MERLIN LEGEND Communications System Release 6.0
Network Reference 555-660-150
2 Call-Handling Scenarios
Networking Guidelines
Remote Access
When setting up your network for intersystem calling, keep the following important
points in mind:
You cannot program the local ARS access code or pool dial-out codes into
non-local dial plan extension ranges; the system blocks this programming.
Non-local extension range numbers cannot begin with the local ARS
access code. If, for example, the ARS access code begins with 9 and a
non-local dial plan extension range is 9230–9330, programming is blocked.
You must not program the ARS access code of a non-local system into the
non-local dial plan because it poses a security risk; it is best if all networked
systems assign the same ARS access code. For more information, see
"Automatic Route Selection (ARS)" on page
The Remote Access codes of non-local systems can be included in the
non-local dial plan for the convenience of technicians for technical support
or for users to program their forwarding home extensions on a non-local
system. Each system should have a unique and unambiguous Remote
Access code. For more information, see
Your non-local dial plan programming has no effect on the remote
system(s) it references. Local dial-plan changes made at a system do not
automatically update the non-local dial plan numbering plans of networked
systems. To avoid misrouting, it is recommended that manual adjustments
to the non-local dial plans made by network system managers be made at
the same time. System managers should provide ranges wide enough to
avoid problems in future non-local dial plan changes.
In most cases, the extension numbers programmed into the non-local dial
plan should be the same extension numbers that users at remote systems
dial in order to reach one another within their systems. The main exception
occurs when non-local dial plan numbers refer to extensions on DEFINITY
Enterprise Communications Server (ECS) or DEFINITY ProLogix Solutions
systems, which include five digits. See
DEFINITY ProLogix Solutions Systems" on page 2–4
Extensions included in ranges must be unique and unambiguous across
systems. In other words, if the local system includes extension 112 , that
system blocks the programming of a non-local extension range that
encompasses extension 112 2. If it allowed the range, calls to 1122 would
be misrouted because the system would send calls for extension 1122 to
extension 112 as soon as it received the first three numbers. In this
example, the local system prevents the numbering conflict. However, if the
local system is connected to more than one other networked system,
programmed extension ranges must assure proper routing. For example, if
the manager on System A must program extension ranges on two
connected systems, System B and C, the specified ranges on Systems B
2–6.
"Remote Access" on page
"Non-Local DEFINITY ECS or
for details.
Issue 1
February 1998
Page 2-3
2–6.