text
stringlengths
0
1.99k
--------------------------
When operators have trouble in handling a call, they can enter trouble
reports that are technically called 'Operator keyed trouble reports'. These
cause messages to be printed on the maintenance TTY and on the trouble report
TTY channel. There are different trouble codes for different things, such as
trouble with the speech scrambler, trouble in the verification network, or
trouble in collecting charges from a customer.
In my area there are 20 such TSPS trouble codes. These are done in MF.
They are entered with the KP TRBL (Key Pulse Trouble) key followed by a two
digit trouble code followed by an ST. A trouble code for beeper trouble could
be entered as KP TRBL+62+ST, and speech scrambler trouble could be KP
TRBL+89+ST. Some of the other reasons for trouble codes are: Crosstalk, No
ring, Noisy, can't hear, improper supervision toward the called and calling
parties, cutoff, positions crossed, coin collecting trouble, third re-order,
distant operator no answer, echo, data transmission, no answer supervision, ST
key lit for more than 4 seconds, and others for person-to-person and
station-to-station completed collect calls.
Maintenance and traffic measurements
------------------------------------
These reports can be output from a maintenance or engineering and service
data TTY, daily or hourly. Each daily report contains data for the previous
day. Some traffic counts are as follows:
Total Verification attempts, VFY key depressions, VFY key depressions when
the requested number is out of TSPS range, VFY key depressions in which the
requested number wasn't verifiable, BLV trunk seizures which pass an
operational test, and EMER INT attempts. Other traffic counts include the
measurements for usage of BLV trunks, the amount of time BLV trunks were
unavailable, and the number of times BLV trunks were seized.
I hope this file has helped people further understand how the BLV system
works. If you haven't read part I, get a copy of Phrack Inc. Issue XI and read
file #10.
As said earlier, most of this information comes directly from Bell System
Publications and so it should be viewed as correct. However, if you do find
any errors then please try to let me know about them so they can be corrected.
Suggested reading
-----------------
TSPS Part I: The console-Written by The Marauder, LOD/H Technical Journal
Issue No. 1, file #4
Busy Line Verification-Phrack Issue XI, file #10
Busy Verification Conference Circuit-Written by 414 Wizard
Verification-TAP issue 88, Written by Fred Steinbeck
Acknowledgements
----------------
Bell System Technical Journal, Vol. 59, No 8.
Bell Labs RECORD periodical
And the following people for contributing information in some form:
Mark Tabas, Doom Prophet, The Marauder
==Phrack Inc.==
Volume Two, Issue 12, Phile #9 of 11
Rebuttal to Phrack Issue 8 and 11 (File 11)
Written by Scan Man.....
It has been requested of Taran King (Who doesn't agree with KL on this subj)
to put this somewhere in the next issue of Phrack (12) for proper
distribution. Whether he does or not I cannot say.
Well a number of months have gone by now and I have been written about
accused of and had rebuttals written for me, all of which were about as clear
and factual as mud. And that includes the rebuttal that Telecomputist has in
effect tried to stand with me, and making matters only worse by inaccurate
information. But then all of this started with inaccurate information from
PWN, didn't it. KL has resorted to interfering in other peoples lives in order
to promote his so called news publication. To this I say, if you are going to
call it news then make it facts. I can buy the Enquirer if I want sensational-
istic readership boosting and inflated gossip. You do no justice to yourself
or your publication. I really shouldn't dignify any of this with comment but
shall as the entire matter has been blown so far out of proportion and since I
have been phreaking since these kiddies were still messing their diapers I
feel it a little more than an inconvenience, particularly since these
gentlemen (and I use the term loosely) can't seem to accomplish anything but
guesswork and conjecture and have cost me (and my wife and son) a $50,000 job
so the least I can do is get a few FACTS out.
First, I was (and I stress was) employed by a company called Telecom
Management Corporation. Notice the initials of this company (TMC). Telecom
Mgnt is a management company, and a management company manages other
companies. Among the companies it manages are 6 TMC Long Distance markets
(none of which are in Vegas), two of which are in Charleston where I live and
NY where I worked (up until two snotty nose teenagers (KL & SR) decided to
stick there nose where didn't belong). At any rate I was hired and paid by
Miami, lived in Charleston, and worked in NY. And yes with regard to your "he
must have been quite an asset to them," I was an asset to them. And KL you