
MERLIN LEGEND Communications System Release 6.1 |
| Issue 1 | |
Network Reference |
| August 1998 | |
6 Troubleshooting |
|
| |
| Call to a |
| Page |
|
|
|
|
| Call to a | 6 | |
| Extension: 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. “Call to
As a first step, the caller should try using Callback. All available local routes for the call may be busy, and Automatic or Selective Callback allows the call to queue for the next available tandem trunk assigned to the Route 1 pool.
If a user is having trouble with the Callback feature, see “Callback Does Not Work” on page 20.
If the wait time for an available local trunk is unacceptable, you may be able to change the local extension or barrier code FRL and/or route FRLs for the UDP pattern in order to make more routes available for the call.
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” on page 9 discusses FRL planning in detail.
■To change a UDP route FRL, see “Uniform Dial Plan Routing” on page 25 or “UDP Routing” in Chapter 4 of System Programming.
■To change the extension FRL, see System Programming, Chapter 3, “Common Administrative Procedures.”
■To change the FRL assigned to a remote access barrier code, see “Remote Access” in System Programming, Chapter 4. Follow the guidelines in “Remote Access Default
!SECURITYlALERT:
FRLs, applied to ARS and UDP routes, default
Changing local FRLs may not work simply because the problem is not on the local system. In this case, see “Call to