Beijing Paradise BBS Backup

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

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / CLBKV352.ZIP / CALLBK.DOC < prev next >

Wrap

Text File | 1993-12-07 | 22.0 KB | 576 lines

┌───────────────────────────────────────────────────────────────┐ │ W E L C O M E to... MYCALBK version 3.45 │ │ │ │ The callback verifier door for RBBS-PC sysops worldwide. │ │ │ │ Copyright (c) 1991-1993 SteveSoft Software. USA. │ │ │ │ All Rights Reserved. │ │ │ └───────────────────────────────────────────────────────────────┘ There has long been a need for a dedicated call back verification program for RBBS sysops. Until now, there were a few that were relatively well programmed, however, after having tried two or three of them, and after having determined that they didn't quite meet my expectations, I felt it necessary to create one. The result is the program that you, the RBBS sysop, will shortly have fully operational on your system. RBBS has long had the ability to allow the use of a verification door built-in, or more accurately, a registration door. This program, MYCALBK takes full advantage of that RBBS ability. CALLBK is small, fast, and above all, reliable. It will run on any IBM system, or compatible computer on which you operate your RBBS (INCLUDING a LAN and DESQVIEW). It will detect DesQview and give up time slices accordingly. Also, it will detect a paper out condition if you are printing your logs and continue without "hanging" the system. It will take some time for you to edit the sysop configurable files which are described in more detail later in this documentation. Other than that, it should be fully operational on your system in about 10 minutes! In RBBS-PC v17.3C, and RBBS v17.4 CONFIG PARAMETER 107 is used to tell RBBS-PC what the door name is to check new users at log-in. For example, I use "F:\RBBS\DOORS\VALIDATE.BAT" CONFIG PARAMETER 108 is the parameter to tell RBBS-PC "This security level AND lower, must be sent to the above named door". For example, I have it set to level 30. Everyone is at level 30 on my RBBS until they are called back with the verifier. The verifier can easily be setup to increase the callers' security level when a given caller has responded successfully to the callback question, and has been logged back into your RBBS. Installation of MYCALBK is pretty much straight forward and should cause no difficulty for most experienced sysops. If you are a 'freshman' RBBS sysop, I strongly suggest that you read this entire document to obtain maximum performance of the CALLBK program. The following describes the required files and their purposes. The batch file needed to call CALLBK from RBBS... ────────────────────────────────────────────────── This example assumes that you are using XU.EXE and it reflects the lines about XU.EXE as shown... You can name the following as CALLBACK.BAT just as a reference when you are looking through the dozens of BAT files on your system. ──────────────────────── The VALIDATE.BAT file... ──────────────────────── @echo off cd \rbbs\doors\mycalbk Mycalbk %1 cd \rbbs :DONE The VERx file is a SEMAPHORE file to allow you to create an Auto-welcome message for your new user. I use MSGFORM.EXE but you may use something different, OR process the new user differently. Possibly "tossing" the user into another door (Now that you know they are who they say the are). TIPS: 1). Do not use a .BAT file named VERIFY as DOS will not execute it. (VERIFY is a DOS keyword.) 2). If you are using WATCHDOG or some sort of carrier watchdog, DISABLE it when running this program! This program DISCONNECTS the caller in order to call back. If you have WATCHDOG (or a similiar program) enabled, watchdog will REBOOT your machine instead of MYCALBK calling back. ─────────────────────────────────────────────────────── The Configuration files and samples... ─────────────────────────────────────────────────────── ──────────── MYCALBKx.CFG (Where 'x' = node number). ─────────── F:\rbbs YELLOW F:\bulletin\b1 ATE1V1Q0X4 00000 Line 1 = Path to your RBBS DORINFOx.DEF file. Line 2 = Background Color of "desktop". (BLACK or BLUE not recommended!). Line 3 = Path to ASCII bulletin...(not used but necessary). Line 4 = MODEM init string to get "OK" out of it. Line 5 = Registration code. The five (5) zeros * MUST * be there! When you register MYCALBK you will receive a registration key which you type in place of the five (5) zeros. The five zeros simply put a small message on the monitor that this copy is not registered. When you do get around to registering, I will send you a registration key which will then put a message on the monitor that you have registered this copy, along with the name of your RBBS. Please see the information about registering near the end of this document. ────── SL.CFG * NOTE * SL.CFG is: Security level configuration. ────── If you do not have a security listed 30,60,30 here, MYCALBK will NOT upgrade thier 65,65,65 security. 60,60,30 Parameter 1 = ENTRANCE security (what they will be when they get here). Parameter 2 = PASS security (what to upgrade to if they pass). Parameter 3 = FAIL security (what to drop them to if they fail). ──────── LDSL.CFG * NOTE * LDSL.CFG is: Long distance security level cfg. ──────── 30,61,30 65,65,65 Parameter 1 = ENTRANCE security (What they will be when they get here). Parameter 2 = PASS security (what to upgrade to if they pass). Parameter 3 = FAIL security (what to drop them to if they fail). If you enable LD calls, you MUST have this file. Otherwise your callers SECURITY LEVEL will be set to 0 (zero) when they return. It allows you to "bump up" LONG DISTANCE callers so they have more time on-line (Some SysOps prefer their long distance callers to have an extra 15 minutes on-line. After all, they are calling long distance to visit your RBBS). If you do not like that, then just set it the same as SL.CFG. ──────────── AREACODE.CFG ──────────── 803,0000,2359,1 919,1800,0800,1 Parameter 1 = areacode approved for call back. Parameter 2 = time to START call backs...(no colons, 24hr time!). Parameter 3 = time to STOP call backs...(no colons, 24hr time!). Parameter 4 = hang up flag. 1 = hang up after verify. 0 = stay on the line (at YOUR expense!). First areacode * MUST * be YOUR area code! Don't make an error here! (Please note, if the supplied AREACODE.CFG file does not contain all United States areacodes, please let me know so I may add them in future releases). ──────────── LCLXCHNG.CFG *NOTE* LCLXCHNG.CFG is: Local exchanges cfg. ──────────── 393 332 669 665 Local exchanges are ones that do NOT require a '1-' in front of them and are in your areacode. If you operate in an area of the country that enables you to dial to another areacode and it still is a local call, you may not want to include this .CFG file. Instead, use the ###XCHNG.CFG explained below. ─────────── ###XCHNG.CFG *NOTE* ###XCHNG.CFG is: The area code is ### and the ─────────── exchanges inside this .CFG file 395 are local calls. Another fine problem to deal with with the "BELLS". Apparantley in some portions of the country, you can dial to more than one area code and it's a local call. So to handle this problem, I have created this .CFG file. If you have defined an exchange in LCLXCHNG.CFG that is NOT in your areacode, remove it from there and enter it in this file. This will allow local calls made across area codes to be made without the program "thinking" they are LD and restrict them. Also, if you are having some difficulties getting CALLBACK to work properly, try renaming LCLXCHNG.CFG to ###XCHNG.CFG (where ### is YOUR areacode). This should straighten out the problem. ─────────── LDXCHNG.CFG *NOTE* LDXCHNG.CFG is: Long distance exchanges cfg. ─────────── 803,1800,0700,1 919,1800,0700,1 LONG DISTANCE exchanges in YOUR state (USA) or province (Canada) that you want to call back to. Parameter 1 = exchange number Parameter 2 = start time...(military time. NO COLONS!) Parameter 3 = end time.....(military time. NO COLONS!) Parameter 4 = hang up flag. 1 = hang up after verify. 0 = stay on the line (at YOUR expense). ─────────── NO-1AC.CFG *NOTE* NO-1AC.CFG is: Area codes that do NOT require ─────────── a 1- in front of the number! 803 What the Bells have done now is this... They make it MUCH easier for you to call Long Distance by now not telling you it's Long Distance! This I feel is wrong, but we have to deal with it! Let's say you have configured a Long distance area code in the ABOVE .CFG file. Now, you can call Long distance to that area code without a 1! So, add it into this .CFG file here. It must be 1 of 2 things. YOUR base areacode or Areacodes defined in the LDXCHNG.CFG file! That's it. ──────────── TRASHCAN.DEF ──────────── ###-###-#### This is to specify any numbers you do NOT want dialed period! If you put 803-###-####, no numbers in areacode 803 will be dialed. ###-6##-#### will NOT dial any exchanges starting with 6 in ANY areacode. There is no need to put 900, 911, or 976 as MYCALBK stops people like that before it would even get to this point. MYCALBK 4 ^ Node number even if you only run 1 node! See the CALLBACK.BAT sample file which will make this clear to you. Command line switches... ──────────────────────── MOST command line switches are no longer needed. You only need to pass the node that is executing the door. Command line switches have been replaced with a ###.SWI file where ### is the node number executing this door. There are 2 command line variables to pass to MYCALBK. 1). The node number executing this copy. 2). A special feature called DIALBACK. When you place /DIALBACK on the command line, MYCALBK expects 2 things. A). The users name in the VERIFIED.LOG (Another words, they've already been verified). B). The user on the other end knows he/she's going to be hung up on and called back. Why /DIALBACK? Some people live in an area that the user is long distance calling the BBS, but the BBS is local calling the user. This gives the SysOp the opportunity to give a user a special door to go thru to allow access to the BBS without incurring long distance charges. Do not use this command line switch in your VALIDATE.BAT file! Use it in one called REDIAL or some other name. New users will NOT be validated if MYCALBK is called with the /DIALBACK switch! SysOp configurable files... ─────────────────────────── Please see the enclosed sample files for each of the following for your convenience. You can edit them with any ASCII text editor to suit your particular system. There are eight (8) files in this package that are SysOp "adjustable". But they must follow some simple guidelines. 1). The FIRST line * MUST * be one of the eight valid IBM colors... (RED, GREEN, BLUE, CYAN, YELLOW, WHITE, BLACK, and MAGENTA) 2). The longest line must * NOT * exceed 70 columns. Here's a description of each file and the output to the caller. ===================================================================== WELCOME Shown to the caller when they first log-in. NODUPES Shown to the caller when that phone number has already been used. SORRYAC Shown to the caller when their area code is not one you selected to call back. INSTRUCT Shown to the caller just before disconnect, explains to caller what to do at his/her end. NOTTIME Shown to the caller when you have configured to call LD callers back but this is not the right time to do it. LDREDIAL Shown to the caller when they try to run thru the DIALBACK door and it is determined that they are long distance. When using the /DIALBACK parameter, the door will not call long distance. DIALME Shown to the caller to explain what is happening when using the /DIALBACK parameter. NOREDIAL Shown to the caller when they try to go thru the DIALBACK procedure and they are not a validated user (by MYCALBK). It should give the caller instructions on how to go thru MYCALBK and be validated by the door first. TRASCHAN Show to the caller when the number they entered matches a number you have defined as uncallable. This lets them know that you are not happy with them, or that they are a bozo etc... Again, please take the time to view the enclosed sample files if you are not quite able to make sense of any of the foregoing. Sometimes a sample can be worth more than a thousand words... Once you have edited the necessary files discussed above, you should be ready to begin using MYCALBK. You may want to make a subdirectory from your RBBS subdirectory and put all the MYCALBK files in it. For example E:\RBBS\CALBAK (You can rename CALBAK as shown, to any legitimate DOS subdirectory). Then put the MYCALBK files into it. The CALLBACK.BAT file can be easily put into your RBBS subdirectory where RBBS can find and read it instantly. It's only a few bytes in size. Don't forget to tell the RBBS config (CONFIG) where the CALLBACK.BAT file is located. Use RBBS config parameter 107 where you type the name of the CALLBACK.BAT file for RBBS to find, and then check the security level for new users for the verification, parameter 108. The enclosed CALLBACK.BAT file will give you a sample of what to put in the CALLBACK.BAT file for those using Ray Gwinn's XU/X00. And while I have your attention, please don't forget to add a line to you RBBS DOORS.DEF file so RBBS can readily find this program. The line you type into your DOORS.DEF file should like something like the following... DOORS.DEF CALLBACK,5,,D,"CALLBACK.BAT [NODE]",N,, *REMEMBER* Do not call this .BAT file VERIFY. VERIFY is a DOS keyword. For more explicit information regarding DOORING, please read the area in the RBBS-PC Technical Reference Manual. It lists complete details and several examples regarding the parameters required to operate doors smoothly and efficiently with RBBS. OUTPUT files generated by MYCALBK... ──────────────────────────────────── MYCALBK will generate files for you with relevant information pertinent to the related activities of callers who are swept into the RBBS registration door. The information generated is for the sysop's information. ─────────── MYCALBK1.LOG ─────────── This file will list any errors that may have been caused by a faulty installation. As an example, if you should accidentally put the MYCALBK.CFG file into the wrong sub-directory, it will generate an error messages as follows... Couldn't find .CFG file! If you should see such information, then it becomes quite clear as to what your next step should be. ...A N D also the following... SAMPLE ONLY! of the MYCALBK1.LOG file generated by MYCALBK.EXE ^^^^^^^^^^^^ ---------------------------- MYCALBK 3.35 Firing up! User on-line -> MIKE ELMORE @ 00:06:50 on 11-21-1993 FOSSIL present and ACTIVATED! Long distance call being made - 1-###-2672 Using a 1. FOSSIL present and ACTIVATED! Modem out String ATE1V1Q0X4 Dialing 1-###-2672 Try # 1 Modem out String ATDT1-537-2672 Timed out. Modem out String AT Dialing 1-###-2672 Try # 1.5 Modem out String ATDT1-537-2672 Timed out. Modem out String AT Dialing 1-###-2672 Try # 2 Modem out String ATDT1-###-2672 Tries = 1 User entered MIKE ELMORE MIKE ELMORE @ 1-###-2672 Verified! Upgraded security to 22 MIKE ELMORE Exited Door. ---------------------------- MYCALBK 3.35 Firing up! User on-line -> ROBERT ORSINO @ 15:07:42 on 11-24-1993 FOSSIL present and ACTIVATED! User dropped carrier! Downgraded security to 10 ROBERT ORSINO Exited Door. ---------------------------- MYCALBK 3.35 Firing up! User on-line -> JOHNNY EADES @ 18:33:11 on 11-25-1993 FOSSIL present and ACTIVATED! FOSSIL present and ACTIVATED! Modem out String ATE1V1Q0X4 Dialing ###-#### Try # 1 Modem out String ATDT###-#### Tries = 1 User entered JOHNNY EADES JOHNNY EADES @ ###-#### Verified! Upgraded security to 24 JOHNNY EADES Exited Door. ---------------------------- ──────────── VERIFIED.LOG ──────────── This file will hold the information regarding new callers to your RBBS. You should note that this file is dynamically expanding, so keep in mind that you have enough disk space to allow this file to grow by leaps and bounds! The information listed contains the phone number of the caller, the name of the caller, the date, and the time that the caller used the MYCALBK door, and whether it was long distance or a local call to your RBBS. SAMPLE ONLY! of the VERIFIED.LOG file generated by MYCALBK.EXE ^^^^^^^^^^^^ 803-555-3844 BUBBA SMITH 10-15-1993 12:31:45 Local 803-555-0923 BILLY-JOE BOB 10-15-1993 15:17:42 Long Distance 803-555-5704 ELVIS PRESLEY 10-15-1993 17:25:05 Local 803-555-1444 JO-DON BAKER 10-16-1993 19:10:11 Local 803-555-3034 STEVE STEVENS 10-16-1993 20:56:01 Local 803-555-9017 GLEN SATHER 10-17-1993 22:04:31 Long Distance 803-555-6239 WAYNE GRETZKY 10-18-1993 09:31:07 Long DIstance 803-555-1117 MIMI LAMOUR 10-18-1993 10:51:40 Local 803-555-0407 EDGAR HOOVER 10-19-1993 11:35:17 Local 803-555-6475 CANDY SAMPLES 10-19-1993 17:54:25 Local 803-555-3705 JOHNNY LARUE 10-20-1993 22:29:19 Local In conclusion, MYCALBK has proven to be highly reliable and stable on the beta test sites, and on other systems that are currently operating with this program. If you are an RBBS sysop in Canada, please feel free to call the two systems listed at the end of this document, Alberta One RBBS @8:990/105 -or- Alberta Express @8:990/106, for any assistance you may require. If you are in the USA, please try your best to get in touch with me, rather than Rod Bowman, who is very busy looking after the RBBSnet worldwide network. Registration... ─────────────── Dear fellow RBBS SysOp... MYCALBK required considerable time and effort, and many updates with suggestions and ideas from several participating beta test sites (in the USA and Canada). Therefore if you like and use MYCALBK on a regular basis on your RBBS, and you find it does exactly what it should do, then please consider registering this quality RBBS utility. Please review the enclosed REGISTER.FRM file and ensure you respond to the questions accurately. I will then mail you your registration key, netmail it to you, -OR- put in on hold in the P)ersonal downloads of my RBBS for you to retrieve. A financial contribution of $25.00 (US Funds) would be much appreciated. Payment may be made with certified cheque, money orders, or personal cheque (Please note, personal cheques require a delay in processing). Your support is much appreciated. Thank you for supporting MYCALBK...THE RBBS-PC caller verification utility. Steve Stevens The Neutral Zone 8:927/2 Queries? Feel free to... 1). Leave questions addressed to me Via NETMAIL 2). Call me VOICE @ (803)-393-0246 3). Call my BBS at (803)-395-6286. *** Special thanks to the following people and beta sites, in the evaluating and for making helpful tips and hints, in the development of CALLBK *** Frank Harman SysOp of Alberta One RBBS (Canada) @8:990/105 Casey Vanloo SysOp of Alberta Express RBBS (Canada) @8:990/106 Rod Bowman SysOp of PC-Spectrum (tm) RBBS (USA) @8:8/8 Dan Shore SysOp of ShoreLine BBS (USA) @1:109/458 Chip Hanna SysOp of The RockCreek BBS (USA) @8:925/200 Greg Snyder SysOp of DGA Systems Alpha (USA) @8:935/130 Plus several others who have slipped my mind at the moment. ─────── Without all of you, this would not have been possible.─────── RBBS-PC is copyright 1992 Tom Mack, and probably Ken Goosens. USA. IBM is the registered trademark of International Business Machines. USA. XU/X00 utilities, v1.01 is copyright 1990. Raymond L. Gwinn. USA. USRobotics, and HST are trademarks of USRobotics, Inc. USA. DESQview is the registered trademark of Quarterdeck Office Systems. USA. POWERBASIC is Copyright 1990,1992 Robert S. Zale. USA One Final Note... This version of MYCALBK has been written with POWER BASIC 3.0c. It contains mostly BASIC source code but it has a lot of DOS Interrupt calls and some inline assembly. I have been using PowerBasic for well over 3 years (it was called Turbo Basic) and have enjoyed programming in it. Please support RBBS's re-write in PowerBasic as it is as powerfull yet as simple as you can get before going to 'C'. Browsing 'C' manuals and the like has helped me immensly in programming in BASIC as well and with PowerBasic it makes it all that much easier. They ability for inline assembly has made it possible for RBBS to be re-programmed by ANYONE as any of the ASM routines that have been written for RBBS should be included as an ASM.BAS file with all the ASM at everyone's finger tips! This should eliminate problems in the future like the Far String mods and the ANSI.ASM routines that have needed constant modifications.