
TIE-DS1 (DS1 Tie Trunk)
Issue 4 May 2002
10-1745
555-233-123
Conference Circuit Test (#7)
One or more NPEs reside on each circuit pack with a TDM Bus interface. The
NPE controls port connectivity and gain, and provides conferencing functions on a
per-port basis. The Conference Circuit Test verifies that the NPE channel for the
port being tested can correctly perform the conferencing function. The NPE is
instructed to listen to several different tones and conference the tones together.
The resulting signal is then measured by a Tone Detector port. If the level of the
tone is within a certain range, the test passes.
Table 10-643.
TEST #7 Conference Circuit Test
Error
Code
Test
Result
Description/Recommendation
ABORT
System resources required for this test are not available.
1. Retry the command at 1-minute intervals a maximum of 5
times.
1000
ABORT
System resources required to run this test were not available.
The port may be busy with a valid call. Use display port
UUCSSpp to determine the trunk group/member number of
the port. Use status trunk to determine the service state of
the port. If the service state indicates that the port is in use,
then the port is unavailable for certain tests. You must wait
until the port is idle before retesting.
1. If the port status is active but the port is not in use (no
calls), check the error log for error type 1025 (see the error
log table for a description of this error and required
actions). The port may be locked up.
2. If the port status is idle, retry the command at 1-minute
intervals for a maximum of 5 times.
1002
ABORT
The system could not allocate time slots for the test. The
system may be under heavy traffic conditions, or it may have
time slots out of service due to TDM-BUS errors. The status
health command can be used to determine if the system is
experiencing heavy traffic. Refer to the TDM-BUS (TDM bus)
Maintenance Documentation to diagnose any active
TDM-BUS errors.
1. If the system has no TDM-BUS errors and is not handling
heavy traffic and the port status is idle, retry the command
at 1-minute intervals for a maximum of 5 times.
Continued on next page
Содержание Definity SI
Страница 1: ...0DLQWHQDQFH IRU YD D 1 7 6HUYHU 6 Volumes 1 2 and 3 555 233 123 Issue 4 May 2002...
Страница 62: ...Maintenance Architecture 555 233 123 1 26 Issue 4 May 2002...
Страница 92: ...Management Terminals 555 233 123 3 26 Issue 4 May 2002...
Страница 204: ...Routine Maintenance Procedures 555 233 123 5 100 Issue 4 May 2002...
Страница 250: ...LED Interpretation 555 233 123 7 10 Issue 4 May 2002...
Страница 2763: ...VC DSPPT Issue 4 May 2002 10 1977 555 233 123 Figure 10 107 VC Circuit Pack DSP Port Local TDM Loopback Test...
Страница 2776: ...Maintenance Object Repair Procedures 555 233 123 10 1990 Issue 4 May 2002 Figure 10 109 VC Circuit Pack Summer Port Loopback Test...
Страница 2804: ...Maintenance Object Repair Procedures 555 233 123 10 2018 Issue 4 May 2002...
Страница 2968: ...Index 555 233 123 IN 10 Issue 4 May 2002...