;$HBBS ; Filename: Device : Location: Nodes/NodeX/ ; Purpose: settings for modem ; if this file is missing from a node directory the bbs software will assume ; the node is a sysop local node. ; We hope the modem configuration options are complete enough for all sysops. ; the modem settings are normally a real pain to get right on other bbs systems ; so we have tried to make this VERY configurable. ; if you would like to see a new feature added to this then PLEASE CONTACT US ; IMMEDIATLY and we will do are very best to implement it as soon as we can! ; Note: most of the setting in this config file should work with all 100% hayes ; compatiable modems, but there is bound to be one make of modem that might ; not support the defaults in this file, in anycase, please check these ; settings with the manual for your modem just in case. ; We recommend you use USRobotics/Miracom modems with this bbs software ; as they are extremly good and reliable modems. ;****************************************************************************** ; serial device driver to use for the node, usually just serial.device ; note that this command is case sensitive. DeviceName=NullModem ; we recommened you that you use USRSerial.device for usrobotics modems ; and BaudBandit.device for other modems, these serial drivers are more ; streamlined, efficent and use less CPU time than the standard C= one. SerialDevice=nullmodem.device SerialUnit=6 SerialBaud=38400 ; now, the following option, if enabled, will make the node open a small window ; on it's screen into which you will see all commands sent to the modem and ; all responces received back from it you can also have these saved to a log ; file by enabling the ModemLog option (below) ; (note that clicking the "ModemDebug" button and on a node button from the ; gui will override this setting for as long as the node is active) ModemDebug=OFF ; If enabled all input and output from the modem will be saved in a time and ; datestamped file (see BBS:Nodes/NodeX/NodeLocal file, option ; ModemLogFile= setting) ModemLog=OFF ; number of retries the software will make before resending the TurnEchoOn ; string (below) EchoRetries=4 ; number of retries the software will make AFTER the echo retries (above) before ; the serial device driver is closed and reopened. ReOpenRetries=2 ; time to wait after closing the serial device before reopening it. ReOpenDelay=60 ; 60 per second ; to recap using the 3 defaults above, The node will retry the command 4 times, ; then it will send the TurnEchoOn string to the modem, it will then retry to more ; times and if it still fails it will close the serial device and reopen it ; after 120 milli seconds. ; using the above three settings we can pretty much cope for any strange error ; that might cause a modem to lockup. Obviously if the modem has totally locked ; up and does not respond at all someone will still have to powercycle the modem ; by hand. ; Now comes a really great feature, if the modem does lockup totally (see above) ; the following script will be run. So in theroy you could have a little ; IO device on you parallel port connected to the power of your modem (via a ; relay or something) that could actually turn the modem off and on again!! ; now how's that for failsafe bbs lockup protection!! :-) LockUpScript=HBBS:Scripts/Lockup.scr ; max time to wait before OK or ERROR is received from the modem. MaxCommandWait=120 ; 60 per second... CommandReTrIeS=3 ; delay to wait before sending another command after OK is received. ; normally set this to about 5 or so. DelayBetweenCommands=5 ; 60 per second... ; specifies how long the software should wait before sending another ; character to the modem TildeDelay=30 ; Also note that the Local Echo Should Be Turned ON, unlike most bbs software ; this software checks that the modem is actually receving the commands ; that you want to send to it. ; the following command is send to the modem as soon as the serial device driver ; is opened, note that the bbs software WILL NOT verify that this command ; has been sent as the modem's local echo setting may be off so we cannot ; check for the characters coming back from the serial port until this ; command has been completed, also make sure that the modem is setup so that ; when a command completed it returns either OK or ERROR rather than a numerical ; result code TurnOnEcho_1=AT ; Modem INIT's get sent when the node is started, a user logs off and ; when the node is reset. ; below are the preferred defaults, this bbs software lets the modem answer ; the call itself using its own auto answer method, so make sure auto answer ; is set to ON in the init string. Normal Hayes Compatable modems use the S0 ; register to set auto answer, it's best to make the modem answer after 2 or 3 ; rings, to give those people going through some sort of international gateway ; or operator to put the modem on after they have finished speaking to an operator ModemInit_1=ATZ ModemInit_2=ATS0=3 ; for determining when a connection has been made the following methods are used ; the first is the strict connect method, the connect string received from the ; modem MUST match letter for letter to one of the strings defined in the ; StrictConnect.x= parameters. ; the second method is what we would normally use and that method is as follows. ; when a string is recevied from the modem it is searched for the word ; defined in RelaxedConnect and if that word is found the connection starts StrictConnect=OFF StrictConnectStr_1=CONNECT 9600 StrictConnectStr_2=CONNECT 12000 StrictConnectStr_3=CONNECT 14400 StrictConnectStr_4=CONNECT 16800 RelaxedConnectStr_1=CONNECT ; Command sent to modem to put the modem in command mode while still on-line. ; Note: command is not checked when sent to modem CommandModeString_1=~~~+++~~~ ; string sent to modem to enforce a hang up. HangUpString=AT ; string sent to modem to make it go off-hook. This is sent after a carrier loss ; and when a user is logging off after the CommandModeString has been sent to ; the modem OffHookString=AT DropDTRHangup=TRUE ImmediateAnswer=ATA TurnOnEchoDelay=10 Incoming=RING