MERLIN LEGEND Communications System Release 6.1 | Issue 1 |
Network Reference | August 1998 |
6 Troubleshooting |
|
Network Call Transmission Level (Volume) Too Low or Too High | Page |
|
|
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 3ULQW option on the System Programming menu and then choose7UXQN,QIRand*HQHUDO.
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 LEGEND Communications 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
22 | 02 | |
tandem |
| System B |
| ||
| Queens, NY | |
trunk | ||
tandem trunk
03
System C
Atlanta, GA
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
01
System A
NY, NY X
21 | 42 |
|
|
|
| ||
|
|
| System B |
|
|
|
|
|
|
|
|
|
| ||
tandem |
|
| Queens, NY X | tandem |
| ||
trunk | trunk | ||||||
03
System C
Atlanta, GA
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 “Switch Identifiers” on page 19 or “UDP Facilities” in Chapter 4 of System Programming. 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.
If changing one or more switch identifiers do not solve the problem,
