home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
EVENTS
/
CBVV14.EXE
/
CBV.DOC
next >
Wrap
Text File
|
1996-11-01
|
144KB
|
4,263 lines
J o h n D a i l e y ' s
▄▄▄▄▄▄ ▄ ▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄ ▄▄▄▄
██ █▀ ▄█▀ ██ ██ █
▄█▀ ▀ ██ ▄██ ██ ▄▀
██ ███▄▄▄▄█▀▀ ███ ▄▀
██ ▄██ ██ ████
██ █ ██▀ ▄█▀ ███
▀█▄▄▄▄▄▀ ▄███▄▄▄▄▄█▀ █▀ v1.4
John Dailey's
Call Back Verification System v1.4
Copyright (c) 1996 John Dailey
Written & programmed by John Dailey
─────────────────────────────────────────────────────────────────────────────
░ Warranty And Disclaimer ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
This software is provided AS IS without any expressed or implied warranties
whatsoever. No warranty of fitness for a particular purpose is offered. The
author of this software cannot be held responsible for DIRECT, INDIRECT
INCIDENTAL, CONSEQUENTIAL, or ANY OTHER damages due to your ability or
inability to use this software, even if the author has been advised of the
possibility of such damages. The user assumes full responsibility for the use
of this software.
As programming shareware is not the author's profession and is merely done as
a hobby in what spare time is available, no guarantee of future versions of
this, or any other software is stated either written or otherwise. New
versions of software will be provided as demand requires or as the author
sees fit.
─────────────────────────────────────────────────────────────────────────────
░ Archive Information ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
This software is being distributed in a secured archive form utilizing the
ARJ archiving software (Copyright (c) Robert Jung) for maximum compression
and ease of portability.
ARJ Security Envelope
Due to the unsecured distribution method of shareware, this software has
been archived with the ARJ security envelope feature. The security
envelope makes it nearly impossible for anyone, other than the original
creator of the archive, to modify the archive in any manner, thus
somewhat ensuring that no files will be missing, modified, or infected
with a virus.
Upon extraction of the archive, you should see the following message
displayed:
*** Valid ARJ-SECURITY envelope signature:
*** John Dailey R#2890
If you do not see this message displayed, DO NOT execute the software
enclosed, as the archive has most-likely been tampered with or is not an
archive created by the author. You may acquire a valid and secured
archive of the current version of this software by contacting John
Dailey at any of the addresses and/or sites listed at the end of this
documentation.
─────────────────────────────────────────────────────────────────────────────
░ Distribution Of CBV ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
The Call Back Verification archive may be distributed freely in its
unmodified, unregistered, security-sealed, archived form. You may freely
use, copy, and distribute CBVV14.EXE provided that no fee is charged for such
use, copying or distribution. It is recommended and highly encouraged that
you upload the shareware CBV archive to all of your favorite bulletin boards
and on-line services.
The Call Back Verification software, and the associated files are copyright
(c) 1996 John Dailey, all rights reserved.
I strongly prefer that the files be distributed in the format originally
released as CBVV14.EXE with the ARJ security envelope as created by the
author. If you must distribute the CBV archive in another archive format,
please archive the CBVV14.EXE as one file inside the other archive.
Re-archival of the software as separate files will not not include the ARJ
security envelope.
─────────────────────────────────────────────────────────────────────────────
░ Table Of Contents ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
Files Included In This Archive. . . . . . . . . . . . . . . . . . . . . 1
What Exactly Is CBV?. . . . . . . . . . . . . . . . . . . . . . . . . . 2
Display File Nomenclature . . . . . . . . . . . . . . . . . . . . . . . 3
Features Of CBV . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Quick Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . 8
The Pre/Post-Processor Concept. . . . . . . . . . . . . . . . . . . . . 10
Developing Pre/Post-Processors . . . . . . . . . . . . . . . . . . 11
Requesting A Pre/Post-Processor. . . . . . . . . . . . . . . . . . 12
Upgrading From Previous Versions. . . . . . . . . . . . . . . . . . . . 13
Installation Of CBV Files . . . . . . . . . . . . . . . . . . . . . . . 15
Configuration of CBV. . . . . . . . . . . . . . . . . . . . . . . . . . 17
File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Info. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Save. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Quit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
BBS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Area Code . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Dial Methods. . . . . . . . . . . . . . . . . . . . . . . . . 19
CBV Path. . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Disp Path . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Mail File . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Colors. . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Password Attempts . . . . . . . . . . . . . . . . . . . . . . 21
Minimum SL To CBV . . . . . . . . . . . . . . . . . . . . . . 21
Maximum SL To CBV . . . . . . . . . . . . . . . . . . . . . . 21
Security Level Settings . . . . . . . . . . . . . . . . . . . 21
System SL (SL) . . . . . . . . . . . . . . . . . . . . . 21
Download SL (DSL). . . . . . . . . . . . . . . . . . . . 21
Exemptions . . . . . . . . . . . . . . . . . . . . . . . 22
Restrictions . . . . . . . . . . . . . . . . . . . . . . 22
User Flags (AR/DAR). . . . . . . . . . . . . . . . . . . 22
Group. . . . . . . . . . . . . . . . . . . . . . . . . . 22
Subdays. . . . . . . . . . . . . . . . . . . . . . . . . 22
Credits. . . . . . . . . . . . . . . . . . . . . . . . . 22
Calls Per Day. . . . . . . . . . . . . . . . . . . . . . 22
Restriction and Flag Settings . . . . . . . . . . . . . . . . 23
Regular User SL . . . . . . . . . . . . . . . . . . . . . . . 24
Long Distance SL. . . . . . . . . . . . . . . . . . . . . . . 24
Bad Password SL . . . . . . . . . . . . . . . . . . . . . . . 24
Aborted SL. . . . . . . . . . . . . . . . . . . . . . . . . . 24
Bad Number SL . . . . . . . . . . . . . . . . . . . . . . . . 25
Duplicate Number SL . . . . . . . . . . . . . . . . . . . . . 25
Modem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Escape Command. . . . . . . . . . . . . . . . . . . . . . . . 26
Hangup. . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Dial Prefix . . . . . . . . . . . . . . . . . . . . . . . . . 26
Pickup. . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Modem Init. . . . . . . . . . . . . . . . . . . . . . . . . . 27
OK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
NO CARRIER. . . . . . . . . . . . . . . . . . . . . . . . . . 27
NO DIAL TONE. . . . . . . . . . . . . . . . . . . . . . . . . 27
CONNECT . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
RING. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
BUSY. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
VOICE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Result Wait . . . . . . . . . . . . . . . . . . . . . . . . . 28
Carrier Wait. . . . . . . . . . . . . . . . . . . . . . . . . 28
Redial Pause. . . . . . . . . . . . . . . . . . . . . . . . . 28
Dial Attempts . . . . . . . . . . . . . . . . . . . . . . . . 29
Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Validated Numbers . . . . . . . . . . . . . . . . . . . . . . 30
Bad Numbers . . . . . . . . . . . . . . . . . . . . . . . . . 30
Valid Exchanges . . . . . . . . . . . . . . . . . . . . . . . 30
Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Ask Password. . . . . . . . . . . . . . . . . . . . . . . . . 32
Allow Walk-through. . . . . . . . . . . . . . . . . . . . . . 32
Allow New Numbers . . . . . . . . . . . . . . . . . . . . . . 32
Allow LD Validations. . . . . . . . . . . . . . . . . . . . . 32
Hangup After LD . . . . . . . . . . . . . . . . . . . . . . . 33
Hangup Aborted User . . . . . . . . . . . . . . . . . . . . . 33
Hangup Bad Password . . . . . . . . . . . . . . . . . . . . . 33
Hangup After Callback . . . . . . . . . . . . . . . . . . . . 33
Validated Duplicates. . . . . . . . . . . . . . . . . . . . . 34
Auto-Validate Duplicates. . . . . . . . . . . . . . . . . . . 34
Phone In User Note. . . . . . . . . . . . . . . . . . . . . . 34
Password In Note. . . . . . . . . . . . . . . . . . . . . . . 34
Controlling Bad Numbers . . . . . . . . . . . . . . . . . . . . . . . . 35
Defining Local Numbers With Area Codes And Exchanges. . . . . . . . . . 36
Utilizing Dialing Methods . . . . . . . . . . . . . . . . . . . . . . . 38
Running CBV From The BBS. . . . . . . . . . . . . . . . . . . . . . . . 40
Installation for systems using EXITINFO.BBS (Remote Access,
ProBoard) . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Installation for systems using DOOR.SYS (TriBBS) . . . . . . . . . 42
Installation for WWIV BBS systems. . . . . . . . . . . . . . . . . 43
Pre/Post-Processors . . . . . . . . . . . . . . . . . . . . . . . . . . 44
EXITINFO.BBS (RA v2.00+, ProBoard) . . . . . . . . . . . . . . . . 44
DOOR.SYS (TriBBS). . . . . . . . . . . . . . . . . . . . . . . . . 45
WWIV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Configuration . . . . . . . . . . . . . . . . . . . . . . . . 46
Modified User Record Structures . . . . . . . . . . . . . . . 48
User E-Mail Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
VOICE.MSG. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
TIMEOUT.MSG. . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
BUSY.MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
FAILED.MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
SUCCESS.MSG. . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
SUCCESSL.MSG . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
ANSI/ASCII Display Files. . . . . . . . . . . . . . . . . . . . . . . . 52
Main Program Display Files . . . . . . . . . . . . . . . . . . . . 52
Walk-through Display Files . . . . . . . . . . . . . . . . . . . . 56
Local Console Key Controls. . . . . . . . . . . . . . . . . . . . . . . 58
Auto Upgrade Keys. . . . . . . . . . . . . . . . . . . . . . . . . 58
Sysop Bar Information. . . . . . . . . . . . . . . . . . . . . . . 58
Return User To BBS . . . . . . . . . . . . . . . . . . . . . . . . 58
Hang Up On User. . . . . . . . . . . . . . . . . . . . . . . . . . 58
Split-Screen Chat. . . . . . . . . . . . . . . . . . . . . . . . . 58
Shell To DOS . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Multi-Node Configuration. . . . . . . . . . . . . . . . . . . . . . . . 60
Node Identification By Command-Line. . . . . . . . . . . . . . . . 61
Node Identification By Environment Variable. . . . . . . . . . . . 62
Registration Of CBV . . . . . . . . . . . . . . . . . . . . . . . . . . 64
CBV Support Information . . . . . . . . . . . . . . . . . . . . . . . . 66
E-Mail Addresses . . . . . . . . . . . . . . . . . . . . . . . . . 66
Bulletin Board System. . . . . . . . . . . . . . . . . . . . . . . 66
World Wide Web . . . . . . . . . . . . . . . . . . . . . . . . . . 66
US Postal Address. . . . . . . . . . . . . . . . . . . . . . . . . 66
Author's Notes And Credits. . . . . . . . . . . . . . . . . . . . . . . 67
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
─────────────────────────────────────────────────────────────────────────────
░ Files Included In This Archive ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
CBV .DOC CBV Documentation
REGISTER.DOC CBV Registration Form
WHATSNEW.DOC CBV Program History File
CBVCFG .EXE CBV Configuration Software
CBV .EXE CBV Main Executable
CBVBAD# .DAT Sample Bad Phone Number Configuration File
DISPLAY1.EXE Sample CBV External ANSI/ASCII Display Files 1
DISPLAY2.EXE Sample CBV External ANSI/ASCII Display Files 2
EXIT_PPP.EXE EXITINFO.BBS (RA v2.00+ Format) Pre/Post-Processor
DOOR_PPP.EXE DOOR.SYS Pre/Post Processor
WWIV_PPP.EXE WWIV v4.20+ Pre/Post Processor
WWIV_PPP.CFG WWIV v4.20+ Pre/Post Processor Sample Config File
WWIV_PPP.OFS Sample WWIV_PPP Offset Configuration File
RACBV .BAT Sample RA Batch File
WWIVCBV .BAT Sample WWIV Batch File
15 Files
Page 1
─────────────────────────────────────────────────────────────────────────────
░ What Exactly Is CBV? ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
CBV, short for "Call Back Verification" has become much the standard for new
user validation on bulletin boards around the globe.
CBV works by gathering the user's phone numbers (either data or voice) from
the BBS user record, and calls the user back at one of those numbers. Upon
modem connection, the user is granted a higher security level because we now
know that indeed, someone is calling from the number specified, and are thus
less likely to wreck havoc (although not always) to the system.
There are many different Call Back Verifiers floating around in the BBS
world. Very few of them are not cripple-ware, meaning that some features of
the program have been disabled until the sysop sends in the suggested
registration fee. John Dailey's Call Back Verification software is NOT
cripple-ware or nag-ware and all functions listed are available in both the
shareware and registered versions of the software.
Page 2
─────────────────────────────────────────────────────────────────────────────
░ Display File Nomenclature ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
Throughout this documentation, external display files may be referenced as
having a filename extension of "A??." The "A??" merely signifies that the
file will either have an ".ANS" or an ".ASC" extension as in "DISPLAY.ASC" or
"DISPLAY.ANS." Files ending with "ANS" are color screens displayed to ANSI
(color) user's, while files ending in "ASC" are straight text screens
displayed to non-ANSI user's.
CBV will attempt to display the ANSI version of a display file if a user has
ANSI capabilities. If the ANSI file is missing, or the user does not have
ANSI graphic abilities, the ASCII (non-color) version of the display file
will be displayed instead.
Page 3
─────────────────────────────────────────────────────────────────────────────
░ Features Of CBV ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
Below is a list of general features that John Dailey's Call Back Verification
system offers:
* Will work with ALL BBS systems given that a pre/post-processor is
used for that system. Direct support for systems that utilize the
EXITINFO.BBS file for external programs (Remote Access, ProBoard),
systems that write and read from the DOOR.SYS dropfile (TriBBS),
and WWIV is included with the package, but support for any other
software can be added by simply adding a pre/post-processor for
that BBS type.
* Extremely configurable look. All screens used by the program are
external in ANSI and ASCII form. Program text colors can be
configured to go with the external display files.
* Multi-node capable.
* Multi-configuration capable, allow you to define different modem
command setups, different setups for different nodes, different
security level settings for different nodes, etc.
* Multiple local area-code support. Up to 25 local area codes may be
defined.
* Optional LD Validation Capability.
* Optional Define LD Calling Hours. Define LD callbacks to only be
allowed during certain times of day.
* Optional Hang-up on LD Callers after Validation.
* Optional capability to define all local exchanges for each area
code. Up to 600 exchanges may be defined for each area code.
* Specify dialing methods to tell CBV exactly how specific numbers,
area codes, or exchanges should be dialed. Useful for systems who
must dial an outside line before placing a call or for sysops who
have custom calling plans set up with phone companies and need to
dial specific code before placing a call to specific areas.
* Five (5) different upgrade security level settings :
For regular validated users
For regular long distance users
For aborted callbacks
For callbacks where number is a "Bad Number"
For callbacks where a number is duplicated
Each of these is optional
* A "Bad Phone Number" Control File to weed out certain phone numbers
that CBV should not call.
Page 4
* Checking of duplicate numbers/validations.
* Option to Auto Validate Duplicate Numbers.
* Sysop quick validation keys to bypass the callback and assign one
of the five pre-defined security settings.
* Secure password checking using CRC32 with RA v2.00+ if passwords
saved in this format. Also supported is RA v2.50's method of
storing passwords as text.
* Support for modifying restrictions and exemptions with WWIV v4.20+.
* Option to hang up on users that abort the call-back.
* Specify values for security levels, download security levels, group
numbers, flags, restrictions, credits, subscription expiration
days, and more.
* Hang up on users that enter an incorrect password or validation
code too many times.
* Hang up on users after validation.
* The ability to write a text file for import as e-mail to the user
upon an error, or successful callback.
* FOSSIL driver interface for bug-free modem support.
* Voice pickup detection (modem supporting only).
* Call-Collision handling. Incoming BBS calls will not interfere
with the callback process.
* Configurable results codes and modem command strings.
* Modem response window that displays responses from modem during
callback.
* Optional capability to allow user to enter a number not in their
information.
* Optional interactive walk-through tutorial on the call-back
process.
* Optional online instructions
* LOG capabilities.
* *NOT* Crippleware. All said features are fully functional in both
shareware and registered versions.
* Support for both modified and unmodified userrecs with WWIV BBS
systems.
Page 5
* Storing of the validated number in the user's note/comment
(pre/post-processor supporting only).
* DOS Shell (with memory swap to EMS or disk).
* Split-Screen and regular chat modes.
* Function Keys To Do The Following:
Return user to BBS
Hang up on user
Do both of the above, AND lock the user from the system by
adding their phone numbers to the BAD Number file and setting
their security level to zero.
Page 6
─────────────────────────────────────────────────────────────────────────────
░ System Requirements ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
In order to utilize Call Back Verification system v1.4 your system will
require the following hardware and software:
200k conventional RAM
Minimum of 300k HD space
Modem
FOSSIL driver (new with version 1.4)
BBS software
The following software is optional:
External e-mail import software for your BBS for importing e-mail
messages to your users.
Page 7
─────────────────────────────────────────────────────────────────────────────
░ Quick Installation ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
It is suggested that sysops read through this documentation in its entirety.
However, for your convienance, I have included this step-by-step quick
installation guide. Refer to the complete documentation for a more thorough
explanation and detailed examples.
If you are upgrading from a previous version of CBV, please refer to the
section on upgrading rather than this quick installation section.
It is assumed that you already have an average knowledge of DOS and
experience in setting up BBS utilities in general during this quick
installation.
1. Unarchive the main archive files into a separate directory off of
your main BBS system directory. I suggest a directory named "CBV"
or something similar such as C:\BBS\CBV.
2. Unarchive a display file archive (DISPLAY1.EXE or DISPLAY2.EXE)
into another directory off of the directory you placed the CBV
files in. If the example directory in step number one is used, I
suggest making this directory C:\BBS\CBV\DISPLAY.
3. Run the configuration program (CBVCFG.EXE), and modify your system
name, local area codes, and the location of the display files.
Modify other items as you see fit. Most are self-explanatory.
WWIV sysops should also modify the WWIV_PPP.CFG file with a
standard text editor. Instructions for the configuration file are
included in the sample configuration file itself.
4. Create a batch file to call CBV from your BBS. Follow the outline
of the example batch file below. As shown, be sure to call the
specific Pre/Post-Processor for your BBS software before AND after
calling CBV.
@ECHO OFF
EXIT_PPP -R C:\BBS C:\BBS\CBV
CBV C:\BBS\DOOR.SYS C:\BBS\CBV\CBV.CFG C:\BBS\CBV
EXIT_PPP -W C:\BBS C:\BBS\CBV -D
Batch files for all BBS types will most likely be identical aside
from which Pre/Post-Processor program you execute before and after
the main CBV program. Select the Pre/Post-Processor that works
correctly with your system.
If you are running RemoteAccess v2.50+ and have chosen to have your
user passwords stored as text, add the command line option
"-TEXTPW" to the first call to the EXIT_PPP.EXE software in your
batch file. For example:
EXIT_PPP -R C:\BBS C:\BBS\CBV -TEXTPW
Page 8
5. Modify your BBS to call the batch file. For WWIV sysops, it is
suggested that you setup your BBS to shrink when calling CBV.
6. Make sure that your FOSSIL driver is installed and working
properly. For BBS software that does not require the use of a
FOSSIL, it is recommended that you install a command-line FOSSIL
driver that can be installed right before CBV is ran and removed
from memory upon return to the BBS. The BNU FOSSIL driver software
is perfect for this application.
Page 9
─────────────────────────────────────────────────────────────────────────────
░ The Pre/Post-Processor Concept ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
While developing the Call Back Verification system, I wanted to make sure
that ALL sysops could benefit from its features, capabilities, and
configurability. This posed quite a problem due to the lack of similarities
between BBS types and their format for storing user records and information.
It was ascertained that most BBS softwares have the following information for
all users on record:
o Name and/or handle
o Voice phone number
o Data phone number
o Security level
o Flags
This is all the basic information needed in order to successfully control a
user's security. However, for this minute amount of information, one would
need to know the structure of each and every BBS software package to directly
support them from within the CBV program.
The idea itself seems quite outlandish, and the actual technical means of
doing so would increase program size and memory requirements, while at the
same time decreasing efficiency, speed, and ease of configuration.
Therefore, I developed a system of acquiring that information without
the actual CBV program needing to support ANY of the BBS structures.
The concept works on the idea similar to BBS door dropfiles, as in the
popular DOOR.SYS. CBV manages its own "drop file" to keep track of a
particular user's security level, thus eliminating the need to know any other
structures but its own. This drop file is stored in a plain text-file format
under the filename of CBV_PPP.DAT. Its format is outlined below, and is
described further in the section concerning development of processors.
User's Real Name
User's Handle (Real Name If No Handle)
User's Text Password
Is Password CRC32 Value Instead Of Text? (1 = Yes, 0 = No)
User's Password CRC32 Value (If supported, 0 if not)
User's Data Phone Number (XXX-XXX-XXXX preferred)
User's Voice Phone Number (XXX-XXX-XXXX preferred)
User's Flags
User's Exemption (0 - 255)
User's Restrictions
User's Security Level
User's Download Security Level
User's Note/Sysop Comment
User's Group Number*
User's Subscription Days*
User's Credits*
User's Max Calls Per Day*
* New in CBV version 1.4
Page 10
Understanding this "drop file" allows us to write programs that read a user's
information directly from the BBS data files, and write the "drop file" that
CBV needs before CBV is ran. After CBV is ran, this same program (or another
program if need be), reads CBV's "drop file", and writes the user's new
information to the BBS data files. Now, all that is needed to support a
particular BBS software is what I've come to call a Pre/Post-Processor; a
program that pre-processes and post-processes the user's information to/from
CBV's built-in format.
CBV is still in itself its own program. There is no need to update the whole
software package when new BBS softwares are developed, nor when a particular
BBS package updates and changes its user structure. Only the pre/post-
processor program needs to be changed, and with an average kilobyte size of
under 10k, this is not a major feat compared to the near 100k of the CBV
executable.
Developing Pre/Post-Processors
CBV comes with three Pre/Post-Processor packages in the distribution archive.
Additional processors will become available as they are developed and/or
discovered. The processors included will pre and post-processes the CBV
"drop file" for:
* Any BBS system that utilizes the EXITINFO.BBS file during execution
of external programs, such as Remote Access v2.00+ software. The
BBS software MUST re-read this file upon return and make changes to
the user's information if any were made. (EXIT_PPP.EXE) Three
popular software packages that utilize this method are Remote
Access, QuickBBS, and ProBoard.
* Any BBS software that directly utilizes the DOOR.SYS dropfile
itself as a means for keeping track of user information, such as
TriBBS. The BBS software must write this drop file before
executing an external program, and then RE-READ the file upon
return to see if any changes were made to the users information.
(DOOR_PPP.EXE) Again, TriBBS is an example BBS software package
that works well with this method.
* WWIV BBS software v4.20+. Due to the non-standardization of WWIV,
it requires its own special Pre/Post-Processor. Modified user
record structures are also supported with the WWIV Pre/Post-
Processor via an offset configuration file. The WWIV Pre/Post-
Processor reads from and writes to the BBS user database directly.
(WWIV_PPP.EXE)
Sysops who wish to develop their own Pre/Post-Processor are encouraged to do
so. Those sysops who do develop a Pre/Post-Processor for their BBS software
are also encouraged to send a working copy to myself to make available for
all users of CBV.
Page 11
Requesting A Pre/Post-Processor
Those sysops who wish to have a processor for their software, but are however
unable to develop one themselves are encouraged to submit a request to myself
at any of my e-mail or postal addresses. Before actually submitting a
request, please be sure that one of the already included Pre/Post-Processors
WILL NOT work with your BBS Software.
Sysops who do submit a request should also enclose with their request:
* A complete copy of the programmer's user record structures for that
particular package. This text file is usually outlined in the BBS
package's documentation, or as a separate text file such as
STRUCT.BBS. In this documentation will be a list of the variables
and their sizes that are stored for each user. User variables are
items such as the user's name, user's handle, date of first call,
screen size, etc.
If possible, it would be appreciated if the actual shareware
version of the BBS software could be uploaded to my BBS for testing
and examination.
* A sample, dummy user database as created by his/her BBS software
(if possible) for testing of the Pre/Post-Processor during
programming. If the BBS software is sent to me, then this option
isn't required.
Requests will be processed and completed as soon as possible. As with
software version updates, I cannot guarantee that a Pre/Post-processor will
be made available. Please allow at least four weeks before inquiring as to
the status of your request. Requestors are encouraged to test out the
particular Pre/Post-Processor for some time before distributing it.
Page 12
─────────────────────────────────────────────────────────────────────────────
░ Upgrading From Previous Versions ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
Upgrading from any version prior to 1.1 will require a total replacement of
executable files and configuration files. If you are upgrading from version
1.1ß, it is also suggested that you do a total re-install of CBV.
With ALL upgrades of CBV, you will need to add a FOSSIL driver software
package to your BBS for version 1.4 of CBV. A FOSSIL driver is merely
software that allows a program to communicate with your modem without having
to worry about the details of program to modem communication. Some examples
of great FOSSIL drivers are:
* WinFOSSIL for Windows 3.1 & Windows95, Woodruff Software Systems.
* X.00, for MS DOS and like Operating Systems, Raymond L. Gwinn
* BNU FOSSIL, David Nugent and Unique Computing Pty Limited
Each of these is available on my bulletin board system.
Before upgrading, be sure to completely back-up your already working copy of
CBV. Upgrading from 1.1 or 1.2 to 1.4 requires no major tasks. Follow these
few simple steps below:
1. Replace all of your current executables with the new executable
files from the 1.4 archive. This includes the CBV program itself,
configuration editor, and Pre/Post-Processor if you are using one
of the three standard ones included. Each has been updated to
support the new security features of CBV.
2. If you're using the standard display files, replace the old
versions that specify the old version number with the new ones from
the 1.4 archive (there are some new ones).
3. Run the new CBVCFG.EXE configuration program from your CBV
directory. CBVCFG will automatically recognize your old
configuration and upgrade it accordingly.
4. If you are upgrading from version 1.1, modify your local area codes
and calling exchanges according to the new format. If you have
defined exchanges, it is easiest to take the exchange data file
(CBVEXCH.DAT) from your old configuration, and separate each group
of numbers for each area code by a blank line, and add their
specific area codes to the top of each list. After completing
this, rename the file to CBVAREA.DAT. For example, if you had area
codes 407, 305, and 904 local to you, and exchanges were configured
in CBVEXCH.DAT as:
855
857
275
859
123
321
987
Page 13
919
And the first four were local to 407, the next two local to 305,
and the last two local to the 904 area code, you would modify the
file to look like so:
407
855
857
275
859
305
123
321
904
987
919
5. If you have upgraded your BBS software to RemoteAccess v2.50 and
are using the option to save user passwords as text, be sure to add
the command-line option "-TEXTPW" to the end of your first call to
EXIT_PPP.EXE in your batch file. For example:
EXIT_PPP.EXE -R C:\BBS C:\BBS\CBV -TEXTPW
6. If you are running WWIV BBS Software and have modified your user
record structure, you'll need to add the following lines to the end
of your offset configuration files WWIV_PPP.OFS. You may refer to
the new WWIV_PPP.OFS file included in this archive for an example
of what your offset file should look like. It is extremely
important that these new additions be added in the exact order at
the END of your offset definitions, flush to the left margin.
; Offset To Subscription Expiration Date (userrec.expires)
814
; Offset To User Credits (userrec.pos_account)
878
Make sure all other options are configured to your specifications, and your
upgrade is complete.
Page 14
─────────────────────────────────────────────────────────────────────────────
░ Installation Of CBV Files ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
Installation of CBV for the first time is fairly simple. Follow the few
steps outlined in this documentation for best results.
First, create a directory off of your main BBS directory that will store
CBV's files. Because there are quite a few files in the CBV archive, it is
a wise idea to store them by themselves and keep your BBS directory
uncluttered. In the following setup examples, I assume that your main BBS
directory is C:\BBS and that you are installing the CBV files in C:\BBS\CBV.
The following DOS commands accomplish this task:
CD\BBS
MD CBV
Next, unarchive or move the CBV package into this newly created
directory. Do this by first moving into the subdirectory you've created, and
run this self-extracting archive. The following commands will accomplish
this:
CD\BBS\CBV
<path to CBV archive>\CBVV12.EXE
Or, if the archive is already in your CBV directory:
CD\BBS\CBV
CBVV14.EXE
All of CBV's screens are external, and because there are a large number
of them, it is advised that you place these display files in their own
directory as well. Throughout this documentation, display files are assumed
to be located in C:\BBS\CBV\DISPLAY. The following commands install the
display screens in this directory:
CD\BBS\CBV
MD DISPLAY
CD DISPLAY
..\DISPLAY1.EXE
Two different display file groups are included with the distribution archive
of CBV. If you wish to use the second group of display files, substitute the
last line above with:
..\DISPLAY2.EXE
The basic files for CBV have now been installed, however, before you are
able to run the software package, you will need to configure it for your
system as outlined in the next section as well as install a FOSSIL driver.
Page 15
As mentioned, a FOSSIL driver is a small program that resides in memory and
allows software to talk to the modem. In my experience, utilizing a FOSSIL
driver with BBS doors is much more reliable versus allowing the DOOR to
communicate directly to the modem. Some examples of quality FOSSIL drivers
are:
* WinFOSSIL for Windows 3.1 & Windows95, Woodruff Software Systems
* X.00, for MS DOS and like Operating Systems, Raymond L. Gwinn
* BNU FOSSIL, David Nugent and Unique Computing Pty Limited
Each of these are available from my bulletin board system.
Page 16
─────────────────────────────────────────────────────────────────────────────
░ Configuration of CBV ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
The next step in installing CBV is to configure the software to your
specific needs. By using the included configuration software (CBVCFG.EXE),
you can configure nearly all aspects of the Call Back Verification door.
To start the configuration software, move to CBV's directory, and type
CBVCFG, followed by the enter key, at the DOS prompt. If you wish to specify
a filename for the configuration file, you may do so on the command line
here. For example:
CBVCFG.EXE [filename]
CBVCFG.EXE NODE1.CFG
Otherwise, CBVCFG will assume the configuration file is to be read from and
written to as CBV.CFG.
Move the highlight bar to the menu item you wish to modify/access and press
the enter key. When you have made all necessary changes, you may save them
by either going under the "File" menu and pressing enter on the save option,
or by pressing ESCape from the main menu to quit. CBVCFG will prompt you if
you wish to save your changes if any are made.
Pressing ESCape will also exit you to the previous menu, or cancel
changes to a specific option that requires input. Each main menu option is
listed in the following pages.
Page 17
File
────
Under this menu, you will find general information about CBV, the save
configuration option, and the selection to quit CBV.
Info
This selection merely gives general information about CBV, and its
cause. The information screen will not disappear until you move the
highlight bar to another menu.
Save
This menu option simply saves the current configuration, bad number
information (if any), and the valid exchanges (if any) to their
respective files. The configuration is saved in CBV.CFG (or the
filename specified on the command line), while the bad number
information is stored in CBVBAD#.DAT, and area codes and valid exchanges
are saved in CBVEXCH.DAT.
Quit
This option simply quits CBVCFG and returns to the operating system
prompt. If any changes have been made, CBVCFG will prompt the user
accordingly.
Page 18
BBS
───
This menu contains configuration aspects that pertain to your system.
Name
Obviously, your bulletin board system's name goes in this setting. Be
sure to enter it exactly as you wish it to be displayed to your new
users. Please note that in some places during software execution, CBV
will chop off extremely long system names to fit the name into parts of
the screen.
Area Code
This selection allows you to specify all area codes that are local to
your BBS system. You must enter at least one area code here, which
should be the primary area code that is part of your BBS phone number.
CBV will abort with a notice that you need to set your area code in the
configuration if you do not specify at least one area code. A maximum
of 25 local area codes may be defined. Pressing the 'A' - 'Z' keys will
assign specific dialing methods to all numbers within a selected area
code. Pressing the space bar will remove a dialing method from the
highlighted area code. Refer to the section on dialing methods for more
information.
Dial Methods
In this option, you may specify up to 26 different dialing methods that
are used to instruct CBV how to dial numbers in a given area code or
exchange. The first dialing method ('A') is always utilized for dialing
long distance numbers NOT LOCAL to your system. In addition to numbers
and dashes, you may specify 'A' for area code, 'E' for exchange, or 'N'
for number here when CBV is to dial that specific part of the phone
number. The default method for the first dial method is "1-A-E-N",
which will be interpreted as "1-407-296-3208" if a 407-296-3208 was the
number to be dialed. Refer to the section on dialing methods for more
information.
CBV Path
Enter on this line the path to your CBV program files, Leaving this
line blank will tell CBV to look in the current directory. In our above
example, you would enter C:\BBS\CBV. An ending backslash is not
required.
Disp Path
This is the full path to where CBV's display files are located. In our
example, this should be set to C:\BBS\CBV\DISPLAY. Again, leaving this
line blank specifies the current directory, and no ending backslash is
needed.
Log
CBV has the ability to log all its actions during use. If you don't
wish to log anything, simply keep this option blank. If you wish to
have CBV create its own log file in the CBV directory, then just specify
a name for the file (CBV.LOG). However, if you'd like, CBV can also add
it right to your BBS log file by specifying the path and name of that
log file (ie. C:\BBS\RA.LOG).
Page 19
Mail File
CBV also has the ability to copy specific files to a general text file
for import as e-mail to your user based on certain events. This
configuration option is where you would specify the complete filename
and path to which CBV is to write the completed text file for import.
See the section on E-Mail Files for more information on the Mail File.
Colors
The first and foremost option on configuring the look of CBV is the
colors that text is to be displayed in. From this menu, you will get to
choose the colors for all text displayed by the door to the user, and as
well, the specific color combination for the sysop information bar
located at the bottom of the screen. Simply move the highlight bar to
the item you wish to change the color for, press enter, and enter the
foreground and background color numbers you desire. For your
convenience, a color chart is displayed next to the menu showing the
available colors and their corresponding numbers.
Page 20
Security
────────
This menu sports various options concerning the security and validation
process of CBV. Security level values are dependent on your BBS
software. For RA systems, these values can range from 0 to 65535, while
for WWIV software, these values can range from 0 to 255. Setting any SL
configuration to zero (0) will tell CBV to NOT modify the user's
security level at any time.
Password Attempts
After a successful callback, CBV has the option to prompt the user to
enter their login password. The password attempts option specifies the
number of tries that a user will receive to enter the correct password
before exiting the call back verification door. Usually, the default of
three (3) attempts should suffice. If the ask for password feature is
disabled, this option has no affect.
The password attempt option also applies to when a user is inputting a
callback random codeword after a successfull connection.
Minimum SL To CBV
This option specifies the security level that a user must have or exceed
in order to run CBV. For example, if this option is set to 10, any user
that enters CBV with a security level of nine (9) or below will not be
permitted to be called back and CBV will merely exit back to the board.
All users with a security level of 10 and above (but below or equal to
the maximum security level) will be permitted.
Maximum SL To CBV
The opposite of Minimum SL To CBV, this option specifies the maximum
security level allowed for call back. For example, if set to 49, all
users with a security level of 50 and above will not be permitted in the
door. Most often, this feature will come in handy for WWIV sysops who
have installed CBV as part of their CHAINS menu.
Security Level Settings
The next nine (9) options deal with specific security levels that you
wish to award users with for certain call backs. Each one contains the
following in a submenu:
System SL (SL)
This is the security level that you wish to assign the user for
main BBS access.
Download SL (DSL)
Mainly for WWIV systems, this is the SL you wish to assign the user
for transfer/file area access. If your system software does not
have more than one security level field, then you may leave this
option to the default setting.
Page 21
Exemptions
Mainly for WWIV systems, this defines the exemption that you wish
to assign the user. It is a number ranging from 0 to 255. Please
consult your WWIV documentation for more information on each
exemption.
Restrictions
Mainly for WWIV systems, this defines the restrictions that you
wish to assign/toggle for users. WWIV's restrictions follow the
order of LCMA*PEVKNU. Each restriction may be turned on, off,
toggled, or left alone via this option. See the section below on
restriction and flag settings for information on how to configure
this portion of CBV.
User Flags (AR/DAR)
This setting pertains to a user's flags. With WWIV, sysops may
recognize these better as the user's ARs and DARs. Regardless,
they work fundamentally the same for each and every BBS type that
utilizes flags. See the section below on restriction and flag
settings for more information on how to configure this portion of
CBV.
Group
The group setting is used for BBS software systems that have
specific groups available to users. For example, some sysops may
have their system setup so that new users are all part of one
group, and after they have been validated, they're assigned to
another group. Setting this value to zero will not affect the
users group number, if any. Note that with all security options,
this feature is limited to BBS software and Pre/Post-Processors
that support it.
Subdays
Subscription days are utilized on some pay systems to determine a
"free-trial" period for new users. Here, you may specify how many
days from the current date that the user is attemptying CBV, a user
is to have until his or her account expires. As with other
security settings, this feature is limited to BBS software and
Pre/Post-Processors the support it. Entering any non-zero value
here will tell CBV to add that many days to the current date (when
performing a callback) and set that value as when the user's
subscription to the system will expire. For example, if the
Subdays was set to 10 and a user performed a successful callback on
March 7, their expiration date would be set to March 17th.
Credits
Some BBS software utilizes a credit, or monetary system to keep
track of how many messages can be posted, games played, or files
downloaded. You may specify a specific amount for this security
feature to be assigned to users assuming your BBS software utilizes
credits and your Pre/Post-Processor supports it.
Calls Per Day
Some systems also have the capability to limit the number of calls
per day users can have. Using this field, you can also set this
Page 22
value if your BBS and Pre/Post-Processor supports it.
Restriction and Flag Settings
CBV uses a very unique method for modifying a users restrictions and
flags, which makes it possible for the verification door to work well
with nearly all types of BBS software.
User flags are used on BBS systems as a signal that a particular user
has access (and in some cases, does not have access) for some particular
function of the BBS. Sysops can use flags to signify if a user has done
certain things, or signify users with extra-special access to areas that
regular users don't get. With Remote Access type systems, the flags are
divided into four (4) groups of eight (8) flags, known as A1-A8, B1-B8,
C1-C8, and D1-D8. WWIV flags (better known as ARs and DARs) are divided
into two (2) groups of sixteen (16) flags as A-P for ARs, and A-P for
DARs. (And it's not coincidence that this is exactly the same number of
flags for both software types)
With CBV, each flag can be represented as a dash (-) in the
configuration program. For Remote Access, this would be:
-------- -------- -------- --------
A1 - A8 B1 - B8 C1 - C8 D1 - D8
For WWIV, this would be:
---------------- ----------------
ABCDEFGHIJKLMNOP ABCDEFGHIJKLMNOP
When you start CBVCFG for the first time (or when a configuration file
is not found), the flags section for each security level will be defined
to either of the two (or blank), depending on the BBS software you are
running. Technically, the location of dashes and spaces in your flags
option does not matter; they are merely there as placeholders for you,
the sysop.
A dash (-) symbol in a flag slot signifies that CBV is to leave that
flag UNCHANGED. Placing an X, or a letter in a specific flags slot will
tell CBV to turn that flag on. Placing an equals sign (=) in a specific
flags slot will tell CBV to turn that flag off, and placing a percent
sign (%) will tell CBV to toggle the current state of the flag (ie. if
it's on, turn it off, and if it's off, turn it on). Spaces in the flags
and restriction settings are ignored. You may include spaces to keep
your flag sections separated into their corresponding groups.
Again:
"-" = Leave Flag Alone. Do Not Modify It.
"A-Z", "0-9" = Turn Flag On.
"=" = Turn Flag Off.
"%" = Toggle Flag's Current State.
" " = Ignore.
Page 23
With that in mind, if we tell CBV the following configuration for a
flags setting (in RemoteAccess format):
-X-----= ---%---- -------- -----%--
The A2 flag will be turned on, the A8 flag will be turned off, and the
B4 and D6 flags current states will be toggled. All other flags will
remain at their current setting.
Likewise, for a WWIV system, if the following configuration for a flags
setting was given:
----X----------- --=-------K---%-
The E AR, and the K DAR would be turned on, the C DAR would be turned
off, and the O DAR would be toggled. All other flags would remain
unchanged.
Restrictions work the same way. WWIV's restrictions are again, in the
order of LCMA*PEVKNU, so given the following example of:
-X---=-VK--
The C, V, and K restrictions would all be turned on, while the P
restriction would be turned off. Notice that you can use a symbolic
letter (or asterisk) as well as the 'X' to turn on specific ARs, DARs,
and restrictions. All other restrictions in this example would remain
unchanged.
Regular User SL
This security level and settings is assigned to a user who successfully
completes the call back verification process.
Long Distance SL
Users that call long distance can have a special security level after
they have been validated. If LD callbacks have been disabled, this menu
option has no effect.
Bad Password SL
If a use enters an incorrect password the maximum number of times, you
can instruct CBV to assign them this security level and settings. This
security level serves just that purpose. If password asking has been
disabled, this option has no effect. This security level also applies
to users who fail to enter the correct codeword if a codeword enabled
callback is failed.
Aborted SL
If a user aborted the callback, then this security level is assigned to
them.
Note that as with the hangup on aborted callback feature, if a long
distance user aborts the callback and long distance callbacks are NOT
allowed, the aborted security level will not be applied to the user.
However, if long distance callbacks are allowed and the aborted security
level will be applied to ALL users who abort the cbv process.
Page 24
Bad Number SL
If a user desires a callback at a number listed in the bad phone numbers
file, this security level is assigned to them.
Duplicate Number SL
If a user has a duplicate number (one that CBV has already validated),
CBV will assign this specific security level to them.
Page 25
Modem
─────
Version 1.4 of CBV now utilizes only an external FOSSIL driver for
accessing the communications port. Unlike previous versions, this
eliminates the need for internal configuration of the modem ports and
address information.
The modem menu lists options specific to controlling the modem during
the callback process. With the modem string commands you may enter
these additional characters that are interpreted by CBV:
| = Carriage Return - most of your commands should end with this.
Without this at the end of a modem command, your modem will not
recognize the commands. The exception to this rule is the dial command.
It is important that you DO NOT place this at the end of the dial
command.
~ = Pause 1/4s - this character will cause CBV to pause for a quarter of
a second while sending the string to the modem.
^ = Raise DTR - this character, if included in a modem string will tell
CBV to raise the DTR. This is the same as picking up the modem and
taking it "off-hook."
v = Lower DTR - is a character that will tell CBV to lower the DTR line.
This has the same affect as hanging up the modem or putting it
"on-hook." Please note that this is a LOWER CASE v.
Escape Command
This is the command that will make a modem already connected to another
modem go into command mode, allowing the use of "AT" commands to control
the modem. For most modems, this is three plus signs in a row (+++).
Your modem may require a delay before and after this command. Enter
enough pauses (~) to suffice. Most modems, in order to issue a standard
hangup command, require this command to be sent first to let the modem
know that text sent to it is to be processed as a modem command.
Hangup
This command tells your modem to hangup, or go on-hook. Usually, this
string should be set to the default, vATH0|. The lower-case "v" that is
in this string as the default lowers the DTR line of the modem. In most
cases, this will cause the modem to hang up. If you experience problems
with CBV hanging up, you may want to remove the "v" from this string.
It is not necessary to enter the escape command (+++) in front of the
hangup string, as CBV will do that automatically during the callback.
Dial Prefix
This command precedes the number in a dialing command. More often than
not, this string should be set to the default of ATDT, and you SHOULD
NOT place a carriage return at the end of it. Some individuals may
discover that they will need to dial a number to get an outside line
before a call can be placed. If so, you can add the correct dialing
Page 26
sequence in this slot. For example, if you need to dial a nine (9) to
get an outside line, you could set your dialing prefix to "ATDT9~" to
dial 9 and pause for a quarter of a second. CBV will automatically add
the number to be dialed and a carriage return to the end of this string.
Pickup
This command, often known as the off-hook string is the command that
tells your modem to pickup, or go off-hook. The default string of ATH1|
should suffice, however, you may need to add a raise DTR command.
Modem Init
This string is sent to your modem before each dial. This command should
merely set your modem to return "voice" or text connect messages and
turn the speaker off if enabled. The default string, with most Hayes
compatible modems, does just that. ATQ0V1X4M0|
The modem responses are keywords returned by your modem when certain
events occur. These should all be in capital letters with no spaces
before or after the string. The defaults are pretty much standard for
Hayes compatible modems.
OK
Otherwise known as the "ready response," this is the response sent by
the modem indicating that the last command was processed completely
without any errors. Usually this is simply set to "OK."
NO CARRIER
When a modem detects that no carrier was present to connect with, this
result is returned. The default setting of "NO CARRIER" should be
sufficient.
NO DIAL TONE
When dialing, sometimes there may not be a dial tone for various
reasons. When the modem detects that no dial tone is present, it
returns this string. The default for this string is set to "NO DIAL."
CONNECT
This is the base for the connect response generated upon a successful
connection. This string should be set to what your modem returns when
it connects, minus the baud/bps rate. For most modems this is either
the default setting of "CONNECT," or "CARRIER."
For example, if your modem returns "CONNECT 2400" upon a successful 2400
baud connection, you would put "CONNECT" in this option, however, if
your modem returned "CARRIER 38400," then you would need to specify
"CARRIER" here. Be sure that you do not include the baud/bps rate in
this option.
Page 27
RING
When the line rings that your modem is connected to, the modem will
generate this response. This is almost always "RING."
If your BBS phone line utilizes distinctive ringing for multiple phone
numbers on a single line, it is a good idea to put in the RING response
string the correct RING for the phone number that causes the BBS to
answer the phone. For example, if the BBS number is the primary phone
number on that line and the modem returns "RING A" when that telephone
number is dialed, you'd place "RING A" in this configuration option.
BUSY
The busy response is the response when a call reports a busy signal.
This is almost always "BUSY."
VOICE
Some modems have a feature that detects when a person talks into the
phone. These modems usually have a result code of "VOICE" when such a
detection is made. If your modem supports this feature, enter the
return string here. CBV will log all voice pickups.
Result Wait
This is the amount of seconds that CBV will wait for the OK results code
to be returned by the modem after commands. If the OK results code is
not received in this time, CBV will abort back to the system.
Carrier Wait
Maximum wait time for carrier specifies the amount of time, in seconds,
that you wish CBV to wait after a dial before determining that no
connection will be made. The default value of 60 seconds should be
fine, however, you may find that you can safely set this to 30 seconds.
Be sure that there is enough time for your modem to connect. If not,
your modem may be in the connection process when this time limit runs
out, and CBV will hang up.
If your modem takes an extra long time to connect to specific modems,
you may want to increase this value to tell CBV to wait long enough so
that the modems may connect. CBV will NOT wait the entire amount if a
successful connection is made before the time is up. This option merely
specifies the maximum amount of time to wait for a successful connection
response code from the modem.
Redial Pause
This setting defines the number of seconds to wait between each dial
attempt to the user. CBV will also pause for this amount of time before
the first dial attempt to give the user time to prepare.
Page 28
Dial Attempts
Maximum attempts for callback specifies the total number of times that
you wish CBV to try for a connect. The default of 3 callback attempts
should be sufficient in most cases. After the dial attempts reaches
this maximum value, CBV will abort and return control back to the BBS.
If the failed callback message file is available, that file will also be
output as the e-mail file for the user CBV was attempting to callback.
See the e-mail section for more information on leaving e-mail for users
that fail a callback.
Page 29
Numbers
───────
This menu sports some features that deal with already validated numbers,
numbers that CBV is not allowed to call, and valid exchanges and area
codes that are local to your calling area.
Validated Numbers
This option will simply display the file CBVNUMS.DAT, which contains
each number validated by CBV.
Bad Numbers
This menu selection will bring up an input window. Here, you may enter
all of the numbers, and parts of numbers, that you do not wish CBV to
call. To enter a number, or part of a phone number, simply being typing
that phone number. To delete a number, move the highlight bar to the
number you wish to delete, and press the delete key on your keyboard.
Simply put any number that you don't want CBV to callback in this menu
entry. Or put a section of a number in this file to limit multiple
phone number restrictions. For example, if the numbers 555-1212
(directory assistance), 123-1234, and 123-4567 were entered in this menu
option, they will not be called. If 911- or 411- were included, any
numbers that include 911- or 411- will also be avoided. Be sure to
include the dash after three digit numbers. If the 911- was entered as
just 911 (no dash), all numbers that had 911 in them would be
restricted, ie. 851-9112, 234-0911, etc. Using the dash as the end
will restrict a three-digit number.
See the section on Controlling Bad Numbers for more information.
Valid Exchanges
By default, CBV will simply ask the user if their phone number is long
distance from the BBS. If you'd like CBV to already know if a user's
number is local or not, you can configure the local exchanges for each
local area code to your system.
Please note that CBV will not be able to decide if a user's phone number
is LD or local (regardless of which method you use) until the user first
selects a phone number to be called back at. It will attempt to guess
however to facilitate some features of the program.
The exchange part of a phone number is the first three digits of a seven
digit number. For example, in 275-5996, 275 is the exchange. Each
calling area in a given area code may call specific exchanges
charge-free by the telephone company. You can usually find a listing of
toll-free exchanges in the first few pages of your residential phone
book. If not, call your local telephone company to acquire a listing.
To enter exchanges for each area code, simply select the "Valid
Exchanges" menu option. Next, a list of local defined area codes will
be presented to you. Select the area code that you wish to modify
exchanges for. Another window will replace the area code listing, and
you may begin entering exchanges for that area code. To enter an
Page 30
exchange, simply start typing the three digit number, and press Enter to
save it in the list. To delete a number from the list, move the
highlight bar to the one you wish to delete, and press the delete key on
your keyboard.
See the section on Defining Local Numbers With Area Codes And Exchanges
for more information.
As with area code definitions, you may assign specific dialing methods
to each exchange by pressing the letter corresponding to that dialing
method in the configuration. Pressing the space bar will remove the
dialing method from the selected exchange. See the section on dialing
methods for more detailed information on defining dialing methods.
Page 31
Options
───────
This menu controls some various miscellaneous features of CBV. Each
setting can either be 'yes' or 'no'. To change the selected feature,
simply press the Enter or space bar.
Ask Password
When a successful connection is made in CBV, you can instruct the
program to ask for the login password the user used to log onto the
system with. Setting this to yes enables this feature. CBV will ask
the user for their password a maximum of the number of times that you
configured CBV to under the security menu.
Allow Walk-through
The CBV software features an interactive walk through explanation of the
call back verification process. If you wish your users to be able to
use this walk through to learn exactly what it's like to do a call back,
enable this feature. The choice will be presented to them from the main
menu.
Allow New Numbers
This setting, when enabled, will add a menu selection from CBV's main
menu to allow the user to enter a number other than their voice or data
number to be called back at. CBV will also ask for a reason, and write
that reason to the log file (if enabled), as well as the number called
itself. CBV will not call a user-entered number until the reason has
been answered.
This may be handy for some user's that may be calling from a friend's
house. However, it can be a major downfall to system security. For
example, a user could call your system, say they are someone, enter a
"supposed" number as their voice and data phone numbers, and be
validated at a totally different number via this feature if it is
enabled. However, CBV will log the phone number used, and if the phone
in user note feature is enabled, will also put the phone number the user
was called back at in their sysop comment field of their user record
information.
Allow LD Validations
If enabled, this will allow CBV to call long distance numbers back for
validation. YOU WILL BE CHARGED FOR THE CALL UNTIL THE USER HANGS UP!
If you wish to not be charged any additional amount after the user has
been validated, be sure to instruct CBV to hangup on the LD users after
validation. Changing this option to yes from a setting of no will bring
up the Long Distance Hours window. In this window, you can set the days
and hours that you wish to allow and disallow long distance call-backs.
Setting this feature to no disables the LD hours submenu.
Each day appears on the menu with two times in 24 hour format
(00:00-23:59). Simply move the highlight bar to the day that
you wish to define the hours for and press the enter key.
CBV's day begins at 00:00 (midnight), and ends at 23:59
(11:59pm). Leaving a specific day blank will disable long
distance call backs on that specific day.
Page 32
For example, if we define Sunday to have the following hours:
12:00 - 19:00
Long distance callbacks will only be allowed between the
hours of noon and 7:00pm. Likewise, if we defined the
hours of:
00:00 - 23:59
Long distance callbacks would be allowed all day long.
If you wish to have long distance callbacks allowed from 9:00pm on
Monday to 7:00am Tuesday, you would need to specify times as
follows:
Monday: 21:00 - 23:59
Tuesday: 00:00 - 07:00
As you can see, Tuesday begins at midnight, therefore, the times
after midnight (12:01am - 7:00am) must be defined on Tuesday, while
the times before midnight are still officially Monday, and must be
defined as such.
Sysops may wish to use this feature to only allow LD callbacks
during the least expensive times of the day, and on weekends.
Hangup After LD
After a long distance validation, you have the option to hang up on the
caller so that he/she can call the system back. If enabled, CBV will
hang up on a long distance caller after successful callback. It is
suggested that if you are enabling LD callbacks, that you also enable
this feature to minimize long distance charges. If CBV calls a LD
number back for verification, and you do not hang up on the user, YOU
WILL BE CHARGED BY YOUR PHONE COMPANY FOR THE REMAINDER OF THE USERS
TIME!
Hangup Aborted User
If a user aborts the call back process, you can also have CBV hang up on
them as well. Enable this feature if you wish to hang up on users that
abort CBV by quitting the program before being called back. If long
distance callbacks are not allowed and a long distance caller aborts the
call back process, CBV will *NOT* hang up on them. However, if long
distance callbacks are allowed and the hangup on aborted user feature is
enabled, CBV WILL hang up on that user.
Hangup Bad Password
As well as for users that abort CBV, you can also have CBV hang up on
users that enter the incorrect password too many times. Enable this
feature if you would like CBV to hang up after the user enters the
incorrect password too many times as defined under the security menu.
Hangup After Callback
If this feature is enabled, CBV will hang up on ALL users after
validation.
Page 33
Validated Duplicates
CBV logs every call that it makes and successfully connects to to a file
called CBVNUMS.DAT. If this feature is disabled, CBV will not let a
user with a number contained in that file to be validated.
Auto-Validate Duplicates
CBV also has the ability to automatically upgrade users whose number has
already been validated by CBV in the past. This feature can be handy
for users who get deleted by the system due to lack of regular calls to
the system. If this feature is enabled, CBV will not call the user back
to verify that they exist if their phone number to be called back at is
found in the CBVNUMS.DAT file, and upgrade their security accordingly.
Please note however, that if more than one user calls with the same
phone numbers and this feature is enabled that they will be validated,
which could allow your users to have duplicate accounts.
Phone In User Note
If enabled, will tell CBV to write the phone number that the user was
validated at to the sysop comment/note line of the user's record.
Password In Note
If enabled, along with the "Ask Password" feature, will tell CBV to
write the user's password as they entered it, into the sysop
comment/note line of the user's record. This feature can be very handy
for BBS software that does not store a text version of the user's
password, but instead stores a CRC 32bit value instead such as
RemoteAccess (versions prior to 2.50).
Use Random Codeword
Instructs CBV to generate a random codeword to present to the user
before callback. Upon a successfull callback, CBV will prompt the user
for this codeword just as if it were the user's password. This random
codeword is significant only for the current call back session and will
help keep user's from arranging "pre-arranged" callbacks.
Note that this is an additional feature that can also be used in
conjunction with the password prompting feature of CBV. Turning both
features on will cause CBV to prompt for the user's password AND the
random codeword that it generates.
If the password feature of CBV does not work properly with your
particular BBS package (due to user-record structure changes, Pre/Post-
Processor incompatibilities, etc.), this option may be used in place of
checking against a user's password with as much security and success.
Page 34
─────────────────────────────────────────────────────────────────────────────
░ Controlling Bad Numbers ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
The CBVBAD#.DAT file is the control file to disallow calls to certain phone
numbers. This file is a plain text file and can be edited with any text
editor that saves in plain text format. Lines that begin with semi-colons
(;) and blank lines are ignored. Below is an example CBVBAD#.DAT file.
; CBV v1.4
; Copyright (c) 1996 John Dailey
; Written & programmed by John Dailey
;
; Bad phone number control file
;
; Lines preceded with a semi-colon (;) are considered comment lines. Blank
; lines are ignored. Enter each phone number that you wish not to be
; called. Entering a part of a phone number will disable calls to any phone
; number that contains the section listed.
;
; ie. If 111 is listed in this file, all numbers that contain '111' in them
; will not be called. That means that 855-1110 will not be called, nor will
; 111-4561, 855-2111, or 111-855-1231.
;
; To disable calls to certain area codes, simply put a three digit area code
; followed by a dash as in '102-'. All area code '102' numbers in this
; example will not be called.
;
; Sysops may wish to put their BBS number in this file as well as the few
; listed below for added security.
911-
411-
555-1212
123-1234
123-4567
; End of bad phone number control file
Page 35
─────────────────────────────────────────────────────────────────────────────
░ Defining Local Numbers With Area Codes And Exchanges ░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
Area codes and phone number exchanges are the key to deciphering what phone
numbers are local and long distance from your BBS. A basic U.S. phone number
can be split up into four parts:
1-407-296-3208
│ │ │ │
│ │ │ Extension
│ │ │
│ │ Exchange
│ │
│ Area Code
│
Country Code (LD access code)
As you can see in the phone number above, the first group of three numbers
after the country code is the area code (407), and the exchange (296) is the
first three non-area code digits of a phone number. Each specific area code
(depending on where you are calling from) has a list of exchanges that can be
called toll free.
Local exchanges for a particular area code can usually be found in the front
few pages of your residential phone book. Call your local telephone company
for information on obtaining a listing if you cannot find one.
By default, only defining the area codes that are local to you will configure
CBV to simply ask each user if their number is long distance from your BBS.
Instead of leaving this up to your users, you may want CBV to be able to tell
automatically. This is easily accomplished by configuring CBV with all local
area codes, and their respective exchanges via CBVCFG. Advantages of this
feature are only for system security. Setting up your copy of CBV to
recognize local numbers will keep users from having your CBV call long
distance numbers for "the fun of it," or by accident.
To define your local calling exchanges, simply enter CBVCFG and modify the
settings to reflect your calling area. First, under the BBS menu, add in all
area codes that are local (non-LD) to your system's phone number. Up to 25
local area codes can be defined. Next, choose the "Numbers" menu, select
each area code, and enter each exchange as listed in your phone book,
respectively. A maximum of 600 exchanges can be defined per each area code.
Beginning with version 1.2 of the Call Back Verification System, all area
code and exchange information is saved in one file named CBVAREA.DAT. This
file is a simple plain ASCII text file with each area code listed in
succession. Under each area code are the valid exchanges for that area code,
and each group of area code/exchanges is separated by a blank line. Below is
an example area code and exchange configuration file:
Page 36
; CBV v1.4
; Copyright (c) 1996 John Dailey
; Written & programmed by John Dailey
;
; Local Area Codes And Exchanges Control File
;
; Lines preceded with a semi-colon (;) are considered comment lines. Blank
; lines are ignored. Enter each area code that is local to your BBS on
; individual lines, followed by all exchanges associated with that area code.
; Separate each group of area codes and exchanges with a blank line:
;
; 407 (Area Code)
; 855 (Exchange)
; 857 (Exchange)
; 275 (Exchange)
;
; 305 (Area Code)
; 565 (Exchange)
;
; 215 (Area Code)
; ...etc.
;
407
855
857
296
658
; End Of Area Code And Exchanges Configuration File
In the above example, only the 407 area code is local to the BBS. The only
exchanges that are local are 855, 857, 296, and 658. Any others are
considered long distance. In this example, if a user was to call with the
phone number 407-296-5996, CBV would know that this number is local because
its exchange (296) is listed in the exchange configuration for its area code
(407). However, if a user with the phone number 407-294-9446 entered CBV,
CBV would only call that number if the sysop has allowed long distance
callbacks because it's exchange (294) is not listed as a local number for the
BBS's 407 area code. A phone number of 305-123-1234 would also be considered
long distance simply because the area code is not listed as a local area code
in the above example.
Page 37
─────────────────────────────────────────────────────────────────────────────
░ Utilizing Dialing Methods ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
Begining with version 1.4 of the Call Back Verification software, sysops may
define specific ways that CBV is to dial phone numbers for a given area code
or exchange. This can be extremely handy for sysops who live in areas with
multiple local area codes and are required to dial in specific ways for each
area code or exchange, or for sysops who must dial a specific sequence of
numbers to get an outside line, access a specific calling plan, etc.
From the BBS menu of CBVCFG.EXE, up to 26 different dialing methods may be
defined. CBV automatically utilizes the first dialing method for all area
codes not defined as local to your BBS system, so define the long distance
dialing method here. The default dialing method 1-A-E-N should be sufficient
for most systems.
Again, dialing method "A" is reserved for calling numbers that are discovered
to be long distance from your system.
Dialing methods can consist of any arangement of numbers and/or dashes. To
signify that the area code, exchange, or 4-digit number of a particular phone
number is to be dialed, simply place an "A," "E," or "N" for each
respectively in the dialing method.
For example, if long distance numbers were to be dialed in the fashion of 1,
the area code, plus the phone number, the correct dialing method would be:
1-A-E-N
In the case of 407-857-3275 being the phone number to dial, CBV would
automatically replace the above dialing method with:
1-407-857-3275
As a more complicated example, let's assume that your BBS's phone number is
in the area code 123, and that CBV is preparing to call back a user located
in area code 321, which is local to your BBS. Also assume that you need to
dial the user's phone number as the area code, plus the seven digits
afterward (without the 1- before the number). The correct dialing method to
accomplish this would be:
A-E-N
CBV would replace the "A" in the above example with the area code of the
user's phone number, in this case, 321. The "E" and "N" would automatically
be replaced with the exchange, and 4-digit number respectively.
After defining all the needed dialing methods for your situation, you'll need
to assign those needed dialing methods to the exchanges or prefixes that
require them in CBV's configuration editor.
Page 38
To assign a dialing method, simply highlight the desired area code or
exchange and type the letter of the dialing method to assign. The dialing
method of a given exchange over-rides the method assigned to the area code to
which the exchange is a member of. In other words, if a number has dialing
method 'B' assigned to it via the Area Code configuration and has dialing
method 'C' assigned to it via the Local Exchange (for that area code)
configuration, CBV will use dialing method 'C' to dial the number.
CBV will always use the dialing method assigned to a number's area code or
exchange
Page 39
─────────────────────────────────────────────────────────────────────────────
░ Running CBV From The BBS ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
The last steps in configuring CBV is to create the actual batch files that
you will call from your BBS software to run the door, and modify your BBS to
call those batch files. It is suggested that you place CBV's batch file in
your main BBS directory, however, it is not required that you do so.
CBV as it is to be run online requires three different command line
parameters. Running CBV with no parameters will bring up a display screen
showing the correct calling method for the program. These parameters, in
order they must appear on the command line, are:
CBV.EXE <drop file> <configuration filename> <CBV_PPP.DAT location>
<drop file> - The full path and filename of your BBS drop file.
Currently, DOOR.SYS and CHAIN.TXT are the two directly supported
drop file formats from within CBV. Using a door drop file
converter such will make many more drop files usable.
<configuration filename> - The full path and filename of your CBV
configuration file. This command line parameter makes it easy to
incorporate different configuration files for specific nodes,
different modems, etc.
<CBV_PPP.DAT location> - The full path to where CBV can find the CBV
Pre/Post-Processor data file as created by the processor software
(CBV_PPP.DAT). The CBV_PPP.DAT file is what CBV uses to read and
write the user's information. CBV will not function if it does not
find this file. For more information on the CBV_PPP processor
file, refer to the section on the Pre/Post-Processor concept, and
the section on setting up CBV's included Pre/Post-Processors.
Depending on your Pre/Post-Processor software, you will probably also need to
specify a few parameters on its command line as well. Refer to the
processor's documentation for specific details when dealing with processor's
not included with the distribution archive of CBV.
Your basic CBV batch file should consist of three lines:
1. A call to the Pre/Post-Processor to read the user's information and
create the CBV_PPP.DAT file.
2. A call to the actual CBV program with needed command-line
parameters.
3. A call to the Pre/Post-Processor to read the CBV_PPP.DAT file and
update the user's information.
Page 40
Installation for systems using EXITINFO.BBS (Remote Access, ProBoard)
For RA BBS Systems, your batch file should resemble the following:
@ECHO OFF
CD\RA\CBV
EXIT_PPP -R C:\RA\ C:\RA\
CBV C:\RA\DOOR.SYS C:\RA\CBV\CBV.CFG C:\RA\
EXIT_PPP -W C:\RA\ -D
CD\RA
After creating a batch file, create a menu option from your BBS that will run
that batch file. For Remote Access v2.00+, the correct command line
(assuming you've installed it into the example directories) is shown below:
*C /C C:\RA\CBV.BAT *M
The *C tells Remote Access to engage a DOS shell that will not remain
permanent (the /C tells DOS that), and run the batch file CBV.BAT located in
the main BBS directory. The *M parameter instructs Remote Access to swap its
memory. This swapping may not be necessary for your system.
If you are running RemoteAccess v2.50 and have setup the system to store the
user's passwords as text instead of a CRC32 bit value, you'll need to add the
command-line option "-TEXTPW" to the command line for your Pre-Processor call
before running CBV. For example:
EXIT_PPP -R C:\RA\ C:\RA\ -TEXTPW
This command-line option tells EXIT_PPP.EXE to correctly write the password
information into the CBV_PPP.DAT file as text instead of a CRC32 bit value.
Page 41
Installation for systems using DOOR.SYS (TriBBS)
@ECHO OFF
CD\TRIBBS\CBV
DOOR_PPP -R C:\TRIBBS\DOOR.SYS C:\TRIBBS\CBV
CBV C:\TRIBBS\DOOR.SYS C:\TRIBBS\CBV\CBV.CFG C:\TRIBBS\CBV
DOOR_PPP -W C:\TRIBBS\DOOR.SYS C:\TRIBBS\CBV -D
CD\TRIBBS
BOARD.BAT
Sample doors menu line for TriBBS:
D,Call Back Verification,CBV.BAT,10
The 'D' at the beginning of the line signifies that TriBBS is to create
the DOOR.SYS type dropfile before running the batch file CBV.BAT. The
10 at the end of the line signifies that users must have at least a
security level of 10 to choose this menu option.
Page 42
Installation for WWIV BBS systems
For WWIV users, you may either call the CBV batch file from your new user
event, or from your on-line programs menu. Wherever you decide to call CBV
from, be sure to shrink the BBS, usually done via a menu/setup option. Below
is a sample batch file for WWIV systems.
CD\WWIV\CBV
WWIV_PPP -R C:\WWIV\CBV\WWIV_PPP.CFG
CBV C:\WWIV\CHAIN.TXT C:\WWIV\CBV\CBV.CFG C:\WWIV\
WWIV_PPP -W C:\WWIV\CBV\WWIV_PPP.CFG -D
CD\WWIV
If you are calling CBV from your chains menu in WWIV, be sure that you have
turned DOS calls OFF, and set the BBS to shrink before running the program.
Not setting the shrink to be on will cause CBV to not update the user's time
remaining online before returning control back to the BBS. All other
settings are left to the sysop's discretion. CBV does not require that your
users have ANSI graphics capabilities in order to function.
Basic installation and configuration is now complete.
Page 43
─────────────────────────────────────────────────────────────────────────────
░ Pre/Post-Processors ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
CBV comes with three complete Pre/Post-Processor programs. One for systems
utilizing the EXITINFO.BBS dropfile (Remote Access, ProBoard), one for
systems using the DOOR.SYS dropfile for all record keeping purposes (TriBBS),
and one for WWIV BBS software. They are named EXIT_PPP.EXE, DOOR_PPP.EXE,
and WWIV_PPP.EXE respectively. Both has its unique command line parameters,
but they are very similar in most respects. Running the executable without
any command line parameters will bring up a screen showing the proper usage
of the program.
The proper command line for the EXITINFO.BBS (RA v2.00+, ProBoard) Pre/Post-
Processor is as follows:
EXIT_PPP.EXE <-R | -W> <EXITINFO.BBS> <CBV_PPP.DAT> [-D] [-TEXTPW]
-R Tells the processor to read the EXITINFO.BBS file, and
write the CBV_PPP.DAT file.
-W Tells the processor to read the CBV_PPP.DAT file, and
write changes (if any) to the EXITINFO.BBS file.
<EXITINFO.BBS> Specifies the full path to the BBS's EXITINFO.BBS file
created when the system gives control to an external
program. Usually created in the main BBS directory, or
in each node's directory.
<CBV_PPP.DAT> Specifies the full path of where to read from and write
to CBV's CBV_PPP.DAT file.
-D Specifying this parameter will tell the Pre/Post-
Processor to delete the CBV_PPP.DAT file after it has
written changes to the EXITINFO.BBS file. This option
only takes affect when using the -W command line
parameter.
-TEXTPW Instructs EXIT_PPP.EXE to correctly write RA's user
password as a text format instead of CRC32 bit into the
CBV_PPP.DAT file. Use this if you're using RemoteAccess
v2.50 and have the system setup to store user's passwords
as text.
Page 44
The proper command line for the DOOR.SYS (TriBBS) reading/writing Pre/Post-
Process is as follows:
DOOR_PPP.EXE <-R | -W> <DOOR.SYS> <CBV_PPP.DAT> [-D]
-R Tells the processor to read the DOOR.SYS BBS dropfile,
and write the CBV_PPP.DAT file.
-W Tells the processor to read the CBV_PPP.DAT file, and
write changes (if any) to the BBS DOOR.SYS dropfile.
<DOOR.SYS> Specifies the full path to BBS's DOOR.SYS drop file
created when the system gives control to an external
program. Usually created in the main BBS directory, or
in each node's directory.
<CBV_PPP.DAT> Specifies the full path of where to read from and write
to CBV's CBV_PPP.DAT file.
-D Specifying this parameter will tell the Pre/Post-
Processor to delete the CBV_PPP.DAT file after it has
written changes to the EXITINFO.BBS file. This option
only takes affect when using the -W command line
parameter.
Page 45
The WWIV Pre/Post-Processor command lines are:
WWIV_PPP.EXE <-R | -W> <CONFIG> [-D]
-R Tells the processor to read the USERS.BBS file, and write
the CBV_PPP.DAT file.
-W Tells the processor to read the CBV_PPP.DAT file, and
write changes (if any) to the USERS.BBS file.
<CONFIG> Specifies the full path AND filename of the WWIV_PPP
configuration file. See the below section for more
information on the format for this configuration file.
-D Specifying this parameter will tell the Pre/Post-
Processor to delete the CBV_PPP.DAT file after it has
written changes to the EXITINFO.BBS file. This option
only takes affect when using the -W command line
parameter.
The WWIV_PPP Configuration File
To facilitate the possibility of some sysops running multi-node systems,
version 1.2+ of the WWIV Pre/Post-Processor uses a configuration file.
Sysops should create a configuration file for each node of their BBS.
The format for this file is very similar to all the other text
configuration files for CBV. Lines that are blank or preceded by a
semi-colon (;) are considered comments and ignored. All other lines are
considered part of the configuration. Each configuration file created
should contain the following options in this specified order:
Path To Read/Write CBV_PPP.DAT CBV Pre/Post-Processor File
Path To WWIV's User Record File USER.LST
Path To Main BBS System Files
Path And Filename Of BBS Drop File (CHAIN.TXT)
Path And Filename Of BBS Shrink File (RESTORE.WWV)
Below is a sample configuration file for the WWIV Pre/Post-Processor:
Page 46
; WWIV_PPP v1.3
; Copyright (c) 1996 John Dailey
; Written & programmed by John Dailey
;
; WWIV_PPP Configuration File
;
; Lines that are blank or contain a semi-colon (;) as the first character are
; considered comments and are ignored. Enter each configuration option on
; the start of a new line in the order shown below.
;
; Sysops who are running multi-node systems should create a configuration
; file for each node that will be utilizing the WWIV Pre/Post-Processor.
;
; Path To Read/Write CBV_PPP.DAT CBV Pre/Post-Processor File
; This path should be the same location you are instructing CBV to look for
; the CBV_PPP.DAT file. This file should be created in separate directories
; for each node of your BBS.
\WWIV\CBV\
; Path To WWIV's User Record File USER.LST
\WWIV\DATA\
; Path To Main BBS System Files
\WWIV\
; Path And Filename Of BBS Drop File (CHAIN.TXT)
; For multi-node systems, you can specify filenames such as CHAIN.001,
; CHAIN.002, etc. for each node.
\WWIV\CHAIN.TXT
; Path And Filename Of BBS Shrink File (RESTORE.WWV)
; This file is created when you instruct WWIV to shrink before running a
; particular external program. It is usually created in the main BBS
; directory. Multi-node systems will need to specify RESTORE.001,
; RESTORE.002, etc. for each node.
\WWIV\RESTORE.WWV
; End Of WWIV_PPP.CFG File
Page 47
Modified User Record Structures
The WWIV Pre/Post-Processor that comes with CBV also has the capability
to support both unmodified and modified user record structures. This
support is accomplished via a offset configuration file named
WWIV_PPP.OFS. This file contains the offsets (in bytes) for each item
in the user record needed by CBV. If this file is not found, the
unmodified user record structure for WWIV v4.20+ will be assumed.
WWIV_PPP.OFS must reside in the directory that WWIV_PPP.EXE is being
called from. The offset configuration file is a plain ASCII text file,
with a configuration items residing on the beginning of each line.
Lines that begin with a semi-colon (;) and blank lines are ignored by
the processor, thus allowing comments within the configuration file.
Below is a sample WWIV Pre/Post-Processor offset configuration file.
There are two new additions to this offset file which should be added to
the end of any existing offset definition file.
PLEASE NOTE! As of the current release, WWIV_PPP.EXE does not support
variable length differences from those of the original WWIV record
structure. In other words, if you have changed the length of ANY of
your user record structures (i.e. from a string of eight characters to
a string of ten characters, or byte to integer, etc.), you will NOT be
able to use WWIV_PPP.EXE without a major risk to your user record.
In these cases, it may be necessary to contact me to configure and
create a Pre/Post-Processor specific to your BBS' modified user record.
Page 48
; WWIV_PPP v1.3
; Copyright (c) 1996 John Dailey
; Written & programmed by John Dailey
;
; WWIV_PPP Offset Configuration File
;
; Each offset is the number of bytes from the beginning of the user record to
; the specific data. Calculate these numbers by adding the byte values for
; each variable in the userrec, up to, but not inclusive of, the variable you
; are defining. Blank lines, and lines beginning with a semi-colon (;) are
; ignored. Below is a list of C variable types and their byte values.
;
; char 1 byte (for each character)
; int 2 bytes
; float 4 bytes
; double 8 bytes
;
; Total Length Of User Record In Bytes (Add Up All Byte Values)
1024
; Offset To User's Handle (userrec.name)
0
; Offset To User's Real Name (userrec.realname)
31
; Offset To User's Voice Phone Number (userrec.phone)
59
; Offset To User's Data Phone Number (userrec.dataphone)
72
; Offset To User's Password (userrec.pw)
165
; Offset To User's Sysop Comment (userrec.note)
192
; Offset To User's Board Security Level (usrerec.sl)
584
; Offset To User's Download Security Level (userrec.dsl)
585
; Offset To User's Exemptions (userrec.exempt)
586
; Offset To User's AR Flags (userrec.ar)
706
Page 49
; Offset To User's DAR Flags (userrec.dar)
708
; Offset To User's Restrictions (userrec.restrict)
710
; Offset To Active Security Level In RESTORE.WWV (actsl)
266
; Offset To Subscription Expiration Date (userrec.expires)
; Please note that as of this release, WWIV_PPP does not
; support this feature of CBV for WWIV. Future versions, however,
; will
814
; Offset To User Credits (userrec.pos_account)
878
; End Of WWIV_PPP.CFG File
All but the last offset can be found in the user record information file
(USERS.BBS). The last offset, which references the file RESTORE.WWV is found
in the actual file RESTORE.WWV when WWIV shrinks to run an external program.
The active security level (actsl), controls aspects such as time remaining
for the user. It is important that this value is modified correctly after a
validation so that users will have the correct amount of time remaining after
validated.
Page 50
─────────────────────────────────────────────────────────────────────────────
░ User E-Mail Files ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
Want to e-mail the user after a successful callback? With the help of a
text-file import program you can do just that. CBV sports the ability to
write a text file for import into your BBS e-mail to notify the user of
certain events. Below are the specific files that may be created to be sent
as e-mail to the user:
VOICE.MSG
This file is copied if a user picked up voice during the callback
process. This feature will only work if your modem returns a result
code for a voice pickup (VOICE).
TIMEOUT.MSG
If no connection was made at all during the callback due to a time-out,
this message can be sent to the user specifying that for some reason, no
connection was made to the user's modem within the given time limit. It
may have resulted from a wrong number.
BUSY.MSG
If the user's phone number was busy for all tries to callback, this
message can be sent to the user explaining that they need to free up the
line as soon as possible so that CBV may get through to their modem.
FAILED.MSG
A general callback failure message for the user. If a callback fails,
and any other failed message file is missing, this one will be copied
for e-mail instead.
SUCCESS.MSG
This file is copied for e-mail for users that successfully completes the
callback process.
SUCCESSL.MSG
This e-mail file is copied to be sent to users that are calling long
distance, and have successfully completed the callback process.
After creating the needed text files, you will need to specify what filename
that this message file is to be copied to via CBV's configuration software.
Under the BBS menu, modify the "E-Mail File" parameter to meet this
specification. You may include the complete path as well as the filename in
this option. For example, if you need a file created in your main BBS
directory (C:\BBS) called INFILE.TXT, you would specify C:\BBS\INFILE.TXT in
the "E-Mail File" configuration slot. CBV would then copy the correct
message file to that file for your import program to import as e-mail.
Please note that in order for this feature to work completely, you will need
to employ an external program that imports text files into your system's e-
mail data file. You should install this program as the last command in your
CBV batch file before returning command to your BBS software.
Page 51
─────────────────────────────────────────────────────────────────────────────
░ ANSI/ASCII Display Files ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
For the ability for sysops to have as much control over the look of the CBV
as possible, I've made nearly every display aspect of the program external in
the files listed below. These files are standard ANSI files, and can be
modified to suit the look of your BBS. An explanation of when each is
displayed is also listed. Files with an .ANS extension are displayed to ANSI
(color) user's, while .ASC files are displayed to non-ANSI user's. If a
particular ANSI display file is not found, CBV will display the ASCII
equivalent instead.
Main Program Display Files
CBVABORT.A??
This file is displayed right after a user has opted to abort the
callback and right before returning control back to the BBS. It should
explain that the user's security level has or has not been modified
according to the sysop's configuration.
CBVBAD# .A??
This file is displayed if a user's phone number they wish to be called
back at is entered in the bad phone numbers control file, and before
returning control to the BBS. This file should explain that the user's
number is not allowable per CBV's configuration.
CBVBADCO.A??
Displayed to users who enter an incorrect CBV random codeword after a
successful callback connection, and before returning control to the BBS.
This file should let the user know that they have entered a bad random
code word too many times and their security level has or has not been
adjusted.
CBVBADPW.A??
This display file is displayed to a user who enters an incorrect
password the maximum times after a successful callback, and before
returning control to the BBS. This file should let the user know that
they have entered a bad password too many times, and their security
level has or has not been adjusted.
CBVBYELD.A??
If the option to hang up on long distance callers is enabled, this file
will be displayed right before dropping carrier on the long distance
user. This file should explain that the user is being hung up on to
keep the sysop's costs down.
CBVCHANG.A??
This display file is displayed to the user when they wish to change the
phone number to be called back at, and right before they are prompted
for a reason for the change.
Page 52
CBVCODE. A??
This display file is displayed to the user right before the random
callback codeword is generated and displayed for the user's reference.
It should include information on what the codeword is for and when it
will be needed after successful re-connection.
CBVDIAL .A??
Displayed to the user right before displaying the number that CBV is
preparing to dial for the callback verification process, and before
determining if a phone number is long distance or local to the system.
CBVDUPE .A??
If a user's phone number has already been validated, and the check
duplicate numbers feature is enable, this file will be displayed right
before returning control to the BBS. It is not shown to users if the
sysop has configured CBV to automatically upgrade users with duplicate
numbers. This file should explain that the user's number has already
been validated by CBV, and therefore, is not allowed to call back.
CBVHABT .A??
This file is displayed to a user who aborts CBV and when CBV has been
configured to hang up on aborted users after the CBVABORT.A?? file has
been displayed. This file should merely state that the BBS is now
hanging up on the user.
CBVHANG .A??
This file is displayed after a user is successfully verified and if the
system has set the "Hang up after validation of all users" option on.
After displaying this file, CBV will hangup if enabled. This display
file should simply state that CBV is hanging up, and the reasons that
CBV is doing it.
CBVHBCO .A??
This display file is displayed to a user who enters a bad callback
random codeword too many times, and when CBV is configured to hang up on
the user. This file is displayed immediately after CBVBADCO.A?? and
should state that the BBS is now hanging up on theuser because they have
entered the codeword incorrect too many times.
CBVHBPW .A??
This file is display to users who enter a bad password too many times,
and when CBV is configured to hang up on the user. This file is
displayed immediately after CBVBADPW.A?? and should merely state that
the BBS is now hanging up on the user.
CBVINVAL.A??
This file is displayed to the user if their format has been entered in
an extremely incorrect format. CBV will correct numbers and place them
in the XXX-XXX-XXXX format, however, if CBV is unable to correct a
number, this file will be displayed before returning control to the BBS.
This display file should let the user know that their phone number is
invalid, and to send the sysop a message with the correct formatted
number.
Page 53
CBVISLD .A??
If CBV is set to NOT allow LD callbacks and BOTH the user's voice and
data are determined to be long distance (per the current configuration),
CBV will present the user with this display file asking if the
assumption is correct and that the sysop is not allowing LD callbacks at
this time. The user will then be prompted to whether or not they wish
to continue.
CBVLDT .A??
This file is displayed to a long distance user who is calling during a
time that CBV is not allowed to validate long distance. After
displaying this file, CBV will display the times that long distance
call-backs are allowed. If the file LDT.A?? is found in the display
directory, however, CBV will display that file (which should contain a
display of the allowable hours) instead of using the built-in format.
This file should merely state that long distance call-backs are only
allowed at the times shown on the screen.
CBVMAXSL.A??
This file is displayed to users if their security level is greater than,
or equal to the maximum SL allowed to use CBV. CBV then returns control
to the BBS. This should explain that the user has already been
validated, or a similar message.
CBVMINSL.A??
This file is displayed to users if their security level is less than the
minimum SL allowed to use CBV. CBV will then return control to the BBS.
This file should explain that the user's security level is too low to
run CBV.
CBVNOLD .A??
If long distance calls are not allowed, and a user wants to initiate a
long distance callback, this file is displayed right before returning
control to the BBS. It should explain to the user that the sysop is not
allowing long distance calls, and that they will be upgraded manually by
the sysop.
CBVPNUM .A??
This display file tells the user to make sure that they have selected
the phone number to which their modem is currently hooked up to. It is
displayed right after the user selects a number to be called back at.
CBVPRED .A??
Displayed right after making sure that CBV will be calling the right
phone number and right before hanging up, CBV displays this file which
should remind the user to type 'ATA' to make their modem answer the BBS
calling them.
CBVSUCC .A??
This display file is shown to the user right after a successful local
callback. If a long distance success display file is not present, this
file is also displayed to LD callbacks completed successfully. This is
the last file displayed to the user before exiting CBV on a successful
callback.
Page 54
CBVSUCCL.A??
Also displayed right after a successful callback, this file is only
display to users calling and being validated Long Distance.
CBVTOP .A??
This display file is simply a top-of-screen attention-getter. It is
displayed before putting up the main menu, and before showing the help
file. To keep uniformity, you may want to place this same display file
at the top of all other display files.
CBVHELP .TXT
When a user wishes to view the help file for CBV, this standard text
file is displayed after clearing the screen and displaying CBVTOP.A??.
It should contain general information on the use of CBV.
CBVVDUPE.A??
This file is displayed to users who have chosen a number that was
previously validated by CBV, and when the sysop has opted to
automatically upgrade users with duplicate numbers. It should explain
that CBV has already validated the user's number, and therefore, has no
need to call it again.
Page 55
Walk-through Display Files
The next eight display files are displayed as part of the walk-through
tutorial. Each one is displayed in succession during the walk-through.
Sysops should try to make these screens as informative as possible. Below is
a complete description of what each file should contain.
CBV_WK1. A??
Displays general information about the callback and that the modem will
almost always display a "NO CARRIER" when the BBS hangs up. It should
also state that the user MUST NOT hang up on the CBV program.
CBV_WK1A.A??
This walkthrough display files explains the function of the random
codeword, and is only displayed to the user during the walkthrough if
the gerenate random codeword feature of CBV is enabled.
CBV_WK2. A??
States that the BBS will call back in a few seconds. Sysops may wish to
specify exactly how many seconds they have configured to wait between
dials, as CBV will wait this length before actually placing the first
call. Also specify that the modem will display a "RING" message on the
screen when the BBS is calling.
CBV_WK3. A??
On this walk-through screen, it is important to instruct the user how to
answer the CBV telephone call with the modem. The last few lines of
this display file should tell the user to type "ATA" (in all capital
letters) to answer a simulated CBV call. After displayed, CBV will
display "RING" on the screen until the user types "ATA" to answer the
simulated call.
CBV_WK4. A??
Displays information about the actual "CONNECT" message returned by the
modem when it actually connects.
CBV_WK5. A??
This display file should explains that the occurrence of line noise
after the connection process is perfectly normal. CBV will simulate
fake line noise at this point.
CBV_WK6. A??
Here, the display file should ask the user to enter their login password
as they would in a real callback after connection. This display file
only takes part if the sysop has configured CBV to actually ask for the
user's password during the callback process.
CBV_WK6A.A??
This display file should ask the user to enter their randomly generated
callback code here as they would in a real callback. Again, this
walkthrough display file and prompt are only displayed if the random
codeword feature of CBV is enabled.
Page 56
CBV_WK7. A??
This screen should instruct the user to call back if the system doesn't
call them back in a few minutes. Something may have gone wrong with the
callback, and therefore they will need to call and try again, or mail
the sysop to let him/her know of a possible problem.
CBV_WK8. A??
Finally, this walk-through screen congratulates the user for completing
sample call back. You may also wish to specify any further instructions
that you feel are necessary here.
CBV will wait for input from the user for 2 minutes. If no input is received
from the modem within that amount of time, CBV will exit with an inactivity
message. CBV beeps at the user, 1 minute into the count to notify them that
they are going to be returned to the BBS.
Page 57
─────────────────────────────────────────────────────────────────────────────
░ Local Console Key Controls ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
At any time while a user is online, you may press one of the sysop functions
keys. Each is described below:
Auto Upgrade Keys (ALT-1 Through ALT-6)
At any time of the callback (aside from the actual time when CBV is
placing a call), the sysop may automatically upgrade OR downgrade
a user by pressing one of the auto-upgrade keys:
ALT-1 = Regular caller security level
ALT-2 = Long distance caller security level
ALT-3 = Bad password security level
ALT-4 = Aborted CBV security level
ALT-5 = Bad number (contained in CBVBAD#.DAT) security level
ALT-6 = Duplicate number (contained in CBVNUMS.DAT) security
level
Each security level setting may be defined via CBVCFG.EXE under the
Security menu.
Sysop Bar Information (F1)
The sysop bar displays vital information about the user currently
online to CBV. There are a few individual display modes for this
information bar, and by pressing the F1 key, the sysop can scroll
through them one at a time. The first few displays contain
information about the user, his or her security level information,
and the current connection rate. The last display of the sysop bar
contains a quick guide to the sysop keys that may be used while in
CBV.
Return User To BBS (F4, Shift-F4)
Pressing the F4 function key will simply exit the user back to the
system without any messages. Pressing the shift key and F4 at the
same time will lock the user out of CBV and return them to the
system. Locking a user from CBV also sets the user's security
level to zero and writes this information to the CBV_PPP.DAT file
for the Pre/Post-Processor to take care of. For most BBS systems,
this should lock out the user from your system totally. CBV also
adds their number to the CBVBAD#.DAT bad phone number file.
Hang Up On User (F5, ALT-H, Shift F5)
Pressing the F5 function key or ALT-H will hangup on the user and
return control to the system without any messages. Again, pressing
shift and the F5 key will lock the user out and hang up on them,
returning control to the system.
Split-Screen Chat (F10, ALT-C)
You may chat with the user at any time by pressing the F10 function
key or ALT-C. If the user has ANSI, this chat will be split screen
with the sysop on the top half of the screen and the user on the
lower half. If a user does not have ANSI, it will be merely
two-way chat mode. Press F10, or ESCape to exit chat mode.
Page 58
Shell To DOS (Shift F10, ALT-J)
Pressing and holding the shift key, while pressing F10 (Or by
pressing ALT-J) will shell to DOS. A short "Please Wait" message
is displayed to the user before shelling, and erased upon return.
Type "EXIT" at the command line to return to CBV. CBV will swap as
much memory as possible to either EMS memory or disk, depending on
which is available first.
Page 59
─────────────────────────────────────────────────────────────────────────────
░ Multi-Node Configuration ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
With the ability to have multiple configuration files, and non-standard
communications port settings, CBV becomes a very multi-node capable program.
Sysops who wish to set up CBV with their multi-node systems should keep the
following points in mind when doing so:
o If your BBS system has the capability to send the current node
number to your CBV batch file via command-line parameters, use that
feature to specify filenames needed for the Pre/Post-Processor and
CBV itself.
o If your BBS system does not do the above, but uses an environment
variable to specify the current node, create a single batch file
for CBV that utilizes that variable.
o Remember that non-standard communication port settings can be
configured for each configuration file. You may specify the exact
port to use, the address and IRQ via CBVCFG.EXE. CBV will use
these values, overriding whatever is contained in the BBS dropfile
DOOR.SYS.
o Name each configuration file in a meaningful way, such as
NODE1.CFG, NODE2.CFG, etc. for each node of your system. If you
will not be making different configurations for each node, using
the standard filename of CBV.CFG will suffice.
Example multi-node batch files are included below.
Page 60
Node Identification By Command-Line
If you are running a multi-node copy of CBV with multiple configurations, and
passing the current node number via command-line parameters, follow the
outline of:
@ECHO OFF
CD\BBS\CBV
EXIT_PPP -R C:\BBS\NODE%1\ C:\BBS\NODE%1\
CBV C:\BBS\NODE%1\DOOR.SYS C:\BBS\CBV\NODE%1.CFG C:\BBS\CBV\NODE%1\
EXIT_PPP -W C:\BBS\NODE%1\ C:\BBS\NODE%1\
CD\BBS
In this example, it is assumed that C:\BBS is your main BBS directory,
CBV's main files are stored in C:\BBS\CBV, and each node's information
files are stored in C:\BBS\NODE%1, where %1 is the corresponding node
number (C:\BBS\NODE1, C:\BBS\NODE2, etc.).
In the example above, we are creating the CBV_PPP.DAT file in each
node's directory to ensure that CBV reads and writes information in a
spot where the correct node will receive it.
Also in this example, each configuration file for the nodes are named
NODE1.CFG, NODE2.CFG, etc. The correct calling of this batch file would
be:
CBV.BAT <node number>
ie. CBV.BAT 1
If you are running a multi-node copy of CBV with ONE configuration, and
passing the current node number via command-line parameters, modify the
fourth line above (the actual call to CBV.EXE) to read:
CBV C:\BBS\NODE%1\DOOR.SYS C:\BBS\CBV\CBV.CFG C:\BBS\CBV\NODE%1\
Page 61
Node Identification By Environment Variable
If you are utilizing a BBS system's environment variable which specifies the
current node number, follow either outline shown below. Where a %v% is
located, be sure to substitute the actual environment variable that your
system uses. For example, if the environment variable is BBS_NODE (SET
BBS_NODE=1, etc.), you would specify a %BBS_NODE% wherever a %v% appears in
the batch file below:
@ECHO OFF
CD\BBS\CBV
EXIT_PPP -R C:\BBS\NODE%v%\ C:\BBS\NODE%v%\
CBV C:\BBS\NODE%v%\DOOR.SYS C:\BBS\CBV\NODE%v%.CFG C:\BBS\CBV\NODE%v%\
EXIT_PPP -W C:\BBS\NODE%v%\ C:\BBS\NODE%v%\
CD\BBS
Again, it is assumed that C:\BBS is your main BBS directory, CBV's main
files are stored in C:\BBS\CBV, and each node's information files are
stored in C:\BBS\NODE%1, where %1 is the corresponding node number
(C:\BBS\NODE1, C:\BBS\NODE2, etc.).
In the example above, we are creating the CBV_PPP.DAT file in each
node's directory to ensure that CBV reads and writes information in a
spot where the correct node will receive it.
Also in this example, each configuration file for the nodes are named
NODE1.CFG, NODE2.CFG, etc. The correct calling of this batch file would
be:
CBV.BAT
Be sure that your BBS environment variable that specifies the current
node number is also set.
If you are running a multi-node copy of CBV with ONE configuration, modify
the fourth line above (the actual call to CBV.EXE) to read:
CBV C:\BBS\NODE%v%\DOOR.SYS C:\BBS\CBV\CBV.CFG C:\BBS\CBV\NODE%v%\
Page 62
You may also wish to follow the format below if your BBS software utilizes
the environment variable method of specifying node numbers. In this example,
we use DOS "GOTO" batch command to list specific instructions for each node's
call to CBV. Again, substitute your actual BBS environment variable wherever
a %v% appears. In this example, you can specify specific instructions for
each node's call to CBV.
@ECHO OFF
GOTO Start
:1
EXIT_PPP -R C:\BBS\NODE1\ C:\BBS\NODE1\
CBV C:\BBS\NODE1\DOOR.SYS C:\BBS\CBV\NODE1.CFG C:\BBS\CBV\NODE1\
EXIT_PPP -W C:\BBS\NODE1\ C:\BBS\NODE1\
Goto End
:2
EXIT_PPP -R C:\BBS\NODE2\ C:\BBS\NODE2\
CBV C:\BBS\NODE2\DOOR.SYS C:\BBS\CBV\NODE2.CFG C:\BBS\CBV\NODE2\
EXIT_PPP -W C:\BBS\NODE2\ C:\BBS\NODE2\
Goto End
:3
EXIT_PPP -R C:\BBS\NODE3\ C:\BBS\NODE3\
CBV C:\BBS\NODE3\DOOR.SYS C:\BBS\CBV\NODE3.CFG C:\BBS\CBV\NODE3\
EXIT_PPP -W C:\BBS\NODE3\ C:\BBS\NODE3\
Goto End
:Start
CD\BBS\CBV
Goto %v%
:End
CD\BBS
Page 63
─────────────────────────────────────────────────────────────────────────────
░ Registration Of CBV ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
As a software developer, I take pride in my efforts to produce quality
shareware with little or no registration. In order to do so, some of my
software requires a small registration fee.
I have spent many years, designing, programming, and testing the Call Back
Verification software.
CBV is being released under the Shareware concept, which encourages the users
of a program to register that software after a trial period of approximately
30 days and continued use thereafter.
This software is not crippled in any way, shape, or form, however, a short
delay is present in the loading of the software in unregistered versions to
encourage sysops to register.
By registering and supporting quality shareware such as this, you are making
the Call Back Verification software bigger, better, and more enjoyable for
you and your users.
Upon receipt of your registration for the CBV software, you will receive a
unique, individual registration code (with instructions), which is easily
used to make the executable registered. Registration of the CBV software
will entitle you to FREE UPDATES of the same major version number, ie. 1.0 -
1.9. All you'll need to do is acquire the update software package and
incorporate your registration code.
Regsitration will also remove all unregistered delays and nag screens. Your
name and registration number will also appear to you and your users as the
software is executed.
If you are unhappy with any part of the Call Back Verification software or
it's operation, please do not send in your registration expecting it to
function more to your likeing. Remember that the great concept of shareware
is "try before you buy." You know exactly what you will receive before you
pay for it.
If you are having problems, please don't hesitate to contact me before
registering the software. I fully support the software for anyone whether
they have or have not registered the Dungeon Master software.
You may have the software mailed to you on disk for a small additional fee.
To register your copy, follow these easy steps:
* Print out the enclosed registration form (or print the information
on paper). Please enclode seperate registration forms for each
order if you will be making multiple registrations.
* Completely fill out all information on the form. Leaving any part
of the form blank may delay your registration.
Page 64
* Select which product or products you wish to register.
* Be sure to check whether or not you wish to recieve the software on
disk along with your registration keycode.
* Total up the registration price, enclose a check or money order (do
not send cash) in US funds payable to John Dailey, and mail your
registration fee with the form to the address at the bottom of the
form.
Upon receipt of your registration, it will be processed as soon as possible,
and a registration keycode, with instructions on how to register your copy of
CBV will be sent along with it.
Please allow two to three weeks from the time you mail your registration to
the time you receive your registration information back.
Page 65
─────────────────────────────────────────────────────────────────────────────
░ CBV Support Information ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
Questions, comments, complaints, or suggestions can be directed to myself,
John Dailey, at any of the following addresses or locations. If private e-
mail, please be sure to include your return e-mail address in the body of
your message to ensure that I can reply.
E-Mail Addresses:
73124,2612 [Compuserve]
John.Dailey%277@satlink.oau.org [Internet]
1:363/277 [FIDONet]
166@2522 [WWIVNet]
1@4706 [TerraNET]
1@4701 [Alliance]
Bulletin Board System:
BBS Avalon
(407) 296-3208
24 hours
1200 - 28.8, N81, ANSI Required
FIDONet 1:363/277
Alliance @4701
TerraNET @4706
World Wide Web:
http://ourworld.compuserve.com/homepages/john_dailey
US Postal Address:
John Dailey
P.O. Box 17
Windermere, FL 34786-0017
Page 66
─────────────────────────────────────────────────────────────────────────────
░ Author's Notes And Credits ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
WWIV BBS Software Copyright (c) Wayne Bell And WWIV Software Services
RemoteAccess Copyright (c) Andrew Milner And Wantree Development
QuickBBS Copyright (c) Steve Gabrilowitz
TriBBS Copyright (c) Mark D. Goodwin
ProBoard Copyright (c) Philippe Leybaert
WinFossil Copyright (c) Woodruff Software Systems
BNU Copyright (c) David Nugent and Unique Computing Pty Limited
X00 Copyright (c) by Raymond L. Gwinn
All other software products mentioned are copyright of their respective
holders.
Thanks to all the sysops who have provided feedback, helped test out and
develop CBV, and it's Pre/Post-Processors to be used with BBS software
of many types.
John Dailey's CBV is dedicated to public Bulletin Board Systems
throughout the world maintaining beyond the aftermath of the Internet.
Page 67
─────────────────────────────────────────────────────────────────────────────
░ Index ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
─────────────────────────────────────────────────────────────────────────────
Archive 3
ARJ Security Envelope 3
Distribution 4
Area Codes 36
Maximum Number Of 19
Sample File 37
v1.2 File Format 13
ARJ Security Envelope 3
Bad Numbers 35
Batch Files
Creating 8
Generic Sample 8
Outline 40
RA, Proboard 41
TriBBS 42
WWIV 9, 43
CBV
Command Line 40
Features 4
Running 40
What Is? 2, 3
Configuration 17
Aborted SL 24
Allow LD Validations 32
Allow New Numbers 32
Allow Walk-through 32
Area Code 19
Ask Password 32
Auto-Validate Duplicates 34
Bad Number SL 25
Bad Numbers 30
Bad Password SL 24
Batch Files 40
BBS 19
BUSY 28
Calls Per Day 22
Carrier Wait 28
CBV Path 19
Colors 20
CONNECT 27
Credits 22
Default Filename 17
Dial Attempts 29
Dial Prefix 26
Dialing Methods 19, 38
Disp Path 19
Download SL (DSL) 21
Duplicate Number SL 25
E-Mail File 20
Escape Command 26
Exchanges 31, 36
Page 68
Exemptions 22
file 17, 18
Group 22
Hangup 26
Hangup Aborted User 33
Hangup After Callback 33
Hangup After LD 33
Hangup Bad Password 33
Info 18
LD Hours 32
LD Prefix 19
Log 19
Long Distance SL 24
Mail File 20
Maximum SL To CBV 21
Minimum SL To CBV 21
Modem 26
Modem Init 27
Multi-Node 60
Multiple 17
Name 19
NO CARRIER 27
NO DIAL TONE 27
Numbers 30
OK 27
Options 32
Password Attempts 21
Password In Note 34
Phone In User Note 34
Pickup 27
Quit 18
Redial Pause 28
Regular User SL 24
Restriction and Flag Settings 23
Restrictions 22
Result Wait 28
RING 28
Save 18
Security 21
Security Level Settings 21
Subdays 22
System SL (SL) 21
User Flags (AR/DAR) 22
Valid Exchanges 30
Validated Duplicates 34
Validated Numbers 30
VOICE 28
Defining Local Numbers 36
Dialing Methods 19, 38
Assigning 39
Display Files 3, 52
CBV_WK1. A?? 56
CBV_WK1A.A?? 56
CBV_WK2. A?? 56
CBV_WK3. A?? 56
Page 69
CBV_WK4. A?? 56
CBV_WK5. A?? 56
CBV_WK6. A?? 56
CBV_WK6A.A?? 56
CBV_WK7. A?? 57
CBV_WK8. A?? 57
CBVABORT.A?? 52
CBVBAD# .A?? 52
CBVBADCO.A?? 52
CBVBADPW.A?? 52
CBVBYELD.A?? 52
CBVCHANG.A?? 52
CBVCODE. A?? 53
CBVDIAL .A?? 53
CBVDUPE .A?? 53
CBVHABT .A?? 53
CBVHANG .A?? 53
CBVHBCO .A?? 53
CBVHBPW .A?? 53
CBVINVAL.A?? 53
CBVISLD .A?? 54
CBVLDT .A?? 54
CBVMAXSL.A?? 54
CBVMINSL.A?? 54
CBVNOLD .A?? 54
CBVPNUM .A?? 54
CBVPRED .A?? 54
CBVSUCC .A?? 54
CBVSUCCL.A?? 55
CBVTOP .A?? 55
CBVVDUPE.A?? 55
Nomenclature 3
Walk-Through 56
Exchanges 30, 31, 36
Defining 36
Entering 30
Locating List Of 30, 36
Maximum Number Of 36
Sample File 37
v1.2 File Format 13
Flags 23
Toggling 23
Turning Off 23
Turning On 23
Unmodified 23
Installation 15
Configuration 17
Quick 8
Upgrading 13
Modem 26
Carriage Return 26
Lower DTR 26
Pause 1/4s 26
Raise DTR 26
String Commands 26
Page 70
Multi-Node Configuration 60
Batch File Examples 61-63
Command-Line Paramaters 60, 61
Configuration Files 60
Environment Variables 60, 62, 63
Non-Standard Ports 60
Pre/Post-Processor 44
Concept 10
Developing 11
DOOR.SYS 45
DOOR.SYS (TriBBS) 11
DOOR_PPP.EXE Command Line 45
Drop File 10
EXIT_PPP.EXE Command Line 44
EXITINFO.BBS 44
EXITINFO.BBS (RA, ProBoard) 11
Offset Configuration 49
ProBoard 44
Remote Access 44
Requesting 12
TriBBS 45
WWIV 11, 46
WWIV Configuration 47
WWIV Modified User Records 48
WWIV_PPP.EXE Command Line 46
Registration 64
Support Information 66
Sysop Keys 58
Auto Upgrade 58
Hang Up On User 58
Locking Out User 58
Return User To BBS 58
Shell To DOS 59
Split-Screen Chat 58
Sysop Bar Information 58
User E-Mail Files 51
BUSY.MSG 51
FAILED.MSG 51
Importing To BBS 51
Specifying Filename For 51
SUCCESS.MSG 51
SUCCESSL.MSG 51
TIMEOUT.MSG 51
VOICE.MSG 51
Page 71