Beijing Paradise BBS Backup

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

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / MC_CBV.RAR / MC_CBV.DOC < prev next >

Wrap

Text File | 1994-07-21 | 54.2 KB | 1,069 lines

Mc_Cbv V3.0 Automated Callback Verifier for RemoteAccess And ProBoard Copyright 1992,1993,1994 McSoft Corp. All Rights Reserved ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Introduction ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ This is Motor City Software's CallBack Verification System for RemoteAccess and ProBoard BBS. Shareware Version ----------------- - Works with RemoteAccess and ProBoard BBS. - Detects and Gives Up Time Slices with DESQView, Windows, AND OS/2 - Works with your Telephone Services Caller-ID feature if you subscribe to it and your modem supports it. - Allow McCbv to build its own LOCAL dialing control file! YES, it will auto- matically verify and add local numbers to its control file as it finds them This feature alone can save you HOURS of searching and typing! - Checks Users Phone Numbers to make sure they are in the correct format if you are using USA Style numbers. - Duplicate Phone Number Checking by Numbers Already Called or by Numbers in Users.BBS or by BOTH - Post Welcome Message to newly verified users. Messages may be posted to a Hudson or a JAM base. - Messages are fully configurable with Message Templates - Excellent Call Collision Handling - Allows Multiple LOCAL Area Codes - Sysop Configurable for Allowing LD Callbacks, including Setting Specific Hours for Long Distance calls, AND Specific Area Codes and Exchanges! - The Sysop can define all text displayed to the user. - One of the easiest doors you ever set up! Reads all its defaults from your RemoteAccess configuration files! - Originally written for the RA Beta Team - Secure Password Checking using CRC32 with RemoteAccess 2.xx - If the User has less than X Minutes remaining when they enter the CallBack Door, they will have their time reset to X minutes in order to allow them to complete the CallBack Process. X is configurable by the Sysop. - The Sysop may abort the callback by hitting ESCAPE, or abort the current call attempt with the SPACE bar. - Fully Multi-Node Aware - The Following Sysop Keys are available in the door for the Sysop : Alt-C Chat With User Alt-J Jump To Dos Alt-R Return To BBS Alt-U Bypass Callback and Upgrade User UpArrow Add 1 Minutes Time DownArrow Deduct 1 Minutes Time ENTER will redraw the menu after a jump to DOS - Added Interactive Online Tutorial! You can replace the first and second screens with TUTOR1.A?? and TUTOR2.A?? - Added new TextFile Control Code support for message templates. If you are using RA 2.xx you have the new codes as well. - Great looking "terminal dialing screen" while dialing the user. - RA-style language file support! - Ability to have separate init strings for different modems in a multinode system. See INITnn.MDM, below, for details. - Added new option. Users Info - Allow Fixed #'s? If a users phone number is not in the correct format, then they will be asked to fix it IF you are using the USA format. If their phone number is entered as XXXXXXX then McCbv will insert the -, making XXX-XXXX If it finds this, it will then prompt for an AREA CODE ONLY. If the number was blank, or not XXXXXXX, or XXX-XXXX then they will be prompted for the whole number. This option will allow you to SAVE the new number to the proper field (i.e. Voice # for Voice #, and Data # for Data #. If you say No, then it will NOT prompt the user to fix the phone number, and it will NOT allow the user to use the Callback Door if it is not already in a valid USA format! If the Voice And Data Line are the same, and missing the area code, then the user will only be prompted once for the area code. Note, they may only fix the number if you ALLOW Users To Fix the numbers. - Optionally FORCE one specific flag ON and/or one specific flag OFF if a user is called back and verified. Because the Group, security level, sub-days, and flags are NOT updated if the user already has a security level higher than the new one defined, this will allow you to use a flag to force all users into the CBV and change that flag for validated users without messing up their other flags, Security Level, Group, or Sub-Days. - Users may not be called back at their previously verified phone number UNLESS you allow Call Returns They may not do this through the Verification option unless they have since been removed from the users.bbs and you allow Re-Verification (See info re: ReVerLoc.A??) - CBVSetup now has option to enable or disable certain log entries. - McCbv now has an internal ANSI interpreter, and does not rely on the host system having ANSI.SYS loaded. - Support for up to 255 Com Ports using DGFossil Registered Version ------------------ - Post Messages To Sysop or Assistant Sysop based on CallBack Completion Results. Messages may be posted to a Hudson or a JAM base. - Set Validated Users Subscription Expiry Date - Set Validated Users User Group Number - Save verified phone numbers to the Users.Bbs (Choice of fields to save in) It will overwrite what is already in those fields, so choose carefully! - Notify user online that they have mail waiting (the welcome message) - Call Return feature, included on opening menu, allows the sysop to use calling services for LD callers, force callback secured link, and allow local callers to reverse a poor connection, all optionally configurable. A separate Call Return minimum security level can be specified. - In conjunction with Call Return, up to 9 LD Macros can specified, each with its own set of flags, security, LD hours, and other parameters. - If you set Dupe Checking to 3, to scan the RA Users.Bbs AND the Mc_Cbv.Ok file, you may automatically update users who have already been validated by the Cbv, but who have been deleted from the Users.Bbs When this is true AND you have created a REVERLD.A?? and or REVERLOC.A?? ascii and ansi file then that file will be shown to the user, and they will be treated as if the callback was a success. REVERLD will be shown to Long Distance Callers, and REVERLOC to local callers. This is useful if you delete users from your bbs after so many days, and they call back, you don't have to call them again. This is even better if you allow LD callbacks. - Multiple Language files supported in registered mode. You may create a language file for any language you have defined in RA. CBVSetup will read your language.ra file to see what languages you have set up. When a user enters the door who is using a language other than 0, then it will use the language they specified. - The WELCOME.MSG template posted to user now has 5 additional versions, plus language specific versions. ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Licensing Information ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ Motor City doors are commercial programs marketed under the "User Supported" or "Shareware" concept. You are allowed to install this program on Your system and evaluate it before deciding whether to purchase a license to continue using it. This program is not public domain or freeware. If you use this program for more than 30 days after successful installation, you are legally required to register it or remove all working copies from your system The User Supported or Shareware concept works only if you and your fellow sysops support it. If you find this program useful, you can register it for only $20.00 in U.S. funds. This will help offset the development costs, and encourage us to write other programs that might be useful to you. After all, no one likes to work for nothing! A Registration Form is included in the distribution archive. Mc_Cbv is Copyrighted 1992,1993 by Motor City Software, ALL RIGHTS RESERVED. You may copy this program and documentation for backup purposes. You also may copy and share UNMODIFIED copies of the original program archive. The copyright notice must remain attached to all copies. You may not sell Motor City Software products for a fee, or distribute them along with other products without written permission of Motor City Software, nor may you modify or remove the Copyright Notice from the program or the documentation. BBS operators who charge for access to their systems are exempt from this provision as long as no additional payment is required for access to Motor City Software products beyond basic file access. These files may NOT be placed on a CDROM medium without written permission of Motor City Software. All Motor City Software products are extensively tested before being publicly released, but as with any software, bugs may still occur. Motor City Software products are provided as is, and neither Motor City Software nor any BBS operator distributing this software is responsible for any damage incurred during the operation of the program. You are advised to test all Motor City Software products thoroughly on a backup copy of your BBS before putting them online. Comments, suggestions and bug reports are welcome. If you have any, you may call one of the Motor City Software Support Systems listed in SUPPORT.DOC and leave a message to the Sysop. If you're reporting a bug, please give as much detail as possible describing the problem you are having, your system configuration, and if you would be willing to test possible corrections to the problem. ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Upgrading From Previous Version ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ Version 1.0: You will be required to delete your MC_CBV.CFG (If you don't, CBVSetup will!) READ this whole document as there are many changes, including NEW FORMATS for the MC_CBV.LOC and MC_CBV.LD files. The /NOAC command line switch is no longer used, as Area Code stripping is now done using the MC_CBV.LD control file. Version 1.1: Run CBVSetup and update all new settings, and review your old ones, as new options are now available. Edit the supplied .A?? files if you wish to use them rather than the default screens. You can delete the old .TXT screens or use them as the basis for your .ASC and .ANS screens. Edit the .MSG files and be sure the filenames conform to the new version (see below). Run the language editor (within CBVSetup) to create the language file, and make any changes you wish. Version 2.0 and 2.1 Run CBVSetup and update all new settings, and review your old ones, as new options are now available. ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Setup ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ Setting Up ---------- Run CBVSetup to configure the CallBack Verifier. Online help is available by hitting the F1 Key on any field. CBVSetup should be fully self explanatory if you read the help screens. Running Mc_Cbv.EXE - The Door itself ------------------------------------ Usage: Mc_Cbv /N2 /N Defines the node number using CBV. You may use /N*N on the optional data line in the RA Menu option. Example: D:\BBS\CBV\Mc_Cbv.EXE /N*N If No Command Line Parameters are used, then it defaults to NODE 1. Place Mc_Cbv.EXE in its own directory, and call the Mc_Cbv.EXE from your Top Menu as a type 7. It will look for the EXITINFO.BBS and DORINFO1.DEF in the CURRENT Directory. It will look for its own files in the same directory which the EXE file resides in, with the exception of multiple language support (REGISTERED only!) SAMPLE RA MENU SETUP: 1 2 3 4 5 6 7 123456789012345678901234567890123456789012345678901234567890123456789012345 ; c:\ra\cbv\mc_cbv.exe /N*N *M Action Execute sub-program (Type 7) Display OptData HotKey AutoExec Yes Colour Colour example MinSec 0 TimeUsed 0 FlatCost 0 MaxSec 0 TimeLeft 0 TimeCost 0 A flags -------- Age 0 Terminal Any B flags -------- MinSpeed 0 Nodes C flags -------- MaxSpeed 0 Groups D flags -------- Credit 0 DayTimes Language support ---------------- This version of McCbv introduces Language File Support. This is similar to RemoteAccess and its .RAL files. McCbv uses .CBL (CallBack Language) files which are not compatable with .RAL files. Language files are edited, and created using CbvSetup. In unregistered mode, you may only use ONE language file, DEFAULT.CBL This language file MUST be created or the door will not function. When the CBV uses the DEFAULT language, it will look in the CBV Directory for the ASCII ANSI and Message Template files. You may modify the DEFAULT.CBL using the Language Editor which is built into CbvSetup. If you do not use the sample ANS and ASC screens included (or have not created your own) then McCbv will display its own default (hard-coded) screens when running. If you do use these files, they must be located in the same directory as MC_CBV.EXE If the message template files do not exist, no messages will be sent. If you have Registered McCbv, then you have the option of creating language files to match those used in RemoteAccess. It is IMPORTANT that you create a DEFAULT.CBL (and any screens or Msg Templates for the default language) even if you are adding other languages! In Registered Mode, you will be given the option of adding a language file for each one defined in RemoteAccess. CbvSetup will read the RemoteAccess LANGUAGE.RA file to determine which languages to allow. McCbv will allow you to define up to 50 different language files! For example, if you use ENGLISH.RAL and FRENCH.RAL on your bbs, and the user has ENGLISH selected, when they enter McCbv, the ENGLISH.CBL file will be used, and ALL *.A?? and *.MSG files for this language must be in a subdirectory off the CBV directory. The subdirectory name should be the same as the language name. e.g. English.Ral will use the ENGLISH.CBL in the CBVDIR\ directory, and ALL ANSI and ASCII files will be displayed from the CBVDIR\ENGLISH\ McCbv will also use the Welcome message templates in CBVDIR\ENGLISH\ This way you may welcome the User in their own language! SAMPLE DIRECTORY TREE C:\RA\CBV\ This directory MUST contain the following files : MC_CBV.EXE Callback Door CBVSETUP.EXE Setup Program MC_CBV.CFG Configuration File (Created by CbvSetup) MC_CBV.LOC Local Control File (You Must create this) DEFAULT.CBL Default Language File (MUST Exist!) MC_CBV.KEY Registration Key if you have one The Following files are optional and are used when the DEFAULT language is being used : *.ANS Replacement ANSI Screens *.ASC Replacement ASCII Screens *.MSG Message Template Files If you wish to create another language file, say FRENCH, then the file FRENCH.CBL will be created in the C:\RA\CBV directory. If you want the user to see French Screens as well as French Prompts you need to create the following subdirectory: C:\RA\CBV\FRENCH This subdirectory will contain any *.ANS and *.ASC files which you may modify so that all of the screens are in French. You may also put the WELCOME.MSG template (including specific welcome templates if you are registered) in this subdirectory, translated to French. This will allow you to greet new users in their own language! If the ANS and ASC files are not found in this directory, then McCbv WILL display the default hard-coded screens in Mc_Cbv.Exe. If the Welcome Message Template files are not found in this directory, then the CBV will NOT post a welcome message to the user. If you create a FRENCH.CBL but DO NOT create a \FRENCH subdirectory, then Mc_Cbv WILL use the DEFAULT directory and display the screens and use the message templates located there. The users Selected Language is read from the ExitInfo.BBS and that same language will be used in McCbv. IF the language file it is looking for does NOT exist, then DEFAULT.CBL will be used instead. If the language file exists, but the subdirectory for that language does NOT, then it will still use the language file, but will use the CBV directory for the ANSI, ASCII and message templates. The Language Files for McCbv are edited from within CbvSetup. To Edit a string, use the cursor keys to move to the line you wish to edit, and hit RETURN. The language editor allows you to define a color for each language string and use RA TextFile Control Codes to change colors in the language strings. To enter the Control-K, simply hit Control-K when editing the string. You can view the string, as it will appear when translated to ANSI in the door, by hitting Alt-V when editing the string. To change the color of the whole string, cursor to the string you wish to change, and hit Alt-C. The Activation keys, or 'hot keys', for any prompts in the language files are also definable. Long Distance Hours ___________________ The long distance hours can be set for the normal Callback Verification function, and for each Long Distance Macro individually (Macros are only available in Registered mode). Read the help in the CBVSetup program so that you understand the way in which this is done. For example, if I want LD allowed from 5 pm until 7 am the next day, you must set the Start Time at 17:00, and the ending time at 07:00 the NEXT day. If, on the weekend, you wish to allow LD all day Saturday and Sunday, and end it at 7 am Monday, set Saturday and Sunday to 00:00 start and end times and set Monday to end at 07:00. Then, if you wish it to start again at 17:00, set that for the Monday start time. Long Distance Macros & Call Return *REGISTERED ONLY* _____________________________________________________ If you subscribe to any long distance calling services, you may use this to enter the codes needed to reach that service. Here is the scenario around which it was designed: For me to call BBSLand is Long Distance. The Sysop in BBSLand has a special plan where he may call here free, but only during certain hours. The Sysop must dial an 18 digit number to gain access to this service, then dial the phone number, and follow it with a # Normally my number is long distance, but at night, and on weekends he may call it for free, by dialing the following: (SAMPLE ONLY... This is NOT a real code!!!!) 111-1111,1111111W9 and then the phone number (without Area Code) and follow this with a # The prefix is entered, then the suffix (in this case, #). A , pauses for one second and the W waits for a dial tone... To set this up, he defines the following in his MC_CBV.LD file.... NOT the .loc, this goes in the .LD file! 123456789012345678901234567890 416-404- [1]404- The 25th column MUST have the [ in it, followed by the Macro Number as set up in CBVSetup, and then the ] with NO SPACES!!! This is the SAME as an entry in the .loc file, except it has the Macro Definition BEFORE the Dial String. This goes in the .LD file because it is a number you WILL allow your system to call, and because it is using a Macro, you can define the Days and Hours that this Macro may be used. You define the hours for each separate Macro in CBVSetup. If a user with a matching phone number calls during the hours that this macro is NOT being used, then he will be shown a list of days and hours that you DO allow, and display an ANSI or ASCII file called MACROTIM.A?? to the user if it exists. Then the door will hang up on them. When a Macro is being used, it will NOT ask the user if the number looks ok to call, because it won't! Besides, you don't want them seeing your macros as they may contain billing codes or PIN numbers, etc. The users will NEVER see the Macro! You may also define whether to hang up on users of these macros. This will override the general settings set up in User Info. This will allow you to hang up on ACTUAL LONG DISTANCE calls which you allow, and use a macro, to reach SPRINT or another LD Carrier etc. In the case above, the sysop does NOT want to hang up, because the call is free. You may also define how to treat a user who calls from a number which you call back using a macro. You can either NOT UPDATE them at all (if used strictly to return calls, and NOT as a CBV) or you may give them either of the security settings (including flags, group, subdays etc) as a Long Distance Non-Verified User, a Verified Long Distance User, or a Local Verified User. You may define this for both when the macro is allowed, and for when it is not. This may open your BBS up to hundreds of thousands of new users. All I do is call his board, go into the CBV and tell it to call me back. It calls me, and I log onto the bbs. I will pay the initial couple minutes worth of Long Distance to get the CBV to call me back, but I will then be able to stay online for FREE once it calls me back. It can also be used to insure a secure BBS, by forcing the user to use Call Return. For this reason, and to aid those in areas where exchanges work better in one direction (from where the BBS is) to another (where the user is calling from) than the reverse, Local Call Return is also an option. If for example you want to be sure the caller is calling from where they say they are, force them to use the Call Return each time. To reverse normal long distance for certain users (for example, an employee calling from a long distance branch office), you will have to use a macro. To do this and still use your usual LD service, simply define the macro without anything in it. Then, put the macro in the .LD file in front of the area codes, exchanges, and perhaps even specific numbers you will call and for which you assume the LD charges. Note well that if you DO define macros you MUST specify the nodes that each each macro may be used on!! Bypass Callback and Update User _______________________________ You may hit Alt-U in order to bypass the actual callback. If you know who the user is, or for any reason want to skip the dialing etc, then you hit Alt-U while the user is at any prompt, and answer Yes when asked if you wish to bypass the callback. This simply sets a flag in memory, and when the Cbv is ready to hang up on the user, it will check this flag. If set, then Cbv skips calling the user, and assumes we have been reconnected and prompts the user for their password. They will then be udgraded exactly as if they had completed the call back. Other considerations ____________________ By using the COMMENT Field to store the phone number the user was validated at, it is easily visible by hitting the F6 key while the user is online. By using option 3 for checking of numbers (checks both the Mc_Cbv.OK and USERS.BBS), you are able to take full advantage of the REVERIFY function, and have the best security as well. ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Optional Message Template Files ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ Mc_Cbv will Post Messages to the Sysop or User if certain Message Template Files exist AND you chose a valid Hudson Message Base in CBVSetup. These files are ASCII Text files created using any text editor. We have included samples in an archive called MESSAGES.ARJ In each of these files, you will notice that line 1 contains the SUBJECT of the message. The rest of the lines may contain whatever you like, and the following TextFile Control Codes are Valid. (As used in RemoteAccess) ^FA - Current Users Full Name ^FW - Users First Name ^FO - Current Users Security Level ^F4 - Date of Current Users FIRST Call to BBS ^F3 - Current Users Subscription Expiry Date ^FE - Current Users Voice Phone Number ^FD - Current Users Data Phone Number ^F6 - Current Users Handle ^FB - Current Users Location ^F5 - Date Of Birth ^FP - Number of times the user has called your bbs ^FH - Users A Flags (8 Characters --XX-X-- ) ^FI - Users B Flags (8 Characters --XX-X-- ) ^FJ - Users C Flags (8 Characters --XX-X-- ) ^FK - Users D Flags (8 Characters --XX-X-- ) ^F$ - Address Line 1 ^F% - Address Line 2 ^F& - Address Line 3 ^KA - Total Calls To Your BBS ^KR - Baud Rate ^KW - Two digit Node Number The following Templates have been included, and if they exist, and a valid Hudson Message Base has been chosen, will cause a message to be written. Feel free to modify these as you see fit. Note that the registered only language support allows you to create the various welcome messages in the user's chosen language, and they must be in the specific language's directory. NONEED.MSG - Registered Version Only If this template exists in the same directory as Mc_Cbv.EXE and a user has a high enough security level to exempt them from using CBV, this message will be posted to alert you. NOTUSED.MSG - Registered Version Only If this template exists in the same directory as Mc_Cbv.EXE and the user for whatever reason does NOT use the CBV, then this will alert you. Once the template has been posted, a one line Reason is added to the message, explaining where the user Quit. VERIFIED.MSG - Registered Version Only If this template exists in the same directory as Mc_Cbv.EXE then this message will be posted to you when the user has completed the callback process. LDUPDATE.MSG - Registered Version Only If this template exists in the same directory as Mc_Cbv.EXE and you update LD callers without calling them back, this message will be posted to you. IEMSI.MSG - Registered Version Only If this template exists in the same directory as Mc_Cbv.EXE and you automatically update IEMSI users, then this message will be posted to you. FAILPW.MSG - Registered Version Only If this template exists in the same directory as Mc_Cbv.EXE and the user reconnects, but gets the password wrong, then this message will be posted to you. MACROTIM.MSG - Registered Version Only Posted to the sysop when a user calls OUTSIDE the hours the macro is allowed to be used. MACRO.MSG - Registered Version Only Posted To Sysop when a user is CALLED BACK using a macro. Registered only alternate welcome messages, with language support, are listed below. If any of these templates are not found, then the standard WELCOME.MSG will be used as the default template. LDVWELC.MSG - Registered Version Only Welcome message sent to Long Distance VERIFIED users. LDWELC.MSG - Registered Version Only Welcome message posted to Non-Verified LD users if you up- date them automatically. LOCWELC.MSG - Registered Version Only Welcome message posted to LOCAL verified users. IEWELC.MSG - Registered Version Only Welcome message posted to IEMSI Users if you update them automatically. MWELCn.MSG - Registered Version Only Welcome message posted to users who have used a Macro to call them back. This is posted ONLY if their security level is being updated. (First successful callback) WELCOME.MSG - If this template exists in the same directory as Mc_Cbv.EXE then it will be posted to the USER when they are verified. This will include IEMSI and LD users if you update them without doing the callback. This can be used to give them more information about joining your BBS, or anything you desire. This message will be posted TO the User, From the Sysop as defined in Dorinfo1.Def NOTE: If you are NOT registered, then the ONLY Message that you may post is WELCOME.MSG to the user. A reminder is written to the end of this message stating that this is an Unregistered Evaluation Copy, and requires registration after evaluating it. Welcome messages are written ONLY when upgrading security level to a higher level than the user had BEFORE the callback. In other words, the first time a user goes through the callback, he will likely be upgraded to the level you specify, and the WELCOME.MSG will be posted to them. If the user ALREADY has a security level equal to or above the one you give to users called back with the macro, it assumes he is using it strictly to get a free call, and no welcome.msg is posted. ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Optional Information text files ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ Mc_Cbv allows up to 25 .A?? files to be used to describe the door for the users. If the file isn't present then Mc_Cbv will use default text. These files should be located in the same directory as Mc_Cbv.EXE Samples of these files are included in the archive SCREENS.ARJ Note the sample screens which have been included are just that, a sample. These screens are based upon the assumption that TITLEBAR.* is being displayed (Registered Only) and may not look right with the default title when unregistered. Brief descriptions are as follows: The files support the RA Text File Control Codes for UserName, Phone Numbers etc. TITLEBAR.A?? *REGISTERED MODE ONLY* This can be used instead of the default 2 line titlebar at the top of the screen. Best to keep it to 3 lines max so it doesn't push other stuff off the screen. The screen is cleared before this is displayed. UINFO.A?? Used to show the user their phone numbers and security level etc when they enter the door. LDVHANG.A?? Displayed to Long Distance Users AFTER calling them back, and just before hanging up on them. This is only shown if you log off long distance users after calling them. GETNUM.A?? Displayed to the user when they are prompted for a new Phone Number if you allow them to Pick Another Number. DUPE.A?? Displayed to a user when their phone number has been detected as a duplicate. You may direct the user as to what they should do next, like leave you a message. PRECALL.A?? Displayed to the user once it has been determined that we will call them back. You can use this to explain to the user how to answer the call. NO_LD.A?? If you do NOT make Long Distance Callbacks to the users number, AND you do NOT update unverified long distance users, then this file will be displayed to them. You may use this to explain to them how they would get more access to your system. If you use the MC_CBV.LD file, you may list the areas codes, states, or regions you will call, explaining that you do not make ALL long distance calls. LDHANG.A?? Displayed to a Long Distance Caller who you have NOT allowed McCbv to call back IF you hang up on them. NOTTIME.A?? Displayed to a Long Distance Caller if you allow calls to that number, but ONLY during specific hours. This is only displayed if the call is not allowed at the current time. McCbv will then display a list of VALID days and times. ASKPHONE.A?? Displayed to the user once it has been determined that we will call this users phone number. Use this to explain the importance of making sure the phone number looks correct. The user will then be shown the number and asked if it looks correct. TELSYSOP.A?? Displayed to the user if they say the phone number does not look correct. EXPLAIN.A?? Displayed to the user if they say they do not know how to make their modem answer. This is a last chance to explain it to them, and then they will be asked once more if the understand. LOCHANG.A?? Displayed to a local user after you have called them back. This is only if you have configure McCbv to hang up on local users. NO_FIX.A?? This is displayed to users if their phone number is not in the proper format (If Using USA Format) and you have configured McCbv to NOT allow them to fix them. IEMSI.A?? Shown to IEMSI users if you validate them. NOUPDATE.A?? Shown to users after callback is completed if you have the CBV configured to NOT upgrade security for callback verified users. Useful for very secure systems in which the sysop wants to manually validate users after the callback. REVERLD.A?? Shown to users who are in the Mc_Cbv.OK file, but no REVERLOC.A?? longer in USERS.BBS, before they are automatically revalidated. This saves LD charges and per-call local charges on users who have previously been validated and then were removed from the USERS.BBS due to inactivity. If it does not exist, then the user is simply asked if they wish to continue the callback in the usual fashion REVERLD is for Long Distance users and REVERLOC is for Local Callers. With RA 1.1x it checks the number of calls to the BBS for this user and if it is their first call, then it assumes they have been deleted SINCE the original entry in the OK file. With RA 2.xx it compares the First Called Date, and if it is LATER than the date in the OK file, it will reverify the user. EVENT.A?? If you use /EVENTTIME-XX ( see Other Considerations above), this will be displayed to the user telling them that they are welcome to call back. TUTOR1.A?? Displayed in place of the first screen of the tutorial. TUTOR2.A?? Displayed in place of the second screen of the tutorial. HELPQUIT.A?? Displayed when Help is requested from the Main Menu. Explains how to quit the door from the menu. HELPCBV.A?? Displayed when Help is requested from the Main Menu. Explains how to access the Callback Verification function from the Main Menu. HELPTUT.A?? Displayed when Help is requested from the Main Menu. Explains how to access the Tutorial from the Main Menu. HELPRET.A?? *REGISTERED MODE ONLY* Displayed when Help is requested from the Main Menu. This part of the Main Menu help is not displayed if the caller does not have Call Return access or if the CBV is not registered. MACRO<n>.A?? *REGISTERED MODE ONLY* Displayed to a user who has been called back using a Long Distance Macro. <n> is the Macro Number. This is displayed following the Welcome Back line once the user types in their correct password. MACTIM<n>.A?? *REGISTERED MODE ONLY* Displayed to a user who would be dialed back using one of the defined Long Distance Macros, but it is outside the hours you allow it. This is displayed AFTER the hours and days have been shown to the user. MNODE<n>.A?? *REGISTERED MODE ONLY* This is displayed to a user who is calling from a phone number which uses a macro which is NOT allowed on the current node. <n> is the Macro Number. Note that when using THEDRAW or a similar ansi screen editor, you should not clear the screen, nor do you need to add a "press ENTER" prompt with a ^a at the end. Most screens display best with a blank line at top and bottom, except for the HELP*.A?? screens, which should only have a blank line at the bottom of each screen. Use "block save" or a recent version that does not save blank lines at the end of ANSI screens, and add the blank line in manually after saving the screen, or use a . as a place marker before saving and edit it out afterwards. ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Data text files ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ Samples are provided in the archive EXAMPLES.ARJ NOTE: Once you have created the MC_CBV.LOC and MC_CBV.LD files, I recommend you Scan them in CBVSetup. This option will scan these files and alert you of any INVALID lines in these files. This is useful if McCbv tells you that a call is NOT local, when you think that it has been defined properly within the MC_CBV.LOC file. This option is available on the EXIT Menu in CBVSetup. Data Text files: (* - means it's required) * Mc_Cbv.LOC - This file is used by McCbv to tell what phone numbers will be LOCAL Calls. This is much like FrontDoor, where it matches the users number against the first number, replacing the matching numbers with the dial string. Any line may be commented out by simply putting a semi-colon (;) in column 1. The first number MUST begin at column 1 in the file, and the string to dial MUST start at column 25 123456789012345678901234567890 416-404- 404- ;416-579- 579- 804-485- 485- 803-288- 803-288- ;This is a comment Field because it starts with ; in Column 1 In this case (416)404-2756 would be dialed as 404-2756 (416)579-XXXX would NOT be found as it is commented out. (804)485-2995 would be dialed as 485-2995 (803)288-2845 would be dialed as 803-288-2845 SPACES must be used to separate the numbers, NOT Tabs! This should make it possible to use Mc_Cbv almost anywhere in the world, all you do is define enough of the phone number to allow McCbv to decide the number is local, and tell it how to dial it. This makes it easy to support more than one Local Area Code. SAVE TIME SETTING UP MC_CBV!!!! If you are using North American Format numbers and you enable 'Attempt Unknown Local Calls' to Y, and a user enters a phone number which matches an AREA CODE from your Mc_Cbv.Loc file, then it will ask the user if this is a Long Distance number. If the user says it is a Local call, then Mc_Cbv will strip the area code, and attempt to dial it Without using a long Distance Prefix, or area code. If it reconnects with the user then obviously it IS a local call, and the proper entry will be made to the Mc_Cbv.Loc file. If it was, in fact, Long distance, you will simply get a recording from Bell, and no charges will be incurred ( I ASSUME NO RESPONSIBILITY for anything arising from using this feature. It DOES work here, I simply hear the recording and the call will fail) The BARE MINIMUM Mc_Cbv.LOC file you will need to create to get started is One Line for each Local Area Code. You MUST enter one exchange from each area code. E.g. 416-404- 404- 403-215- 215- From this point on, Mc_Cbv can build your Local Control File for you!!! Mc_Cbv.LD - If you set YES to call Long Distance in CbvSetup, then it will call ANY long distance number. If you would like to limit long distance to certain Area Codes, or Exchanges within Area Codes then you may define them in Mc_Cbv.LD This file is Exactly like Mc_Cbv.LOC, and if it exists, ANY NUMBERS which match will be allowed. In CBVSetup, set Allow LD Calls to NO, and define the ones you WILL call in here. If you don't wish to call any Long Distance, or don't want to limit the numbers which can be called, then do not create this file. Numbers in this file OVERRIDE the setting in CBVSetup. Note: This file DOES OVERRIDE the settings in CbvSetup, but it WILL still honor the defined Long Distance Hours. IMPORTANT! If you wish to allow calls to TOLL numbers, that is numbers in your area code, which are NOT free calls, you MUST define that Area code in your .LD file. If you dial them as 1-AAA-XXX-XXXX then this is not needed, but if you dial them as 1-XXX-XXXX then define your area code as follows: Assume 416 is your local area code. 123456789012345678901234567890 416- 1- See also the discussion of Long Distance Macros & Call Return above for the syntax used in the .LD file for the Macros. Mc_CbvNN.LD If you have multiple lines, but one, or some of them are limited to LOCAL and/or TOLL calls, but you DO want the other lines to call long distance, you may override the defaults by creating a node specific .LD file. For example, Node 1 can call anywhere, or at least what you have allowed it to using the MC_CBV.LD file, but Node 2 does NOT have a long distance service as part of your phone package. You may now create a MC_CBV02.LD file which defines the TOLL calls you will make from this node. NOTE, if you auto-update long distance users, they will be upgraded to NonVerified Long Distance levels if their number is NOT local and NOT defined in the node specific LD file. If you do NOT upgrade NonVerified LD users, then NO_LD.A?? will be displayed to them (you may use this to tell them to use another node to call specific areas) and they will not be upgraded. Mc_Cbv.LOG - Log of the doors activity. Made by the door. Mc_Cbv.BAD - List of phone numbers NOT TO CALL (your local police station fire station, etc.) Mc_Cbv will automatically not call 411, 911, 900 numbers and 555-1212 (directory assistance). You have to make this file if you want to define other Bad Numbers. If you wish to comment out a line, simply place a semi-colon ; in the first column. Each entry must be a complete phone number. In other words, putting 555- will NOT stop a user from using 555-1212 Wildcards are allowed: ? is a match with ANY number... 1-???-555-1212 will never match any long distance directory assistance. 911??????????? will not dial ANY number starting with 911 1-???-976-???? will never call ANY 976 number.... Mc_Cbv.OK - List of numbers the door has successfully called. INITnn.MDM - You may now override the modem init string for a specific node by creating a straight ASCII file called INITnn.MDM where nn is a two digit node number i.e. INIT01.MDM This file should contain one line, with the modem init string. The modem init string is limited to 38 characters. If you have Caller-ID on one or more of your modems, but not ALL, you may add a second line here with the String to send to the modem to recall the Caller-ID information. (eg. AT*T) If you do this, please leave the field blank in CbvSetup and use this to override each node on an individual basis. ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Frequently Asked Questions ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ Q: I have two nodes, and have long distance service on one node only, with NO LD service, and do NOT want to do even toll calls, on the other node. How do I do this? I understand that if I create a MC_CBV02.LD with the entry, for example, 123456789012345678901234567890 [column gauge only] 416- 1- that that node will only call toll calls in area code 416 and dial only the 1- in front of it. But what if I do NOT want to dial toll calls from that node? A: Simple! Just create a MC_CBV02.LD with a semicolon in column 1, add nothing else, and save it! Q: I am having problems with the language support. It does not seem to work for me! A: This is a setup problem. Your [language name].CBL must be in the same directory as MC_CBV.EXE, and all .MSG and .A?? must be in a subdirectory off the CBV's directory, named the same as [language name]. Go back and reread Language Support, above! Q: The door NEVER seems to know what the modem is doing! All the logs indicate that the modem returned nothing! A: Make SURE your modem is set to display result codes as words, usually V1. Q: While my modem usually returns extended result codes, such as CARRIER, PROTOCOL, COMPRESSION, and CONNECT strings, in my mailer I have to use W2 result codes instead. Do I need to do that in the CBV as well? A: No. MC_CBV understands and logs the extended result codes used by the W1 set in BT/Hayes command set modems, like the Hayes, PPI, Rockwell chipset, and other modems support. Q: I am having problems with the Call Return. People who are not even verified have it as a choice, and it is very confusing to them! A: Understandably! Just be sure that Call Return security in CBVSETUP is higher than new user, unverified security is set for your bbs, and it will work properly. Q: People who *have* been verified get CallBack Verification as a menu choice in the door! Why is this? A: You must set Exempt from callback verification to be the same as the LOWEST upgraded security level in CBVSETUP, and your problem is solved! Q: When some high speed modems call, the CBV's first attempt to call out *always* fails. It sounds like the caller's modem is still online! What can I do about this? A: MC_CBV allows you to specify the Modem Escape Code. If set to 0, it sends none at all. However, if you have the sort of problems you indicate, set it to 43 (the + character), or to whatever you have set your modem's escape character to (usually the S2 register). This will often force a cleaner and faster disconnect, at a slightly higher risk of call collision as the modem is on hook and open to callers for a few moments longer when the modem sends the escape sequence. Q: I run under Windows, and the CBV keeps bombing out. Why is this? A: Make sure you have SHARE loaded on your computer. Q: I run CBV from a batch file, and it does not seem to be upgrading the users when they complete the Call Back Verification? A: Run CBV as stated in the docs, do NOT run it from a batch file, but call it directly from the menu. ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Still Having Problems? ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ It is important to us that you are able to install and run our software with a minimum amount of effort on your part. Although we have tried to make this software as easy to use as possible, we do know that occasionally someone will have a problem. In order to provide the quickest response, we have a voice support number available, and all problems are usually solved with one quick phone call. See info at the top of this file. This is the FASTEST way to resolve any problems, although netmail messages will be replied to within 24 hours. (905) 404-8991 BBS (ZyXEL) FidoNet : 1:229/418 (905) 728-9910 FAX (905) 404-2756 Tech Support McSoft Corp. 22 Simcoe St N - BOX 229 Oshawa Ontario Canada L1G 4R8 ┌─────────────────────────────────────────────────────────────────────────────┐ │▓▓▓▓▓ Special Thanks To... ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ └─────────────────────────────────────────────────────────────────────────────┘ I would like to thank the following people for all their help and wisdom.... Bob R., Geoffrey Booher, Bruce Bodger, David Smart, Chuck Corvec, and all those who contacted me with problems and helped to test the fixes... Special thanks to Mark McKay, who wrote the original code which this door is based on, and Peter Kling, and Jeff Wilson who each helped out as well. And, of course, Andrew Milner, for such a fantastic Bulletin Board System! The biggest thanks of all go to those who have already registered this program! It is their support which has made this new version possible. Rod Hancock Motor City Software (905) 404-2756 Voice Support <end of document>