Loop-Back [PPE] Call-Back Verifier v5.05 Copyright (c)96,1997 by Practical Computer Services For use with PCBoard v15.2x and above ------------------------------------------------------------------------------ Trademarks & Copyright Information: ----------------------------------- PCBoard is a registered trademark of Clark Development Company, Inc. PCBoard is copyright (c) 1985-1997 by Clark Development Company, Inc. PPLC is copyright (c) 1993-1997 by Clark Development Company, Inc. PPL is a trademark of Clark Development Company, Inc. PCBEdit is copyright (c) 1993 by Clark Development Company, Inc. LoopBack is copyright (c) 1993-1997 by Practical Computer Services LoopUtil is copyright (c) 1994-1997 by Practical Computer Services All other brand and product names mentioned in this manual are trademarks or registered trademarks of their respective companies. ------------------------------------------------------------------------------ Disclaimer: ----------- Practical Computer Services (herein referred to as PCS) does not assume any liability arising out of the application or use of any products described herein. PCS reserves the right to make changes of any products described herein without notice. This document is subject to change without notice. ------------------------------------------------------------------------------ License: -------- LoopBack/LoopUtil is in no way, shape, or form public domain. Upon installing LoopBack/LoopUtil, the user agrees to abide by all terms and conditions contained in this and all documentation. The user is granted a 30 day license to run LoopBack/LoopUtil. After 30 days, the user must either delete all operating copies of LoopBack/LoopUtil or register the software with PCS. If the user has copies of LoopBack present on his/her bulletin board, in their original archived format, for users to download, then he/she need not delete those copies. Only copies that the SysOp is using to callback users on his/her BBS must be deleted. Any part or contents of this manual may not be reproduced or transmitted in any form or by any means without the express written permission of PCS. You may not attempt to disassemble or decompile any of the products contained in the archive. ------------------------------------------------------------------------------ Warranty: --------- LoopBack and LoopUtil do not contain any kind of warranty, express or implied. LoopBack and LoopUtil are provided `as is'. Any bugs or compatibility problems reported will be corrected as soon as possible. ------------------------------------------------------------------------------ Registration & Support: ------------------------ Registering LoopBack will do the following for you: 1) Remove the UNREGISTERED delay at the beginning of LoopBack. 2) Place your name & security code in the (L)oopInfo screen. 3) You will receive VOICE and BBS support. 4) You will receive our periodic newsletter announcing updates and other product developments. If you have an internet e-mail address, we also have a PCS-NEWS listserv available. To register LoopBack/LoopUtil, fill out the file REGISTER.FRM and do one of the following: 1) : Print out the form and mail it along with a check or money order to the following address: Practical Computer Services 483 Klockner Road Hamilton, NJ 08619 After receiving the check/money order an account will be setup for you on The TAO BBS. (If you do not already have one setup). You may then call in to receive your registration codes. Or, your codes can be mailed to you. The choice is yours. Calling our support BBS is of course a lot faster then the mail. :) 2) : Register with your info, online. Recieve your keys immediately. Logon on to the support board, and type KEY. The registration prices of LoopBack/LoopUtil are as follows: LoopBack Registration ------------------------ $25 registration LoopBack Major Update ------------------------ $10 upgrade fee Universal Registration (registers all UNIVERSAL PPE's) ------------------------ $40.00 All minor updates may be freely downloaded and do not cost you a penny. However, if you wish to have a new disk sent to you, there will be a $5 fee. How to contact PCS: Practical Computer Services 483 Klockner Road Hamilton, NJ 08619 The TAO BBS: (33.6K baud) (609) 587-2672 (MAIN SUPPORT BBS) Voice: (609) 584-7947 Fax: (609) 587-0583 E-Mail: bob.watson@tao.com Web Site: http://www.nerc.com/~pcs/ ------------------------------------------------------------------------------ Use and function: ----------------- LoopBack is a PCBoard Programming Language Executable file, or commonly referred to as PPE. This PPE will allow you to provide tighter and more efficient security for yourself, your co-SysOp, and your users. LoopBack can be configured to call the user back and then upgrade their security according to the type of call and the connection. In this way, you can make sure your users are using correct telephone numbers and in the same instance keep multiple accounts out of your system. LoopUtil is also a PPE. This PPE maintains most of the maintenance and file editing/configuration for LoopBack. With this PPE, the SysOp can edit the prompt files, configuration file, trash files, etc. This will enable your remote co-SysOps to maintain LoopBack without the use of an external door program. ------------------------------------------------------------------------------ Why choose a [PPE] over a door? -------------------------------- There are many advantages to running a PPE rather than a door. Here is a simple list of some of the advantages that you will have as a result of running a PPE. 1) Flexibility - With a PPE, you can replace any of your display prompts and actually rewrite that part of PCBoard to your specifications. You may also place PPEs in display files. So if you wanted to only run LoopBack for users with a security level of ten, then all you need to do is create a login security file, and place the following line in it to execute LoopBack: !C:\PCB\PPE\LOOPBACK\LOOPBACK.PPE 2) Communications - With a PPE, communication with your COMM port is not a problem. Do you run a FOSSIL driver and just can't seem to find a door to work right with it? Are you using an Intelligent Multi-Port serial card and cannot find a door to support it? Are you running OS/2 and cannot find anything to support your multi port driver? Then look no further! Since a PPE runs within PCBoard, PCBoard handles all the communications for the PPE. So if you have PCBoard setup to work with a 16-Port DigiBoard IM card, then your PPE will also know how to correctly talk to your modem.. Same goes for FOSSIL drivers, the OS/2 COMM Routines, etc. 3) Smooth operation - Ever had a door that could never figure out when someone has dropped carrier? Or maybe you have a door that is very slow to load and sometimes locks your system up.. If so, then you need to replace that door with a PPE. Again, since a PPE runs within PCBoard, PCBoard handles all carrier detection, etc. If someone drops carrier in a PPE, PCBoard recycles. If someone has not entered a keystroke for the specified # of minutes, PCBoard logs them off. etc., etc. ------------------------------------------------------------------------------ Online Help: ------------- It is recommended that you read the documentation in its entirety, but if you still do not understand something (particularly the dialing templates or allowed #s calling file) then try viewing the online help. We are constantly adding new help files to each part of the LoopUtil maintenance utility. If you still do not understand after viewing the online help, or there is no help available for the subject you do not understand, then call The TAO BBS at (609) 587-2672 and leave a private message for Bob Watson. ------------------------------------------------------------------------------ Excessive command line violations: ----------------------------------- If you see the message "Excessive command line violations" in your callers log, do not be alarmed. This is not a bug in the call-back verifier. This is just the way that PCBoard processes the HANGUP statement in PPL. I have been trying to find a way aroung it, but have had no luck. I will keep trying though. ------------------------------------------------------------------------------ Error loading PPE: ------------------- If PCBoard displays a message such as "Error loading PPE from disk", then check to make sure you are running PCBoard v15.2x. If you are not running PCBoard v15.2x, then you must call Salt Air (1-801-261-8976) and download the v15.2x code by typing PCBOARD at the main menu. LoopBack will not run with a version of PCBoard prior to v15.2. ------------------------------------------------------------------------------ Overlay buffers and memory problems: ------------------------------------- The OVLSIZE.EXE program, included with PCBoard, is a very useful tool for configuring the performance of your PPEs. First, you need to know how much memory you have available, and how much memory your largest PPE or door neLoop to operate. Second, the more overlay buffers you have, the faster your PPEs will operate. But you cannot make the buffers to large, or some of your PPEs and doors may not have enough memory to operate. I suggest that if your PCBoard status line shows at least around 170K or so, you'll be alright. I have my overlay buffers set at 21 (or 84K). To change your overlay buffers, run OVLSIZE with the following parameters: OVLSIZE.EXE is the path & filename of your PCBoard executable. is the size of your overlay buffers.. Valid sizes are as follows: 1 = 4K 9 = 36K 17 = 68K 25 = 100K 2 = 8K 10 = 40K 18 = 72K 26 = 104K 3 = 12K 11 = 44K 19 = 76K 27 = 108K 4 = 16K 12 = 48K 20 = 80K 28 = 112K 5 = 20K 13 = 52K 21 = 84K 29 = 116K 6 = 24K 14 = 56K 22 = 88K 30 = 120K 7 = 28K 15 = 60K 23 = 92K 31 = 124K 8 = 32K 16 = 64K 24 = 96K 32 = 128K When searching through the already used number trash file, I noticed a 30% speed increase when I changed my overlay buffers from 16 (or 64K) to 21 (or 84K). NOTE: You MUST be sure that all your programs and PPE files will be able to execute after you change the overlay buffer setting. If LoopBack or LoopUtil will not execute because PCBoard is reporting "Unable to allocate memory (SCRIPT BUFFER)", then you will need to do one of the following things. 1) Try to maximize your window if using DESQview. 2) Set "Pre-Load PCBTEXT" setting in PCBSetup to NO 3) Set "Pre-Load CNAMES" setting in PCBSetup to NO 4) Lower the amount of overlay buffers in your PCBOARD.EXE or PCBBOARDM.EXE file. ------------------------------------------------------------------------------ Installation: ------------- The following is a list of steps for the first time installation process: Step #1: Make a directory to hold your LOOPBACK files ie: MD C:\PCB\PPE\LOOPBACK Step #2: Unarchive LoopBack into this directory. Step #3: Add both LOOPBACK & LOOPUTIL into your CMD.LST file (see the heading EXECUTING the LOOPBACK.PPE later in this document) Step #4: Load up PCBoard and type the command that you setup to run the LOOPUTIL.PPE file. (ie., LOOPUTIL) Step #5: Select C to edit your configuration file. (Information on configuration is explained later in the manual.) Step #6: Select P to modify the prompts to your specifications. (The prompting system is explained later in the manual.) Step #7: Select N to modify your "Already Used # File". You can use the BUILD feature to do this. (The BUILD feature is explained later in the manual.) Step #8: Select T to modify the timetables, if you need to use them. (The timetable system is explained later in the manual.) Step #9: Select B to modify the bad numbers file. (This is the file that you want to put 911 in.) Step #10: Select F to modify the name & security trash files to keep out those users that you do not want to be called back. Step #11: Select A to modify the numbers that LoopBack is allowed to callback. (This is explained later in the manual) Make sure you define your dialing templates! (This is explained later in the manual) Step #12: If you wish to install LoopBack as a NewUser login PPE, please read the section in the manual entitled "Executing the LOOPBACK.PPE file". Step #13: Read the documentation in its entirety. ------------------------------------------------------------------------------ Configuration file maintenance via LoopUtil: -------------------------------------------- Configuration Toggles ----------------------- (1) Allow international callbacks : This toggle will tell LoopBack whether or not it is allowed to callback international numbers. (If you do not absolutely need international callbacks, then set this option to No. Certain features of LoopBack are not present when International callbacks are allowed.) (2) User's time adjustment : This toggle will tell LoopBack how to adjust the user's time. If it is set to (R)eplace, then the value set in the config settings will replace the user's time. If it is set to (A)dd then the time value will be added to the user's time. (If you do not want to adjust the user's time, then set this toggle to (A)dd and set the time value in the dialing template to 0) (3) Message type to send to the SysOp : This toggle will tell LoopBack what kind of message to send to the SysOp. If it is set to (I)nternal LoopBack will generate an internal message to the SysOp. (E)xternal will tell LoopBack to send the file defined in the configuration paths (SysOp.MSG) to the SysOp. (N)one will tell LoopBack to send no message at all. (4) Message type to send to the User : This toggle will tell LoopBack what kind of message to send to the User. If it is set to (I)nternal LoopBack will generate an internal message to the user. (E)xternal will tell LoopBack to send the file defined in the configuration paths (USER.MSG) to the user. (N)one will tell LoopBack to send no message at all. (5) Comment to use : This toggle will tell LoopBack what kind of comment to add to the user's record after a successful verification. (D)ate will tell LoopBack to put the date and time that the user was verified in the user record. (P)hone will tell LoopBack to put the phone number that was called back in the user record. (B)oth will tell LoopBack to put both the date & time verified and the phone number called back into the user's record. (N)one will tell LoopBack to not place any kind of comment in the user's record. (6) Check user's name : This toggle will tell LoopBack whether or not it should ask the user to enter his/her name for verification after callback. (7) Check user's password : This toggle will tell LoopBack whether or not it should ask the user to enter his/her password for verification after callback. (8) Check user's verification string : This toggle will tell LoopBack whether or not it should ask the user to enter his/her verification string (mother's maiden name) for verification after callback. (9) Check user's city : This toggle will tell LoopBack whether or not it should ask the user to enter his/her city (calling from) for verification after callback. (10) Upgrade local callers : This toggle will tell LoopBack whether or not it should upgrade the status of a local caller after a successful verification. You may want to turn this toggle off if you will be frequently texting LoopBack from a local node. (11) Update user's data phone # : This toggle will tell LoopBack whether or not it should change the user's data phone # to the number that was used to call the user back. (12) Verify user's city : This toggle will tell LoopBack whether or not it should ask the user if his/her name and city are correct. This is only needed for large systems who may have different callers that have the same name. (13) Allow user to use logoff command : This toggle will tell LoopBack whether or not it should allow the user to logoff within LoopBack without undergoing verification. (14) Allow user to return to main : This toggle will tell LoopBack whether or not it should allow the user to return to the BBS without undergoing verification. (15) Allow multiple callbacks : This toggle will tell LoopBack whether or not it should callback numbers that have already been called back. (LoopBack will still read in the "already used number" trash file and will still update it, but it will call the user back even if it finds a record matching the user's phone #) (16) Allow trash file display : This toggle will tell LoopBack whether or not to display the trash file information to the user if a record was found matching the user's phone number. The user will be shown the caller that was called back with the matching # and the date & time of the callback. (17) Place to put date comment (Comment #1) : This toggle will tell LoopBack where it should put the date comment (if configured to use the date comment). In the configuration (LoopUtil) you will be given a menu of choices. This comment can be placed in either of the 2 user record comment fields or any of the 5 Notes PSA fields (If Notes PSA is installed). (18) Place to put phone # comment (Comment #2) : This toggle will tell LoopBack where it should put the phone # comment (if configured to use the phone # comment). In the configuration (LoopUtil) you will be given a menu of choices. This comment can be placed in either of the 2 user record comment fields or any of the 5 Notes PSA fields (If Notes PSA is installed). (19) Filetype to execute at the end : This toggle will tell LoopBack what kind of file (if any) it should execute after the user has been verified, but before the user is upgraded. (P)pe will tell LoopBack to call a PPE file. (B)atch will tell LoopBack to execute a DOS Batch file. (N)one will tell LoopBack to not execute a file at all. (The file to execute may be configured under the configuration paths) (20) Do not allow broadcast messages : This toggle will tell LoopBack whether or not to allow the user to receive broadcast messages from other nodes. If set to Yes, LoopBack will modify the USERNET.XXX file to prevent the user from receiving a broadcast message. If set to No, LoopBack will not modify the USERNET.XXX status flag. (21) Hangup on bad numbers : This toggle will tell LoopBack whether or not it should hang up on the user if he/she enters a number that was found in the Bad #'s file. If set to Yes, LoopBack will hangup on the user.. If set to No, LoopBack will simply return back to the BBS. (22) Immediately start download : This toggle will tell LoopBack whether or not it should immediately start the download process after it flags the files for download. You may wish to do this if your new users tend to logoff without downloading the files that were flagged. NOTE: If LoopBack is supposed to logoff the user after callback, it will NOT attempt to flag a file for download, nor will it attempt to initiate the download process. (23) Check Caller-ID string : This toggle will tell LoopBack whether or not it should search for the user's home and/or data numbers in the caller id string. If either number is found, LoopBack will upgrade the user according to the default settings in the Configuration settings (Default Sec. Lvl if no callback, Default Exp. Sec. Lvl, etc.) and it will exit back to PCBoard without calling the user back. If either number is not found in the caller-id string, it will proceed as normal. Configuration Settings ------------------------ (1) Modem dialstring : This setting will tell LoopBack the dialstring to use when calling the user back. If you have touchtone dialing, then set this setting to ATDT. If you have pulse dialing, set it to ATDP. (2) Number dialing prefix : This setting will tell LoopBack the prefix to dial before it dials the number. This can be used if you need to dial 9 to get out, etc. If this setting is not needed, do not set it equal to anything. (3) Number dialing suffix : This setting will tell LoopBack the number to dial after it dials the number. I personally cannot think of any use for this, but if you find one, please tell me. (4) Maximum # of redial attempts : This setting will tell LoopBack the maximum # of times that it will try to redial the number if a connection is not made the first time. If LoopBack still does not connect after it redials the maximum # of times, it will exit back to PCBoard. (5) Maximum # of ticks to wait for connection : This setting will tell LoopBack the maximum # of ticks that it should wait for a connection. (The term ticks and its conversion factor to seconds is defined in the explanation section later in the manual) (6) Amount of time to adjust : This setting will tell LoopBack the amount of time in which to adjust the user's time. (To configure how to adjust the time, see configuration toggles) (7) Modem initialization string before callback : This setting will tell LoopBack the string in which to send to the modem (to initialize it) before it dials the number. (8) Maximum # of ticks to wait for hangup : This setting will tell LoopBack the maximum # of ticks to wait for the modem to hangup on the user. NOTE: As soon as LoopBack detects a carrier loss, it will go on to initialize the modem, dial the number, etc. (9) Long distance access string : This setting will tell LoopBack the string to dial before it calls a long distance, toll call, or International number. For example, to use AT&T you would set this equal to 102881. If you just want to use 1+ dialing and no special LD company, set it equal to 1. You can specify when to use this in dialing templates maintenance. (10) Minimum # of digits to dial : This setting will tell LoopBack the minimum # of digits allowed in the callback #. For example, if you set this equal to 10 and the user enters a number like 212-77-022, then LoopBack will tell them that it does not contain enough digits and reask the user for the callback number. (11) Default Exp. Lvl. if no callback : This setting will tell LoopBack the value to put in place of the user's expired security level if no callback occurs. (Not in allowed # calling file, # found in caller-id string, timetables, etc.) A setting of 0 will tell LoopBack not to touch the user's expired security level. (12) Default days till expire if no callback : This setting will tell LoopBack the number of days to add to the verification date to replace the user's expiration date. For example, if you enter 30 in this field, and the date that the user entered LoopBack was 12-01-94, then the user's new expiration date (if he/she was not called back) will be 12-31-94. (13) Default Sec. level if no callback : This setting will tell LoopBack the value to put in place of the user's security level if no callback occurs. (Not in allowed # calling file, # found in caller-id string, timetables, etc.) A setting of 0 will tell LoopBack not to touch the user's security level. (14) Maximum # of name input tries : This setting will tell LoopBack the maximum number of times to allow the user to enter his/her name for verification. If the user does not enter a valid name in the maximum # of tries, then LoopBack will issue the BYE command and will exit back to PCBoard. (15) Maximum # of password input tries : This setting will tell LoopBack the maximum number of times to allow the user to enter his/her password for verification. If the user does not enter a valid password in the maximum number of tries, then LoopBack will issue the BYE command and will exit back to PCBoard. (16) Maximum # of verification string input tries : This setting will tell LoopBack the maximum number of times to allow the user to enter his/her verification string for verification. If the user does not enter a valid verification string in the maximum number of tries, then LoopBack will issue the BYE command and will exit back to PCBoard. (17) Maximum # of city input tries : This setting will tell LoopBack the maximum number of times to allow the user to enter his/her city for verification. If the user does not enter a valid city in the maximum number of tries, then LoopBack will issue the BYE command and will exit back to PCBoard. (18) Maximum # of hangup attempts : This setting will tell LoopBack the maximum number of times to try to hangup the modem. If a carrier is still detected after LoopBack has tried to hangup for the maximum # of attempts, then LoopBack will issue the BYE command and exit back to PCBoard. (19) Time delay after connection : This setting will tell LoopBack the # of ticks to delay after a connection is detected. (20) Your BBS line's areacode : This setting will tell LoopBack the default areacode to put in the areacode field when asking the user for their phone number. (If the user did not pick their home or data number) If you do not wish to provide your users with a default, then do not set this equal to anything. (21) Number of minutes to add on entry : This setting will tell LoopBack the # of minutes to add to the user's time upon entry of LoopBack. If your newusers may not have enough time to undergo the verification process, then LoopBack will add the number of minutes defined in this setting to their time.. This will help to give them enough time to be verified. (22) Daily download bytes to add. Set this equal to the # of bytes to add to the number of bytes the user has already downloaded for the current day. ie., a setting of 100000 will let LoopBack tell PCBoard that the user has already downloaded 100,000 bytes for the current day. (Thus indicating that he/she can download 100,000 less bytes than before verification. To let the user download more bytes for the current day, use a negative number. ie, a setting of -100000 will let LoopBack tell PCBoard that the user can download 100,000 more bytes for the current day. (23) Total download bytes to add. Set this equal to the # of bytes to add to number of total bytes the user has already downloaded since his/her first logon date. ie., a setting of 100000 will let LoopBack tell PCBoard that the user has already downloaded 100,000 bytes since his/her first logon date. (Thus indicating that he/she can download 100,000 less bytes than before verification.) To let the user download more bytes, a setting of -100000 will let LoopBack tell PCBoard that the user can download 100,000 more bytes. (24) Total files to add. Set this equal to the # of files to add to the number of total files the user has downloaded since his/her first logon date. ie., a setting of 10 will let LoopBack tell PCBoard that the user has already downloaded 10 files since his/her first logon date. (Thus indicating that he/she can download 10 less files than before verification.) To let the user download more files, a setting of -10 will let Loopback tell PCBoard that the user can download 10 more files. Configuration Paths --------------------- (1) Trash can file : This is the path & filename of the file that LoopBack should use to search for phone numbers that have already been called back. (2) Allowed # calling file : This is the path & filename of the file that LoopBack should use to determine whether or not it is allowed to call back the number that the user entered. (This file is explained later in the documentation. (3) User name trash file : This is the path & filename of the file that LoopBack should search to determine whether or not the user is allowed to enter LoopBack. (4) Bad numbers file : This is the path & filename of the file that LoopBack should use to determine whether or not the number it is about to call is a bad number number. (5) SysOp message file : This is the path & filename of the file that LoopBack should send to the SysOp as a message after a successful callback. LoopBack will not use this file if the message to send to the SysOp has been configured as an Internal message or no message at all. (6) User message file : This is the path & filename of the file that LoopBack should send to the user as a message after a successful callback. LoopBack will not use this file if the message to send to the user has been configured as an Internal message or no message at all. (7) Numbers menu file : This is the path & filename of the menu displayed to the user when he/she is selecting the number to use for callback. (8) Help file : This is the path & filename of the help file displayed to the user when he/she selects the (H)elp command from the LoopBack main menu. (9) Locking timetable : This is the path & filename to the file that LoopBack will use to determine whether or not it should be operating at the time. (10) Security trashfile : This is the path & filename to the file that LoopBack should search to determine if the user's security level is allowed to enter LoopBack. (11) File to flag for user : This is the path & filename of the file that LoopBack should flag for download after a successful callback. If you do not wish to have LoopBack flag a file for download, then do not set this equal to anything. (12) File to execute upon verification : This is the path & filename of the file that LoopBack should execute after the user has been verified, but before the user is upgraded. (The file type to execute is defined in configuration toggles) Registration Information -------------------------- The following registration information is only required to be entered when LoopBack has been registered. (1) SysOp name : This is the SysOp's name that registered LoopBack. (2) Registration # : This is the registration # given to the SysOp after he/she registered LoopBack. (3) Date + time registered : This is the date + time registered value given to the SysOp after he/she registered LoopBack. (4) Version registered : This is the version # that was given to the SysOp when he/she registered LoopBack. This is NOT the version of LoopBack that you are running! ------------------------------------------------------------------------------ Environment Switches: ---------------------- In addition to all the configuration toggles and settings, LoopBack contains some additional configurability with the use of Environment switches. Environment switches are very simply to use. All you do is place them in your BOARD.BAT file, and your off. The variable name to use is LOOPBACK. Each node's board.bat must be modified for the changes to take affect for all nodes. ie., SET LOOPBACK=/ALERT /BYPASS The above is an example of the use of environment switches. By placing that line at the top of your BOARD.BAT file, you will turn on the bad number alarm, and bypass the main menu upon entry. Here is a listing of all the possible environment switches: /ALERT -- Will sound a 5 second siren whenever the user enters a number that was found in the bad number files. Will also display a message on screen to the SysOp that only the SysOp will be able to see. /LOCALONLY -- Only allow local users in LoopBack. (For testing purposes before you actually put it online.) /NOINFO -- Do not allow the caller to view the (L)oopinfo screen. (You may also wish to edit the prompt so that it no longer contains the (L)oopInfo selection. It is prompt #15.) /BYPASS -- This environment switch will tell LoopBack to bypass the LoopBack main menu and go directly into the callback process. So, if you were to configure a node on your system to sound the bad # alert, bypass the main menu, and disallow the (L)oopInfo screen viewing, your BOARD.BAT for that particular node might look like the following: ECHO OFF C: CD \PCB\NODE1 SET PCB= SET DSZLOG=PCBDSZ.LOG SET LOOPBACK=/ALERT /BYPASS /NOINFO IF EXIST REMOTE.BAT RENAME REMOTE.BAT REMOTE.SYS IF EXIST DOOR.BAT DEL DOOR.BAT IF EXIST ENDPCB DEL ENDPCB PCBOARDM IF EXIST REMOTE.BAT REMOTE IF EXIST DOOR.BAT DOOR IF EXIST EVENT.BAT EVENT IF EXIST ENDPCB GOTO END BOARD :END exit If you will be using multiple environment switches, they should be seperated by a space (as shown above). If you would only like to bypass the LoopBack main menu, your LoopBack environment variable might look like this: SET LOOPBACK=/BYPASS ------------------------------------------------------------------------------ Statistics file maintenance via LoopUtil: ----------------------------------------- The statistics file holds information for the last 6 callbacks and the total number of callbacks. The only time that you will want to edit this file is when you want to reset the stats file or change either one of the last 6 callbacks or the total # of callbacks. ------------------------------------------------------------------------------ Prompt file maintenance via LoopUtil: ------------------------------------- The prompt file is somewhat like PCBoard's own PCBTEXT file with a few differences.. First, you can actually "turn off" a prompt in LoopBack. Second, you can tell LoopBack whether or not to add a linefeed before the prompt is displayed, etc. To search for a prompt : Type P from the LoopUtil main menu... After entering the full path & filename of the prompt you want to edit, type S. Then enter your search criteria. (Since this is a BOYER - MOORE search you can enter criteria with the && and || symbols. As well as parentheses enclosure, etc.) LoopUtil will then search for the prompt. If found it will display the prompt's record and halt the search. If not found, you will be returned to the record you were editing when you initiated the search. To change a prompt : Type P from the LoopUtil main menu... Then you must enter the full path & filename of the prompt file that you want to edit... After the prompt module is loaded, find the prompt you want to edit and type P to change the prompt. Then, just type your text and hit return.. To change a prompt to a PPE file or Display file : Do exactly the same as you would in PCBoard. For example, this would execute the file DOSUM.PPE (!C:\PCB\PPE\DOSUM.PPE). The following would display the file OK. (%C:\PCB\PPE\OK). The Type field in the prompt editor is not used by LoopBack and is there for informational purposes only. So if you change a prompt to a PPE file, you do not have to update the Type, but you can so that you will know it is a PPE file. To turn off a prompt : Typing U from the prompt editor will toggle the Utilize Prompt flag. To add a linefeed before the prompt : Typing L in the prompt editor toggle the linefeed flag. For more information on replacing prompts with display files and PPE files, see the PCBoard manual. ------------------------------------------------------------------------------ Already used number trashcan file maintenance via LoopUtil: ----------------------------------------------------------- The already used number trashcan holds the numbers that have already been called back. If you have the Multiple Callbacks toggle toggled to Yes, then you can disregard this part of the manual. Converting the trashfile -------------------------- If you are just now upgrading from a release prior to v1.07, then please read this section carefully. In v1.07 of LoopBack, the already used number trash file format was changed. You will need to convert your old format to the new 1.07 specifications. Please type N at the LoopUtil main menu, then type C at the next menu to convert the file. After the conversion, you may wish to go through your already used number trash file and edit any records that seem to be missing leading zeros. (For a definition of leading zeros, please see the explanation section of this manual) This new file format fixes the problem of LoopBack not recognizing leading zeros in versions prior to v1.07. An example of a number that may be missing some leading zeros: Original number : 212-777-0225 Number in file : 212-777-225 Notice the zero is gone... Building the trashfile ----------------------- If you are switching call-back verifier's to LoopBack and/or you are installing LoopBack for the first time, then you will probably wan to BUILD your already used number trash can LoopUtil will either BUILD a new trash can file or it will add to your existing trash file. LoopUtil will add records by security level also. IMPORTANT NOTES: LoopUtil will NOT add a number to the trash file if it does not contain at least 10 numbers or if it contains MORE than 10 numbers. LoopUtil strips out all characters except numbers and then determines if the number is in the correct format or not. (AREACODE + PREFIX + OTHER 4 NUMBERS) LoopUtil will also keep a log file called BUILD.RPT. This file contains the user's name that met the security level requirement, the user's record number, whether or not the user's DATA number was added to the trash file, the user's DATA number, whether or not the user's HOME number was added to the trash file, and the user's HOME number. You may wish to print out this file after you are done building the trash file. You can look at each number that was not added to the trash file and add it manually within LoopUtil. It's all in the log file. LoopBack also backs up your already used number trash file. The backup file is located in your LoopUTIL directory and the filename is TRASH.BAK. If something should go wrong during the trash file building process, then all you have to do is delete your trash file and replace it with the backup. Add to the trash file or build a new one? If you are running LoopBack for the first time, then I would tell you to build a new one. If you have been running LoopBack for awhile and just now found the BUILD feature, then let LoopUtil add to the trash file. (L)owest security level to process : This is the lowest security level of the users that you want LoopBack to import into the already used # trash file. (H)ighest security level to process : This is the highest security level of the users that you want LoopBack to import into the already used # trash file. (U)sers file path & filename : This is the path & filename of your USERS. file. There should be no need to change this, as LoopBack extracts the information directly from your PCBOARD.DAT file. When LoopUtil finds a user record that meets the security level and fluctuation requirements, then that user will be added to the log file and if his/her DATA number is the correct format (10 characters/numbers) then it will be added. Also, if the user's HOME number is the correct format, it will be added to the trash file. IF YOU ARE ADDING TO THE TRASH FILE AND NOT BUILDING A NEW ONE, I RECOMMEND THAT YOU PACK IT FIRST. THIS IS AN AWFULLY SLOW PROCESS! IT IS SUGGESTED THAT ALL NODES ARE TAKEN DOWN DURING THIS PROCESS... (Although not required, it may slow down your computer if you are multi-tasking) Also, the more overlay buffers that you have, the faster it works. Indexing the trashfile ------------------------ LoopBack has an index file for the trash file. It uses this index file when searching for numbers that have already been used. LoopBack will NOT operate correctly without this file.. That's why you have to create it.. To index the trash file, type N from the LoopUtil main menu, then type I at the next menu. This will start the indexing process and LoopUtil will automatically extract the information from the already used # trash file and place it into the TRASH.IDX file. Exporting the trash file to a text file ----------------------------------------- When exporting, LoopUtil will ONLY export numbers that are not international numbers. It will place those numbers that were not exported in the report file so that you may add them yourself You must first type N from the LoopUtil main menu. At the next menu, you need to type X to invoke the used # trash MODULE in EXPORT mode. LoopUtil will then ask you for the path & filename of the text file to export to. After that, you must enter the path & filename of the file to use as your report file. After this, LoopUtil will begin its exporting process. Importing a text file into the trash file ------------------------------------------- When importing, LoopUtil will ONLY import numbers that are of the following format: XXX-XXX-XXXX In other words, LoopUtil will only import American and Canadian phone numbers. 212-777-0225 will work, but 34-545-987678 will not work. You must first type N from the LoopUtil main menu. At the next menu, you need to type M to invoke the used # trash MODULE in IMPORT mode. LoopUtil will then ask you for the path & filename of the text file to import. After that, you must enter the default username that will be placed in all records that are imported. After this, LoopUtil will begin its importing process. Text file format is as follows: EACH LINE : 212-777-0225 OR : 2127770225 OR : (212)777-0225 OR : (212) 777-0225 OR : 212 777-0225 ETC., ETC. LoopUtil will strip out the following characters: ( ) - , It will also strip out spaces... There must be only one number per line! A text file to import may look something like this: 212-777-0225 801-261-8976 801-261-8979 801-261-1686 Editing the trashfile ----------------------- Searching for a record : To search for specific text in the Name field of a record, type S from the trashcan editor. Then you must enter your search criteria. (BOYER-MOORE search format) If LoopUtil finds your text in the name field of one of the records, that record will be displayed and the search will halt. If LoopUtil does not find your search criteria, you will be returned to the record in which you were editing. Deleting a record : To delete a record, type E from the trashcan editor and that will toggle the delete flag. This will only "turn the record off". In other words, LoopBack will ignore this record when searching for a duplicate phone number. To physically delete the record, see "Packing the trashfile". Adding a record : To add a record, type A from the trashcan editor. You will then be asked a series of questions, and as soon as you finish entering all the information, you will be returned to the editor. Changing the username called back : To change the name, type N from the trashcan editor. This field is not case sensitive since LoopBack automatically changes it to uppercase. Changing the number called : To change the number that was called back, type # from the trashcan editor. If you have the international toggle set to yes, then LoopBack will ask you for the country code, city code, etc. If the international toggle is set to no, then LoopBack will ask for the areacode, prefix, & number. Changing the international toggle : To change the international toggle, type I from the trashcan editor. Changing the date called back : To change the date called back, type D from the trashcan editor. Changing the time called back : To change the time called back, type T from the trashcan editor. Packing the trashfile ----------------------- To pack the already used number trashcan file, type N from the LoopUtil main menu. Then, when asked whether you want to pack or edit the trashfile, type P. After that, LoopUtil will ask you if you want to check the trash file against the PCBoard USERS file for validity. If you select Y for this option, it will go through each trash file record and search the PCBoard USERS file to make sure that user still exists on the system. If the user does not exist in the PCBoard USERS file, LoopUtil will mark that user for deletion from the LoopBack trash file and he/she will be packed out. If you select N for this option, it will not check the LoopBack trash file against the PCBoard USERS file for validity. LoopUtil will then show the filesize of the trash file and the number of records in the trashfile. It will also display a percentage bar and percent done while it is packing the trashfile. Packing the trashfile will remove all records that have the Delete flag set to Yes. NOTE: If you elect to check the trash file against the PCBoard USERS file for validity, a file called COMPARE.RPT will be created in your LoopBack directory. This file will contain the names of all the users that were removed from your LoopBack trash file. ------------------------------------------------------------------------------ Timetable maintenance via LoopUtil: ----------------------------------------------------------- These timetables control the times that LoopBack is allowed to operate and callback using your specific dialing templates. With these timetables, you can set the dates, times & nodes to lock and to unlock these functions from use. Editing the timetables ------------------------ When editing the timetables, you must first select the timetable that you would like to edit. (If editing a dialing template timetable, you must specify the name of the dialing template) Deleting a record : To delete a record from the timetable, type D to toggle the delete flag. Adding a record : To add a record, type A from the timetable editor. After you enter all the information, the record is saved to the timetable file. Changing the node affected : To change the node affected, type N from the timetable editor and type the node # in which you would like the record to affect. If you select 0 as the node number, the record you are editing will affect all nodes. Changing the date to lock : To change the date to lock, type 1 from the timetable editor and type the new date to lock. If you set the date to lock field equal to 0 then LoopBack will assume that you don't care what date it is and will look at the time field. Changing the time to lock : To change the time to lock, type 2 from the timetable editor and type the new time to lock. If you set the time to lock field equal to 0 and the date to lock field equal to 0 then LoopBack will ignore the record and go on to the next. Changing the date to unlock : This works the same way as the date to lock, but you type 3 to access it. Changing the time to unlock : This works the same way as the time to lock, but you type 4 to access it. The two different timetables you can edit are: Locking timetable : This timetable tells LoopBack what time to not allow users to use LoopBack and what time to "unlock" and allow users to use LoopBack. Dialing template timetable : This allows you to specify a seperate timetable for each of your dialing templates. These timetables tell LoopBack what time to allow callback utilizing the specific dialing tempalte. (Dialing templates are discussed later in the manual.) The filename for the locking timetable is defined in the configuration paths. The filenames for the dialing template timetables are as follows: .TBL = The first 8 characters of the template name. Packing the timetables ------------------------ To pack the timetables, select the Timetable option from LoopBack, then select Pack timetables. You will then need to specify which timetable you want to pack. While LoopUtil is packing the timetables, it will display a percentage bar and percent done on the screen so you will have an idea when the packing procedure will end. ------------------------------------------------------------------------------ Bad number file maintenance via LoopUtil: ----------------------------------------- The bad number file is the file where you specify which numbers that you do NOT want to be called back. You can specify whether or not the number is an international number.. Wildcards can also be specified for each field in the number. (Areacode, Prefix, etc.) (See section on wildcards later in the manual for more information) Exporting the bad number file to a text file ---------------------------------------------- When exporting, LoopUtil will ONLY export number that are not international numbers. All numbers not exported will be placed in the report file so that you can add them manually. You must first type B from the LoopUtil main menu. At the next menu, you need to type X to invoke the Bad Number MODULE in EXPORT mode. LoopUtil will then ask you for the path & filename of the text file to export to. After that, you must enter the path & filename of the file to use for your report file. Then, LoopUtil will begin its exporting process. Importing a text file into the bad number file ------------------------------------------------ When importing, LoopUtil will ONLY import numbers that are of the following format: XXX-XXX-XXXX In other words, LoopUtil will only import American and Canadian phone numbers. You must first type B from the LoopUtil main menu. At the next menu, you need to type I to invoke the Bad Number MODULE in IMPORT mode. LoopUtil will then ask you for the path & filename of the text file to import. After that, you must enter the default node affected that LoopUtil will put in all records that are imported. Then, LoopUtil will begin its importing process. Text file format is as follows: EACH LINE : XXX-XXX-XXXX OR : XXXXXXXXXX OR : (XXX)XXX-XXXX OR : (XXX) XXX-XXXX OR : XXX XXX-XXXX ETC., ETC. LoopUtil will strip out the following characters: ( ) - , It will also strip out spaces... There must be only one number per line! A text file to import may look something like this: 212-777-0225 XXX-555-1212 XXX-XXX-911 XXX-911-XXXX 911-XXX-XXXX Editing the bad number file ----------------------------- Deleting a record : Type D from the bad number editing menu. This will toggle the delete flag. Adding a record : Type A from the bad number editing menu. You will then be asked a series of questions and after you enter all the information then the the record will be saved to disk and you will be returned to the editor. Toggling the International flag : If you wish to toggle the international flag, type I from the editor menu. Changing the node # affected : If you wish to change the node # that this record affects, type O from the editor menu. If you specify 0 as the node # affected, then LoopBack will assume that you want this record to affect ALL nodes. Changing the number : If you have the international flag toggled to yes, then LoopUtil will ask you for the country code, city code, and number. If you have the international flag set to no, then LoopUtil will ask you for the areacode, prefix, and number. Packing the bad number file ----------------------------- To pack the bad number file, select Bad number file maintenance from the LoopUtil main menu.. Then tell LoopUtil that you want to Pack the file. After all this is completed, LoopUtil will remove all records that have the delete flag set to yes. ------------------------------------------------------------------------------ Name & security trash file maintenance via LoopUtil: ---------------------------------------------------- The name trash file will be searched everytime LoopBack is loaded. If the file exists, then LoopBack will not allow a user with a name found in this file to enter LoopBack. The security trash file will be searched everytime LoopBack is loaded. If the file exists, then LoopBack will not allow a user with a security level that is found in this file to enter LoopBack. Exporting the trash files to a text file ------------------------------------------ To one of the trash file databases to a text file, type F at the LoopUtil main menu. At the next menu, type X to invoke the Name & security trash file MODULE in EXPORT mode. Then, you must select which trash file that you would like to export. After that, you must enter the path & filename of the text file to export to. Then, LoopUtil will begin the exportation process. Importing a text file into the trash files -------------------------------------------- To import a text file into one of the trash file databases, type F at the LoopUtil main menu. At the next menu, type I to invoke the Name & security trash file MODULE in IMPORT mode. After that, select which trash file that you would like to import to. LoopUtil will then ask you for the filename of the text file that you would like to import into the trash file. After that, you must enter the node affected for all imported records. (0 will tell LoopUtil that it affects all nodes) Then, LoopUtil will begin the importation process. Text file format for Username importation: Each line must contain the name or name subset that you would like imported to the username trash file. ie. Your text file might look like this: BOB WATSON JOHN DOE SysOp The first two are obvious, but the 3rd entry will deny access to anyone that has the word SysOp anywhere in their name Text file format for Security importation: Each line must contain the security level that you would like imported to the security trash file. ie. Your text file might look like this: 20 50 110 The first entry would deny access to all users with a security level of 20. The second would deny level 50 users, etc. Editing the name trash file ----------------------------- Deleting a record : To delete a record, type D from the name editing menu. This will toggle the delete flag in the record. Adding a record : To add a record, type A from the name editing menu. After entering all the information, the record will be saved to disk. Changing the node affected : To change the node affected, type O from the name editing menu. If you select 0 as the node affected, LoopBack will assume that you would like this record to affect all nodes. Changing the name : To change the name that is being disallowed access from LoopBack, type N from the name editing menu. This field is not case sensitive, because after you enter the information, the field is automatically converted to uppercase. NOTE: The text you enter for the name need not be a name at all.. It can be a subset of a name. The reason for this is that LoopBack tests to see if the text in the name trash file exists within the user's name. ie. Say you have the following name in the Username trash file: JONES A person with the name of Frank Jones would be denied access, as well as someone with the name of Allison Jones. But say you have this in the Username trash file: AL SMITH A person with the the name of Al Smith would be denied access, but someone with the name of Lacy Smith would NOT be denied access. Editing the security trash file --------------------------------- Deleting a record : To delete a record, type D from the editor menu. This will toggle the delete flag in the record. Adding a record : To add a record, type A from the editor menu. After all the information has been edited, the record will be saved to the file. Changing the node affected : To change the node affected, type O from the editor menu. If you select 0 as the node affected, LoopBack will assume that you would like this record to affect all nodes. Changing the security level : To change the security level that will be disallowed access from LoopBack, type S from the editor menu. Packing the trash files ------------------------- To pack the trash files, you must first select "Security & Name trash files" from the LoopUtil menu. Then select Pack. After that, you must select which file you would like to pack. During the packing process, LoopUtil will remove any records that have the delete flag set to yes. ------------------------------------------------------------------------------ Allowed Calling #s listing: ---------------------------- The allowed calling numbers listing is the file where you define which areacodes/country codes & prefixes/city codes that LoopBack is allowed to callback. Editing the Allowed Calling #s listing: ----------------------------------------- (See section on wildcards later in the manual for more information) Wildcard support : LoopUtil boasts the support of wildcards in both the areacode/country code and prefix/city code fields! Here is a brief example of how you would use wildcards in the allowed calling #s file. Say you are in the 812 areacode and the local prefixes in this areacode are 421, 422, 423, and 464. You do not want to allow toll calls. (Long distance calls to numbers in the same areacode) But you also want LoopBack to callback long distance numbers. (It doesn't matter which areacode they are in) You could set your allowed calling #s file up like this: Record #1: Areacode = 812 Prefix = 421 International = No Dialing template = LOCAL Record #2: Areacode = 812 Prefix = 422 International = No Dialing template = LOCAL Record #3: Areacode = 812 Prefix = 423 International = No Dialing template = LOCAL Record #4: Areacode = 812 Prefix = 464 International = No Dialing template = LOCAL Record #5: Areacode = XXX Prefix = XXX International = No Dialing template = LONGDIST Notice record number 5.. It may look strange, but this is the way it works. Say someone types in a number with the areacode 812 and prefix 422. LoopBack will search record 1 and see there is no match. It will then search record 2 and see that there is a match and it will use the LOCAL dialing template. Say someone enter a number with areacode 801 and prefix 261. LoopBack will search the first four records and see that there is not a match. It will then go on to the fifth record and see that the areacode field is a wildcard field. So the 801 areacode is ok. It will then notice that the prefix field is a wildcard field. So it has found a match and it will be using the LONGDIST dialing template. Here's another situtation.. You are in the 812 areacode and the prefixes 421 and 422 are local. All other prefixes are toll calls and require the TOLL dialing template. (Dialing templates will be discussed later in the manual). You do not want to allow long distance callbacks.. Just local and toll callbacks. Your allowed #'s calling file might look like this. Record #1: Areacode = 812 Prefix = 421 International = No Dialing template = LOCAL Record #2: Areacode = 812 Prefix = 422 International = No Dialing template = LOCAL Record #3: Areacode = 812 Prefix = XXX International = No Dialing template = TOLL Notice the 3rd record. You may be thinking, "Well, won't LoopBack consider every prefix a toll call since I have the wildcard XXX specified in the 3rd record?". The answer is no. If a user enters a number with the areacode 812 and the prefix 421, then LoopBack will see a match in the first record and it will look no further. However, if a user enters a number with the areacode 812 and prefix 874, then LoopBack will see the wildcard in record 3 and will look no further. NOTE: If your allowed # calling file contains a LOT of wildcards, then the searching process may be slow. If you have a wildcard that stands for approximately 50 numbers or more, go ahead and leave it in there. If you have a wildcard that stands for less than 50 numbers, it would be better to enter each number individually. This will help to speed up the searches. I realize this may be confusing, so if you are still confused, please call (609) 587-2672 and leave Bob Watson a private message. I will get back to you with a followup message on the same day. Deleting a record : To delete a record, type D from the editor menu. This will toggle the delete flag. Adding a record : To add a record, type A from the editor menu. After entering all the information, your record will be saved. International flag : To flag a record as an international record, type I from the editor menu. This will tell LoopBack & LoopUtil that the areacode is really a countrycode and that the prefix is really a city code. Changing the areacode/country code : To change the areacode field, type C from the editor menu. Changing the prefix/city code : To change the prefix field, type P from the editor menu. Changing the dialing template : To change the name of the dialing template to use, type T from the editor menu. (Dialing templates are discussed later in the manual) Exporting the allowed calling #s file to a text file ------------------------------------------------------ LoopUtil will only export NON-INTERNATIONAL numbers. All international numbers that were not exported will be placed in a report file so that you may enter them manually. To export the allowed calling #s file to a text file, you must first select A from the LoopUtil main menu. Then you must type X at the next menu. After that, LoopUtil will ask you for the path & filename of the file to export to. Then LoopUtil will ask you for the path & filename of the file to use as your report file. After all this is done, LoopUtil will begin to export the records. Importing a text file into the allowed calling #s file -------------------------------------------------------- If you have a list of areacodes and prefixes in a text file that you would like to import into the allowed calling #s file, then this is the option for you. NOTE: LoopUTIL WILL ONLY IMPORT NON-INTERNATIONAL NUMBERS! INTERNATIONAL NUMBERS MUST BE IMPORTED MANUALLY! To import a text file into the allowed calling #s file, you must first select A from the LoopUtil main menu. Then you must type I at the next menu. After that, LoopUtil will ask you for the path and filename of the text file to import. Then, LoopUtil will ask you for the dialing template that it should use for each record that it imports into the database. After all that, LoopBack will begin to read in your text file and import each line as a seperate record in the allowed calling #s database. The text file must be formatted in the following way: EACH LINE : XXX-XXX OR : XXXXXX OR : (XXX)XXX ETC., ETC. LoopUtil will strip out the following characters: ( ) - , as well as spaces. The first three characters must be either XXX (Areacode wildcard) or the areacode. The next three characters must be XXX (Prefix wildcard) or the prefix Your file may look like this: 812-421 812-422 812-423 Indexing the allowed calling #s file -------------------------------------- LoopBack supports the ability to search an index file in order to locate records in the allowed calling #s file. In order for LoopBack to operate properly, you MUST create an index file. To index the allowed calling #s file, type A at the LoopUtil main menu. Then type N at the next menu. After you do this, LoopUtil will begin to index each record in the allowed calling #s file. Packing the allowed calling #s file ------------------------------------- To pack the allowed calling #s file, type A at the LoopUtil main menu. Then type P at the next menu. After you do this, LoopUtil will go through the database and remove any records that have the delete flag set to "Yes". ------------------------------------------------------------------------------ Dialing templates file: ------------------------ The dialing templates file is used by LoopBack to figure out how it should dial the numbers. In the allowed calling #s file, you define which dialing template LoopBack should use for each record. Editing the dialing templates file ------------------------------------ To enter the dialing templates editor, type A from the LoopUtil main menu. Then, type D from the next menu. Deleting a record : To delete a record, type D from the editor menu. This will toggle the delete flag. Adding a record : To add a record, type A from the editor menu. After entering all the information, your record will be saved. Changing the name of the template : To change the name of one of the dialing templates, type N from the editor menu. Then type the new name of the template. Logoff the user after callback : This toggle will tell LoopBack whether or not it should log the user off after calling him/her back with that template. To change the toggle, type L from the editor menu. Security level to upgrade to : This setting will tell LoopBack what value to put in place of the user's security level when he/she is successfully verified with that template. To change this setting, type S from the editor menu. If you set this value equal to 0, LoopBack will not attempt to upgrade the user's security level. Expired security level to upgrade to : This setting will tell LoopBack what value to put in place of the user's expired security level when he/she is successfully verified with that template. To change this setting, type E from the editor menu. If you set this value to 0, LoopBack will not attempt to upgrade the user's expired security level. # of days till expiration : This setting will tell LoopBack the number of days to add to the verification date (The date that the user was called back). The value obtained from the adding of the current date plus this setting will be put in place of the user's expiration date. To change this setting, type # from the editor menu. If you set this value to 0, LoopBack will not attempt to upgrade the user's expiration date. Template to use when dialing : This setting will tell LoopBack the way that it is supposed to dial numbers that use this template. You may either select one of the (R)eady-made templates, or you may (D)esign your own. Here is a list of the (R)eady-made templates: (L)ocal -- Ready-made local dialing template Long (D)istance -- Ready-made long distance dialing template (T)oll -- Ready-made toll call dialing template (L)ocal settings : LoopBack will dial a number with the following settings when using a template setup with the (L)ocal ready-made settings: NUMPREFIX + PREFIX/CITYCODE + NUMBER + NUMSUFFIX Long (D)istance settings : LoopBack will dial a number with the following settings when using a template setup with the Long (D)istance ready-made settings: NUMPREFIX+LDACCESS+COUNTRYCODE/AREACODE+PREFIX/CITYCODE+NUMBER+NUMSUFFIX (T)oll settings : LoopBack will dial a number with the following settings when using a template setup with the (T)oll ready-made settings: NUMPREFIX + LDACCESS + PREFIX/CITYCODE + NUMBER + NUMSUFFIX Should you decide to design your own dialing templates because of a different dialing scheme in your area, then you need to read this section very carefully. There are 6 different fields that LoopBack can use when dialing. Each field can contain any one of 7 different strings. The seven strings are as follows: 0 = None 1 = NUMPREFIX (As setup in config settings) 2 = Long distance access code (As setup in config settings) 3 = AreaCode/Country Code 4 = Prefix/City Code 5 = Number 6 = NUMSUFFIX (As setup in config settings) LoopBack dial with each field in order. For example, if you have the NUMPREFIX set for Field 1, the Prefix/City Code for Field 2, the Number for Field 3, and None for the other 3 fields, LoopBack will dial like this: NUMPREFIX = 9, Number user enters = 812-423-3394 LoopBack will dial : NUMPREFIX + PREFIX/CITYCODE + NUMBER or : 9,4233394 If you have any questions on this, please call (609) 587-2672 and leave a private to Bob Watson. I will get back to you the same day with a followup message. Packing the dialing templates file ------------------------------------ To pack the dialing templates file, you must first type A from the LoopUtil main menu. Then, you must type T from the next menu. After that, LoopBack will begin to pack the dialing templates file by removing any record that has the delete flag set to "Yes". ------------------------------------------------------------------------------ Wildcards: ----------- Wildcards may be used in both the Bad Number file and the Allowed # calling file. In the Bad number file, you may specify a wildcard in any of the three fields. (Areacode/CountryCode, Prefix/CityCode, and Number) If the allowed # calling file, you may specify a wildcard in any of the two fields. (Areacode/CountryCode, Prefix/CityCode, and Number) NOTE: When using wildcards in the Allowed #s Calling file, please keep in mind that the more wildcards you have, the slower the searches will be. So try to have as little as you can. Use of wildcards in Bad Number File ------------------------------------- You may use wildcards in the bad number file to specify an areacode/country code, prefix/city code or number as a bad number. For example. If you wanted to specify all calls to long distance information as a bad number, you would specify the following in the bad number file editor. XXX = Areacode/Country Code 555 = Prefix/City Code 1212 = Number Notice the XXX in the Areacode/Country Code field. This means that if a user enters 801-555-1212 or 212-555-1212 as a number, LoopBack will see it in the Bad number file and act accordingly. But what if we wanted to specify any number with an areacode that begins with 9 as a bad number. You would specify the following in the bad number file editor. 9XX = Areacode/Country Code XXX = Prefix/City Code XXXX = Number Notice the 9XX in the Areacode/Country Code field. This means that if a user enters the number 900-867-9888 or 976-887-6764, then LoopBack will recognize it as a bad number. But if the user enters 800-867-9888, then LoopBack will not recognize it as a bad number. Use of wildcards in the Allowed #s Calling File ------------------------------------------------- You may use wildcards in the bad number file to specify an areacode/country code, or prefix/city code or number as a number that LoopBack is allowed to call back. For example. If you wanted LoopBack to callback the prefixes 421, and 422 in the areacode 812 (These are local prefixes using the LOCAL template), but wanted to specify every other prefix in the areacode 812 as a long distance number (Utilizing the LONGDIST template), then you would set it up something like this: Record #1 812 = AreaCode/Country Code 421 = Prefix/City Code LOCAL = Dialing Template Record #2 812 = AreaCode/Country Code 422 = Prefix/City Code LOCAL = Dialing Template Record #3 812 = AreaCode/Country Code XXX = Prefix/City COde LONGDIST = Dialing Template If a user called and entered the number 812-422-8765, then LoopBack would find that in record #2 and use the LOCAL dialing template. If, however, a user called and entered the number 812-682-8475, then LoopBack would not find a match in either of the first two records, but it would see the wildcard in the third record. That would tell LoopBack that it had a match and it would stop the search and continue along. ------------------------------------------------------------------------------ Call-Back Only Mode: --------------------- The only difference between regular call-back mode and call-back only mode is that when the user is called back he/she does not have to enter verification information, and he/she will not be upgraded upon callback. Also, the "Logoff user after callback" information in the dialing templates will be disregarded. After callback, the user will simply be returned to the main board. You can tell LoopBack to execute in call-back ONLY mode with a simple commandline parameter. Let's assume the command to execute the LOOPBACK.PPE file is CALLBACK. To execute LoopBack in call-back only mode, you could type CALLBACK CBONLY at the main menu. There are many other ways in which you could do this. Here are a couple.. LoopBack will also keep a log of who was called back in call-back only mode, what time & date they were called back, and what number was used to call them back. It keeps all this information in an ASCII text file called LOOPBACK.CAL. This file can be used to keep track of who used the service and bill them accordingly. Seperate command on the main menu ----------------------------------- Run PCBSetup and make the following entries into your CMD.LST file: Command Security PPE/Menu File -------------------------------------------- CALLME 110 C:\PCB\PPE\LOOPBACK\LOOPBACK.PPE CBONLY Note: You can specify any command, security, or path to the PPE files. The command CALLME would initiate LOOPBACK into call-back only mode automatically with only one command from the main menu... Login security file --------------------- Create a file with the name matching the security level that you want to be called back in call-back only mode automatically upon every logon. ie., if you wish to have users with a security level of 50 be automatically called back in call-back only mode whenever they logon, create the filename 50. Enter a line in the login security file to execute LoopBack in call-back only mode. ie., !C:\PCB\PPE\LOOPBACK\LOOPBACK CBONLY ------------------------------------------------------------------------------ Caller-ID Detection: --------------------- If you have caller-id searching enabled, LoopBack will search the caller-id string for the user's home phone # and his/her data phone #. If either of the numbers are found in the caller-id string (As returned by the modem), then LoopBack will simply upgrade them according to the default settings defined in the Configuration Settings. After upgrading them, LoopBack will return to the main board. If neither of the numbers are found in the caller-id string, LoopBack will proceed as normal. (It will allow the user to initiate a callback.) Please see the Configuration Toggles section of this manual to figure out how to turn caller-id searching on and off. Also, if you wish to use the extended caller-id search capability, you can create a file called LBKCID.CFG and LoopBack will do a few more things for caller-id searching. In this file, you can configure a filename that contains caller-id information (if your modem does not return the caller-id information and you have some sort of peripheral hooked up direct to your phone lines), etc. You can edit this file with your favorite text editor. NOTE: You do not have to use this file! If you want to use all the default settings, and read caller-id info from the modem, you don't need this file. However, if you want a more flexible setup, simply create this file with the following format: Line #1: Path & name of file that contains caller-id info. (If using caller-id info provided by modem, simply leave this field blank) Line #2: Security level to place user at if either of his/her phone numbers are found in the caller ID string. (A setting of 0 will disable this option.) Line #3: # of days to add to date of verification to place as user's expiration date if his/her phone numbers are found in the caller-id string. (A setting of 0 will disable this option) Line #4: Value to put in place of user's expiration sec. level if either of his/her phone numbers are found in the caller-id string. Your file might look like this: (BLANK) 80 365 20 This would search for caller-id information from the modem, and if either of the user's phone numbers were found in the caller-id string, it would give the user a security level of 80, an expiration date 365 days from the verification date, and an expired security level of 20. NOTE: Here is a step-by-step list of procedures that LoopBack will do if either of the user's telephone numbers are found in the caller-id string. 1) Notify the user that his/her number was found in the Caller-ID string. 2) Upgrade the user's security level to the value in the "Default Security level if no callback" in config settings. (LBKCID.CFG file can be used to specify a value other than the Default security level) 3) Upgrade the user's expired security level to the value in the "Default Expired Security level if no callback" in config settings. (LBKCID.CFG file can be used to specify a value other than the default expired security level.) 4) Upgrade the user's expiration date to the value in the "Default # days to add to verification date if no callback" in config settings plus the date in which the user entered LoopBack. (LBKCID.CFG file can be used to specify an expiration date other than that configured as the default.) 5) Upgrade the user's time, bytes, and files according to their respective settings. 6) Flag a file for download (if so configured) and start the download process (if so configured). 7) Exit back to PCBoard. ------------------------------------------------------------------------------ Configuring a file to execute before upgrading the user: --------------------------------------------------------- If you have a questionnaire of some sort that you would like to execute prior to upgrading the user, you can do this with LoopBack. See Configuration Toggles and Configuration Settings section in this manual for info on the filename and filetype to execute. A good example of something you could use this for would be to execute a PPE file or batch file to generate a postcard for printout. All you need to do is specify the filename to execute (via Configuration Paths) and the filetype to execute (via Configuration Toggles). Prior to executing any file, LoopBack will save the screen contents. After returning from the external PPE or program, LoopBack will restore the previously saved screen contents. If you have a batch file setup to execute, then LoopBack will write an up-to-date USERS.SYS file and PCBOARD.SYS file prior to shelling out to the external batch file. ------------------------------------------------------------------------------ (L)oopInfo Selection From LoopBack Main Menu: -------------------------------------------- The (L)oopInfo command from the LoopBack main menu provides the SysOp and/or user with a wealth of information. It will display the Executable status. (Date, time, size, and name of the PPE file) It will display the status of certain LoopBack data files. (name of file, # of records, file size, etc.) It will display the registration status. (SysOp's name, registration code, etc.) It will also display a graph of the total # of users on the system that have been verified. When you build your Already Used # database or when you pack your users file, this graph will become inaccurate. When you build your Already Used # database or when you pack your users file, update the Total Number of Callbacks setting in the Statistics file maintenance. For example, if you have 500 users (300 Total Callbacks) and you pack your USERS file (from PCBoard) which packs it down to 475 users, then you must adjust your Total Callbacks setting accordingly. So if 25 users were deleted from the users file, and say 15 of them were verified users, then you must subtract 15 from your Total Callbacks setting. (Thus leaving it at 285 Total Callbacks) If you wish, the (L)oopInfo screen can be disabled via an environment switch. (Please read the section on "Environment Switches", explained earlier in the manual. ------------------------------------------------------------------------------ Display Files: --------------- LoopBack Main Menu ------------------- You may wish to customize the LoopBack main menu file. The filename is LoopWC. It can be graphics, security, and/or language specific. (See your PCBoard manual for more information on graphics, language, and security specific files.) LoopBack Number Menu --------------------- The number menu file is the menu that is displayed when the user is selecting the number that is to be called back. The filename is defined in the configuration paths. (Default filename is LoopNMNU) It can be graphics and/or language specific. LoopBack Searching Display --------------------------- The searching display file is the file that is displayed prior to searching all the database files. The filename is SCDISP. This file can be graphics and/or language specific. LoopBack CallBack Display -------------------------- The callback display is the file that is displayed prior to hanging up on the user and calling him/her back. This screen will remain on the caller's screen until he/she is called back. The filename is LoopCAL. This file can be graphics and/or language specific. ------------------------------------------------------------------------------ Executing the LOOPBACK.PPE file: -------------------------------- There are many ways to execute the LoopBack [PPE] file. Here are a few examples: Login Security File --------------------- Step #1 : Go to your login security files directory (Configured in PCBSetup) Step #2 : Create a file with the filename matching the security level of the users that you want to be automatically sent to LOOPBACK.PPE upon login (Your NEWUSER security level is usually 10) Example. If your NEWUSER security level (user that you want to enter LoopBack) is level 10, then your filename would be: 10 To create this with the DOS editor, type: EDIT 10. at the command line. Step #3 : This is just a display file so you can add some text to tell the caller that he/she is about to enter the LoopBack Call-Back verifier. Step #4 : Put an exclamation mark followed by the path & filename of the LoopBack PPE file flush against the left column of the file after your display text. Example. If LOOPBACK.PPE resides in the directory C:\PCB\PPE\LOOPBACK then this may be what your login security file (10.) would look like. Stuff to display to next caller..... blah blah blah !C:\PCB\PPE\LOOPBACK\LOOPBACK.PPE Step #5 : When all else fails, consult your PCBoard manual and/or call our support BBS at (609) 587-2672 for support. Command From the Main Menu --------------------------- Step #1 : Run PCBSETUP and edit your CMD.LST file to have the following information. Command Security PPE/Menu File -------------------------------------------- CALLBACK 0 C:\PCB\PPE\LOOPBACK\LOOPBACK.PPE ^^^^^^^^ ^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | | This is the path & filename of | | the LoopBack PPE file. | | | Set this to your NEWUSER security level or the | security level you want entering LOOPBACK / This can be any command you like. (This is the command from the main menu that executes LOOPBACK Step #2 : Save your CMD.LST file and that's it. ------------------------------------------------------------------------------ Explanation of terms: ---------------------- Archive - A file (usually a ZIP file) that contains other files and/or other paths within it. Archives are used by bulletin boards to compress data and make file transfers faster. You will need a program, such as PKZip to compress and decompress archives. BOYER-MOORE - The BOYER-MOORE searching algorithm that LoopBack supports is very powerful. You can use the & (LOGICAL AND), | (LOGICAL OR) etc. to search for a specific criteria. Leading zero - A leading zero is a zero in front of a number. An example of leading zeros in phone numbers: 812-423-0043 ^^ These two zeros are leading zeros. PPE - PCBoard Programming Language Executable PPL - PCBoard Programming Language Setting - See Variable Tick - A tick is merely a fraction of a second. 18.2 ticks equals one second. 182 ticks equals 10 seconds. 1080 ticks equals 60 seconds, etc. Toggle - A toggle is a switch, or something you can turn on or off. For example, "Logoff user after verification" is a toggle because you do not give it a value, you just turn it on or off. Toll Call - A toll call is a call to a phone number that has a local area code, but a long distance prefix. Some larger cities require that you dial the areacode along with the number, while other cities do not require this. Variable - A setting which variates or can be changed. For example, the expired security level is a variable because you can change it to different values. ------------------------------------------------------------------------------ Manual updates: ---------------- If you see something missing in this manual that you would like included, or if there is something you are confused about, then contact PCS (Ways to contact are listed in the Registration section of this manual) and state the changes that you would like to see in the next revision. ------------------------------------------------------------------------------