Lucent Technologies MERLIN LEGEND Release 6.0 Network Reference Manual page 126

MERLIN LEGEND Communications System Release 6.0
Network Reference 555-660-150
2 Call-Handling Scenarios
Network Configuration Scenarios
Intersystem voice calls to and from System G do not display calling name
or number information at MLX display telephone or PassageWay
recipients, because these calls travel over tandem tie trunks.
Notice that because System G is connected to the network by analog
tandem tie trunks, PSTN pools are used when users at other systems call
the single 2B data extension on System G (these calls could be made as
outside toll calls using ARS but instead are routed via the non-local dial
plan). The 2B data extension on System G is a video system, and users
there call only certain video extensions on other network systems (only the
executive video extension on System E is accessed, for example). If a
System H user calls a 2B data extension on System G, the call is routed
first over tandem PRI facilities to System E, which adds the necessary
digits and sends the call over the PSTN on a PRI facility. When the call
arrives on the System G BRI facility, it is routed directly to the video
system.
Similarly, the System G users access its PSTN BRI facilities when they
must reach 2B data extensions on other network systems. The UDP FRLs
assigned to these routes are high, which helps safeguard against toll fraud
and reserves System G's BRI facilities for authorized use. Digit
manipulation is used to route these calls correctly to PSTN facilities.
To reach System G, the routes for intersystem voice calls direct them from
Systems F and H via the hub, System E, where they are then sent to
System G over tandem tie facilities. FRLs for routes to System G are
slightly higher to avoid excessive call volume over the analog tandem tie
trunks.
Calls between extensions on Systems E, F, and H do display caller
information, according to display preference settings, at the destination
MLX display extensions.
Table 2–20, page 2–70
systems for use of local PSTN facilities and non-local PSTN facilities. Remote
Access codes are not shown but are set up to be unique and unambiguous across
the network. As you review the table, keep the following points in mind:
As in earlier Scenarios 1 and 2, SMDR reports, if programmed at all
systems to include outgoing calls, may trace the same call on separate
SMDR reports for different systems. System managers must consider time
zone differences as they review reports for systems in the private network.
To avoid confusion and for future planning purposes, tandem trunks and
pools of tandem trunks are also numbered uniquely and unambiguously.
System H users do not make Interexchange calls. The system's loop-start
line is assigned to the main pool, Pool 70.
shows how the system managers set up their local
Issue 1
February 1998
Page 2-66