Avaya MERLIN MAGIX Maintenance And Troubleshooting Manual page 140

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

Advertisement

the duration of the occurrences, consider changing the routing of the call, pool sizes, or add trunks
to the pool if empty.
To add more routes that can handle the call, see "Uniform Dial Plan Routing" in Chapter 5 of
I
Network Reference.
If more trunks are available and need to be assigned, follow the procedure in "Trunks to Pools
I
Assignment" in 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 the system.
I
If there are sufficient trunks assigned and the problem persists, the cause of the problem may
I
be at an intervening system between the one where the calls are received from the PSTN and
the destination. Go to Possible Cause 2.
If there are sufficient trunks and routes and there are no intervening systems between the one
I
where the calls are received from the PSTN and the destination, contact the provider of the
DID service. If this does not solve the problem, call the Technical Support Organization at 1
800 628-2888; consultation charges may apply.
Possible Cause 2: The FRL for the default COR for all tie (T-1 emulated voice or data, or analog)
or non-tie trunks (PRI) on the remote system may be blocking tandem calls.
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
System B
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.
System C
Destination System D
Central Office and Private Network Problems
Troubleshooting Guidelines and Preparation
5-23

Advertisement

Table of Contents
loading

Table of Contents