. .__ . : .__________.____| \ .________ .___________________ : -)-O-----|______ \ | \| . \-| / ____/------O-(- : | | \ _ \ | \| \ / .__)_ : | | .______/ | \ _ \ \ /| | \ | | | | | | \ | \RtX! \/ | ` \ | : | ___| |____|____ /__|____ /___ / |________ / : -)-O-----|/-------------------\/--------\/----\/------------\/-----O-(- : : . . VOLUME ONE. ISSUE TWO. RELEASED FEBRUARY, 20. 1993. ----------- ---------- ---------------------------- --------------------------------------------------------------------------- THE TABLE OF CONTENTS --------------------------------------------------------------------------- 1.2.1 Intro & Editorial to PHATE 1.02 by NeUR0NoM [ 015k ] 1.2.2 British Telecom Payphone 190 Manual by Axiom & Death Jester [ 032k ] 1.2.3 Eavesdropping UK (Cordless Phones) by Slycath [ 003k ] 1.2.4 Eavesdropping USA (Cordless & More) by NeUR0NoM [ 028k ] 1.2.5 Packet Switched Network DNIC List by Ronnie [ 010k ] 1.2.6 The Police National Computer 2 by Slycath [ 011k ] 1.2.7 NUARDIALER v2.0A Network Scanner by NeUR0NoM [ 016k ] 1.2.8 UK Information Sources by Slycath [ 003k ] 1.2.9 News And Reviews by NeUR0NoM & Janx [ 045k ] -------- [ Total: 163k ] --------------------------------------------------------------------------- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + PHATE MAGAZINE. VOLUME ONE. ISSUE TWO. FILE 1 OF 9. + + + + "INTRO AND EDITORIAL TO PHATE 1.02" + + BY NeUR0NoM/PHATE + +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ PHATE VOLUME 1 Issue 02. Introduction. "Ruff In the Phuture Bizniz" Hello, and welcome to PHATE magazine's sophmore edditon.. Well, its our second time out and I think we've increased our magazine size by 3 times since our first issue. I would like to say that we could not have possibly created this mag without all the help of the writers who contributed somthing to the magazine. There are some excellent articles in this issue from Axiom's Brittish Telecom Payfone article, to Slycath's Police National Computer article. A thick read all the way through. Now looking at the table of contents you may feel that myself the editor, has alot of articles printed in this issh.. actually there really is only two.. the article I included as an addition to Slycath's UK Cordless evesdropping file, and my scanner which I originally planned to release in the article. All the rest of this, what you are reading now, and the news at the end is just a little journalism that re-inforces the backbone of the magazine. Generaly what this all calls for more articles from more people, and this means YOU! It is not nessisary to be a member of PHATE to write articles for our magazine. We will except all well writen articles concerning but not limited to telecomunications, hacking, networks, drugs, surveilance, explosives, networks, etc. Your news items will also be excepted. News items must be current, and must not have appeared in any other electronic newsletter. If you send us news about someone you know that got busted or something scene related Any articles or recent news that you have (please include a source if your news was published previously in either electronic or paper format) are welcome for publishing. We accept any articles on telephones and telecomunications, general hacking, networks, drugs, surveilance, explosives, and any and all other well writen articles on any form of hard to get, and little known information of such nature. As well, in the future we are including a letters to the editor section, so if you have gripes or praises, questions or suggestions, please mail them to me on Hanger 18, the number should be listed at the end of this magazine. Also, if you have contributions, please mail them to me in private on Hanger 18 and only on Hanger 18. I dont have to time to go checking on all of our boards for articles, so please, if you want your letter or article included in the next issue, send them ONLY to Hanger 18. -*- I think that it might be a little utopian to say that we are living in an information age (as i do a few paragraphs below). You might say that you who are reading this for entertainment/information value, myself, and all of our cohorts, piers and inspirations are part of the information CULT. We all share information amoungst each other and we all inform each other of new and interesting tidbits of data that may be relevant to each others interest. Many people, the United States government, big businesses, etc, may feel that this information is private and that it should not even be looked at by such mere mortal souls. The same organizations freely trade information about yourself: your name, number, social security, & address amoungst themselves. Moreover, they often sell said information at a high cost to solicitors for their own usage. These same companies that hoard so much information on both you and itself, are deadly afraid of "US". Who are US? The technological/security/computer criminal justice writer, the hacker, the telephone enthusiast. All of those individuals who will some day, if they have not already, assimilate themselves into the companies they once "hacked", by word or deed, to make them stronger and to reinforce the company's technological structure. Sounds alot like selling out to big brother doesnt it? But its not. Its staying in love with the things you've always loved: phones, electronics, radio phrequencies, computer systems, networks etc.. and getting payed at the same time. We at PHATE, and many of our contacts, friends, and associates, seek never to destroy ANY information whatsoever. In fact we feel such actions to be inexcusable and unforgivable. We catagoricaly look unfavourably upon the fraudluent actions of the REAL computer criminals, the CARREER CRIMINALS, who seek their fortunes preying upon their company by means of technology. Further- more, we look unfavourably upon any actions involving technology and computers which may fraudulently attempt to transfer funds or otherwise obtain said monies for unauthorized personal use. This may sound like some disclaimer bullshit, but its the honest truth. Any of you inquiring "journalists" can question any one of the supposed members of the hacker and technologist/security/crime community and they would probably tell you much the same. This is an idea however alien it may seem is shared by many people, not just the aformentioned groups. It is held dear by the MIT AE Lab originals, the hackers of yesteryear, and the technological reporters and writers of our day. In conclusion, if you read this magazine and you find it dangerous, throw it away; but if you read this magazine and you find it interesting and enjoying, send it to another one of your friends and wait for more to come. Be secure in the knowlege that as long as we can exist before there comes ANOTHER bust motivated by fear and lack of knowlege, we are living somewhat uneasy, somewhat self-assured, in the information age. - NeUR0NoM / PHATE Editor In Chief, PHATE MAGAZINE -*- PHATE VOLUME ONE. ISSUE TWO. Main Organisers : Slycath and Coaxial Group Organization : Coaxial Editor In Chief : NeUR0NoM News : Janx/NeUR0NoM Proofreading : /\> / / PSN : Lutzifer (26245400080177) Mailname: \ \ QSD (208057040540) Mailname: / / SecTec (26245400050045) Mailname: \ X/X\X/X\X/X\X/X\X/X\X/X\X/X\X/X\X/X\X/X\X/X\X/X\X/X\X/X\X/X\X/X\X/X\X/X\X/X ----------------------------------------------------------------------------- DNIC Country Network Format or # of Digits(If known) ----------------------------------------------------------------------------- ^ZZ is automatic on the end for^ ^the port number^^^^^^^^^^^^^^^^ 2022 Greece HELPAK 2023 Greece EURONET 2040? Netherlands DATANET1 2041 Netherlands DATANET1 2042 Netherlands DATANET1 2043 Netherlands Euronet/Dabas 2044 Netherlands DABAS 2049? Netherlands DATANET1 2062 Belgium DCS 2062XXXXXX 2063 Belgium DCS 2068 Belgium DCS 2069 Belgium DCS 2080 France TRANSPAC 2080XXXXXXXX 2081 France NTI 2083 France Euronet 2089? France VX32 2141 Spain NID/TIDA 2145 Spain IBERPAC 2145XXXYYYYYY 2160 Hungary Nedix 2161 Hungary DATEX-P 2201 Yugoslavia YUPAC ?2201XXXXXXXX 2222 Italy ITAPAC 2222XXXXXXX 2223 Italy EURONET 2227 Italy ITAPAC 2283 Switzerland EURONET 2284 Switzerland TELEPAK 2289 Switzerland TELEPAK 2322 Austria Datex-P 2322XXXXXXX 2323 Austria DATEX-P TTX 2329? Norway(Austria?) RADAUS 2341 Great Brit. BTI IPSS 2342 Great Brit. BT PSS 2342XXXYYYYY 2343 Great Brit. EURONET 2348? UK ???? 2350? Great Brit. Mercury 2351 Great Brit. MERCURY 2352 Great Brit. TELEMATIC 2381 Denmark DATEX 2382 Denmark DATAPAK 2383 Denmark EURONET 2401 Sweden DATEX-L 2402 Sweden DATAPAK 2403? Sweden DATAPAK 2405 Sweden EURONET 2421 Norway DATAPAC TTX 2422 Norway DATAPAK 2423 Norway DATAPAC 2427 Norway DATAPAK 2441 Finland TELETEX 2442 Finland FINNPAK 2442XXXXX 2443 Finland TELENET 2502 USSR IASNET 2502XXXXXX 2624 Germany TELEPAK 2624XXXXXYYYYY 2680 Portugal TELEPAC 2680XXXXYYYY 2682 Portugal TELEPAC 2683 Portugal EURONET 2703 Luxemburg EURONET 2704 Luxemburg LUXPAC 2704XXXXX 2709 Luxemburg LUXPAC 2721 Ireland EIRPAC 2723 Ireland EURONET 2724 Ireland via IPSS 2724XXXYYYYY 2740 Iceland ICEPAC 2763 Turks&Caicos IDAS 2802 Cyprus CYTAPAC 2862 Turkey TURPAC 2863 Turkey TURPAC 2782 Malta MALTAPAC \___Not Sure which 2782 Martinique TRANSPAC / one it is ... 2802 Cyprus CYTAPAC 2807 Cyprus CYTAPAC 2808 Cyprus CYTAPAC 2809 Cyprus CYTAPAC 2841? Bulgaria BULPAC 2901 Greenland KANUPAK 2922 San Marino X-NET SMP 2945 Andora ANDORPAC 3020 Canada DATAPAC 3020XXXYYYYY 3025 Canada GLOBEDAT-P 3028 Canada INFOGRAM 3029 Canada INFOSWITCH 3101 US PTN-1 3102 US MCI-Data-Tran. 3103 US ITT-UTDS II 3104 US WUI 3104XXXXXX 3106 US TYMNET 3106XXXXXX 3110 US TELENET/SPRINT 3110XXXYYYYY 3113 US RCA 3119 US DATAPAK 3124 US PSTS 3125 US UNINET 3126 US ADP-AutoNet 3127 US TELENET 3132 US COMPUSERVE 3134 US AT&T AccuNet 3134XXXYYYYY 3140 US SNET 3142 US BELL SOUTH 3145 US PACIFIC BELL 3146 US SWEST BELL 3147 US DIGIPAC 3150 US GLOBENET 3300 Puerto Rico UDTS 3301 Puerto Rico UDTS 3320 ???? ???? 3340 Mexico TELEPAC 3380 Jamaica JAMANTEL 3400 ???? ???? 3423? Barbados IDAS 3443? Antigua&Barbuda AGANET 3463? Cayman Islands IDAS 3483 Tortola IDAS 3503 Bermuda C&W(IDAS) 3620 Curacao UDTS 3640 Bahamas Batelco 3700 Dom. Republic UDTS 3701? Dom. Republic UDTS-I 3740 Trinidad&Tobago TEXTEL 3745 Trinidad&Tobago DATANET 3862? Turkey TURPAC 4042? India GPSS 4155 Lebanon CEDARPAC 4201 Saudi Arabia ALWASEED 4251 Israel ISRANET ?4251XXXXXXXXX 4241 U. Arab Emirates EMDAN 4243(4310)U. Arab Emirates EMDAN 4263 Bahrain(Kuwait) IDAS 4271 Qatar DOHPAC 4400 Japan GLOBALNET 4401 Japan DDX-P 4406 Japan-9995Incoming NIS-NET 4408 Japan VENUS-P 4409 Japan VENUS-C 4501 Korea DACOM-NET 4503 Korea DNS 4542 Hong Kong IDAS 4544 Hong Kong PSDS 4545 Hong Kong DATAPAK 4546 Hong Kong INET HK 4550 4600 China PKTELKOM 4872 China/Taiwan PACNET 4872XXXXX 4873? Taiwan PACNETII 4877 China/Taiwan UDAS 5021 Malaysia MAYPAC 5052 Australia AustPac 5052XXXYYYYY 5053 Australia Midas 5054 Australia Midas 5101 Indonesia INDOSAT 5150 Phillippines CAPWIRE 5151? Phillippines DATANET 5152? Phillippines WORLDNET 5154? Phillippines GMCR 5156 Phillippines EASTNET 5200 Thailand THAIPAC 5201 Thialand IDAR 5252 Singapore TELEPAC 5258 Singapore TELEPAC 5301 New Zealand PACNET 5301XXXXXXXX 5350 Guam LSDS-RCA 5351? Guam PACNET 5410? Vanuatu VIAPAC 5460 New Caledon. TOMPAC-NC 5470 France Polinesian TOMPAC-PF 6020 Egypt ARENTO 6040 Morroco MORROCO 6050 Tunesia RED25 6081? Senegal SENPAC 6122 Ivory-Coast SYTRANPAC 6142 Niger NIGERPAC 6152 Togolese Rep. TOGOPAC 6170 Mauritius MAURIDATA 6222? Chad CHAD 6242? Cameroon CAMPAC 6282 Gabon GABOPAC 6352 Rwanda RWANDA 6382 Djibouti STIPAC 6482 Zimbabwe ZIMNET 6490? Namibia SWANET 6550 South-Africa SAPONET-P 6550XXXYYYYY 6551 South-Africa SAPONET 6559 South-Africa SAPOPAC 7040 Guatemala GUATEL 7043 Guatemala GUATEL 7080 Honduras HONDUTEL 7082 Honduras HONDUTEL 7089 Honduras HONDUTEL 7120 Costa Rica RACSA-DATOS 7122 Costa Rica RACSA-DATOS 7128 Costa Rica RACSA-DATOS 7129 Costa Rica RACSA-DATOS 7141 Panama INTELPAQ 7142 Panama INTELPAQ 7160 Peru DICOTEL 7220 Argentina ArPac 7222 Argentina ArPac 7240 Brazil INTERDATA 7241 Brazil RENPAC 7248 Brazil RENPAC 7249 Brazil RENPAC 7300? Chile ENTEL 7302 Chile E-COM 7303 Chile CHILEPAC 7305 Chile TOMNET 7320 Columbia TOMNET 7322 Columbia COLDAPAQ 7420 France/Guinia DOMPAC 7482 Uruguay URUPAC 7489 Uruguay URUPAC --------------------------------------------------------------------------- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + PHATE MAGAZINE. VOLUME ONE. ISSUE TWO. FILE 6 OF 9. + + + + "THE POLICE NATIONAL COMPUTER 2 (PNC 2) U.K." + + BY SLYCATH/PHATE + +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= A BRIEF GUIDE TO THE POLICE NATIONAL COMPUTER 2 (PNC 2) U.K. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Introduction: ------------- Hi all, SLYCATH here and this is just Another of my many contributions to this month's Mag. Ok this is part ONE of a brief guide to the PNC computer version 2. This will only be useful if you can actually get into a cop shop, it's always better to know someone inside rather than try and sneak in. The reason I have created this article is that this is a subject NOBODY has writted about EVER BEFORE in ANY other disk magazines, so I thought "If it benefits Just 1 person in any way then it will be worth the trouble" and anyway it will broaden your minds to a totally new system which I know hardly any (!) will know anything about. So Here Goes......................................... And If You like it then tell me Coz i'll write part 2 !! P.N.C. 2 ENQUIRY SCREEN ----------------------- All transactions carried out are recorded at the Computer Centre, Hendon. An integral part of the interface system is the ability to record details of PNC transactions locally. Every transaction carried out through the interface is recorded on th Interface Equipment at Bradford. Here is an example Interface Logging Screen: ......................................................................... . . . PNC ENQUIRER DETAILS . . . . . . 1 Enquirer [ ] . . . . . . . . 2 Force Enquiry [ ] . . . . 3 Reason Code [ ] . . . . 4 Location [ ] . . . . . . Enter F,field number . . . ......................................................................... ENQUIRER, --------- This field is completed by entering the collar numbar, in respect of PC's and Sgts; the Post Number in respect of Police Support Staff; or the callsign in respect of Police Officers of the rank of Inspector or Above. Entry of this information will result in a check being made against a personnel file within the system and an appropriate reply will be recieved from the computer. e.g. The entry of < 3229 > in the enquirer field will result in the following display:- PC/B/SPEIGHT 27/01/71 This display indicates that the enquirer is authorised and that the enquirer's date of joining is 27/01/71. This will facilitate the verification of enquirer details. FORCE, ------ Circumstances will arise however, where enquirer identification cannot be directly linked with personnel records. Inspectors and other officers working in Headquaters Departments fall into this category. In these circumstances appropriate information should be entered in the ENQUIRER FIELD. e.g. < Inspector Jenkins >. This will result in the remainder of the enquirer field being left blank and the cursor being positioned in the force field. This field will now be mandatory. The entry of < Y > indicates that the enquirer is legitimate and that the operator wishes to force the enquiry past the personnel system. The remainder of the format is completed as follows and the PNC response can be recieved. NOTE. ----- A no trace response from the personnel system does not indicate that the enquirer is not entitled to accept PNC information. This response merely indicates that the enquirer is not recorded on the personell system. If this field is completed with an 'N' the transaction logging screen will be deleted and the transaction response from the PNC will be abandoned and not displayed. REASON, ------- PNC 2 operates a system of National reason codes. The entry of a valid reason code will result in the automatic display of an explanatory literal. e.g. the entry of the reason code 1 will result in the following:- Reason [1] VEHICLE OR PERSON STOPPED The following PNC reason codes are National and must be used in all transactions. CODE REASON ---- ------ 1 VEHICLE OR PERSON STOPPED 2 MOVING VEHICLE 3 ABANDONED VEHICLE / UNACCOMPANIED PROPERTY 4 R.T.A. 5 PROCESS / INVESTIGATION ENQUIRY 6 ADMINISTRATION ENQUIRY 7 CHILD ACCESS 8 ON BEHALF OF ANOTHER AGENCY 9 UPDATING / BROADCAST TRANSACTION 10 AUDITING ---- ------ LOCATION, -------- The location of the subject of the transaction, In the majority of cases this will be a valid location. However, on occasions the location of the enquirer may be more appropriate, e.g. < CID Admin. > or < Vehicle reported stolen >. It is advisable that as much detail as possible is recorded in this field. Information accurately recorded may be of value in any subsequent enquiry. For example, in a missing person enquiry it is insufficient to merely record < misper enquiry >, it is better practice to include the name of the person also. IT MAY BE ANTICIPATED HOWEVER, THAT THE MAJORITY OF PNC CHECKS CARRIED OUT IN CUSTODY AREAS WILL FALL WITHIN REASON CODE 5, AND THAT THE LOCATION WILL BE SHOWN AS < CUSTODY AREA - [LOCATION] >.A At the completion of the transaction logging screen the operator will be given the opportunity of selecting a field number in order to amend any of the field in the format. The entry of 'F' will file the information onto an Audit log and permit the reciept of the PNC response. HERE IS A HELPFUL TIP FOR ALL YOU NAUGHTY BOYS AND GIRLS (Heheheheh): |----------------------------------------------------------------------------| | The Identity of the operator is NOT required as part of transaction logging| | as all transactions will be accredited to the operator currently logged on.| | The operator Identity will be displayed on the bottom line of the VDU | | screen and will be printed as a part of all responses from the Audit log. | |----------------------------------------------------------------------------| THE PERSON CONCEPT ------------------ Each record held on this application relates to one person and will contain information appropriate to the reason for their prescence on the system. It consists of the NOMINAL information (personal identification details), NAME AGE ( D.O.B.) SEX COLOUR HEIGHT. Nominal Information is supported by one or a combination of the following elements:- NIB, Wanted/Missing, Disqualified Driver. THE PNC ID, ---------- Each record created on the Names Application will be allocated a unique PNC reference number called the PNC ID. The PNC ID consists of a 2 figure year element followed by a sequential number, of up to 7 figures, and a check letter. e.g. 90/57129D Migrated records from the old PNC were allocated a PNC ID according to the year the person was first recorded. The PNC ID will ALWAYS be displayed on a person's Nominal page. ENQUIRIES, --------- The transaction code #NE is used for ALL enquiries, whether using a persons NASCH factors, or using a unique number, the #NE transaction can be carried out either with or without a format. N.A.S.C.H. FACTOR ENQUIRIES --------------------------- NAME ---- As all persons recorded on this index are identified primarily by their names, this fiels MUST be completed. The remainder of the input is optional The surname is always entered first followed by the fornames or initials where known. e.g. NIXON/ NIXON/D/C NIXON/DAVID/CHARLES Note the oblique strokes to indicate the end of the surname and SEPERATE each forname or initial. An Oblique stroke is NOT included after the LAST forename or initial. The minimum input in this field is two characters, including the oblique strokea, and the maximum is 54 characters. A name exceeding 54 characters is entered with 53 characters and the final character being replaced with a < + >. Permissible characters in this field are ALL ALPHA CHARACTERS and the following :- A full stop after ST or STE only, e.g. ST.JOHN An apostrophe, e.g. O'CONNOR Hyphens, e.g. HALL-BROWN A maximum of two hyphens may be included in any name. Hyphens will cause the computer to search on all combinations of the name and produce results accordingly. Titles such as REV, DR, SIR, LORD or PROF must NOT be included in this field. D.O.B. ------ A date of birth, of eight characters length, should be included if known and can be entered in the following ways :- 31011943 --011943 OR ^^011943 ----1943 OR ^^^^1943 The computer will not accept non-existent dates, e.g. 29021943 OR 31041943 SEX --- A one character input to denote the sex of the subject, if known:- M = MALE F = FEMALE U = UNKNOWN COLOUR ------ A one character input to denote the colour of the subject, if known:- W = WHITE N = NON WHITE U = UNKNOWN HEIGHT ------ The height of the subject is entered as a four figure number and either Imperial or Metric measurements can be used. The first character of the input MUST indicate the type of measurement being used :- F601 = 6 feet 1 inch M180 = 1.8 metres The height cannot be less than 2 feet nor more than 8 feet 11 inches. NASCH factor enquiries can be entered either by first requesting a format, or can be entered in the DATA field of the PNC 2 enquiry screen as and unformatted entry. In an unformatted entry each of the five fields must be seperated by a colon (:) or semi colon (;). e.g. NIXON/DAVID/CHARLES:10041959:M:W:M601 If a factor such as birthdate is unknown the entry would be thus:- e.g. NIXON/DAVID/CHARLES::M:W:M601 However trailing field seperators need not be included. NAMES RECORDS DESCRIPTION ------------------------- The following is an example of a nominal page:- ........................................................................ . 15/10/91 14:46 13TF NE71/0001 . . . . SRCH PNC 81/2251D . . WM:6 DD:2 CH:11 AL:1 . . RICHARDSON, ANTHONY DAVID PNCID 81/2251D . . 19/09/69 CLIFTON (13) MALE WHITE EUROPEAN CRO 3183/81M . . F510 (M178) PRCD L EARS / TATT L FING / TATT R FING . . . . . . DRUGS COCAAINE 03/02/91 13GA/13791/90 . . F/IMPERS ATTENDS GAY CLUB 03/02/91 13FB/1384/91 . . . . DRIVER NUMBER: RICHA/609199/AF9NF . . LAST KNOWN ADDRESS . . 294A, HIPPERHOLME ROAD, BRIGHOUSE HX7 5TN . . HOME FORCE: 13 WEST YORKSHIRE . . INF POLICE: OFF BAIL . . . . NOMINAL OWNER: 13HQ RECORD LAST UPDATED: 03/02/91 14:51 . . . . . . PAGE WM... (ENTER 'DF' IF REQUIRED) ABANDON TRANSACTION? N . ........................................................................ < TO BE CONTINUED... > --------------------------------------------------------------------------- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + PHATE MAGAZINE. VOLUME ONE. ISSUE TWO. FILE 7 OF 9. + + + + "NUARDIALER V2.0A NETWORK SCANNER" + + BY NeUR0NoM/PHATE + +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ --------------------------------------------------------------------------- NUArdialer Version 2.0A Documentation --------------------------------------------------------------------------- ANOTHER TRIPPLE-PHAT -PHATE- RELEASE! --------------------------------------------------------------------------- !ALL RIGHTS OF THE HARDCORE RESERVED! ------------------------------------- Disclaimer: These things are pretty popular arent they? Well here it is: I, the creator of this soft, take no responsibility for its usage what- soever, no how, no way... Dont come crying to me about anything! I wrote this as an experiment and nothing else... Its yr own damn business what you do with it and I dont wanna know anyways.. WHAT IT IS: ----------- Okay, now that bits over with... i'm happy to release this fine product NUARdialer Telenet Scanner. Version 2.0a. This proggy is a lil' AREXX script for use with the worlds sorriest term program in the world: BAUDBANDIT II V2.X Gee, whyd you make it for such a naff term anyways? Well, as i have yet to find a great term program that is actualy usefull to me and completely bug free, and as well has an AREXX port, i made it for this little 50k term program... You can stick it (the term) wherever, and not worry about its config file... no fuss no muss.. I'm still using Jr-Comm myself, because Term V2.4 RANKS, is too slow and buggy, and i havent checked out the lastest X-Comm, and Terminus hasnt been released bug free. If there really is a need, or a request, i will write this scanner for the popular vote. Besides, it was the first term when i started writing this thing that didnt give me trouble just outputing somthing to screen... anyways... THE SPECS: ---------- I have really no idea how amazingly fast that this scanner works. It will do the standard deal depending on how many connections you get.. the more connections, the slower it will take to scan through the area (because connecting to a system, and disconnecting takes 3 times as long as getting an error message and continuing). The program is sufficently fast however, and you should hav no problems scanning through an area over night... To note, this scanner is not soley capbable of scanning telenet dnics. As you should know, you can reach many other networks through telenet, and these networks are equally scannable with this programm. Of course however, not all networks are reachable and those that are not give contant REFUSED COLLECT CONNECTION responses. FEATURES: --------- 1. CONFIGURATION FILE FOR AUTOMATED STARTUP 2. CONFIGURATION FILE THAT REMEMBERS YOUR TELENET DIALUP 3. SMART PATHS THAT SEND THE SAVE FILE TO WHATEVER PATH YOU SELECT 4. RECORDS ALL CONNECT, REFUSED COLLECT CONNECTION, AND BUSY RESPONSES 5. ORGANIZED OUTPUT FILE THAT MAKES RE-EDITING QUICK AND EASY HOW TO USE IT: -------------- Okay, well, the basic opperation of the scanner depends on two text files entitled NUARDIALER.CFG1 and NUARDIALER.CFG2 respectively. You can run the scanner without CFG2 but you CAN'T run it witout CFG1. Both of these files need to be in your SYS:S directory. NUARDIALER.CFG1: ---------------- This file contains two items. on the first line is the modem dial string to connect to Telenet. This can be whatever you use to connect including commas, disable call waiting commands... any acceptable AT command is valid here. The second line of this file is where to store the output text. This does not include a directory slash at the end. For example, DH3:HPA/CAPTURE would be correct, whereas DH3:HPA/CAPTURE/, will not work. AN EXAMPLE OF THE CONTENTS OF NUARDIALER.CFG1: ---------------------------------------------- ATDT*70,18002220555 <- THIS IS THE MODEM DIAL STRING DH3:HPA/PHILES/CAPTURE <- THIS IS THE PATH TO SAVE TO. Of course the items including <- and after are not in the file, but you understand that. Make sure that each line concludes with a carriage return, otherwise the scanner will read the two lines as one entire line. If this file is not pressent in the S: directory, the program will prompt you to enter this information and ask you if you want to save it to your S: directory. NUARDIALER.CFG2: ---------------- This file is not really as important as CFG1, but still important for quick automation. It contains on 5 lines the various characteristics about the DNIC and area you are going to scan. Before I go further into this configuration file, I will briefly explain the format of most NUAS and how the NUA itself breaks down into seperate parts. we will take one nua, 3110 202 00202. \__/ \_/ \___/ \ \ \__ NETWORK ADRESS \ \______ AREA PREFIX \_________ DNIC The DNIC denotes what country, and more specificly, what network you are reaching. The AREA PREFIX denotes a specific area, or a specific segment of the network acording to landmass or corporation both, or niether. Suffice it to say, that it is a subgrouping of the DNIC. The NETWORK ADRESS is node number that coresponds to one particular computer connected to the network. ** QUICK NOTE: normally, to connect to a Telenet adress through telenet you would not need to enter the DNIC, but it does not matter if you do. This program always requires a DNIC so if you are going to scan telenet, use Telenet DNIC: 3110. To conclude, most all of the networks NUA configurations are differnt it is up to you to discern where the area starts and ends, and where the network adress continues. The DNIC is ALWAYS the first 4 digits of the NUA.. if someone finds this to be different let me know, I would be very suprised. For Telenet and DataPac, the area is almost always a three digit number, I am not sure about other NUAS area prefix length, but I can be pretty sure that they are all the same size relative to the network they are on.. for example if you were scanning Finland, with a DNIC of 2442, AREA PREFIX was 02, and a NETWORK ADRESS of 223 the rest of the area prefixs would be 2 digits long, and the network adresses would be three digits long. The lengths are ususaly dependant on the relative size of the network. Okay, now that that is over with, the firstline of the file NUARDIALER.CFG2 is the DNIC, whatever DNICS that are reachable through Telenet are valid, for example: 3110 TO SCAN TELENET ADRESSES 3020 TO SCAN DATAPAC ADRESSES 7305 TO SCAN VTRNET ADRESSES Those are just a few that are reachable through telenet. of course you can still only connect to the ones that accept collect charges, but the scanner will still record the ones that wont. The second line of the file is the area to be scanned, this is the number as stated above that denotes a certain area or subdevision of the network. This number can start with a zero, but must always end with an interger. For example: 203,025,974,332,02,234,723,802. You get the idea... do not include zeros at the end of the area, that zero does not belong to the area, but rather the adress. Remember, you always know that the DNIC is the first four digits, deciding where the area starts and ends and where the network adress starts is all that is left. This is very easy when it comes to some NUAS, like Telenet or DataPac, but when you look at for example, some of the UK NUAS.. sometimes not one digit will be zero. In this case, my best advice to those not experienced with the networks, is just simply to compare NUAS of the same DNIC. You will start to see similarities and from there you can make logical estimations. The third line of this file is the total number of digits that folow after the adress. The reason for this number is so that the maximum amount of adresses can be scanned through.. I can not just assume that there will always be a 3 digit area, 2 zeros, and then a 3 digit adress. As you've seen, differnt NUAS have different configurations. Just count the number of digits that fall after the area, and that is the number here. For example, 302097500123 has a 5 digit area ___ \___/ / \_______________________/ The next line is simple, what area to start at. And the line after that the fith and final line, is where to stop at. Neither of these numbers require leading zeros, simply think of the area prefix as a number from zero to 99999, and enter is accordingly. AN EXAMPLE OF THE CONTENTS OF NUARDIALER.CFG2: ---------------------------------------------- 3020 <- The DNIC 974 <- The AREA PREFIX 5 <- The length of the NETWORK ADRESS in digits 200 <- What adress to start at 1000 <- What adress to finish at. ** SOME NOTES ABOUT CFG2: If this is set up in your S: directory, the program will automaticly dial telenet and start scanning when you run the arexx program. You can run the program without the file in your S: directory, the program will ask you for the information that would normally be loaded from the file, save it to your S: directory, and then begin scanning. THE CLOSING BITS: ----------------- Well, that really about rapps it up. I hope everyone enjoys this simple to use AREXX scanner, and I encourage others to start programing their own AREXX utils. AREXX is really a fantastic language, and its an instant Amiga Basic beater... One last note about this program, it will create a file for you in the directory you specify whos name is dependant on what your scanning. For example, if your scanning 3020 207 000 - 050, then it will create a file called 3020207.SCAN. This makes keeping track of all your scans nice and simple. If you have any bug reports send them to me on Hanger 18. If this file is removed from its original publication, ask the "elite" they know the number. And coincidently, as this is an arexx program and fully editiable it gives you the owner chance to screw it up... ie re-program it. So go ahead I suppose, but please give credit and respect to me when its due. Also, this program is dedicated to Ronnie, who I have have been promising a copy to for about a month.. sorry it took so long m8!! THE GREETINGS BITS: ------------------- Phresh Greetings go out to all corners of the lands, to all of the PHATE all the Hanger & DT crews, who know who they are, and I want to extend a special greet to SCSI, who I believe, and I think I speak for most, to be one of the coolest guys in the scene. SCSI man, yr the kind of person the scene needs more of! THE STOP READING THIS BIT: -------------------------- Respect to those who deserve it.. L8tr..! /* CUT HERE - CUT HERE - CUT HERE - CUT HERE - CUT HERE - CUT HERE - */ /* NUARDIALER. V2.0 1993 -_NeUR0NoM_- COMIN' ON STRONG! */ /* SUBVERSION (A) FOR USE WITH BAUD BANDIT II V2.XX */ /* A -_PH/\TE - PRODUCT, COMMIN' IN SLOW AND LOW IN 1993 */ MAIN: CALL SETUP() CALL GETINPUT() CALL OPENFILES() CALL DIALTELENET() DO NUACOUNT = COUNTSTART TO COUNTEND RETRYCOUNT = 0 CALL ENTERNUA() CALL GETRESULTS() CALL CHECKERROR() CALL CHECKNUA() END SIGNAL DONE() SETUP: ADRESS "BAUD" /* SET AREXX PORT FOR BAUDBANDIT */ SET 7E1 /* SET SERIAL DEVICE PARAMS */ BAUDRATE 1200 /* SET BAUDRATE TO 2400 BAUD */ QUIET OFF /* INSURE SERIAL COMMUNICATION */ OPTIONS RESULTS /* TURN ON RESULTS OPTION */ BUSY = "NO" /* SETUP INITL VALUE OF WAITCHECK */ RETRYCOUNT = 0 /* SETUP # OF BUSY RETRIES TO ZERO */ SEND "\AW" /* CLEAR SCREEN */ SCRATCH = "X" /* THIS IS A COSMETIC FOR OUTPUT */ RETURN OPENFILES: IF EXISTS("SYS:S/NUARDIALER.CFG1") THEN DO CALL OPEN IN, "SYS:S/NUARDIALER.CFG1" TELENET = READLN(IN) OUTPUTF = READLN(IN) IF EXISTS(OUTPUTF"/"DNIC""AREA".SCAN") THEN DO CALL OPEN OUT,OUTPUTF"/"DNIC""AREA".SCAN",APPEND END ELSE DO CALL OPEN OUT,OUTPUTF"/"DNIC""AREA".SCAN",WRITE CALL WRITEHEADER() END END ELSE DO SAY " " SAY "WARNING: FILE 'NUARDIALER.CFG1' MISSING FROM S: DIRECTORY" SAY "DO YOU WANT TO CREATE THE CONFIGURATION FILE NOW?" OPTIONS PROMPT "ENTER (YES/NO) :" PULL RESPONSE IF (RESPONSE="YES"|RESPONSE="Y") THEN DO QUIET ON SET DUPLEX HALF CALL OPEN OUT,"SYS:S/NUARDIALER.CFG1",WRITE SAY " " SAY "ENTER THE DIALING SEQUENCE THAT YOU PERSONALY" SAY "USE TO ACCESS TELENET/SPRINTNET." SAY " " SAY "EXAMPLES: ATDT*70,4540218 OR ATDT18005461000" SAY " " PULL TELENET SAY " " SAY "ENTER THE PATH THAT YOU WANT TO STORE THE " SAY "SAVE FILE TO. EXAMPLE: DH0:S OR DH3:HPA/STORAGE" SAY "DO NOT PUT A DIRECTORY SLASH AT THE END." SAY " " OPTIONS PROMPT "ENTER PATH :" PULL OUTPUTF SAY " " CALL WRITELN OUT,TELENET CALL WRITELN OUT,OUTPUTF CALL CLOSE IN CALL CLOSE OUT QUIET OFF SET DUPLEX FULL IF EXISTS(OUTPUTF"/"DNIC""AREA".SCAN") THEN DO CALL OPEN OUT,OUTPUTF"/"DNIC""AREA".SCAN",APPEND END ELSE DO CALL OPEN OUT,OUTPUTF"/"DNIC""AREA".SCAN",WRITE CALL WRITEHEADER() END END ELSE DO SIGNAL DONE() END END RETURN GETINPUT: SAY "NUARDIALER. V2.0 1993 -_NeUR0NoM_- COMIN' ON STRONG!" SAY " " IF EXISTS("SYS:S/NUARDIALER.CFG2") THEN DO CALL OPEN IN, "SYS:S/NUARDIALER.CFG2" DNIC = READLN(IN) AREA = READLN(IN) LENGTH = READLN(IN) NETADRESS = READLN(IN) COUNTEND = READLN(IN) COUNTSTART = NETADRESS CALL CLOSE IN SAY " " SAY "DNIC :"DNIC SAY "AREA PREFIX :"AREA SAY "NET ADRESS LENGTH :"LENGTH SAY "START ADRESS :"NETADRESS SAY "END ADRESS :"COUNTEND SAY " " OPTIONS PROMPT "USE THESE DEFAULTS ? (YES/NO) :" PULL RESPONSE SAY " " END IF (RESPONSE ~= "YES"|RESPONSE ~="Y") THEN DO OPTIONS PROMPT "ENTER DNIC :" PULL DNIC /* GET DNIC FROM KEYBOARD */ OPTIONS PROMPT "ENTER AREA PREFIX :" PULL AREA /* GET AREA PREFIX FROM KEYBOARD */ OPTIONS PROMPT "NET ADRESS LENGTH :" PULL LENGTH /* GET NUMBER OF DIGITS AFTER AREA */ OPTIONS PROMPT "ENTER START ADRESS :" PULL NETADRESS /* GET FIRST ADRESS TO START AT */ OPTIONS PROMPT "ENTER STOP ADRESS :" PULL COUNTEND /* GET LAST ADRESS TO END AT */ OPTIONS /* RESET OPTIONS */ OPTIONS RESULTS COUNTSTART = NETADRESS CALL OPEN OUT,"SYS:S/NUARDIALER.CFG2",WRITE CALL WRITELN OUT, DNIC CALL WRITELN OUT, AREA CALL WRITELN OUT, LENGTH CALL WRITELN OUT, NETADRESS CALL WRITELN OUT, COUNTEND CALL CLOSE OUT END RETURN WRITEHEADER: CALL WRITELN OUT,"NUARDIALER. V2.0A | 1993 -_NeUR0NoM_- COMIN' ON STRONG!" CALL WRITELN OUT,"---------------------------------------------------------" CALL WRITELN OUT,"RANGE: "DNIC" "AREA" "LEFT(SCRATCH,LENGTH,"X")" | DATE: "DATE("N")" TIME: "TIME("C") CALL WRITELN OUT,"---------------------------------------------------------" RETURN DIALTELENET: SAY " " SAY "DIALING TELENET." SAY " " TIMEOUT 25 SEND TELENET"\R" /* DIAL TELENET */ WAIT "CONNECT 1200/ARQ" TIMEOUT 1 /* WAIT FOR A FEW SECONDS */ WAIT SEND "\R\R" SEND "A5\R" /* SET TELENET TERMINAL TO D1 */ TIMEOUT 5 /* SET TIMEOUT BACK TO 10 SECONDS */ WAIT "@" /* WAIT FOR TELENET COMMAND MODE */ RETURN ENTERNUA: NUA = "C 0"DNIC""AREA""RIGHT(NETADRESS,LENGTH,"0")"\R" SEND NUA RETURN GETRESULTS: TIMEOUT 5 SIGNAL ON BREAK_C OPTIONS RESULTS WAIT "0A"X WAIT DNIC IF (RC = 0) THEN DO PULL = "YES" PULL YDNIC XDNIC RESULTCODE . . . . END BREAK_C: PULL = "NO" RETURN CHECKERROR: IF (YDNIC ~= DNIC) THEN DO IF (PULL = "YES") THEN DO PULL = "NO" SEND "\R" SEND "@\R" SEND "D\R" WAIT "@" IF (RC = 1) THEN DO CALL REDIAL() END SEND "D\R" WAIT "@" IF (RETRYCOUNT <=2) THEN DO CALL ENTERNUA() CALL GETRESULTS() END END ELSE DO SEND "\AL" SEND "D\R" WAIT "@" IF (RETRYCOUNT <=2) THEN DO CALL ENTERNUA() CALL GETRESULTS() END END END RETURN CHECKNUA: IF (RESULTCODE = "CONNECTED"|RESULTCODE="REFUSED"|RESULTCODE="BUSY") THEN DO BEEP /* SEND A BEEP TO THE SCREEN */ IF (RESULTCODE = "CONNECTED") THEN RESMES = " CONNECTED "CONNECTEXT IF (RESULTCODE = "BUSY") THEN RESMES = " BUSY" IF (RESULTCODE = "REFUSED") THEN RESMES = "$ REFUSED COLLECT CONNECTION" CALL WRITELN OUT," "DNIC AREA" "RIGHT(NETADRESS,LENGTH,"0")" "RESMES IF (RESULTCODE="CONNECTED") THEN DO SEND "\R" /* AFTER WRITING FOUND HOST TO */ SEND "@\R" /* OUTPUT FILE, DISCONNECT */ WAIT "@" /* AND CONTINUE SCANNING. */ IF (RC = 1) THEN DO CALL DIALTELENET() END SEND "D\R" WAIT "@" END END NETADRESS = NETADRESS + 1 RETURN DONE: SEND "HANGUP" /* TELL TELENET TO HANGUP */ SEND "\AH" SEND "\R\R\R" SAY "DNIC "DNIC" AREA "AREA" SCANNED." SAY "TELENET SCAN ENDED. SHUTTING DOWN." SAY " " EXIT /* CUT HERE - CUT HERE - CUT HERE - CUT HERE - CUT HERE - CUT HERE - */ --------------------------------------------------------------------------- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + PHATE MAGAZINE. VOLUME ONE. ISSUE TWO. FILE 8 OF 9. + + + + "HELPFUL INFORMATION SOURCES IN THE UK" + + BY SLYCATH/PHATE + +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- HELPFUL INFORMATION SOURCES IN THE UK =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= ONLINE HOSTS ------------ These are the organisations through which individual databases are obtained. -------------------------- Dialog Information Service PO BOX 188 Oxford OX1 5AX (0865)-730-275 -------------------------- FT Profile PO BOX 12 Sunbury on Thames Middlesex TW16 7UD (0932)-761-444 -------------------------- Maxwell Online (ahahaha) Achilles House Western Avenue London W3 0UA (081)-992-7335 -------------------------- Reuters Textline 85 Fleet Street London EC4P 4AJ (071)-250-1122 -------------------------- BT Managed Network Service Network House PO Box 402 Hemel Hempstead HP3 9XT (0800)-200-700 -------------------------- Nexis International House St Katherines Way London E1 (072)-488-9187 -------------------------- Istel-I-Net PO Box 1488 Redditch Worcestershire B98 8PD (0527)-285-150 -------------------------- Compu$erve PO Box 676 Bristol BS99 1NZ FREEPHONE Compu$erve -------------------------- CREDIT DATABASES ---------------- The following are various Credit Databases for which you 'must always' (hehe) pay lots of money to get the information. Please note these are not accessable online databases to you, you get the computer operator to give you the information you require, i.e. there is great opening for those amongst you, who, like me take great pleasure out of social engineering stints. -------------------------- InfoLink Coombe Cross 2-4 South End Croydon CR0 1DL (081)-686-7777 -------------------------- InfoCheck Scrutton Street London EC2R 4RQ (071)-377-8872 -------------------------- CCN Systems Ltd. Talbot House Talbot Street Nottingham NG1 5HF (0602)-410-888 -------------------------- Dun & Bradstreet Intl. Holmers Farm Way High Wycombe Bucks HP12 4UL (0494)-422-154 -------------------------- TELEPHONE NUMBERS ----------------- This is the best place for obtaining peoples information which relates to the telephone network. This is much deeper than your Directory Enquiries Facility and hence costs a Bomb! -------------------------- Phone Base British Tele$cum Tinsley Park Computer Centre Units 1,2 & 3 Tinsley Park Close Sheffield S9 5DE (0800) FUCK THE NUMBERS GONE NOW WHERE DI I PUT IT ? PLEASE LOOK FOR AN ADDENDUM IN PHATE ISSUE 3........... -------------------------- [SLYCATH'93 FOR PHATE] --------------------------------------------------------------------------- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ + PHATE MAGAZINE. VOLUME ONE. ISSUE TWO. FILE 9 OF 9. + + + + NEWS AND REVIEWS + + BY NeUR0NoM/PHATE & Janx/Poison/PHATE + +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ * PHATE NEWS AND REVIEWS * PHATE NEWS AND REVIEWS * PHATE NEWS AND REVIEWS * ** This file was not written by PHATE, and unfortunately is of unknown origin. We make every attempt to cite an author of any news item. ** 800 Number Portability FOR IMMEDIATE RELEASE: BASKING RIDGE, N.J. -- After 25 years of growth and innovation, toll-free calling will soon face another change: "portable" 800 numbers. Portability means that for the first time companies with established 800 numbers will be able take their numbers with them if they decide to change long distance companies. And, any new 800 number application can obtain service from any company. Until the advent of portability, customers were unable to change long distance companies without changing their 800 number. As of March 1993, they will be able to keep their number and seek out the long distance company offering them the best value in terms of reliability, quality, features, service and cost. However, customers are not required to take any action in connection with portability. Their 800 service will remain with their chosen long distance carrier unless they decide to change. Portability will give customers greater freedom of choice and will allow AT&T reduced regulation. AT&T expects this will speed the introduction of new services to the marketplace. In a 1991 ruling, the Federal Communications Commission ordered that portability begin by March 4, 1993, to increase competition in 800 services. "In reality, the market is highly competitive today," said Shaun Gilmore, marketing vice president for AT&T 800 Services. "In fact, our studies show that 80 percent of all 800 numbers in use today have come into existence since the advent of competition in 1987. And, because we have the best value, customers continue to overwhelmingly choose us." Gilmore said that only half of the existing "vanity" numbers are AT&T's and sees portability as an opportunity to attract customers who now get 800 services from competing carriers. He went on to say that it's clear carriers were chosen, at times, for the vanity number they had rather than for their superior value. AT&T studies indicate that many of those customers can't wait to switch to AT&T. "We believe that while 800 numbers are portable, the quality, reliability and innovation of AT&T 800 Services are not," said Gilmore. "Customers who previously used other 800 services can now change to AT&T." To make portability a reality, local and long distance telephone companies are spending hundreds of millions of dollars for the necessary changes and additions to their networks. Although the work has begun, it will not be complete for several years. While these changes are being made, some 800 calls may take a few seconds longer to be connected. When the work is finished, however, most calls should go through more quickly than they do today. And, AT&T is committed to delivering the fastest call set- up time in the industry. The new technology will also make it possible for telephone companies to handle calls more efficiently. In addition, it is expected that portability will provide AT&T some regulatory relief that will enable AT&T to offer new integrated services and even more features tailored to the different needs of individual telephone customers. * PHATE NEWS AND REVIEWS * PHATE NEWS AND REVIEWS * PHATE NEWS AND REVIEWS * ** This file was not written by PHATE, and unfortunately is of unknown origin. We make every attempt to cite an author of any news item. ** 800 Number Portability: AT&T's Perspective Background: In 1967, AT&T launched toll-free calling as an innovative way for large businesses to receive collect calls from their customers and suppliers. The service was viewed initially as a technological convenience with limited appeal. Since then, new technology and marketing techniques have turned 800 Service into a $7 billion industry. AT&T invented the technology for toll-free calling and the network architecture to support it. AT&T's system enabled local telephone companies to handle 800-number calls quickly and easily by having its switching equipment look at the first few digits a customer dialed. Identifying it as toll-free service, the call was immediately routed to one of AT&T's network-based computer databases for instructions on completing the call according to specific customer directions. In the mid-eighties, other long-distance companies began to enter the 800 market. To accommodate their entry, Bellcore, as the administrator of the North American Numbering Plan, assigned to each company a discrete set of 800 numbers for their respective customers. By screening the first six digits dialed, the local telephone company could pass the call to the appropriate long distance company for completion. Although this network architecture afforded other long distance companies access to the marketplace, it required a stable number base to operate effectively. An 800 customer could switch from one long distance provider to another, but the customer would have to accept a new 800 number from the set assigned to the new long distance provider. Because 800 numbers were sometimes promoted widely, and because some numbers were chosen because they could spell out an easily-remembered word or phrase (e.g., "800- FIND ATT"), some customers wanted to be able to use an 800 number assigned to them and have the freedom to choose the long distance company that gave them the best service and value. On September 4, 1991, the Federal Communications Commission (FCC) issued an order (FCC Docket 86-10) requiring the Regional Bell Operating Companies (RBOCs) and GTE to deploy the technology necessary to allow 800 number portability. The FCC directed the industry to complete this structure by March 4, 1993, subject to certain call set-up time delay standards. This FCC mandate is commonly referred to as "800 Number Portability" because the 800 number itself becomes portable from one long distance company to another. A Colossal Effort: The implementation of this new network architecture, although full of technological promise, is rife with operational challenges involving the integrity of 800 service. This is not to suggest that the task is so big that it can't be done; but it must be done in a very precise manner to ensure that each and every customer's calls will continue to be completed promptly and reliably. Hundreds of millions of dollars will be spent by the local and long distance companies to implement the changes to the network that are necessary to make portability a reality. At the heart of this new network, the local telephone companies are installing equipment to support SS7. The transition to SS7 may take another two years due to some technical limitations within the local telephone companies. Until that happens, callers may face increased delays in completing their 800 calls. Many customers are concerned because the delays will cause some callers to abandon their calls before they are completed, and lost calls translate into possible lost revenue. To reduce the customer's potential for any call connection delays, AT&T has ordered state-of-the-art SS7 connections wherever available. Where these preeminent connections are made directly to the local telephone company offices, callers may in fact experience quicker connection times than today. The nationwide 800 network architecture is built on the local telephone companies' new ability to determine which long distance company is serving a particular 800 customer. To accomplish this task, the local telephone company must look at all ten digits dialed and compare that number against a centralized database. It then sends the call to the appropriate long distance company, or, it may follow pre-subscribed routing directions as originally determined by the subscriber. The work required to accomplish this is considerably more complex than it might first appear. Communications networks are often described as high-tech, silicon highways that carry calls like the nation's highway network handles traffic. Updating either infrastructure requires a major overhaul. And that's what's happening today with the implementation of a common, nationwide signaling network (SS7) to accommodate 800 number portability. Essentially, each of the long distance companies has to connect its network to precise locations identified by the local telephone companies. These Signaling Points of Interface (SPOIs) may be thought of as bridges needed to connect the local telephone facilities to long distance telephone facilities. The industry must build these bridges, and all their connecting roads, while traffic continues to flow over them. One mistake, or misconnection, and thousands of calls could go uncompleted. To the subscriber of the service this means lost revenue opportunities. For AT&T's part, it has to move and connect more than 1.1 million lines to accomplish signaling connections to the local telephone networks around the United States. AT&T is tackling this monumental task while connecting some 140 million telephone calls each business day. All while maintaining the the quality and reliability of service and the call completion rates AT&T customers have come to expect. Administrative Hurdles: Just as there are technological feats to overcome, the operational issues associated with establishing a new system in the post-portability environment are equally challenging. In the past, the administrative functions of 800 service rested with individual long distance companies. Once a customer placed an order, it was up to the carrier to assign a number and to provide and maintain that service. The new post-portability environment calls for a centralized database and operational support system called the Service Management System (SMS). SMS will enable all long distance companies to reserve, activate, and deactivate 800 numbers. This database will contain the records for all 800 service customers nationwide. These records will then be shared with local telephone companies' systems so they can switch calls to the proper long distance company for completion. NASC: The Number Administration and Service Center (NASC) will provide the centralized administration for this 800 database access approach. It will perform two basic functions: o the assignment of 800 numbers; o and, the resolution of problems that may surface between the organizations representing 800 customers and the long distance companies. Currently, Bellcore is seeking an independent third party to perform these functions under long-term contract. Until a suitable organization can be identified, Bellcore will act as the administrator. RESPORGs: The term "Responsible Organization," or "RESPORG" for short, was adopted by the industry to identify a customer's primary point of contact for a given 800 number. The industry agreed that only this designated entity will be authorized to make SMS changes for a given customer's 800 application. This basically means that it is the RESPORG that will reserve 800 numbers, create and update customer-specific records, and support maintenance activities such as tracking and clearing troubles. The RESPORG clearly provides an important function. To date, there is no industry agreement as to which parties should be permitted to perform the RESPORG function. In many cases, it will be the customer's long distance carrier. However, since more than one carrier may provide services to a customer, the RESPORG responsibilities and duties must be clearly agreed upon. There is general consensus among the long distance companies that customers should not perform this function themselves because the carriers need to know of changes that may affect traffic flows. Without this knowledge, long distance carriers would face difficulty in designing, sizing, and maintaining their networks. Further, AT&T believes that the NASC also should be disqualified from RESPORG consideration if it is to remain the neutral third party that it is designed to be. To date, various scenarios surfaced, but none which have garnered universal appeal. It is AT&T's position that only purchasers of access may perform RESPORG functions for interstate 800 services. To allow anyone else to perform this function could potentially interfere with the relationship between a long distance company and its customer. AT&T does however recognize that the need may exist for a long distance company to authorize a third party to perform these functions as an agent on their behalf. AT&T believes that this will accommodate those smaller long distance companies that don't have the systems to perform these functions themselves. The FCC is expected to rule on the RESPORG issue shortly. Service Features: The transition to ten digit screening is the basic technology that will en