Calls To Non-Local Extensions: Unexpected Busy Tone; This Topic Discusses Unexpected Busy Tones That May Be Caused By System Features. It Applies Not; Only To Regular Calls From One Private Network Extension To Another But Also To Remote Access Calls - Avaya MERLIN MAGIX Maintenance And Troubleshooting Manual

If you change one or more route FRLs, the modification may restrict or unrestrict calling from
I
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" in Chapter 5 of the Network Reference. For details about FRLs in private networks,
see "Facility Restriction Levels and Remote Access" in Chapter 4 of the Network Reference.
If a local extension or route FRL is not the problem, the coordinating system manager must
I
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.
I
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
In this configuration, the coordinating system manager must check routes and default COR
attributes for Systems B and C.
Check to make sure the calling restriction of the default COR is set to unrestricted. The factory
I
setting is outward restricted, which blocks calls across the private network.
Check that the routes voice/data capability is correct for the type of call being made. The
I
factory setting is Both, which will support both voice and data calls.
In each intervening system, compare the FRLs assigned to routes for the call with the default
I
COR FRL. The route FRL must be equal to or lower than the default COR value or the call is
blocked. The factory setting is 3.
If FRL settings are not the cause, call the Technical Support Organization at 1 800 628-2888;
I
consultation charges may apply.
Calls to Non-Local Extensions:
Unexpected Busy Tone

This topic discusses unexpected busy tones that may be caused by system features. It applies not

only to regular calls from one private network extension to another but also to remote access calls

that are routed among private network systems.
Possible Cause: Intersystem callers may receive a busy tone that is unexpected because they
know that the call recipient has coverage. However, in a private network non-local calls are treated
as outside calls by the system. The non-local extension may not have coverage for outside calls
turned on.
What to Do: Depending upon how the non-local system is set up, try one of the following
techniques in order to reach the extension:
→
System B System C
Central Office and Private Network Problems
→
Destination System D
5
Troubleshooting Guidelines and Preparation
5-19