Maintenance-Object Repair Procedures
555-233-143
8-516
Issue 1 May 2002
DID Trunk Testing
The system uses four tests of on-board circuitry to diagnose the health of the
trunk. These are described in the following sections. Additionally, in-line testing
which can generate errors, is performed while a call is in progress. See the Error
Log table for a description of these errors. These errors may be reproduced by
placing a call on the trunk and checking the Hardware Error Log.
Problems detected during signaling may be caused by off-board faults in the CO
switch or connections for which a Warning alarm is raised.
Before a maintenance test can be run on a port, the port must be idle. If an
incoming call seizes a port that is being tested, the test will abort and the incoming
call will proceed.
For transmission and signaling standard specification, refer to Digital PBX
Standards, RS4648.
Ports Out-of-Service without Errors or Alarms
A common trouble on DID trunks that produces no errors or alarms occurs when
the CO busies out (disconnects) the port. This situation occurs when the CO
thinks there are problems with the DID port. In this case, no incoming calls will be
possible through this port. This may result in complaints from outside callers
trying unsuccessfully to call in. This problem can be diagnosed by listing
measurements on lightly used trunks. If a particular port is detected as idle, a call
to the CO will be necessary to get the connection back in service.
Error Log Entries and Test to Clear Values
Table 8-208.
DID Trunk Error Log Entries
Error
Type
Aux
Data
Associated Test
Alarm
Level
On/Off
Board
Test to Clear Value
0
1
0
Any
Any
Any
test port UUCSSpp sh r 1
1 (a)
Any
None
WARNING
OFF
1 (b)
57476
None
WARNING
OFF
1 (c)
57477
None
WARNING
OFF
1 (d)
57483
None
WARNING
OFF
15 (e)
Any
Port Audit Update
(#36)
18
0
busyout trunk
grp/mbr
WARNING
OFF
release trunk grp/mbr
130 (f)
None
WARNING
ON
test trunk grp/mbr
Continued on next page
Summary of Contents for S8700 Series
Page 50: ...Maintenance Architecture 555 233 143 1 26 Issue 1 May 2002 ...
Page 74: ...Initialization and Recovery 555 233 143 3 12 Issue 1 May 2002 ...
Page 186: ...Alarms Errors and Troubleshooting 555 233 143 4 112 Issue 1 May 2002 ...
Page 232: ...Additional Maintenance Procedures 555 233 143 5 46 Issue 1 May 2002 ...
Page 635: ...status psa Issue 1 May 2002 7 379 555 233 143 status psa See status tti on page 7 406 ...
Page 722: ...Maintenance Commands 555 233 143 7 466 Issue 1 May 2002 ...