Nortel Communication Server 1000 Manual page 53

Prompt Response
LBTY X
LBTN XXXX
MPH loopback tests
If a particular packet call setup is not working, check the communication
links using the corresponding interface loopback test:
•
•
•
These tests are described in the following section.
MPH and PSDN through MCU continuity test
Figure 8 "MPH-to-PSDN continuity test using MCU" (page 54)
this test, which provides loopback testing between the MPH and PSDN
through the MCU. The continuity check originates from the MPH through
the Superloop network card, the Controller card, the line card, and then
responds back at the MCU level. If the MCU was set up originally to operate
in transparent mode (64 Kbps or 56 Kbps to the PSDN interface), the
connection between the MPH and the MCU must be brought down and then
reestablished. To perform this test, the dedicated connection between the
MCU and the MPH must be in a manually disabled state.
MPH and PSDN through PRI continuity test
Figure 9 "MPH-to-PSDN continuity test using MCU" (page 55)
illustrates this test, which provides loopback testing between the MPH and
PSDN using a PRI connection. To perform this loopback test, the dedicated
connection between the PRI and the MPH must be in a manually disabled
state.
Copyright © 2003-2007, Nortel Networks
.
Description
X = 8 is the PSDN – MCU loopback
X= 9 is the MCU loopback
X = 10 is the PDL2 loopback
X = 11 is the BCH loopback
X = 12 is the BRSC loopback.
If LBTY = 8, LBTN is the MISP loop and NWIF is 1-3
If LBTY = 9 LBTN is MCU TN
If LBTY = 10 LBTN is either BRIL loop or BRSC TN
If LBTY = 11 LBTN is the BCH TN
For PSDN packet calls from a network interface, use the MPH and
MCU-to-PSDN or the MPH and PRI-to-PSDN continuity test
For B-channel packet data call setups, use the MPH-to-B-channel
continuity test.
For D-channel packet data call setups, use the MPH-to-MISP or
MPH-to-BRSC loopback test.
Nortel Communication Server 1000
ISDN Basic Rate Interface Maintenance
NN43001-718 01.01 Standard
Release 5.0 30 May 2007
MPH fault isolation and correction 53
Nortel Networks Confidential
illustrates
also