The default for the verbose option is inhibited. An SM/SM-2000 which is in the verbose mode will report all PCTF
occurrences to the RSB by sending the normal REPT PCTF message. However, an SM/SM-2000 which is not in the
verbose mode will only report the first and tenth occurrence of a PCTF type on a line to the RSB. The first
occurrence generates a REPT PCTF FIRST message and the tenth occurrence generates a REPT PCTF TENTH
message.
The Touch-Tone Fraud (TTF) PCTF is handled in a slightly different manner than the rest of the PCTF types. First of
all, the individual REPT PCTF TTF messages are also sent to the SCC at all times; the mode of the SM/SM-2000
has no affect on the reporting of the TTF PCTFs to the SCC. Secondly, the TTF PCTFs will not be reported to the
RSB at all if the system is not in the verbose mode.
To resolve problems specified in the PCTF summary report, follow procedures specified in 235-105-220 for clearing
line problems.
3.5.7 STUCK COIN FAILURES (SCF)
Stuck Coin Failures are reported at routine intervals. At each routine interval, the entire list of coin phones which
have experienced stuck coin failures during the previous interval are printed (using the REPT SCF output message).
The list of stuck coin failures that have occurred during the current interval can also be requested manually (using
the OP SCF input message).
The SCF reporting is administered using RC/V to update the COIN INT global office parameter (see RC/V view 8.1).
The allowed values for COIN INT are 15, 30, 45, and 60, corresponding to the number of minutes between interval
reports of the stuck coin list.
The SCF report indicates the number of stuck coin failures on an individual coin line. When a stuck coin is detected,
a second attempt to clear the coin is made. If the coin clears on the second attempt, the failure is recorded as a
single attempt failure (1F). If both attempts fail, the failure is recorded as a dual attempt failure (1+2F). A count is
maintained of the number of failure attempts (if both 1F and 1+2F failures occur, then only the number of 1+2F
failures are retained).
To resolve problems specified in the SCF report, follow procedures specified in 235-105-220 for clearing coin line
problems.
3.5.8 AUTOMATIC MISMATCH DETECTION
This section describes the NT1 mismatch test that was introduced with a previous software release. This test
performs Integrated Services Line Unit (ISLU) Network Termination (NT1), or first Basic Rate Interface
Transmission Extension (BRITE) Channel Unit (CU), mismatch detection for U-interface Digital Subscriber Lines
(U-DSLs). This test is needed because with the introduction of the previous software release, two types of U-DSL
technologies exist. The NT1/CU mismatch detection will detect if the wrong type of NT1 or CU is connected to the
ISLU U-card.
The two types of ISLU U-DSL technologies are commonly referred to as:
Alternate Mark Inversion (AMI) - this is the U-DSL service provided by the KCB10 U-card.
ANSI
®
2B1Q Standard U-DSL - this is the U-DSL service that is provided by the KCB17 ISLU U-card.
A mismatch exists if either one or both of the following conditions exist.
The line card installed in the line card slot does not match the type of service assigned to the customer at line
card provisioning time. An example is if the customer subscribes to AMI U-DSL services, but an
ANSI
U-card is
installed in the line card slot. This is a line card mismatch.
235-105-210
October 1999
Copyright © 1999
Page 13
Summary of Contents for 5ESS-2000
Page 96: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 184: ...235 105 210 October 1999 Copyright 1999 Page 3 ...
Page 300: ...13 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 55 ...
Page 339: ...7 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 342: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 359: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 609: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 12 ...
Page 676: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 792: ...3 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 799: ...Figure 11 36 3 1 Cleaning Points 235 105 210 October 1999 Copyright 1999 Page 7 ...
Page 801: ...235 105 210 October 1999 Copyright 1999 Page 9 ...
Page 839: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 16 ...
Page 999: ...2 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 13 ...
Page 1008: ...Figure 11 55 1 CTSNS DIP Switch Settings 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1011: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1053: ...235 105 210 October 1999 Copyright 1999 Page 15 ...
Page 1289: ...Figure 15 17 2 AMATPS Data Link 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1292: ...235 105 210 October 1999 Copyright 1999 Page 5 ...
Page 1303: ...9 STOP YOU HAVE COMPLETED THIS PROCEDURE 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1360: ...Figure 15 47 2 Typical SCANS III Link Diagram 235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1372: ...235 105 210 October 1999 Copyright 1999 Page 2 ...
Page 1374: ...235 105 210 October 1999 Copyright 1999 Page 4 ...
Page 1421: ...Table 1 1 O M Checklist 235 105 210 October 1999 Copyright 1999 Page 3 ...