If A User Is Having Trouble With The Callback Feature, See; 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; I "How Facility Restrictions Levels Work In A Network" In Chapter 4 Of Network Reference Discusses Frl Planning In Detail; I To Change The Frl Assigned To A Remote Access Barrier Code, See "Remote Access" In - Avaya MERLIN MAGIX Maintenance And Troubleshooting Manual

Integrated system release 2.0 and earlier
Hide thumbs Also See for MERLIN MAGIX:
Table of Contents

Advertisement

Maintenance and Troubleshooting
If the routing is correct and enough routes are included in the pattern, but the problem persists,
I
check if PRI lines are used. If they are, check the error log for D-channel inoperative and loss
of signal alarms indicating lines are inoperative. If the D-channel inoperative alarm has
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

[programmers: make link]
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 Print option on the System
Programming menu and then choose Trunk Info and General .
If more trunks are available and need to be assigned, follow the procedure in the System
I
Programing section of the Pools feature in the Feature Reference 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.
I
If there are sufficient trunks assigned but the problem persists, go to Possible Cause 4.
I
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.
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" in Chapter 4 of Network Reference
I
discusses FRL planning in detail.
To change a UDP route FRL, see "Uniform Dial Plan Routing" in Chapter 5 of Network
I
Reference.
To change the extension FRL, see System Programming, Chapter 3, "Programming
I
Procedures."
To change the FRL assigned to a remote access barrier code, see "Remote Access" in
I
Feature Reference. Follow the guidelines in "Remote Access Default Class-of-Restriction

Settings" in Chapter 4 of Network Reference.

Troubleshooting Guidelines and Preparation
5-14
''Callback Does Not Work''
on page 5-24.

Advertisement

Table of Contents
loading

Table of Contents