Datasets:
Devilishcode
/
hacking

Dataset card Data Studio Files
xet
 Community
text
stringlengths
0
1.99k
3. Coin Control Failures (COIN CONTR FAILURES): Counts the number of stuck
coin conditions and coin telephones served by the office which had coin
relays that were out of limits.
4. Automatic Identification Outward Dialing Special Billing Number Billing
(AIOD SBN BILLING): Counts the number of times the AIOD equipment fails to
bill a local PBX number correctly.
5. Dial Tone Speed Test (DTST): Counts the number of times the customer has to
wait an excessive amount of time for the system to process the call because
trunks in the desired trunk group are busy or the system is overloaded,
causing queuing for equipment. The count includes 3-second and 11-second
delays.
NOTE:
Maintenance personnel may find it necessary
to suspend the running of the DTST because in
certain trouble conditions DTST may generate
traffic that would interfere with maintenance
activities. Extended or frequent use of this
feature is not recommended. To discourage the
unnecessary use of this function, the PM01 output
message will include a one-line message alerting
maintenance personnel to it's use.
6. CAMA Lost Billing (CAMA LOST BILLING): Counts the number of times a CAMA
call is handled but due to hardware failure, no AMA register is available
which is necessary for billing.
7. CAMA ANI Failures (CAMA ANI FAILURES): Counts the number of calls for which
ANI failure digit is received.
8. Receiver Attachment Delay (RCVR ATT DELAY): Counts the number of times a
receiver connection was not made in 4 seconds.
9. Receiver Attachment Delay Recorder (RADR Inhibit Usage): Counts tR described.
This is rather simple when you think about it and is one example of how a once
shattered network is working together.
Some Sample CP ID Uses
----------------------
This can be used by large telephone ordering companies to instantly display a
record of that persons credit, previous orders, etc... before the call is even
answered on the attendant's terminal.
When someone logs onto a computer, the originating # is listed on the user log
along with the account name, etc... so that if---------
The software EA phases may be initiated by the following sources:
1. A failure by the system to answer an interrupt request
2. An E-to-E cycle becoming excessive
3. An E-to-E priority class frequency failure
4. An excessive rate of interrupts
5. Two successive data validation failures
6. The time spent in a phase becoming excessive
7. Aborting of a phase
The number of EA phases is printed on the PM01 output message.
Interrupts
----------
The number of various maintenance interrupts provides a picture of nonroutine
maintenance action taken by the system. These interrupts are generally not as
serious as a higher order EA phase, but they do interrupt normal call
processing to correct possible hardware problems. A counts of these interrupts
will give a good indication of the state of the systems' equipment. This is
printed on the PM01 output message.
Network Failures
----------------
The network failure counts are provided to give an indication of how well the
network is completing and terminating calls. Each time a network failure
occurs in the system an 'NT' output message is printed. The following are
printed as part of the PM01 message:
1. Supervisory Scan failure (SUPF)
2. False cross and ground test failure (FCGF)
3. Ringing Current Failure (RC)
4. Low-line resistance failure (LLR)
5. Power Cross test (PX)
6. Restore verify failure count (RVFY)
7. Showering line test failure (SHWL)
8. Call Cutoff Failure (CO)
================================
=An Example of the PM01 Message=
================================
PM01
201-232 PLANT MEASUREMENTS SUMMARY
TUES
10/17/86
SERVICE AFFECTING DATA
BASE MEASUREMENTS