Avaya MERLIN MAGIX Maintenance And Troubleshooting Manual page 134

If you want more information about the Switch Type setting, consult the system Non-Local UDP
Administration Form in the Installation Specification. To see a report including the switch type
programmed for PRI facilities on your system, select the Print option on the System
Programming menu, and then choose PRI Info . See "PRI Facilities Switch Type" in Chapter 5 of
the Network Reference for instructions on changing the switch type programmed at your system.
If the switch type settings are correct and problem persists, do one of the following:
If the call is a data call, go to Possible Cause 8.
I
If the call is not a data call, call the Technical Support Organization
I
at 1 800 628-2888; consultation charges may apply.
Possible Cause 8: The FRL for the default COR for tie trunks (T1-emulated voice or data, or
analog) on the remote system may be blocking tandem calls. The private network includes at least
one analog tie trunk.
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 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, go to Possible Cause 9.
Possible Cause 9: If the call is a 64-kbps data call, all routing facilities may not support this data
speed.
What to Do: Unless you are directly connected to the destination system, the coordinating system
manager must check the routes for the call. To check the local routes, see Reviewing the
Non-Local Dial Plan and Routing. To change the routing in order to specify facilities that can
handle the call, see "Uniform Dial Plan Routing" in Chapter 5 of Network Reference.
If the call is routed over any analog facilities (tie or loop-start, for example), T1-emulated voice or
data facilities, it cannot go through. If the call is routed over PRI and/or BRI facilities, a speed of 64
kbps may be possible. If this is not the cause of the problem, call the Technical Support
Organization at 1 800 628-2888; consultation charges may apply.
→ →
System C Destination System D
Central Office and Private Network Problems
Troubleshooting Guidelines and Preparation
5-17