Call To Non-Local Extension: Warble Tone (Error Tone) - Avaya MERLIN MAGIX Maintenance And Troubleshooting Manual

Maintenance and Troubleshooting
Possible Cause 10: Switch B has more B-channels than Switch A. When Switch B calls Switch A,
it is trying to establish contact on a higher number B-channel than Switch A has. Therefore, Switch
B receives the fast busy tone.
What to Do: Remove the extra B-channel from Switch B so that Switch B has the same number of
B-channels as Switch A.
Call to Non-Local Extension: Warble Tone (Error
Tone)
There are several reasons why a call to a non-local extension receives warble tone. The first two
possibilities are easy to check, because they all derive from the local system. The third possible
cause only occurs when there are tandem PRI facilities included in the route for the call.
Possible Cause 1: The extension number is omitted from the non-local dial plan.
What to do: Check your system's non-local dial plan to see whether the destination extension
number is included in a programmed extension range. If it is not, you have solved the problem. If it
is included, check all tandem switches to ensure that the extension is in their non-local dial plans.
To add the extension to the non-local dial plan, consult the coordinating system manager and see
Reviewing the Non-Local Dial Plan Numbering or System Renumbering in the Feature Reference.
If it is included in all programmed extension ranges, proceed to Possible Cause 2.
Possible Cause 2: The remote system rejects the dialed number on an all PRI network route.
What to do: Check that the number that arrived is in the non-local dial plan. If the number is in the
non-local dial plan, verify that it is a valid extension number for a station, adjunct, calling group,
Listed Directory Number (LDN), Remote Access, Dial 0, or ARS.
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 (TDL, 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
Programming menu, then selecting
choosing
Non-Lcl UDP
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
I
the Automatic Route Selection feature in the Feature Reference.
Troubleshooting Guidelines and Preparation
5-18
Ext Direct
from the same menu.
5
option on the System
Print
. You can see programmed route FRLs by