MERLIN LEGEND Communications System Release 6.1
Network Reference
555-661-150
Issue 1
August 1998
Call-Handling Scenarios
Page 2-78Network Configuration Scenarios
2
■ To insure correct routing for emergency and other N11 calls, and for
interexchange calls (IXC), assign PRI trunks to the main pool.
■ Using tandem PRI trunks, an additional system could be connected to
either System F or System H. Were an additional system connected to
System G, its features and performance would be limited by the tandem tie
trunks that link System G to the private network.
■ Default remote access COR settings are not shown. As in earlier
scenarios, the system managers require barrier codes for remote access
calls via PSTN facilities and those dialed as intersystem calls using a
Remote Access code; this requirement is ignored for ARS routing across
the private network. Instead, the default COR FRL is compared to the UDP
or ARS route before a call leaves the local system to reach another private
network system or the PSTN.
■ A detailed table of ARS routing is not shown; this has been described in
earlier scenarios. The ARS access code for all systems is 9.
■ The integrated VMI calling group (at each remote system) used to route
calls to the centralized VMS/AA is set up as described in “Implementation
of Centralized VMS/AA” in Chapter 5.