Filter
Top Products
MERLIN LEGEND Communications System Release 6.1
Network Reference
555-661-150
Issue 1
August 1998
Troubleshooting
Page 6-12Call to Non-Local Extension: Warble Tone (Error Tone)
6
Possible Cause 3: The pattern does not have pools assigned to any routes.
What to do:
Verify that the correct pattern is assigned to the range. If the pattern
is correct, assign the pools to the routes.
Possible Cause 4: The FRL assigned to the extension may not permit the call on
any of the routes included in the pattern for the call.
What to do:
Look at the system form for the caller’s extension. Depending on the
type of extension (analog multiline, MLX, digital or analog data, operator, and so
on) the extension form varies. You can see a report that lists all extension FRLs by
choosing the
3ULQW option on the System Programming menu, then selecting ([W
'LUHFW
. You can see programmed route FRLs by choosing 1RQ/FO8'3 from the
same menu.
For the call to go through, the extension FRL must be equal to or greater than at
least one of the route FRLs for the pattern that is programmed to reach the
destination extension range.
■ If it is appropriate to change the extension FRL, see “ARS Restriction
Levels for Extensions” in Chapter 4 of
System Programming.
■ If you change one or more route FRLs, the modification may restrict or
unrestrict calling from some private network extensions. Be sure to clear
any changes with the coordinating system manager for the private network.
If you decide to make this change, see “Uniform Dial Plan Routing” on
page 25 or “UDP Routing” in Chapter 4 of
System Programming.
For
details about FRLs in private networks, see “Facility Restriction Levels and
Remote Access” on page 5.
■ If a local extension or route FRL is not the problem, the coordinating
system manager must determine the private network route for the call once
it leaves your local system. If there is an intervening system between yours
and the destination, proceed to Possible Cause 5.
■ If there is no intervening system between yours and the destination, 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:
Origin System A
→System B→System C→Destination System D
In this configuration, the coordinating system manager must check routes and
default COR attributes for Systems B and C.