home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
BBS_UTIL
/
CLBKV372.ZIP
/
CALLBK.DOC
< prev
next >
Wrap
Text File
|
1994-03-01
|
23KB
|
545 lines
┌───────────────────────────────────────────────────────────────┐
│ W E L C O M E to... MYCALBK version 3.72 │
│ │
│ The callback verifier door for RBBS-PC sysops and │
│ │
│ finally other BBS's as well. │
│ │
│ │
│ Copyright (c) 1991-1994 SteveSoft Software. USA. │
│ │
│ All Rights Reserved. │
│ │
└───────────────────────────────────────────────────────────────┘
There has long been a need for a dedicated call back verification
program for RBBS sysops. Until now, there were a few that were
relatively well programmed, however, after having tried two or three of
them, and after having determined that they didn't quite meet my
expectations, I felt it necessary to create one. The result is the
program that you, the RBBS sysop, will shortly have fully operational on
your system.
RBBS has long had the ability to allow the use of a verification door
built-in, or more accurately, a registration door. This program, MYCALBK
takes full advantage of that RBBS ability.
***
MYCALBK now supports a multitude of BBS systems! Please read on.
***
MYCALLBK is small, fast, and above all, reliable. It will run on any IBM
system, or compatible computer on which you operate your RBBS (or any
other BBS MYCALBK currently suports). MYCALBK will detect DesQview and
give up time slices accordingly. Also, it will detect a paper out
condition if you are printing your logs and continue without "hanging"
the system.
It will take some time for you to edit the sysop configurable files
which are described in more detail later in this documentation. Other
than that, it should be fully operational on your system in about 15
minutes!
In RBBS-PC v17.3C, and RBBS v17.4 CONFIG PARAMETER 107 is used to tell
RBBS-PC what the door name is to check new users at log-in. For example,
I use "F:\RBBS\DOORS\VALIDATE.BAT"
CONFIG PARAMETER 108 is the parameter to tell RBBS-PC "This security
level AND lower, must be sent to the above named door". For example, I
have it set to level 30. Everyone is at level 30 on my RBBS until they
are called back with the verifier. The verifier can easily be setup to
increase the callers' security level when a given caller has responded
successfully to the callback question, and has been logged back into
your BBS.
For other BBS's, please follow thier instructions on how to setup a
validation door. If your system does not support auto-verifying, then
please set MYCALBK up as a regular and instruct your users that they
must execute this door before being able to have access to your system.
Installation of MYCALBK is pretty much straight forward and should cause
no difficulty for most experienced sysops. If you are a 'freshman' BBS
sysop, I strongly suggest that you read this entire document to obtain
maximum performance of the CALLBK program. The following describes the
required files and their purposes.
The batch file needed to call CALLBK from RBBS...
──────────────────────────────────────────────────
You can name the following as CALLBACK.BAT just as a reference when you
are looking through the dozens of BAT files on your system. This
example is for an RBBS system. If your system requires a different
approach or different settings, please refer to your BBS documentation.
────────────────────────
The VALIDATE.BAT file...
────────────────────────
@echo off
cd
\rbbs\doors\mycalbk
Mycalbk %1
cd \rbbs
:DONE
The VERx file is a SEMAPHORE file to allow you to create an Auto-welcome
message for your new user. I use MSGFORM.EXE (for RBBS) but you may
use something different, OR process the new user differently. Possibly
"tossing" the user into another door (Now that you know they are who
they say the are).
TIPS:
1). Do not use a .BAT file named VERIFY as DOS will not execute it.
(VERIFY is a DOS keyword.)
2). If you are using WATCHDOG or some sort of carrier watchdog,
DISABLE it when running this program! This program DISCONNECTS the
caller in order to call back. If you have WATCHDOG (or a similiar
program) enabled, watchdog will REBOOT your machine instead of MYCALBK
calling back.
───────────────────────────────────────────────────────
The Configuration files and samples...
───────────────────────────────────────────────────────
────────────
MYCALBKx.CFG (Where 'x' = node number).
───────────
F:\rbbs
YELLOW
F:\bulletin\b1
ATE1V1Q0X4
00000
Line 1 = Path to your Drop file. DORINFOx.DEF, DOOR.SYS, etc...
Line 2 = Background Color of "desktop". (BLACK or BLUE not recommended!).
Line 3 = RESERVED
Line 4 = MODEM init string to get "OK" out of it.
Line 5 = Registration code. The five (5) zeros * MUST * be there!
When you register MYCALBK you will receive a registration key which you
type in place of the five (5) zeros. The five zeros simply put a small
message on the monitor that this copy is not registered. When you do
get around to registering, I will send you a registration key which will
then put a message on the monitor that you have registered this copy,
along with the name of your BBS. Please see the information about
registering near the end of this document.
──────
SL.CFG * NOTE * SL.CFG is: Security level configuration.
────── If you do not have a security listed
30,60,30 here, MYCALBK will NOT upgrade thier
65,65,65 security.
60,60,30
Parameter 1 = ENTRANCE security (what they will be when they get here).
Parameter 2 = PASS security (what to upgrade to if they pass).
Parameter 3 = FAIL security (what to drop them to if they fail).
────────
LDSL.CFG * NOTE * LDSL.CFG is: Long distance security level cfg.
────────
30,61,30
65,65,65
Parameter 1 = ENTRANCE security (What they will be when they get here).
Parameter 2 = PASS security (what to upgrade to if they pass).
Parameter 3 = FAIL security (what to drop them to if they fail).
If you enable LD calls, you MUST have this file. Otherwise your callers
SECURITY LEVEL will be set to 0 (zero) when they return. It allows you
to "bump up" LONG DISTANCE callers so they have more time on-line (Some
SysOps prefer their long distance callers to have an extra 15 minutes
on-line. After all, they are calling long distance to visit your BBS).
If you do not like that, then just set it the same as SL.CFG.
────────────
AREACODE.CFG
────────────
803,0000,2359,1
919,1800,0800,1
Parameter 1 = areacode approved for call back.
Parameter 2 = time to START (LONG DISTANCE) call backs.
(no colons, 24hr time!).
Parameter 3 = time to STOP (LONG DISTANCE) call backs.
(no colons, 24hr time!).
Parameter 4 = hang up flag. 1 = hang up after verify.
0 = stay on the line (at YOUR expense!).
First areacode *MUST* be YOUR area code! Don't make an error here!
(Please note, if the supplied AREACODE.CFG file does not contain all
United States areacodes, please let me know so I may add them in future
releases).
*NOTE*
If you only wish to call local users back, use 0000 as your
start time and 0000 as your stop time. MYCALBK will only call
LONG DISTANCE between those 2 times.
────────────
LCLXCHNG.CFG *NOTE* LCLXCHNG.CFG is: Local exchanges cfg.
────────────
393
332
669
665
Local exchanges are ones that do NOT require a '1-' in front of them and
are in your areacode. If you operate in an area of the country that
enables you to dial to another areacode and it still is a local call,
you may not want to include this .CFG file. Instead, use the
###XCHNG.CFG explained below.
───────────
###XCHNG.CFG *NOTE* ###XCHNG.CFG is: The area code is ### and the
─────────── exchanges inside this .CFG file
395 are local calls.
Another fine problem to deal with with the "BELLS". Apparantley in some
portions of the country, you can dial to more than one area code and
it's a local call. So to handle this problem, I have created this .CFG
file. If you have defined an exchange in LCLXCHNG.CFG that is NOT in
your areacode, remove it from there and enter it in this file. This
will allow local calls made across area codes to be made without the
program "thinking" they are LD and restrict them. Also, if you are
having some difficulties getting CALLBACK to work properly, try renaming
LCLXCHNG.CFG to ###XCHNG.CFG (where ### is YOUR areacode). This should
straighten out the problem.
───────────
NO-1AC.CFG *NOTE* NO-1AC.CFG is: Area codes that do NOT require
─────────── a 1- in front of the number!
803
What the Bells have done now is this... They make it MUCH easier for
you to call Long Distance by now not telling you it's Long Distance!
This I feel is wrong, but we have to deal with it!
Let's say you have configured a Long distance area code in the ABOVE
.CFG file. Now, you can call Long distance to that area code without a
1! So, add it into this .CFG file here. It must be 1 of 2 things. YOUR
base areacode or Areacodes defined in the LDXCHNG.CFG file! That's it.
────────────
TRASHCAN.DEF
────────────
###-###-####
This is to specify any numbers you do NOT want dialed period! If you
put 803-###-####, no numbers in areacode 803 will be dialed.
###-6##-#### will NOT dial any exchanges starting with 6 in ANY
areacode.
There is no need to put 900, 911, or 976 as MYCALBK stops people like
that before it would even get to this point.
────────────
x.SWI
────────────
This file is replacing the multitude of command line switches that
became to cumbersome for smooth installation of MYCALBK. MOST of the
selections in the file are self explanatory except for 1.
BBS.Type=x
The BBS.Type switch is used to tel MYCALBK which BBS you are using
and how to handle a security change (depending on BBS type).
TYPE
----
1 RBBS. Obviously, this was developed with RBBS first.
2 ANY BBS that supports reading a the DOOR.SYS file after a door
has executed. Please refer to your BBS documentation to
determine whether your BBS supports this or not. At the
moment I can list 1 BBS that supports this.
GAP
3 WildCat! Version 3.0. This one is a bit tricky but here it
goes!
After placing a 3 in BBS.Type MYCALBK expects the following.
*Please note that the data after the = are for example only!
You MUST place your data here!
;
User.Info.Path=F:\WCWORK\NODE4\ <-Path to your UserInfo.Dat file
;
Pass.Name=VERIFIED <- Security name for Passing verification
;
LD.Pass.Name=LDVERIFIED <- same as above except for LD callers
;
Fail.Name=UNVERIFIED <- Security name for Failing verification
;
LD.Fail.Name=LDUNVERIFIED <- same as above except for LD callers
;
MYCALBK 4
^ Node number even if you only run 1 node! See the
CALLBACK.BAT sample file which will make this clear to you.
Command line switches...
────────────────────────
MOST command line switches are no longer needed. You only need to pass
the node that is executing the door. Command line switches have been
replaced with a ###.SWI file where ### is the node number executing this
door.
There are 2 command line variables to pass to MYCALBK.
1). The node number executing this copy.
2). A special feature called DIALBACK.
When you place /DIALBACK on the command line, MYCALBK expects 2 things.
A). The users name in the VERIFIED.LOG (Another words, they've already
been verified).
B). The user on the other end knows he/she's going to be hung up on and
called back.
Why /DIALBACK? Some people live in an area that the user is long
distance calling the BBS, but the BBS is local calling the user.
This gives the SysOp the opportunity to give a user a special door to go
thru to allow access to the BBS without incurring long distance charges.
Do not use this command line switch in your VALIDATE.BAT file! Use it
in one called REDIAL or some other name. New users will NOT be
validated if MYCALBK is called with the /DIALBACK switch!
SysOp configurable files...
───────────────────────────
Please see the enclosed sample files for each of the following for
your convenience. You can edit them with any ASCII text editor to suit
your particular system.
There are eight (8) files in this package that are SysOp "adjustable".
But they must follow some simple guidelines.
1). The FIRST line * MUST * be one of the eight valid IBM colors...
(RED, GREEN, BLUE, CYAN, YELLOW, WHITE, BLACK, and MAGENTA)
2). The longest line must * NOT * exceed 70 columns.
Here's a description of each file and the output to the caller.
=====================================================================
WELCOME Shown to the caller when they first log-in.
NODUPES Shown to the caller when that phone number has already been used.
SORRYAC Shown to the caller when their area code is not one you
selected to call back.
INSTRUCT Shown to the caller just before disconnect, explains to caller
what to do at his/her end.
NOTTIME Shown to the caller when you have configured to call LD
callers back but this is not the right time to do it.
LDREDIAL Shown to the caller when they try to run thru the DIALBACK door
and it is determined that they are long distance. When using
the /DIALBACK parameter, the door will not call long distance.
DIALME Shown to the caller to explain what is happening when using
the /DIALBACK parameter.
NOREDIAL Shown to the caller when they try to go thru the DIALBACK
procedure and they are not a validated user (by MYCALBK). It
should give the caller instructions on how to go thru MYCALBK
and be validated by the door first.
TRASCHAN Show to the caller when the number they entered matches a
number you have defined as uncallable. This lets them know
that you are not happy with them, or that they are a bozo
etc...
TESTTIME A new file (3.72+) that is shown to the user after they have
been re-connected to your BBS. Please review what it says and
make it suit your BBS's needs. Do NOT make it exceed 20
LINES! It will mess up the display.
Again, please take the time to view the enclosed sample files if you
are not quite able to make sense of any of the foregoing. Sometimes a
sample can be worth more than a thousand words...
Once you have edited the necessary files discussed above, you should be
ready to begin using MYCALBK. You may want to make a subdirectory from
your BBS subdirectory and put all the MYCALBK files in it. For example
F:\RBBS\CALLBAK (You can rename CALLBAK as shown, to any legitimate DOS
subdirectory). Then put the MYCALBK files into it. The CALLBACK.BAT file
can be easily put into your BBS subdirectory where your BBS can find and
read it. It's only a few bytes in size. Don't forget to tell the RBBS
config (CONFIG) where the CALLBACK.BAT file is located. Use RBBS config
parameter 107 where you type the name of the CALLBACK.BAT file for RBBS
to find, and then check the security level for new users for the
verification, parameter 108. If you are using a BBS package other than
RBBS, then please refer to your BBS documentation on how to implement
the above. Your system may not support a validator automatically, in
which case setting MYCALBK like a regular door will suffice.
*REMEMBER* Do not call this .BAT file VERIFY. VERIFY is a DOS keyword.
For more explicit information regarding DOORING, please read the area in
your BBS Technical Reference Manual. It should list complete details
and several examples regarding the parameters required to operate doors
smoothly and efficiently with BBS.
OUTPUT files generated by MYCALBK...
────────────────────────────────────
MYCALBK will generate files for you with relevant information pertinent
to the related activities of callers who are swept into the RBBS
registration door. The information generated is for the sysop's
information.
───────────
MYCALBK1.LOG
───────────
This file will list any errors that may have been caused by a faulty
installation. As an example, if you should accidentally put the
MYCALBK.CFG file into the wrong sub-directory, it will generate an
error messages as follows...
Couldn't find .CFG file!
If you should see such information, then it becomes quite clear as to
what your next step should be. ...A N D also the following...
SAMPLE ONLY! of the MYCALBK1.LOG file generated by MYCALBK.EXE
^^^^^^^^^^^^
----------------------------
MYCALBK 3.72 - MULTI! Firing up!
User on-line -> JIM MADORY @ 16:38:16 on 03-01-1994
FOSSIL present and ACTIVATED!
FOSSIL present and ACTIVATED!
661-1245 Try # 1
Tries = 1 User entered JIM MADORY
JIM MADORY @ 803-661-1245 (Local) Verified!
Original security: 20
Notified BBS to change security: 200
JIM MADORY exited door.
----------------------------
────────────
VERIFIED.LOG
────────────
This file will hold the information regarding new callers to your BBS.
You should note that this file is dynamically expanding, so keep in mind
that you have enough disk space to allow this file to grow by leaps and
bounds! The information listed contains the phone number of the caller,
the name of the caller, the date, and the time that the caller used the
MYCALBK door, and whether it was long distance or a local call to your
BBS.
SAMPLE ONLY! of the VERIFIED.LOG file generated by MYCALBK.EXE
^^^^^^^^^^^^
803-555-3844 BUBBA SMITH 10-15-1993 12:31:45 Local
803-555-0923 BILLY-JOE BOB 10-15-1993 15:17:42 Long Distance
803-555-5704 ELVIS PRESLEY 10-15-1993 17:25:05 Local
803-555-1444 JO-DON BAKER 10-16-1993 19:10:11 Local
803-555-3034 STEVE STEVENS 10-16-1993 20:56:01 Local
803-555-9017 GLEN SATHER 10-17-1993 22:04:31 Long Distance
803-555-6239 WAYNE GRETZKY 10-18-1993 09:31:07 Long DIstance
803-555-1117 MIMI LAMOUR 10-18-1993 10:51:40 Local
803-555-0407 EDGAR HOOVER 10-19-1993 11:35:17 Local
803-555-6475 CANDY SAMPLES 10-19-1993 17:54:25 Local
803-555-3705 JOHNNY LARUE 10-20-1993 22:29:19 Local
In conclusion, MYCALBK has proven to be highly reliable and stable on
the beta test sites, and on other systems that are currently operating
with this program. If you are an RBBS sysop in Canada, please feel free
to call the two systems listed at the end of this document, Alberta One
RBBS @8:990/105 -or- Alberta Express @8:990/106, for any assistance you
may require. If you are in the USA, please try your best to get in
touch with me, rather than Rod Bowman, who is very busy looking after
the RBBSnet worldwide network.
Registration...
───────────────
Dear fellow SysOp...
MYCALBK required considerable time and effort, and many updates with
suggestions and ideas from several participating beta test sites (in the
USA and Canada). Therefore if you like and use MYCALBK on a regular
basis on your BBS, and you find it does exactly what it should do, then
please consider registering this quality BBS utility.
Please review the enclosed REGISTER.FRM file and ensure you respond to
the questions accurately. I will then mail you your registration key,
netmail it to you, -OR- put in on hold in the P)ersonal downloads of my
BBS for you to retrieve.
A financial contribution of $25.00 (US Funds) would be much appreciated.
Payment may be made with certified cheque, money orders, or personal
cheque (Please note, personal cheques require a delay in processing).
Your support is much appreciated.
Thank you for supporting MYCALBK...THE RBBS-PC caller verification
utility (Now more BBS's supported!).
Steve Stevens The Neutral Zone 8:927/2 1:3651/666
Queries? Feel free to...
1). Leave questions addressed to me Via NETMAIL
2). Call me VOICE @ (803)-393-0246
3). Call my BBS at (803)-395-6286.
*** Special thanks to the following people and beta sites, in the
evaluating and for making helpful tips and hints, in the development of
MYCALBK ***
Frank Harman SysOp of Alberta One RBBS (Canada) @8:990/105
Casey Vanloo SysOp of Alberta Express RBBS (Canada) @8:990/106
Rod Bowman SysOp of PC-Spectrum (tm) RBBS (USA) @8:8/8
Dan Shore SysOp of ShoreLine BBS (USA) @1:109/458
Chip Hanna SysOp of The RockCreek BBS (USA) @8:925/200
Greg Snyder SysOp of DGA Systems Alpha (USA) @8:935/130
Plus several others who have slipped my mind at the moment.
─────── Without all of you, this would not have been possible.───────
RBBS-PC is copyright 1992 Tom Mack, and probably Ken Goosens. USA.
IBM is the registered trademark of International Business Machines. USA.
XU/X00 utilities, v1.01 is copyright 1990. Raymond L. Gwinn. USA.
USRobotics, and HST are trademarks of USRobotics, Inc. USA.
DESQview is the registered trademark of Quarterdeck Office Systems. USA.
POWERBASIC is Copyright 1990,1992 Robert S. Zale. USA
GAP is copyright (unknown)
WildCat! is copyright (unknown)
***********************************************************************
One Final Note...
This version of MYCALBK has been written with POWER BASIC 3.0c. It
contains mostly BASIC source code but it has a several DOS Interrupt
calls and some inline assembly.
I have been using PowerBasic for well over 3 years (it was called Turbo
Basic) and have enjoyed programming in it. Please support RBBS's
re-write in PowerBasic as it is as powerfull yet as simple as you can
get before going to 'C'. Browsing 'C' manuals and the like has helped
me immensly in programming in BASIC as well and with PowerBasic it makes
it all that much easier.