home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
World_Of_Computer_Software-02-387-Vol-3of3.iso
/
c
/
csver228.zip
/
CSVERIFY.DOC
< prev
next >
Wrap
Text File
|
1993-03-16
|
11KB
|
216 lines
(*****************************************************)
(* CSVerify 2.0 Written by Gary Bouchard *)
(* SysOp - The Computer Store BBS *)
(* St. Augustine, Florida (904)794-0063 *)
(* Copyright(c) 1992....All Rights Reserved *)
(* Released Modified *)
(*****************************************************)
What is it?
CSVerify is a Callback verification Door written specifically for PCBoard
version 14.5 or greater. CSVerify can handle local or long distance callbacks,
including International Numbers, and has many SysOp configurable options for
ease of use and setup. CSVerify supports multiple communications
configurations, and provides Fossil Driver Support to make it also compatible
with PCBoards new "/M" versions.
CSVerify can also be used as a noisy line callback door with complete checking
of long distance parameters.
CSVerify allows for local testing of the program, and automatically enters
TEST mode on local calls.
Upon successful callback verification, CSVerify will update the users record
to reflect any changes made to the phone number used, security level updates,
and Expiration date changes.
Information diplayed to the user while running the program comes from display
files which support all PCBoard @x## macros, and Multi-Language requirements.
These files are easily updated, and or maintained by the SysOp.
Installation of CSVerify
Create a directory to keep CSVerify in. There is a sample PCB bat file
included that you can modify to your liking. Go into PCBsetup, and go to the
MainBoard setup. Move the cursor to Doors.dat and press F2 to edit it. Make an
entry for CSVerify, the security required to access it, then answer YES to
logon, and YES to USERS.SYS.
USERS.SYS is important, because once a caller is verified thru the phone
number given, the information is then written back to the USERS.SYS file and
in turn PCBoard updates the users record from the USERS.SYS file.
Example;
╔══════════════════════════════════════════════════════════════════════════════
║ Edit User Record (Long Form) Record 125 of 125
║
║ Name : PETER FONDA Last DIR Listing : 07-18-92
║ City : ST. AUGUSTINE, FLORIDA Last Date On : 07-18-92
║ B/D Phone : 904 999-9999 <<Updated .Last Time On : 19:12
║ H/V Phone : 904 794-0063 Elapsed Time On : 5
║ Password : TEST Number Times On : 1
║ Security : 60 <<Updated Info. Number Uploads : 0
║ Expert : N Number Downloads : 0
║ Protocol : Z Daily Download : 0
║ Page Len : 23 Total Upload : 0
║ Reg Ex Date : 03-18-93 Total Download : 0
║ Expired Sec : 30 Messages Read : 0
║ Msg Clear : Y Messages Left : 0
║ Last in : 0 Editor Default : A
║ Delete User : N
║
║ Comment1 : IBM
║ Comment2 : XXX XXX-XXXX was/not verified. <<Updated information
║
╚══ 08:49:16 ═══ 07-19-92 ══════ F1 ═ help ════ caps: OFF num: ON ins: OFF ═
The B/D phone number is optionally replaced with the telephone number the user
entered into the program to be verified. This phone number is formatted to
PCBoard specs, and in the SysOp Comment Field (Comment 2) the text "XXX
XXX-XXXX was/not verified." is optionally inserted.
In this way you can tell which users in your users file have been verified by
this program.
The text files included are used by my board, and can be modified to your
liking. They have the capability, as you will see, to expand the standard
PCBoard @xxxx@ macros, and color macros.
Activities performed by the program are logged into your PCBoard Callers log.
If you have multiple nodes, the program will make the entry into the proper
caller# log. If you require additional entries of some sort, please let me
know, and if feasible, I will expand this.
Make sure that the information in the CSVerify.cnf file is correct for your
BBS. The configuration file is setup using KEYWORDS, for ease of use, and
allows for easy expansion in the future should the need arise.
Neither the KEYWORD's or the data are case sensitive, but you DO need to make
sure that they are spelled correctly. If CSV does not recognize a KEYWORD in
the file, it will use the DEFAULT for the keyword that is missing.
I do not include the area code or any prefixes in the dialing string unless
you either specify the allowable callback areas, or allow long distance
callback. If you do not include this information the program WILL NOT CALL
LONG DISTANCE.
There are two files you should be using, even if you allow long distance
callbacks. One is the Areacode File, and the other is the Exchangefile. In the
front of you local phone book, you will find the area codes and exchanges in
your calling area that are considered local calls. When the user's phone
number is parsed into it's components, CSV checks these files for a match, and
if NOT found, considers the call long distance, and it is dealt with
accordingly.
If Long Distance callbacks are allowed, then the user is dealt with security
level wise, as a local caller. If you do not allow long distance callbacks,
you can alter the security level to the number you choose, including a Long
Distance Expiration date, then return the caller back to the board.
The security level you give to the long distance user is entirely up to you...
I usually give an intermediate level until I determine if the user is a
visiting SysOp, then upgrade him/her later.
If you allow long distance calls, there is an option which you can configure
so you can have CSV verify the number, then once the user is upgraded, tells
the user that he/she is now verified, and tells them to call back for access.
The program will them drop carrier and recycle.
There is a time table file included in the ZIP which is used to specify when a
long distance callback can be made. This time table is very simple to work
with. Each line contains a 3 letter Day of Week word, and following the word
are 24 spaces which represent a time slot on the 24hour clock. Example;
HOURS
"0--------1----------2---"
DOW "012345678901234567890123"
=============================
SUN xxxxxxxxxxxxxxxx xxx
MON xxxxxxx xxxxx
TUE xxxxxxx xxxxx
WED xxxxxxx xxxxx
THU xxxxxxx xxxxx
FRI xxxxxxx xxxxx
SAT xxxxxxxxxxxxxxxxxxxxxxxx
Times start with Midnight or 00 hours military time, and go through to 23:00
hours according to your PC clock. If there is an "x" in the time slot for that
particular day, the system call the user back. If there is not "x" in that
slot, the user will be displayed the file CALLTIME.CSV.
In this example, Saturday, long distance calls can be made all day. Sunday,
calls can be made from 24:00 - 15:00 hours, then resumes at 21:00 hours.
There is a trashcan type of file included in the zip file you can use as a
sample. You can add numbers to this list that you want rejected should they be
entered by a user. Each time a user is successfully verified, the phone number
and Name used by the caller is added to this list.
If a caller attempts to enter a number that has been used before, the program
will display the phone number, and the user who used it to the caller, and
give them a message to contact the SysOp if this is in error.
The SysOp has the ability to alter the users expiration date once he/she is
verified. There is a variable in the configuration file called
EXPIRATION_DAYS. This can be set anywhere from 1 day to whenever, and is
adjusted by the day. If you set EXPIRATION_DAYS=730 then the users expiration
date would be set for two years from the date of registration. On the other
hand if you set it for 1 day, it would expire 1 day after registration.
Leaving it blank defaults to 365 days or 1 year, which is pretty much
standard.
The program will support the 13 digit international phone numbers. To activate
this feature, just add the keyword "INTERNATIONAL=Yes" to the configuration
file, and it will accept the long dialing string. What is not available here
is support for local exchange/area code verification. The program accepts the
number without spaces for 13 digits, and is not broken into its separate
parts. The program will however check for a match in the trashcan.csv file
before continuing.
Let me know if you need something else added to the program or datafile.
CSVerify has the ability to perform CALLBACK only type calls. Once a user has
registered, and been successfully verified, you can set the program up to just
disconnect the caller, and have CSV call the user back. Once connected, the
usr is returned to PCBoard. In order to accomplish this task, you must in some
way send an environment variable to CSV. CSV looks for the environment
variable "PCBDOOR" when it is executed. If PCBDOOR is set to "CB" that the
program will do a CALLBACK only, rather than a registration verification.
You can do this one of two ways, and I'll give you a couple of examples here;
1) From the PCBoard menu, I have the letters "CSV" which open the callback
door. If I type CSV<space>CB, then when CSV executes, it is in callback
only mode. If I type CSV by itself, then the program is in
registration/verification mode. Typing the "CB" after the CSV command
places the "CB" into the environment variable PCBDOOR, and CSV will pick it
up.
2) You can create a separate batch file for PCB to execute for callbacks which
would contain a line like "SET PCBDOOR=CB". You would then call the CSV
program as documented. At the end of the batch file you place the command
"SET PCBDOOR=" which would clear the environment variable for you when it
was finished.
By the Way:
I am awful at writing documentation.<g> If there is something missing from the
documentation that you do not understand, please contact my BBS at the above
number for clarification.
I use the History file as an addendum to the documentation, and there is a lot
of information contained in the file, so please pay attention to what is in
there, ok?
Helpful Information!
CSVerify is free to locally/privately owned PCBoard SysOps. Companies or
Corpororations that wish to use CSVerify on their systems can obtain a license
to use at a modest fee, and site licensing is available. Contact me at the
number on the top of this document for details.