Lucent Technologies MERLIN LEGEND Release 6.0 Network Reference Manual page 77

MERLIN LEGEND Communications System Release 6.0
Network Reference 555-660-150
2 Call-Handling Scenarios
Network Configuration Scenarios
Figure 2–1 on page 2–15
hypothetical network that includes two MERLIN LEGEND Communications
Systems. A few extensions are shown so that the scenario can demonstrate how
calls are handled and how they display at different types of extension equipment.
Sample PSTN facilities are shown to illustrate routing when non-local callers use
them or when outside calls are transferred or routed across the network.
Note the following general facts about this small network:
Each system has its own voice mail/auto attendant. These might both, for
example, be MERLIN LEGEND Mail applications.
The two systems are located in different area codes in the same large
Mid-Atlantic metropolis. They are not, however, geographically distant or in
different time zones.
Users at each system must make certain ARS calls that are routed over
tandem trunks to the other system, where they go out to the PSTN. For
example, if a local user on System A needs to reach an outside party in the
732 (Holmdel, NJ) area code, the call goes over tandem PRI facilities and
then to the PSTN through an outside facility connected to System B; if a
local user on System B needs to reach an outside party in the 212 (New
York, NY) area code, the call goes over tandem PRI facilities and then to
the PSTN through an outside facility connected to System A. When the
preferred routes are used, toll savings are optimal.
Non-Local Dial Plans and Facilities Planning
This section shows how non-local dial plans, switch identifiers, UDP routing, ARS
routing, and remote access are set up for each system. Not all details are
provided for all facilities and extensions.
Table 2–1, page 2–19
routes for pools when people in one system call people at non-local extensions.
For each route, there is a pool number, an FRL, and assignment of voice and/or
data service. Digit manipulation is required for routes that use PSTN trunks, which
are assigned high-numbered FRLs and are available to only a few users.
Reserved pools are assigned for high-speed 2B data calls, which must not be
queued using the Automatic Callback feature. Restrictive FRLs are unnecessary
for these routes, because they are for data only and cannot be used for voice
calls.
In this example, voice calls over tandem trunks to the non-local system are
permitted for all users. When all network routes are unavailable, voice users
employ Automatic or Selective Callback feature to queue for Route 1. To ensure
that high-priority callers are not waiting too long for tandem trunks to become
available, split the tandem trunks into separate routes with different FRLs.
The Remote Access code for each system is unique and unambiguous, so that
users from one system can make lower cost remote access calls into the other
shows some PSTN facilities and PRI tandem trunks in a
shows some applicable extension ranges, patterns, and
2
Issue 1
February 1998
Page 2-17