Calls To Non-Local Extensions Unexpected Busy Tone - Lucent Technologies MERLIN LEGEND Release 6.1 Maintenance And Troubleshooting Manual

MERLIN LEGEND Communications System Release 6.1
Maintenance and Troubleshooting 555-661-140
Calls to Non-Local Extensions: Unexpected Busy Tone
Check to make sure the calling restriction of the default COR is
set to unrestricted. The factory 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 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 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 Lucent Technologies
Helpline at 1 800 628-2888; 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:
If the destination extension can be dialed directly via Direct
Inward Dialing (DID) or PRI dial-plan routing, try calling the
destination extension over public switched telephone network
tandem trunks. If you receive the same busy tone, then the
Coverage setting may be the problem. Call the system manager
Issue 1
August 1998
Page 5-58