(* 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 *)
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.
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 797-1713 <
H/V Phone : 904 794-0063 Elapsed Time On : 5
Password : TEST Number Times On : 1
Security : 60 <
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. <
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
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 @[email protected]
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.
Make sure that the information in the CSVerify.cnf file is correct for your
BBS. The lines are fully commented in the configuration file for ease of
modification. Call me if you have any trouble, or want something added.
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. I ask the user if the number is long distance if the area code
or exchange entered does not match what you specify in the CSVerify.cnf or
If the number entered is deemed long distance, the program will adjust the
users security level to that you have specified in the config file the user
will be notified of that fact, and returned to PCB.
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, you can configure the program to 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 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
used by the caller is added to this list.
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 EXPIRED. This
can be set anywhere from 1 day to whenever, and is adjusted by the day. If you
set EXPIRED=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 number now. To
activate this feature, just add the keyword "INTERNATIONAL" to line 23
of 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
1) From the PCBoard menu, I have the letters "CSV" which open the callback
door. If I type CSVCB, 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
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
By the Way:
I am awful at writing documentation. 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