The Hacker's Encyclopedia 1998

home *** CD-ROM | disk | FTP | other *** search

/ The Hacker's Encyclopedia 1998 / hackers_encyclopedia.iso / zines / phrack2 / phrack40.007 < prev next >

Wrap

Text File | 2003-06-11 | 66.2 KB | 1,380 lines

==Phrack Inc.== Volume Four, Issue Forty, File 7 of 14 =/=/=/=/=/=/=/=^=\=\=\=\=\=\=\= = = = The Fine Art of Telephony = = = = by Crimson Flash = = = =\=\=\=\=\=\=\=!=/=/=/=/=/=/=/= Bell! Bell! Bell! Your reign of tyranny is threatened, your secrets will be exposed. The hackers have come to stake their claim and punch holes in your monopolistic control. The 1990s began with an attack on us, but will end with our victory of exposing the secret government and corruption that lies behind your walls and screens. Oppose us with all your might, with all your lies, with all your accountants and bogus security "professionals." You can stop the one, but you'll never stop the many. A. Introduction B. Basic Switching C. RCMAC 1. Office Equipment 2. How Does All This Fit Into RCMAC 3. Function of RCMAC a. Coordination of Recent Change Source Documentation b. Processing of Recent Change Requests c. Administrative Responsibilities and Interface Groups D. The FACS Environment E. Getting Ready For Recent Change Message 1. When MARCH Receives A Translation Packet (TP) 2. When MARCH Receives A Service Order Image F. MARCH Background Processing G. User Transaction in MARCH H. Service Order Forms I. COSMOS Service Order From The SOI Command J. MSR - MARCH Status Report (MARCH) K. Other Notes L. Recommended Reading - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - A. Introduction ~~~~~~~~~~~~~~~ Bell. Bell Bell Bell! What is it about Bell? I am not sure what my fascination is with them, but it never ceases nor does it ever diminish. Maybe its because they are so private. Maybe its because they find it possible to rip millions of people off daily and they do it with such great ease. Or perhaps its just that they do not want anyone to know what they are doing. Around my area down here in Texas (512), the Central Office buildings have large brick walls, cameras at each door, bright lights, and every piece of paper says in big block letters: "PROPRIETARY INFORMATION -- NOT FOR USE OR DISCLOSURE OUTSIDE OF SOUTHWESTERN BELL." This message can be found on everything, but their phone books! Why? This files are about RCMAC and FACS/MARCH. The information presented here is largely from memory. If you think the information is wrong, then get the information yourself! One thing to keep in mind is that nothing is in stone! Different BOCs (Bell Operating Companies) use different systems and have different ways of doing the same thing. Like in some areas RCMAC is the CIC, the MLAC may not exist, so on and so forth. So nothing is ever fully true with Bell, but then why should things like their systems differ from their policies and promises. There is a Bellcore standard and then there is the real way it is done by your local BOC. B. Basic Switching ~~~~~~~~~~~~~~~~~~ A switching system (a switch) allows connect between two (or more) phone lines, or two trunks. A basic T1 trunk is 24 lines on a 22 gauge, 4-wire twisted pair. Not only does it allow connect, it also controls connection, where you call, and when someone calls you. In short it controls everything about your phone! From a large AT&T 5ESS switching 150,000+ line to a small 24 line PABX (Private Automatic Branch Exchange, a switch), they control your phone service. What's the big deal about telephone switches? Telephony is the largest form of communications for just about everyone in the world! Just try life without a phone line to your house. I have four phone lines and sometimes that is still not enough. Today's switches are digital. This means that when you talk on the phone, your voice is converted to 1s and 0s (on or off, true or false). This works in several steps: [0] You call someone. [1] Sampling -- The analog signal (your voice) is sampled at certain parts. The output is called Pulse Amplitude Modulation (PAM) signal. [2] Quantize -- The PAM signal is now measured for wave length high (or amplitude) where numbers are given to the signal. [3] Encoding -- In this step, the Quantized signal (with the numbers for the height of the wavelength (amplitude)) is converted to an 8-bit binary number. The output of the 8-bit "word" may be either a "1" (a pulse) or a "0" (no pulse). [4] Encoding -- Produces a signal called a Pulse-Code Modulation (PCM) signal. PCM just means that the signal is modulating pulses (digital). From this point, the signal is switched to where it needs to go. [5] The PCM signal is where it needs to go. The signal is now converted back to analog. [6] Decoding -- The 8-bit PCM signal is sent to the decoder to get the number that measured the amplitude of the wave. [7] Filtering -- This takes the PAM signal (the decoding produced) and it reproduces the analog signal just as it was. ___ [1] [2] [3] [4] | S | [5] [6] [7] ________ _________ ______ | w | ________ ______ | | | | | | __ | i | __ | | | | \/\/|Sampling|-|Quantize|-|Encode|__| |__| t |__| |__|Decoding|-|Filter|/\/ |________| |________| |______| | c | |________| |______| | | | |_h_| | | PAM PCM PCM | Analog Signal (You Talking) / \ Analog Signal__| / \ / \ / \ / \ Blow Up / of the Switch \ / \ / \ ___________________________ _____ | | _____ 1 T | | T 1 | | 1 T | | 1 -------| T |------| |------| T |----- |_____| | | |_____| _____ | | _____ 2 T | | T 2 | S | 2 T | | 2 -------| T |------| mxn |------| T |----- |_____| o | | o |_____| _____ o | | o _____ m T | | T m | | n T | | n -------| T |------| |------| T |----- |_____| | | |_____| |___________________________| The basic design of most of the switches today is a Time-Space-Time (TST) topology. In the Time-Space-Time in the arrangement shown, time slot interchangers will interchange information between external channels and internal (space array) channels. This is just a quick run through to gives you a general idea about switches without going into math and more technical ideas. For a better understanding, get "Fundamentals of Digital Switching" by John C. McDonald. This book is well written and describes ideas that I cannot get into. C. RCMAC ~~~~~~~~ The Recent Change Memory Administration Center's (RCMAC) purpose is to make changes to the software in various Electronic Switching Systems (ESS). An ESS uses a Stored Program Control (SPC) to provide telephone service. Since people with phones and their services change often, the ESS uses a memory called Recent Change. This Recent Change area of memory is used on a standby basis until the information can be updated into the semipermanent memory area of the ESS. It is in the templar area that changes (or Recent Change Messages) are typed and held for updating into the semipermanent memory area (Recent Change Memory). The following Switching Systems (switches for short) that have Recent Change: - 1/1AESS - 2/2BESS - 3ESS - 5ESS - Remote Switching System (RSS) - #5ETS - DMS100/200/250/300 Here is a typical hookup. As you follow the diagram below, you will see: [1] Telephone subscriber connected to the Central Office by cables. [2] At the Central Office, each subscriber is connected to the Main Distributing Frame. [3] The Cable and Pair is now connected to the Office Equipment (OE) at another location on the MDF. _______________ (Home Phone Lines) M.D.F. | | |--(Home Phone) ___________ | | |--(Home Phone) /__/| /__ /| | D.S.S. | |--(Home Phone) |\ ||__|/ | |-----| | | | _|_/_|__| |-----| Equipment | | | /|/ \| | |-----| | | | /||__| \| |-----| | |_________________|/_|/ |__|/ |_______________| / | Cables Cross-Connects [1] [2] [3] 1. Office Equipment ~~~~~~~~~~~~~~~~~~~ The Office Equipment (OE) is identified by a unique numbering plan. The equipment numbers identify the equipment location within the system. The Equipment Numbers also vary from one type of equipment to another. You also may find the OE (Office Equipment) referred to as the LEN (Line Equipment Number). It is called a REN (Remote Equipment Number) in a case of RSS (Remote Switching System). Each telephone number is assigned to a specific equipment location where they bid for dial tone. Here is an example of different types of Office Equipment: 1/1AESS #2ESS ~~~~~~~ ~~~~~ OE 0 0 4 - 1 0 1 - 3 1 2 OE 0 1 1 - 2 1 4 0 | |/ | | | | |/ | |/ | | |/ | | | | | | | | | | | | | | | | | | Level | | | | Switch and Level | | | | | Switch | | | Concentrator | | | | Concentrator | | Concentrator Group | | | Bay | Link Trunk Network | | Line Switch Frame Control Group | Line Link Control Group #3ESS Others ~~~~~ ~~~~~~ OE 0 0 1 - 2 1 4 0 1XB = XXXX-XXX-XX | |/ | | | | 1XB = XXXX-XXXX-XX | | | | | Level 5XB = XXX-XX-XX | | | | Switch SXS = XXXX-XXX | | | Switch Group DMS-10 = XXX-X-XX-X | | Concentrator 5ESS = XXXX-XXX-XX | Concentrator Group 5ESS = XXXX-XX-XX Control Group RSS = XXXX-X-XXXX DMS-1/200 = XXX-X-XX-XX 2. How Does All This Fit Into RCMAC? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ RCMAC (Recent Change Memory Administration Center) is responsible for updating any Service Order activity. This action will change a customer line or service in the Recent Change memory of the SPC switches. 3. Function of RCMAC ~~~~~~~~~~~~~~~~~~~~ The three basic functions performed in RCMAC are: a. Coordination of Recent Change Source Documentation b. Processing of Recent Change Requests c. Administrative Responsibilities and Interface Groups In more detail: - Coordination of Recent Change Source Documentation The first function is the coordination of Source Documents. The main source of RC (Recent Change) is the Service Orders. Service Orders are changes in a subscriber's service. RCMAC, in addition to the input of the service order in the switches, is responsible for other activities such as: - Simulated Facilities (SFG) - Route Indexes - Traffic Registers (TR) - Subscriber Line Usages (SLU) - Service Observing Assignment (SOB) - MARCH (MIZAR) RPM Updates Terminal Communications to the switches and/or MARCH (MIZAR) typically use the AT&T Datakit. RCMAC also is responsible for "HOT" requests from the I.C. (Installation Center) and other transmissions from the I.C. - Processing of Recent Change Requests The second function of RCMAC is processing of RC messages. This involves inputting and editing RC messages in the switches. When RCMAC inputs messages, they are making a change to their customer's service. The customers service is dependent on the prompt, accurate processing of RC source documents (Service Orders). The due date (sometimes referred to as the Frame Due Date) remarks and time interval assigned to the order will govern the release of RC input to ESS. Due date is important because this is the date that the Service Order has to be completed (going through the FACS system, frame work done, and RC message inputted into the switch). Recent Change Requests The RCMAC receives documentation for changes to the temporary memory areas of the various types of ESS equipment. These changes may come in many forms and from many different sources. _________ _____ | | | | Service Orders---------------->| R |--------->| ESS | _____ Line Station Transfer--------->| C | |_____| | | Service Observing------------->| M |---------------------->| ESS | Special Studies--------------->| A | ______ |_____| Trouble Reports--------------->| C | | | Verifications----------------->| |--------->| ESS | |_________| |_____| Some Recent Changes requests are Service Orders, Line Equipment Transfers (LET), Service Observing Requests (SOB), Special Studies (SLU), Trouble Reports and Verification (follow local procedure). In short, it is taking this information and making the correct changes into the SPC switches. - Administrative Responsibilities and Interface Groups - Control of errors. - Monitor activity. - Prepare administrative reports. - Coordination of RCMAC operations and interface with other departments. - Restore RC area of the switches in the event that RC memory is damaged due to machine failure. Operational Interface RCMAC must coordinate activities with many work groups to achieve accurate and quick RC for the ESSes. BSC/RSC & MKTG | | SCC | RSB \ | / \ | / \ | / NAC ---------- RCMAC ---------- IC / \ / \ / \ Frame MLAC To help understand this better, here is a short description of each group that interfaces with RCMAC: SCC (Switching Control Center) - Technical assistance to RCMAC - Provide emergency coverage (off hours) for RCMAC. This includes service affecting problems. They also coordinate any updates in the ESS programs with RCMAC. NAC (Network Administration Center) provides RCMAC with: - Line Class Codes (LCC) like 1FR (1-party Flat Rate). - List of numbers that must be changed (in ESS memory) from one intercept route index to another, prior to reassignment. - Translation Assignments; Example: Simulated Facilities Group (SFG). - Area Transfer/Dial for Dial Assignment. - Service Observing assignment. - Subscriber Line Usages (SLU) study assignment. - Customer Line Overflow study assignment. - RPM updates for DMS 100 change in COSMOS tables USOC/NXX/Ltg. Frame (Frame Jeopardy Reports) Central Office (FCC) will interface with RCMAC for Line Equipment transfers. - Problems encountered by the frame group when completing Service Orders may be coordinated with the MLAC (Loop Assignment Center), or when appropriate will be called directly to RCMAC (i.e. No Dial Tone on a new connect). Business/Residence Service Center (BSC/RSC) and Marketing (MKTG) - The BSC/RSC and MKTG determine what kind of service the customer wants, generates Service Orders, and coordinates with RCMAC regarding special services to customers. Repair Service Bureau (RSB) or Single Point of Contact (SPOC) - Customer trouble reports may involve RC inputs; the RCMAC would work closely with RSB or SPOC to clear such troubles. - RCMAC is responsible for analyzing, investigating and resolving customer trouble caused by RC input. Installation Center (IC) and/or Maintenance Center (MC) - The IC/MC group is responsible for the administration function associated with the completion and control of Service Order load. This invokes all orders whether they require field work or no field work. - This Group is responsible for ensuring all service orders are taken care of on the proper due date. Mechanized Loop Assignment Center (MLAC) or LAC - Assigns Service Orders for RCMAC. - Assigns customers loops (this group is not in all BOCs). D. The FACS Environment ~~~~~~~~~~~~~~~~~~~~~~~ To better understand RCMAC, Source Document flow, and a typical BOC as a whole, the FACS (Facility Administration Control System) is an important part of this. Systems in a FACS environment PREMIS - PREMises Information System This system is divided into three parts: the main PREMIS database, PREMLAC (Loop Assignment) and PREMLAS (Loop Assignment Special circuit). This contains customer and address inventory and assigns numbers. SOAC - Service Order Analysis and Control This system receives Service Orders from SORD and interprets and determines facility requirements. The system requests and receives assignments from LFACS and COSMOS and forwards orders to MARCH, forwards assignments to SORD, and also maintains Service Order history and manages changes. LFACS - Loop FACS contains all loop facilities inventory and responds to requests for assignment. COSMOS - COmputer System for Mainframe OperationS contains all the OE inventory and responds for OE request. SORD - Service ORder and Distribution distributes Service Orders throughout the system. MARCH - MARCH is the Mizar upgrade which will come into play when the Stromberg-Carlson (SxS and XBAR) is upgraded to Generic 17.1 (the software interface is called NAC). Though there is a problem with the interface between MARCH and COSMOS (because the Generic Interface is not supported by COSMOS), templates are used for MAN, AGE, LETS, etc. Anyway, MARCH plays a big part in this system. MARCH, aside from what was talked about above, has a basic function of keeping RCMAC up to date on the switches (MSR user transaction). It is an RC message manager which will allow one to modify messages (ORE), show usages (MAR) and logs all transmissions. BASIC ORDER FLOW ~~~~~~~~~~~~~~~~ PHASE I - COSMOS/MIZAR __________ | | | Customer | | Request | |__________| | V _________ | | | SORD | |_________| | V _________ __________ | | | | | Work | | SOAC | ----------> | Manager | |__________| | (WM) | |_________| | | V * * * * * * _________ * * | | * COSMOS * -------> | MIZAR | * * |_________| * * * * * * | | V _________ | | | SPCS/ | | DIGITAL | | SWITCH | |_________| =============================================================================== PHASE II - SOAC/MARCH __________ | | | CUSTOMER | | REQUEST | |__________| | | V __________ | | | SORD | |__________| | | V ___________ _________ __________ | | _________ | | | | | WORK | | | | SPCS/ | | SOAC | ------> | MANAGER | ------> | MARCH | ---> | DIGITAL | |__________| | (WM) | |_________| | SWITCH | |___________| |_________| =============================================================================== .. Then There Was MLAC With conversion to FACS, a shift in the service order provisioning process was made from manual input by the LAC and NAC to mechanized data flow from SOAC to COSMOS (via Work Manager). Tables used for Recent Change (CFINIT, USL, and CXM) and spare OE assignments reside in COSMOS, along with the Recent Change Message Generator (RCMG). The LAC and NAC are now involved only on an exception basis (This will be explained in more detail later on). ________ | | | SORD | |________| | | V ____________ _________ | | | | ---------> | FACS |--- | SOAC | | COMPONENTS | | |_________| <--------- | FOR ASGNS. |--- | |____________| | V * * * * * * * * * * * * * * * * * * _________ * ___________ * | | * | | ________ * _______ | WM |---> * | o SP OE | | | * RC | | |_________| * | o CFINIT |----> | RCMG | * ----->| MARCH | * | o USL | |________| * MSG |_______| * | o CMX | * | * |___________| * | * * V * C O S M O S * _________ * * * * * * * * * * * * * * * * * * | | | SPCS/ | | DIGITAL | | SWITCH | |_________| . . . NOW THERE IS SOAC/MARCH With the SOAC/MARCH application (FACS/MARCH configuration), the primary source of service order data continues to be SOAC. COSMOS is taken out of the Recent Change business with this application (except, like the LAC and NAC, on an exception basis) and becomes just another FACS Component. The tables that resided in COSMOS or Recent Change are now duplicated in MARCH. Instead of retrieving, storing, and passing on already-formatted Recent Change messages, MARCH now generates the Recent Change from the data passed from SOAC, as did COSMOS previously. ________ | | | SORD | |________| | | V ____________ _________ | | | | ---------> | FACS |--- | SOAC | | COMPONENTS | | |_________| <--------- | FOR ASGNS. |--- | |____________| | V * * * * * * * * * * * * * * * * * * _________ * ___________ * | | * | | ________ * _________ | WM |---> * | o RPM | | | * RC | | |_________| * | o CFINIT |----> | RCMG | * -----> | SPCS/ | * | o USL | |________| * MSG | DIGITAL | * |___________| * | SWITCH | * * |_________| * M A R C H * * * * * * * * * * * * * * * * * * * E. Getting Ready For Recent Change Message ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ STARTING WITH SORD Service Orders (SORD) contain FIDs and USOCs (Universal Service Order Codes [these codes tell the type of service the customer may have or get]) followed by data specific to a customer's service request (SORD accesses PREMIS for telephone number and address data; other entries are made by the Service Representative). The order is then passed to SOAC. THEN TO SOAC SOAC uses internal tables to read the FIDs and USOCs passed by SORD to determine what information is required from the various components of FACS. SOAC then accesses the appropriate FACS components (LFACS for Cable Pair assignment; COSMOS for OE assignment) and gathers the required data. Once all the data has been collected, SOAC passes the information to the Work Manager. Data is either passed as is or translated by SOAC (again using internal tables) into language acceptable to the receiving systems (i.e., COSMOS and MARCH). SOAC passes information intended for MARCH in one of two ways: TP-Flow-Through Translation Packets Translation Packets (TPs) contain fully translatable data from which MARCH can generate a Recent Change message. Determination is made by SOAC based on the interface capabilities and its ability to read, translate as required, and pass data. Service Order Image Service Order Images are sent to MARCH if SOAC is not able to pass all required data. Images require additional information, either input manually or retrieved from COSMOS before Recent Change messages are generated. WORK MANAGER - THE TRAFFIC COP The primary function of Work Manager is to read the service order and determine where the data must be sent. Decisions include: COSMOS System MARCH System COSMOS Wire Center MARCH Switch COSMOS Control Group Serving RCMA Work Manager passes the service order data to MARCH on a real time basis (orders that were previously held in COSMOS until requested by Frame Due Date [FDD] are now held in MARCH), either as a TP or an Image. 1. When MARCH Receives A Translation Packet (TP) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (1) A Translation Packet, passed from SOAC via Work Manager is received in MARCH by the CIP, Communication Interface Program. (2) When data is received by the CIP, it calls up the CTI or Job Control Module. The Job Control Module or CTI writes the data that is received to a temporary file and informs TP Trans (Translation Translator) that an order has been received. It also controls the number of simultaneous jobs submitted to TPTrans. (3) TPTrans analyzes the order in the temporary file, does appropriate FID conversion (such as stripping out dashes), reformats the order, and passes it to the Recent Change Message Generator (RCMG). (4) RCMG performs all Recent Change message generation and, upon completion, writes the order into a MARCH pending file (Pending Header or Review file). In addition to the data passed from SOAC, RCMG uses the following data in MARCH to translate into switch-acceptable messages: NXX Switch Specific Parameters (RPM) USOC (RPM) CCF Keywords (CFINIT) USOC/NXX (RPM) Review Triggers (RVT) Release Times (SRM) ________ | | | SOAC | |________| | | V ______ | | | WM | |______| | | * * * * * * * * * * * * * * * * * * * * * * * * * M A R C H * * _______ _______ _________ ______ * * | | | | | | | | * * | CIP | -----> | CTI | -----> | TP TRANS| -----> | RCMG | * * |_______| |_______| |_________| |______| * * | /\ * * | / * * ______|______ / * * | | / * * | /TMP |------/ * * |_____________| * * * * * * * * * * * * * * * * * * * * * * * * * * * 2. When MARCH Receives A Service Order Image ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ (1) A Service Order Image, passed from SOAC via Work Manager is received in MARCH by the CIP, Communication Interface Program. (2) When the image is received by the CIP, it calls up the CTI or Job Control Module. The Job Control Module or CTI writes the data that is received to a temporary file and informs TP TRANS (Translation Translator) that an order has been received. It also controls the number of simultaneous jobs submitted to TPTrans. (3) TP TRANS analyzes the order in the temporary file, sees that it is a service order image, and creates a SOI (Service Order Image) file using the order number and file name. The entire image is written to the SOI file. TP TRANS signals the Service Order Image Processor (SOIP) program for the remaining processing. (4) If SOIP can determine the switch for which the image is intended, it passes a request to the Call COSMOS file and stores the image data in the IH file (Image Header). If SOIP cannot determine the switch, the image is placed in the PAC (Unknown Switch Advisory) for manual processing. (5) For images where the switch has been determined, MARCH calls COSMOS at its next scheduled call time and runs RCP by Order Number (if the last call time is past, it will defer the request to the first call time for the next day). (6) If the order is received from COSMOS, it is placed in the PH or RV file appropriately and the Image Header is purged. A flag is set indicating that a Service Order Image text exists in the system. If the order is not received from COSMOS, the image is placed in the PAC for manual processing. * * * * * * * * * * * * * * * * * * * * * * * * * M A R C H * * _______ _______ _________ ______ * * | | | | | | | | * * | CIP | -----> | CTI | -----> | TP TRANS| -----> | RCMG | * * |_______| |_______| |_________| |______| * * | /\ | * * | / | * * ______|______ / _V___________ * * | | / | | * * | /TMP |------/-----| /SOI | * * |_____________| |_____________| * * * * * * * * * * * * * * * * * * * * * * * * * * * It is not necessary for you to know all the programs MARCH uses to process Service Orders in a SOAC/MARCH environment. That gets trivial and all stuck in various commands that do not mean anything unless, of course, one is on the system at hand. _________ _________ ___________ TP | | TP _______ TP | | | |-------> | Work | -------> | | -----> | SPCS/ | | SOAC | Image | Manager | Image | MARCH | Image | Digital | |___________|=======> | (WM) | =======> |_______| =====> | Switch | |_________| |_________| | | ^ ^ | | | | | | | | V V | | * * * * * * * * * * * COSMOS * * * * * * * * * * * | | | | | |__| | |______| Though it is trivial to understand just how all these system work, here is a rough overview of MARCH. To Cover MARCH, this will first cover the background processing. F. MARCH Background Processing ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ RECENT CHANGE PARAMETER (RPM) In conjunction with ORI Patterns and Recent Change Templates, the RPM determines how information from SOAC is changed and/or manipulated to create acceptable switch Recent Change messages. RCMA Supervisor has overall responsibility for the RPM. Although specific categories may be maintained by Staff Manager, it is overviewed by RCMAC as a whole. This includes Line Class Code (LCC) conversion data previously under the sole responsibility of the NAC in COSMOS. It requires a change of procedures for the RCMA to ensure proper LCC information is passed on the RPM and updated appropriately. Initial USOC is LCC conversion data and will be copied into MARCH from the COSMOS USOC Table. SWITCH RELEASE MANAGER (SDR) With SOAC/MARCH, it no longer determines the types of orders to be pulled from COSMOS, and thus establishes the date and time orders are to be released to the switch, coming both from SOAC and from COSMOS. It is based on Package Type (PKT) and Package Category (PKC) SWINIT TRANSACTION Contains switch-specific data for MARCH to communicate with SOAC (via Work Manager), COSMOS, and the switch. Establishes the call times for COSMOS. - RCP by Order Number for Service Order Images. - Suspends, Restores, and Nonpayment Disconnects. - Automated AGE Requests (as applicable). - Automated MAN Report. SDR - SWITCH DATA REPORT SDR is a report transaction intended for use by the RCMA Associate. The Switch Data Report provides a printout of the SWINIT information that was populated from the Perpetrations Questionnaire submitted by the RCMA Supervisor (see Order Description part of this file). MOI of an Order in History Orders in the History Header (HH) file will reflect the history source. The history source indicated how the order was written to the history file. G. User Transaction in MARCH ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Most Commonly Used MARCH Commands .-------------------------------------------------------------------------. | Transaction | Name | Function | Search keys | Prompts | | ------------|--------------|---------------|-----------------|----------| | MSR <CR> | MARCH Status |office status | . <CR> | ---- | | | Report | | sw address | | | ------------|--------------|---------------|-----------------|----------| | MOI <CR> | MARCH Order | status of | fn rv | ---- | | | Inquiry | order, tn, | fn rj | | | | | file | fn hh/adt xx-xx | | | | | | so n12345678 | | | | | | tn xxxxxxx | | | ------------|--------------|---------------|-----------------|----------| | ONC <CR> | On Line | Access COSMOS | ------ | login | | | COSMOS | | | password | | ------------|--------------|---------------|-----------------|----------| | ONS <CR> | On Line | Access Switch | ------ | Switch | | | Switch | | | logon | | ------------|--------------|---------------|-----------------|----------| | ORE <CR> | Order Edit | Edit Header or| fn rv | ---- | | | | message text | fn rj | | | | | of MARCH file| so n12345678 | | | | | | tn xxxxxxx | | | ------------|--------------|---------------|-----------------|----------| | ORE -G <CR> | Order Edit | edit multiple | 2 Search keys | ---- | | | Global | files | Required | | | ------------|--------------|---------------|-----------------|----------| | ORI <CR> | Order Input | Build MARCH | ------ | Patterns | | | | file | | | | ------------|--------------|---------------|-----------------|----------| | ORS <CR> | Order Send | Send to Switch| so n12345678 | ---- | | | | immediately | tn xxxxxxx | | | ------------|--------------|---------------|-----------------|----------| | TLC <CR> | Tail COSMOS | watch MARCH | ------ | ---- | | | | pull orders | | | | ------------|--------------|---------------|-----------------|----------| | TLS <CR> | Tail Switch | Watch orders | ______ | ____ | | | | sent to switch| | | | ------------|--------------|---------------|-----------------|----------| | VFY <CR> | Verify | Request Verify| ------ | rltm,type| | | | | | tn,oe,hml| | ------------|--------------|---------------|-----------------|----------| | VFD <CR> | Verify | Show Completed| ------ | ---- | | | Display | verifies | | | | ------------|--------------|---------------|-----------------|----------| | VFS <CR> | Verify Status| Show pending | ------ | | | | | verities | | | ` ------------------------------------------------------------------------' Here is a detailed explanation of some of the commands: MOI - MARCH ORDER INQUIRY MOI is a conversational inquiry transaction intended for use by the RCMAC Clerk. MOI is used to inquire on Recent Change messages in a pending file(s): Pending Header, Review, Reject, and/or History Header. It may be used to inquire on one message, an entire order, several messages in more than one file, or all orders in a file, determined by the search keys entered. ONS - ON line Switch Each switch has its own login sequence. DMS-100 Login 1) Give a Hard Break 2) At the "?" prompt type "login" 3) There will be an "Enter User Name" prompt. Enter the user name. 4) Then "Enter Password" with a row of @, *, & and # covering the password. 5) Once on, type "SERVORD" and you are on the RC channel of the switch. Logout 1) Type "LOGOUT" and CONTROL-P 1AESS Login 1) Set Echo on, Line Feeds on and Caps Lock on. 2) End each VFY message with " . CONTROL-D" and each RC message with "! CONTROL-D". Logout 1) Hit CONTROL-P 5ESS Login 1) Type "rcv:menu:apprc" at the "<" prompt. Logout 1) Type "Q" and hit CONTROL-P ONC - On Line COSMOS 1) You will see "login:" so type in username and then there will be a "Password:" prompt to enter password. ORE - Order Edit ORE Commands are used to move between windows and to previous and subsequent headers and text within an editing session. Commands may be input at any point in the ORE session regardless of the cursor location. They are capital letters requiring use of the shift key or control commands. Here are the movement commands: Commands Description ~~~~~~~~ ~~~~~~~~~~~ N (ext header) Replaces the data on the screen with the next header and associated text that matches the search keys entered. M (ore text) Replaces the data in the message text window with the next message associated with the existing header (for multiple text message). P (revious header) Replaces data in the header windows with the header you looked at previously (in the same editing session). B (ackup text) Replaces data in the message text window with the text you looked at previously (in the same editing session). S (earch window) Moves the cursor to the search window permitting additional search keys to be entered. Control-D Next Page Control-U Previous Page < Move cursor from text window to header. > Moves to text window from header. Q (uit) Quit ORE -G ORE -G is a conversational transaction intended for use by the RCMA associate. ORE -G is used to globally edit Recent Change messages existing in a MARCH pending file: Pending Header, Review, and Reject. Editing capabilities include adding information on an order. ORE -G is also used to change header information and to remove messages. ORI - ORder Input ORder Input enables one to input an order and change orders. The changes that can be made are in the telephone number, OE, so on. This command is too complex to really get into here. VFY - Verify This is used to manually input verify messages into MARCH, thus to the switches. MSR - MARCH Status Report This used to count the amount of service orders stored in SOAC. It also shows the amount of change messages that have been sent to the switch. H. Service Order Forms ~~~~~~~~~~~~~~~~~~~~~~ In my time, I have come across a lot of printouts that have made no sense to me. After several months, I could start to understand some of the codes. Here are what some of the common service orders are and what they are for. SORD Service Order: _________________________________________________________________ | | | | |TN CUS TD DD APT MAC ACC AO CS SLS HU | |415-343-8765 529 T DUE W AS OF 1FR ABCDE4W | |ORD SU EX STA APP CD IOP CT TX RA SP CON AC | |C14327658 SMIUX R R | |ACNA R | |WA 343# EXETER,SMT | |WN IDOL, BILLY | |---S&E | |I1 ESL | |O1 1FR/TN 343-8321/ADL | | /PIC 10288 | |O1 ESL/FN 3438321 | |---BILL | |MSN IDOL, BILLY | |MSTN 555-1212 | |---RMKS | |RMK BLAH | | | | /**** END | | | |_________________________________________________________________| _________________________________________________________________ | | |[1] [2] [3] [9] | | | | | | | |TN CUS TD DD APT MAC ACC AO CS SLS HU | |407-343-8765 529 T DUE W AS OF 1FR ABCDE4W | | | | [8] | | | | | ORD SU EX STA APP CD IOP CT TX RA SP CON AC | |C14327658 SMIUX R R | |ACNA R | | | |[4] | | | | |WA 343# EXETER,SMT | | | |[6] | | | | |WN AT&T | |---S&E \ | |I1 ESL | | |O1 1FR/TN 343-8321/ADL | [5] | | /PIC 10288 | | |O1 ESL/FN 3438321 / | |---BILL | | | | [6] | | | | | MSN IDOL, BILLY | | | | [7] | | | | | MSTN 555-1212 | |---RMKS | |RMK BLAH | | | | /**** END | | | |_________________________________________________________________| [1] Telephone Number. Format is XXX-XXX-XXXX. [2] Customer number. [3] Due Date. [4] Work Address. [5] The S&E field: ACTION CODE -- This is the code at the far left-most side of the page. These codes end with a 1 or a 0. The 1 says to add this feature and the 0 says to not do the feature. There are several different action codes. Here is a list: Action Code Used to ~~~~~~~~~~~ ~~~~~~~ I Add features O Remove features C-T Change designated number of rings, "forward to" number, or both on Busy/Delay call forwarding features. E-D Enter or Delete a feature for record purposes only. R Recap CCS USOC to advise Here is a list of some common USOCs (features): ESC Three Way Calling ESF Speed Calling ESL Speed Calling 8 Code ESM Call Forwarding ESX Call Waiting EVB Busy Call Forward EVC Bust Call Forward Extended EVD Delayed Call Forwarding HM1 Intercom Plus HMP Intercom Plus MVCCW Commstar II Call Waiting [6] Billing name [7] Billing number [8] Service Order Number [9] Class of Service or LCC (See appendix 1) SDR File Header Information Order (MARCH) 1. Switchname 7. Package Type 2. Header File Name 8. Package Category 3. Current Date & Time 9. Reject Reason 4. Service Order Number 10. Release Date & Time 5. Service Order Type 11. Accept Date & Time 6. Telephone Number Reject Date & Time 12. Input Source History Header File [1] [2] [3] | | | sw: swad0 history header file fri may 31 07:50:12 1992 [4]- so=janet3 tn= pkt-in pkc=other [11]- act=05-30 0750 src=ori | | | history text= | [6] [7] [8] rc:sclist: [12] ord 31235 cx =031235 adn 2 ! ~ Reject File [1]- sw:swad2 [2]- reject file [3]- fri may 30 11:22:01 1992 [4]- so=c238 [5]- ver=7 tn=5551212 -[6] [9]- rj reason=ot rldt=05-30 1059 rjdt=05-30 :106 src=cosmos message test= | | | rc:line:chg: [10] [11] [12] ord 87102 "=238-7102' "ord c231" "restoration from ssv-db" tn 555 1212 lcc 1mr ! ~ ve data= , er m 07 rc18 0 87102 0 4 valar new 00001605 err 00000307 05/30/92 11:07:16 I. COSMOS Service Order From The SOI Command ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ________________________________________________________________________ |WC% | |WC% SOI | |H ORD N73322444 | | | | DEC 19, 1992 10:12:21 AM | | SERVICE ORDER ASSIGNMENT INQUIRY | | | |ORD N733224444-A OT(NC) ST(AC- ) FACS(YES) | | DD(12-20-92) FDD(12-20-92) EST(11-16:14) SG(G) DT(XX ) OC(COR) | | MDF WORK REQ(YES) MDF COMPL(NO) LAC COMPL(NO) RCP(NO) | | WPN 9446 WLST 1= P 2= 3= 4= 5= 6= 7= 8= | | COORDINATION REQUIRED | | RMK FAT TBCC,RO D77901070 | | RMK FAT TBCC,RO D77901070 | |CP 48-0942 | | ST SF PC FS WK DATE 11-28-89 RZ 13 | | LOC PF01008 | |OE 012-25-006 | | ST SF PC FS WK DATE 11-12-91 CZ 1MB US 1MS FEA TNNL| | PIC 10288 | | LCC BB1 | | CCF ESX | | LOC PF01007 | |TN 571-5425 | | ST WK PD FS WK DATE 12-03-91 TYPE X | | **ORD D77901070-C OT CD ST AC- DD 12-20-92 FDD 12-20-92 | | | |** SOI COMPLEATED | |WC% | |________________________________________________________________________| ________________________________________________________________________ | | | WC% | | WC% SOI | | | | | | H ORD N73322444 | | | | [1]- DEC 19, 1992 10:12:21 AM | | [2]- SERVICE ORDER ASSIGNMNET INQUIRY | | | | [3] [4] [5] | | | | | | | ORD N733224444-A OT(NC) ST(AC- ) FACS(YES) | | | | [7] [8] [6] [9] | | | | | | | | DD(12-20-92) FDD(12-20-92) EST(11-16:14) SG(G) DT(XX ) OC(COR) | | | | [10] [11] [12] [13] | | | | | | | | MDF WORK REQ(YES) MDF COMPL(NO) LAC COMPL(NO) RCP(NO) | | | | | | WPN 9446 WLST 1= P 2= 3= 4= 5= 6= 7= 8= | | COORDINATION REQUIRED | | RMK FAT TBCC,RO D77901070 | | RMK FAT TBCC,RO D77901070 | | | |[35] | | | | | CP 48-0942 | | | | [34] [35] [36] [37] | | | | | | | | ST SF PC FS WK DATE 11-28-89 RZ 13 | | | | LOC PF01008 -[39] | | | | OE 012-25-006 -[19] | | | | [20] [21] [22] [23] [24] [25] | | | | | | | | | | ST SF PC FS WK DATE 11-12-91 CS 1MB US 1MS FEA TNNL| | | | PIC 10288 | | | | LCC BB1 -[27] | | | | CCF ESX -[26] | | | | LOC PF01007 -[32] | | | | TN 571-5425 -[14] | | | | [15] [16] [17] [18] | | | | | | | | ST WK PD FS WK DATE 12-03-91 TYPE X | | | | [38] [28] [29] [30] [31] | | | | | | | | | **ORD D77901070-C OT CD ST AC- DD 12-20-92 FDD 12-20-92 | | | | ** SOI COMPLETED -[40] | | | | WC% -[41] | |________________________________________________________________________| [1] Date and Time the SOI was Requested in COSMOS [2] Title of Output Message [3] Order Number [4] Order Type [5] Status of Order [6] EST (11-16:14) When Service Order was Established into COSMOS [7] Due Date [8] Frame Due Date [9] Segment Group [10] Main Distributing Frame Work Required [11] Main Distributing Frame Work Complete [12] Loop Assignment Center Completed [13] FACS Y >-- The order has downloaded from SOAC to MARCH(MARCH) RCP N [14] Telephone Number [15] Present State of Telephone Number [16] Future Status of Telephone Number [17] Date of Last Activity on Telephone Number [18] Type of Telephone Number [19] Line Equipment [20] Present Status of Line Equipment [21] Future Status of Phone Line [22] Date of Last Activity on Line Equipment [23] Class of Service [24] USOC [25] Features [26] Custom Calling Feature [27] Line Class Code [28] Order Type that is Clearing Telephone Number [29] Status of Order that is Clearing Telephone Number [30] Due Date [31] Frame Due Date [32] Location of Line Equipment on Frame [33] Cable and Pair [34] Present Status of Cable and Pair [35] Future Status of Cable and Pair [36] Date of Last Activity on Cable and Pair [37] Resistance Zone [38] Order Number Clearing Cable [39] Location of Cable and Pair on Frame [40] SOI Complete Message [41] Wire Center and Prompt Symbol to Indicate Computer is Ready for Another Transaction [42] Primary Independent Carrier is 10288 (AT&T's Ten Triple X Code) J. MSR - MARCH Status Report (MARCH) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ _______________________________________________________________________ | | | switch name | | | | ==================================================================== | | march status report | | sw:switch name tue oct 30 11:14:48 1992 | | pending work functions | | ==================================================================== | | past due due today future due | | ____________________________________________________________________ | | use moi for: 0 0 0 | | reject file 0 1 270 | | review file 0 0 0 | | held release status 28 14 44 | | normal release status 0 7 184 | | ____________________________________________________________________ | | use pac for: 0 15 | | change notices 0 3 | | unknown switch notices 0 0 | | =====================================================================| | | | ** msr completed | |_______________________________________________________________________| _______________________________________________________________________ | | | switch name | | | | | | ==================================================================== | | [1] | | | march status report | | sw:switch name [2]- tue oct 30 11:14:48 1992 | | pending work functions | | ==================================================================== | | [3] [5] [12] | | | | | | | past due due today future due | | ____________________________________________________________________ | | | | use moi for: 0 2 -[6] 0 | | | | reject file 0 1 -[7] 0 | | | | held release status 5 -[4] 6 -[8] 0 | | | | normal release status 0 3 -[9] 3 -[13] | | ____________________________________________________________________ | | | | use pac for: 0 15 -[10] | | | | change notices 0 3 -[11] | | | | unknown switch notices 0 0 | | =====================================================================| | | | ** msr completed | |_______________________________________________________________________| [1] Office MSR request in (switch name/address) [2] Date and time of request [3] Past due service order column [4] Past due service order on hold [5] Due today service order column [6] Order due today in the reject file [7] Orders due today in review file [8] Orders due today on hold [9] Orders due today with a normal release status [10] PAC service orders which have been changed [11] PAC switch advisory notices encountered today [12] Future due service order column [13] Order due in the future with a normal release status K. Other Notes ~~~~~~~~~~~~~~ LCC or Line Class Code is, in short, what kind of line the Bell customer may have. They are the phone line type ID. These IDs are used by the SCC (Switching Control Center) and the switches as an ID to what type of billing you have. Here is a list of some common LCCs that a standard BOC uses. Note: This is not in stone. These may change from area to area. 1FR - One Flat Rate 1MR - One Measured Rate 1PC - One Pay Phone CDF - DTF Coin PBX - Private Branch Exchange (Direct Inward Dialing ext.) CFD - Coinless ANI7 Charge-a-Call INW - InWATS OWT - OutWATS PBM - 0 HO/MO MSG REG (No ANI) PMB - LTG = 1 HO/MO Regular ANI6 L. Recommended Reading ~~~~~~~~~~~~~~~~~~~~~~ Agent Steal's file in LODTJ #4 Acronyms 1988 [from Metal Shop Private BBS] (Phrack 20, File 11) Lifting Ma Bell's Cloak Of Secrecy by VaxCat (Phrack 24, File 9) _______________________________________________________________________________