Lucent Technologies MERLIN LEGEND Release 6.1 Maintenance And Troubleshooting Manual page 294

MERLIN LEGEND Communications System Release 6.1
Maintenance and Troubleshooting 555-661-140
Private Network Calling Problems
If you want to make changes in FRLs for routes, speak with the coordinating
system manager for your private network and consult the following resources:
"How Facility Restrictions Levels Work in a Network" in Chapter 4 of
Network Reference discusses FRL planning in detail.
To change a UDP route FRL, see "Uniform Dial Plan Routing" in Chapter
5 of Network Reference , or "UDP Routing" in Chapter 3 of System
Programming.
To change the extension FRL, see System Programming, Chapter 3,
"Programming Procedures."
To change the FRL assigned to a remote access barrier code, see
"Remote Access" in System Programming , Chapter 3. Follow the
guidelines in "Remote Access Default Class-of-Restriction Settings" in
Chapter 4 of Network Reference .
!
SECURITY ALERT:
FRLs, applied to ARS and UDP routes, default CORs for all tie and/or all
non-tie tandem trunks, extensions, and remote access barrier codes are
particularly important for maintaining security in a private network. Before
changing FRLs in your system, check with the coordinating system
manager, who should understand the security implications for your local
system and for the private network as a whole.
Changing local FRLs may not work simply because the problem is not on the
local system. In this case, go to Possible Cause 5.
Possible Cause 5: The FRL for the default COR for non-tie trunks (PRI) on the
remote system may be blocking tandem calls. The private network is an all-PRI
network.
What to Do: Check with the coordinating system manager so that he or she can
determine where the problem exists. This may involve more than one system,
depending upon how your private network is set up. For example, a call might
be routed across the private network in a fashion such as this:
Issue 1
August 1998
Page 5-48