Avaya MERLIN MAGIX Maintenance And Troubleshooting Manual page 142

DEFINITY ECS and DEFINITY ProLogix Solutions systems are beyond the scope of this
guide. For information about how these systems identify tandem facilities, see the
documentation for the applicable system.
Follow the steps below to check on the problem.
1. Check the routing for the call, and identify each system where the call is routed, including the
system where the call originated or was received from the public switched telephone network.
See Reviewing the Non-Local Dial Plan and Routing.
2. As necessary, note the switch identifier programmed on each system for the trunks that carry
the calls. To review a report including the switch identifiers programmed on a system, select
the Print option on the System Programming menu and then choose Trunk Info and
General .
3. Look for switch identifiers that incorrectly specify the distance between systems or that specify
the incorrect type of system. The diagram below shows how switch identifiers might be
programmed at either end of tandem trunks in a hypothetical private network. A switch
identifier is programmed to identify the system at the opposite end of the tandem trunk. In the
example, all three switches are MERLIN MAGIX systems. On the facility that links Systems A
and B, the system managers program identifiers to indicate that they are within 200 miles of
one another. Next to the name of each system, is the switch identifier associated with that
switch. The switch is programmed on the switches on the other end of the tandem trunk.
Systems B and C are linked by trunks whose identifiers indicate distant systems.
21
System A
NY, NY
The example below shows programming that would be incorrect in the same private network.
The link between Systems A and B has mismatched identifiers, because System B specifies
that System A is more than 200 miles away. System C incorrectly specifies System B as a
non-MERLIN MAGIX system.
01
System A
X
NY, NY
4. If any of the programming is incorrect, one or more system managers must correct it. The
coordinating system manager must clear any changes. To change the switch identifiers at your
local system, see the UDP feature in the Feature Reference. If the programming appears to be
correct, skip to Step 6.
5. Make some test calls across the private network. If calls are at the proper levels, the problem
is solved. If transmission levels are still incorrect, proceed to Step 6.
6. If the identifiers appear correct but the distance between systems is between 180 and 220
miles, you may need to experiment with switch identifiers in order to achieve the correct
transmission levels. Return to Step 4.
22
System B
tandem
Queens, NY
trunk
21
System B
tandem
Queens, NY
trunk
Central Office and Private Network Problems
03
02
System C
tandem
Atlanta, GA
trunk
42 03
System C
tandem
X
Atlanta, GA
trunk
Troubleshooting Guidelines and Preparation
5-25