Lucent Technologies MERLIN LEGEND Release 6.1 Maintenance And Troubleshooting Manual page 293

MERLIN LEGEND Communications System Release 6.1
Maintenance and Troubleshooting 555-661-140
Private Network Calling Problems
occurred, check the CSU/DSU associated with the line for correct
programming. If the loss at signal alarm has occurred, check for open
cables, etc. If these conditions are not present, go to Possible Cause 3.
Possible Cause 2: Callback Queuing is not used.
What to Do: 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. As a first step, the caller should try using
Callback.
If a user is having trouble with the Callback feature, see "Callback Does Not
Work" in Chapter 6 of Network Reference .
Possible Cause 3: Not enough trunks are assigned to the pools for UDP
routes.
What to Do: Consult System Form 2c, System Numbering: Line/Trunk Jacks to
determine the assignments. To see a report of pool assignments, select the
option on the System Programming menu and then choose
and .
If more trunks are available and need to be assigned, follow the
procedure in "Trunks to Pools Assignment" in Chapter 3 of System
Programming to assign more tandem trunks. All the tandem trunks in a
pool must be of the same type (tie or PRI).
If not enough trunks are available, consider adding more to your system.
If there are sufficient trunks assigned but the problem persists, go to
Possible Cause 4.
Possible Cause 4: Facilities are available but restricted and the caller is not
able to access them.
What to Do: Verify that the extension's FRL is higher than or equal to the UDP
route FRL.
Issue 1
August 1998
Page 5-47