Media Share 9

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

/ Media Share 9 / MEDIASHARE_09.ISO / bbs / vfy_29a.zip / VERIFY!.DOC < prev next >

Wrap

Text File | 1993-07-24 | 33KB | 713 lines

************************************************************** * * * VERIFY!.EXE v2.9a Copyright (c) 1992, 1993 * * * * Sagerquist Micro Engineering * * * * 1414 W. Kerrick Street * * Lancaster, Ca. 93534 * * Data (805) 723-6908 * * * ************************************************************** DESCRIPTION ----------- VERIFY! is a program designed to verify a BBS caller. When invoked, VERIFY! will ask for specific information from the caller, hang up, return the call, and ask for the same data for verification. If the information matches, the caller is verified. ERRORLEVELs are returned to the calling batch file which will allow the sysop to make the necessary adjustments to the BBS as appropriate. A log file is kept and maintains the caller's name and phone number for future reference. SYNTAX ------ VERIFY! [/B:(bbstype)] [/D:(directory)] [/L:(optional log file)] /B:... BBS switch. Choose from the list under SUPPORTED BBS's. /D:... Directory (no file name) where the BBS's caller information file is located. If this switch is not used, VERIFY! will look for this file in the current directory only. /L:... Optional log file path and name. If you want VERIFY! to log its operations in your BBS log file, use this switch to define the full drive:\path\filename.ext. If this switch is not used, the default file VERIFY!.LOG will be created and updated. EXAMPLES -------- VERIFY! /B:MH1 VERIFY! /B:MH1 /D:C:\MEGAHOST\DATA VERIFY! /B:WILDCAT /D:C:\WC30\WCWORK /L:C:\WC30\WCWORK\WC.LOG Note: # is Node Number SUPPORTED BBS's Switch: Caller Info File: ---------------------------------------------------------- MegaHost: MH# MEGAHST#.DEF PcBoard: PCBOARD DOOR.SYS QuickBBS: QBBS# DORINFO#.DEF RBBS: RBBS# DORINFO#.DEF Remote Access: RA DOOR.SYS Remote Access: RA# DORINFO#.DEF Teleguard: TELEGUARD CHAIN.TXT TGP: TGP CHAIN.TXT TRIBBS: TRIBBS_D DOOR.SYS TRIBBS: TRIBBS_T TRIBBS.SYS Wildcat: WILDCAT CALLINFO.BBS World War IV: WWIV CHAIN.TXT FILES IN THIS ZIP PACKAGE ------------------------- VERIFY!.EXE <----------- Executable program. VERIFY!.DOC <----------- Document for VERIFY!.EXE - this file. SETUP.EXE <----------- Set up program, sets sysop's variables. SETUP.DOC <----------- Document for SETUP.EXE. TRAPDOOA.BAT <----------- Example of a Trap Door batch file. TRAPDOOB.BAT <----------- Example of a GAME Trap Door batch file. REGISTER.FRM <----------- Fill-Out form for registration. VERIFY!.DAT <----------- Created or adjusted by SETUP.EXE, holds the reg number, modem strings, phone numbers for screening, etc. FIX_DAT.EXE <----------- Adjusts the file VERIFY!.DAT created by version 2.7 and earlier. 4-TRIBBS.ZIP <----------- Utility programs for use with TRIBBS. FILE_ID.DIZ <----------- Description file for BBS use. OTHER FILES ----------- VERIFY!.LST <----------- Created by VERIFY!, contains a list of verified callers and their phone numbers. VERIFY! checks this list for duplicate phone numbers, and to ensure that a caller isn't verified more than once. VERIFY!.LOG <----------- Default log file created by VERIFY!, logs the caller's actions, for sysop's information, if the /L: switch is not used. SETUP ----- SETUP.EXE must be run prior to going on line. All data, modem strings, authorized area codes and prefixes, long distance call back times, registration number, etc., must be edited with this program. ALT S saves the new data. ALT X exits. Use ALT (n) for the data windows: ALT R for Registration, etc. SETUP.DOC explains the setup operation in better detail. Your calling batch file must be edited, or renamed. TRAPDOOA.BAT and TRAPDOOB.BAT is supplied to help you start. VERIFY!.DAT ADJUSTMENT ---------------------- If you've been using VERIFY!.EXE v2.7 or earlier, you'll need to run FIX_DAT.EXE to adjust the binary file VERIFY!.DAT for use with v2.9. Then run SETUP.EXE to ensure that all data is in its proper places. The program FIX_DAT.EXE will not alter VERIFY!.DAT more than once. REGISTRATION AND SUPPORT ------------------------ This is important! Until VERIFY! is registered with the programmer, one very important feature is inhibited: The call screening. After the sysop name and registration number is entered via SETUP.EXE, you will be able to screen out toll and long distance calls, and designate the time of day to make these calls. Your number will be mailed upon receipt of the registration fee. Without this feature, (BEFORE REGISTRATION), any request to call back verify is granted! If your BBS is in Los Angeles, Ca., and a caller from New York, Ny. requests to be verified, YOUR PHONE BILL WILL REFLECT THIS EXPENSIVE CALL! With this feature (after registration), you can adjust VERIFY! to call back verify ONLY local calls, or long distance numbers ONLY within the area code(s) you designate. This is a user supported product. VERIFY! represents many hours of work. This software is Shareware, not free or public domain. You are granted a 30 day limited license to evaluate this program, after which you must either register the product, or discontinue its use. If you choose to register this program, please make out a check or money order for $15.00 payable to: Sagerquist Micro Engineering 1414 W. Kerrick St. Lancaster, Ca. 93534 California residents add 8.25% Sales Tax of $1.24, total: $16.24. Your registration number will be mailed on receipt of your payment. It is recommended that you register this program promptly, as the toll charges for long distance call backs have the potential to far exceed the $15.00 requested! Payment is a one time investment which allows you all further revisions at no extra expense. Please distribute this program, i.e. place it in your communications program download area for others to evaluate and use. Your comments on this program are gladly accepted (requested, actually) at the number below. Please use the BBS as our communication vehicle. I will gladly respond to all comments through the BBS. The Antelope Valley Aviator Carl Sagerquist - Programmer/Sysop 300-16800 BAUD 24 Hours (805) 723-6908 Thank you for supporting VERIFY!! OVERVIEW -------- VERIFY! was written by request from a MAXIHOST BBS sysop who had some difficulty with some rude callers. These people would call under fake names and leave foul messages, upload rude material, etc. This sysop needed a program that would validate each caller prior to authorizing access. VERIFY! performs this duty by returning the call to the user, and comparing the name and password left behind with the name and password typed in after the call back. If verified, VERIFY!.LST keeps a ready reference of verified callers and their phone numbers, and is read by VERIFY! to avoid double verification, and duplicate phone numbers. After verification, the callers are accountable, and they know it! OPERATION --------- VERIFY! performs a series of steps to complete the task of on-line verification. The caller is given the opportunity to stop the process and exit the program, if desired. 1 - Caller is asked if he wants to be verified for access. 2 - The caller's name is compared to the names in the file VERIFY!.LST. If found, the caller is advised that verification has already been successful, and the program exits. 3 - Instructions are issued, then caller is asked if he wants to proceed. 4 - The caller must type in his personal information: First and last names are placed for the caller. Caller types in a password. Caller types in phone number with area code. Caller is then asked if the information is correct. Process is repeated if necessary. 5 - Phone number is checked against all others within the file VERIFY!.LST. If the number provided by the caller is already in this list, the verification process stops and the caller is notified to leave a message to the sysop regarding his access. It could be that this caller is a previous verified user under a fake name! You might want to place other BBS phone numbers here, so a prankster won't have your BBS hook to another BBS! 6a- REGISTERED VERSION ONLY: Phone number is checked against the local prefixes, non-local prefixes, and area codes from SETUP.EXE. If the area code and/or prefix is not found, the call is not placed, and the caller is notified to leave a message to the sysop, regarding BBS access. This controls the sysop phone bill. 6b- UNREGISTERED VERSION: All requests for call back verify will be granted. The sysop phone bill will reflect any long distance call backs! It is recommended that you register this program promptly, as your increased phone bill will quickly exceed the registration price if you have a lot of long distance callers!!! 7 - BOTH REGISTERED and UNREGISTERED: Certain calls can be very expensive. Calls to a 976 prefix or area code 900 can be extremely costly. From SETUP.EXE, define the unauthorized area codes or prefixes and these numbers will not be dialed. The first prankster that gets upset through your use of this program might try to get even by typing in a 976 number, or 911! VERIFY!.EXE is one step ahead! 8 - REGISTERED VERSION ONLY: If the call back will be a long distance number, and it checks out OK, the time is checked to be within the two times defined from SETUP.EXE. If this function is not disabled, (with 0 - 0), VERIFY! will either return the call, or advise the caller of the normal times that his call back can be placed. 9 - Modem hangs up. 10 - The caller's phone number is dialed. 11 - When the caller answers, he will be given the opportunity to type in his name and password again. VERIFY! compares this data to the data left behind before the call back. If it matches, the caller is advised that he is verified. 12 - If verification is successful, caller is thanked for proper verification. If the call was local, the caller is returned to the BBS. If the call was long distance, a message is issued stating that this is a toll call, and that access will be granted on next call. The phone line is then disconnected. Without this feature, the BBS would continue at the sysop's expense. If the call back was long distance, it could become extremely costly to the sysop. The UNREGISTERED version WILL disconnect on toll calls. 13 - The log file is created or appended with information regarding the caller's actions. The data includes the caller's name, phone number (if he got that far), the date and time, and the result of VERIFY!. Results include statements like: "***** VERIFIED! Local *****", "Carrier lost", "Decided not to be verified", etc. The log file is either VERIFY!.LOG, or the file name defined on the command line with the /L: switch. 14 - On exit of VERIFY!, ERRORLEVELs are returned to the calling batch file. It is then your responsibility to invoke a BBS utility program to adjust your caller's BBS security level or perform what ever duty you need. Even if nothing is done to the BBS at all, you will have the new name in VERIFY!.LST with the correct phone number. If you don't understand DOS ERRORLEVELs, you'll need to review your DOS manual. AREA CODES AND PREFIXES FROM SETUP.EXE -------------------------------------- If VERIFY! calls back the user, how can you keep a tab on your phone bill? This was a major consideration for this program. There are 5 different number windows in SETUP.EXE: 1 - Local Area Code for the BBS This is the local area code at the location where the BBS is run. 2 - Unauthorized Numbers If the caller's AREA CODE or PREFIX matches any 3 digit number on this line, then the call is not placed. This protects you from those very expensive 976 numbers and area code 900 numbers. This function is operational whether registered or not. Place any area code or prefix you need. Be sure 911 is listed here. 3 - LOCAL Prefixes If the caller's area code matches the Local Area Code for the BBS, then these numbers is checked for a match. If the prefix is found, then the callback will be a local call, and the dial string will only contain the 7 digit local number. Defining the local prefixes allows you to screen out those toll calls that look like local calls. If this line contains the number 000, then ALL numbers within the area code will be called, just as they are before registration. For example: These numbers are in the window of Local Prefixes: 943 944 945 948 949 723 722 264 and the Local Area Code for the BBS is 805. (805) 723-6908 is the caller's number. The caller's area code 805 matches the BBS's area code, so the Local line is searched for the prefix 723. 723 is found, so the dialed number will be 7236908. If the prefix is not found, the next set of numbers labeled "Authorized toll prefixes within the local area code" is checked. 4 - Authorized toll prefixes within the local area code If the caller's area code matches the Local Area Code for the BBS, and the caller's prefix is NOT found among the Local Prefixes, then this group of numbers is checked for the caller's prefix. If the prefix is found, then the callback will be an authorized toll call within the local area code. The dial string will only contain the 7 digit number. If this line contained the number 000, then ALL numbers within the area code will be called, just as they are before registration. For example: These numbers are on the line of Authorized toll prefixes...: 724 942 The search in 3 above was unsuccessful, so this line is searched for the prefix. (805) 942-0889 is the caller's number. The line is searched for the prefix 942. 942 is found, so the dialed number will be 9420889. If the prefix is not found, then the call back is not within the local area code. This allows you to designate the toll calls within your local area code you will allow to be called. Depending on your entry from SETUP.EXE, the number dialed here may or may not begin with a '1'. The number in this example will either be 9420889 or 19420889. 5 - Authorized long distance area codes If the caller's area code does not match the BBS's, the prefix checks are skipped, and this group of numbers is searched for the area code. If it is found, the number is called. If the number 000 is in this line, then ALL long distance calls will be placed, just as they are before registration. For example: These numbers are on the line of Authorized long distance area codes: 602 818 213 (602) 555-1212 is the caller's number. 602 is found, but the number is incomplete. First, the number 1 is appended to the dial string, then the full number, resulting in the dial string being 16025551212. If the area code is still not found, then the call is not placed. SYSOP HAS FULL CONTROL OF WHAT NUMBERS MAY BE CALLED! (REGISTERED VERSION ONLY!!!!!) NOTE: If the number called is a toll call (inside or outside the local area code), the line will hang up (be disconnected) after verification. This controls the sysop phone bill. Caller is advised that access is authorized on next call. REDIALS ------- VERIFY! can reattempt the phone call if the first attempt does not work. Often, an unsuspecting family member will pickup the phone on VERIFY!'s call back and break the modem connection. Sometimes, a caller is confused and just needs to try it more than once. Designate the amount of redial attempts through SETUP.EXE, Other window. TOLL CALL BACK HOURS -------------------- Most long distance carriers (phone companies) offer reduced rates within certain times. You can define your call back time for long distance calls to be within these times. These times are defined in SETUP.EXE, Other window. The numbers to be placed are the hours from the 24 hour clock. 1:00 pm is 13, 12:00 am is 24, etc. Hours only, no minutes. Example: 21 6 is for performing long distance call backs between 9:00 pm and 6:00 am. If you do not require screening your long distance call back time, place the number 0 (zero) for both: 0 0 to disable this function, allowing long distance call back at any time. CARRIER MONITOR --------------- VERIFY! monitors the Carrier Detect. If a caller hangs up, or gets disconnected, VERIFY! will exit clean and return to the BBS. The BBS will then reset and await the next call. You can test this feature by typing the ~ character at any prompt. TIME LIMIT ---------- The caller has 60 seconds to complete each entry, or carrier is dropped and the program exits. That way, if your caller's computer freezes, you aren't stuck on line! This feature was added to disallow remote's control of the carrier. Without this feature, the call back could last as long as the remote caller would allow. If the call back was long distance, your phone bill could sink you. You can test this feature by typing the (^A) character at any prompt or waiting 60 seconds without input. ALTERNATE OPERATION ------------------- If you want to use VERIFY! to screen users of on-line games, place a copy of VERIFY!.EXE and its data files in the game directory. Copy DOOR.SYS (or the appropriate BBS file) to this directory. The game Trap Door must be available to all callers. After verification, allow entry into the game. On exit of the door, run your BBS utility program for adjusting security levels for the caller's next entry. BATCH file commands should check the security level of the caller and he/she should be entered into the VERIFY! program, or directly into the game. This protects the BBS game door from having callers play under multiple names, because two callers cannot be automatically verified from the same originating phone number. If its legitimate, like brother and sister both want to play the game, the message left to the sysop will explain, and you'll have to manually adjust the security for that player. See the file TRAPDOOB.BAT included in this ZIP package for an example of this operation. BBS ADJUSTMENTS --------------- VERIFY! does no adjustments to your BBS itself. You, as sysop, are responsible to code your calling batch file appropriately to effect change. The returned ERRORLEVELs from VERIFY! will allow you to to do this. ERRORLEVELS ----------- VERIFY! will return different errorlevels for further processing by the calling batch file: ERRORLEVEL 0 means the caller is verified, and all data matched. Call back was LOCAL. ERRORLEVEL 1 means the caller is verified, and all data matched. Call back was LONG DISTANCE. ERRORLEVEL 2 means the caller has already been verified. ERRORLEVEL 3 means the caller reentered the wrong data on callback. Caller not verified. ERRORLEVEL 4 means no modem on callback. Caller not verified. ERRORLEVEL 5 means the caller's phone number duplicates another verified caller's phone number. Could be a bogus call. ERRORLEVEL 6 means the callback phone number is not authorized. ERRORLEVEL 7 means long distance callback not within time envelope. ERRORLEVEL 10 means the caller decided not to be verified. ERRORLEVEL 15 means the remote input time limit (60 seconds) exceeded. ERRORLEVEL 20 means carrier was dropped. ERRORLEVEL 30 means the BBS file (DOOR.SYS, DORINFO1.DEF, CALLINFO.BBS, CHAIN.TXT) cannot be found, or another file could not be be opened or created. ERRORLEVEL 35 means an unsupported COM port is in use. ERRORLEVEL 40 means the log file could not be written to. SAMPLE BATCH FILE FOR MEGAHOST ------------------------------ @echo off cls C: CD\MEGAHOST\VERIFY! VERIFY! /B:MH1 /D:C:\MEGAHOST\DATA /L:C:\MEGAHOST\DATA\MEGAHST1.LOG IF ERRORLEVEL 1 IF NOT ERRORLEVEL 2 goto SET IF ERRORLEVEL 0 IF NOT ERRORLEVEL 1 goto SET GOTO END :SET CD\MEGAHOST rem MEGAAPI1 svc 5 will increase the caller's security while on line. rem MEGAAPI1 svc 7 will increase the caller's time limit while on line. MEGAAPI1 5 10, 7 60 :END CD\MEGAHOST\UPLOADS PRANKSTER CONTROL ----------------- If everyone was honest and respectful, there would be no need for this program. Some people spray paint on walls. Some people throw rocks through windows. The same mentality will call a BBS incognito and raise havoc with the sysop and his users through foul messages, uploaded dirty files, etc. When a prankster is caught by this program, he may feel a desire to get even. This program was written with this prankster mentality in mind. The controlling features are: 1 - 60 second timer for user input. A caller cannot hook you to his computer indefinitely, thus controlling your phone bill (long distance/toll calls). 2 - No duplicate phone numbers on automatic verify. - A new caller with the same phone number of a previously verified caller could be the same person under a different name! - A prankster might try to make your BBS hook up to another BBS! Place ALL possible BBS numbers into the file VERIFY!.LST, and this will not happen! 3 - Numbers defined as UNAUTHORIZED NUMBERS (through SETUP.EXE) are screened out. A prankster might try to make your computer call a 976 or area code 900 number. Also, if the call back was 911-####, the 911 would connect you to the emergency dispatch in your city! These numbers should be placed in the window labeled: UNAUTHORIZED NUMBERS through SETUP.EXE. This feature is operational prior to registration. 4 - Long distance numbers are not called unless the area code is designated. (REGISTERED VERSION ONLY). Lets face it, even honest people will use this program without compensation to the programmer if every feature was operational! Use caution, though, ALL long distance calls are placed until VERIFY! is registered, and your phone bill will quickly exceed the $15.00 requested. 5 - Log file appended after caller is done. The result of the caller's actions are placed in the file VERIFY!.LOG with the date and time. If you find a need for more techniques on handling pranksters, please make the suggestion via my BBS at (805) 723-6908. CREDITS ------- Many thanks to Tim Gimber of Phoenix, Az., who suggested this program, directed its features, and tested its operation. Many thanks to David Swift of Waldorf, Md., for advising me of the fatal error fixed with revision 2.2. This problem didn't occur on my modem, and I still don't understand why. VERIFY! is now compatible with many more modems. Many thanks to Kent Craig of Vincennes, In., for advising me of the methods used by the Indiana phone system: Toll Local numbers there require the number to begin with a '1'. Now, through SETUP.EXE, the sysop may choose to prefix a Toll Local number with a '1'. Verify! is now compatible with more phone systems. Thanks to Raymond Swigirt of Baltimore, Md., for requesting room necessary to handle all 281 of the local prefixes available in Baltimore. The suggestion motivated me to revise the serial port routines, command line switches, and shared file access for multi- tasking environments. Thanks to James Mann of Littlerock, CA. for requesting the TRIBBS support programs and testing them online. DISCLAIMER ---------- This program is distributed as is. No warranty, either expressed or implied is offered and the programmer is not responsible for any damages or expenses that may occur through the use of this program. The user shall determine its suitability. Please communicate any difficulties with the programmer through the BBS at (805) 723-6908. History ------- Version 2.9a - 07/24/93 - Revised programs that support TRIBBS v4.0+, all of which are found in the file "4-TRIBBS.ZIP". Version 2.9 - 07/11/93 - Utilities created for security level adjustment on a TRIBBS BBS, through TRIBBS.SYS. - Fatal error found: If all data in the file VERIFY!.LST is removed, yet the zero length file still exists, the program would freeze. FIXED! Version 2.8 - 04/04/93 - Comm port routines overhauled. Now, all data transmitted and received is interrupt driven, and more thorough error checking is performed. - All file access is performed in share mode. Files are "locked" prior to writing which allows for a clean operation in a multi- tasking environment where a multi-line BBS might be operating VERIFY! simultaneously on more than one node. - Command line switches overhauled. - VERIFY! may now log its actions into the BBS's log file through the /L: command line switch. - Amount of definable local prefixes is now 510, double from v2.6. - MEGAHOST now supported through MEGAHST#.DEF rather than DOOR.SYS. - TRIBBS now supported through TRIBBS.SYS and DOOR.SYS. - WILDCAT! v3.0+ now supported through the new format of DOOR.SYS. Version 2.7 - ??/??/?? - Beta test only, not released to the public. Version 2.6 - 04/24/92 - Local Prefixes, Toll Local Prefixes, and L/D Area Codes are increased from 3 lines to 9 lines of 67 characters. - Toll Local call back number may be prefixed with a 1 if necessary. Use SETUP.EXE to make the adjustment. Version 2.5 - 04/08/92 - Added an option allowing the caller to quit. For example: "Are you ready to proceed? (Y/n)" is replaced with "Are you ready to proceed? (Y/n/q)" where 'Y' is default, and 'Q' exits the program. - SETUP.EXE adjusted. New features: - If data is changed, you are prompted to save. - <CTRL> Right Arrow moves the curser to the beginning of the next number in the "Numbers" window. - <CTRL> Left Arrow moves the curser to the beginning of the previous number in the "Numbers" window. - Up Arrow/Down arrow moves to different lines in the "Numbers" window. Version 2.4 - 01/01/92 - SETUP.EXE added to automate the setup operation. All data from SETUP.EXE is written to VERIFY!.DAT, which is now a binary structure file. - VERIFY!.NUM is no longer needed. - MAXIHOST no longer listed as supported since M-VERIFY v 1.09 is still available. Version 2.3 - 12/15/91 - Beta test version not released. Version 2.2 - 12/10/91 - Fatal error found with some modems (not mine) that would disrupt the comm port interrupts. Unnecessary code removed that set some modem parameters. Thanks, Dave! - More BBS's supported: PcBoard Remote Access Teleguard TGP World War IV Version 2.1 - 10/14/91 - Bug in toll/long distance call timer fixed. - When the toll/ld call is screened out, the current time is displayed before the message explaining the time window for toll calls. - Caller is now informed how many attempts will be made to call back and connect. Version 2.0 - 10/10/91 - Program renamed from M-VERIFY to VERIFY!. - Supports MAXIHOST, MEGAHOST, QBBS, RBBS, PCBoard, and WILDCAT. Syntax different while retaining the old method. - No adjustments to MAXIHOST or its assoc'd files anymore. - ERRORLEVELS returned. The sysop must make the appropriate adjustments to the BBS depending on the ERRORLEVEL returned. Version 1.09 - 11/29/91 - Modem parameters (BAUD, Parity, Stop bits, and Character length) are no longer set. This was causing trouble with some modems. Unfortunately, not mine. This may have been the culprit causing trouble with earlier versions. These parameters are set by the BBS anyway, so there's no harm in removing this code. Same code removed from version 2.1. Version 1.08 - 09/16/91 - Sorry about that, another bug got by me. Version 1.07 - 09/16/91 - Some code rewritten for efficiency and safety. No changes in operation from 1.06. Version 1.06 - 09/15/91 - Fixed FATAL ERROR in delay function that violated memory not its own which eventually caused system to crash. Version 1.05 - 08/09/91 - 'REDIALS = ' added to M-VERIFY.DAT to control the amount of attempts to recontact the caller. Version 1.04 - 08/07/91 - Long Distance call back time now definable, since most long distance carriers allow for cheaper rates at different times. - Removed the advertisement at beginning of output on registered version. Version 1.03 - 07/28/91 - Fixed bug in log file entry that says "**** VERIFIED (Long Distance) ****" when caller really "Already Verified". - Fixed bug that created M-VERIFY.LOG in the root directory if M-VERIFY.EXE was called without the proper command line parameters. Version 1.02 - 07/26/91 - Registration required. Without the reg #, all call backs are placed regardless of the area code or resultant phone charges. Call back screening enabled with registration. - M-VERIFY now screens OUT certain area codes or prefixes, like 976 and 900, while author- ized numbers are screened IN. (Sysop can define these numbers in M-VERIFY.NUM). - M-VERIFY now checks for toll calls within the local area code. Caller is disconnected after verification if callback is a toll call. - ERRORLEVELs 1 through 5 become 2 through 6, and ERRORLEVEL 1 redefined: ERRORLEVEL 1 returned if caller is verified and call back is long distance. ERRORLEVEL 0 if call back is local. Version 1.01 - 07/21/91 - Delay added after "Returning Your Call" sent, as it was being cut off by hanging up too quick. - Bug in hangup routine: After verification, if call back was long distance, dropping DTR wasn't enough to disconnect. Hangup routine fixed. Version 1.0 - 07/19/91 - Initial release. Version 0.2 - 07/14/91 - Beta test released to requesting official, not to be released to public. Partially completed. Version 0.1 - 07/09/91 - Beta test released to requesting official, not to be released to public. Partially completed.