PC Online 1996 October

home *** CD-ROM | disk | FTP | other *** search

/ PC Online 1996 October / PCO_10.ISO / filesbbs / cfos2.arj / CFOS.ENG < prev next >

Wrap

Text File | 1996-09-05 | 131.5 KB | 3,054 lines

FFFFFFFF FF an ISDN CAPI FOSSIL driver ccc FF ooooo sssss cc FFFF oo oo ss by Martin Winkler & cc FF oo oo ssss Christoph Lueders ccc FF ooooo ss ssssssssssssssssssssssss from Zaphods BBS, Bonn/FRG --- Documentation --- for cFos and cFos/Pro 0. Distribution Files README Introduction ORDER.DOC How to obtain the professional version (German) ORDER.ENG How to obtain the professional version (English) COPYING.CF License Agreement WHATSNEW Revision history - What has changed ? CFOS.DOC German documentation CFOS.ENG English documentation MODEM.DOC Survey of the modem commands APPEND.DOC 'cFos' ISDN appendage documentation CFOS.FAQ Frequently asked questions about 'cFos' CFOS.EXE 'cFos' executable CFOS.HLP 'cFos' online help file FILE_ID.DIZ File description for mailboxes CFOSCFG.EXE 'cFosCFG' configurationprogram CFOSCFG.HLP 'cFosCFG' helpfile CFOSCFG.HLX 'cFosCFG' helpfile (index) HARDWARE.DAT 'cFosCFG' hardware database SOFTWARE.DAT 'cFosCFG' software database 'cFos' is distributed as a ZIP-Archive including a AV. PKZIP's AV is a kind of seal that will break when files of the archive are deleted, changed or new files are added. The 'cFos' archive is the authors' original version only iff the following message appears after unpacking ┌────────────────────────────────────────────────────────────────────╖ │ This is an original cFos distribution, iff the above lines read: ║ │ ║ │ Authentic files Verified! # MFA364 ║ │ Zaphods BBS ║ │ ║ │ Thanx for using cFos! ║ ╘════════════════════════════════════════════════════════════════════╝ If you see anything else the archive is not the same as released by the authors. If you get a warning like PKUNZIP: (W16) Warning! Authenticity Verification Failed! One or more of these files has most likely been tampered with. be careful, the contends may be corrupted. 'cFos/Pro' (see below for further explanation) may come in different flavours and may not have this AV-seal. So don't be alarmed. Contents: Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1 Features at glance . . . . . . . . . . . . . . . . . . . . . 2 'cFos' Command Line Parameters . . . . . . . . . . . . . . . 3 AT Command Emulator . . . . . . . . . . . . . . . . . . . . . 4 Outgoing calls . . . . . . . . . . . . . . . . . . . . . . . 5 Incoming calls and automatic protocol selection . . . . . . . 6 'cFos' Status Line . . . . . . . . . . . . . . . . . . . . . 7 Safety/Debug features . . . . . . . . . . . . . . . . . . . . 8 Blocksizes and memory requirements . . . . . . . . . . . . . 9 Windowsizes, the ultimate speed . . . . . . . . . . . . . . . 10 'cFos' as a multiport fossil . . . . . . . . . . . . . . . . 11 'cFos' channel bundling (CCB) . . . . . . . . . . . . . . . . 12 'cFos' compatibility with current software . . . . . . . . . 13 ISDN hardware/software . . . . . . . . . . . . . . . . . . . 14 Miscellaneous things . . . . . . . . . . . . . . . . . . . . 15 Adresses, authors, support, availability . . . . . . . . . . 16 Credits . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 End of Documentation, Thanks for using 'cFos' . . . . . . . . 18 Appendix Capi error messages . . . . . . . . . . . . . . . . . . . . . A Format of V.110 user rate (ATS27) . . . . . . . . . . . . . . B B2 frames and windowsizes X.75 . . . . . . . . . . . . . . . C Connect problems with ISDN Blaster (X.75) . . . . . . . . . . D Connect problems with ELINK Modems . . . . . . . . . . . . . E CCB with several S0-busses of different phone numbers . . . . F 'cFos' modem error messages . . . . . . . . . . . . . . . . . G Software compatibility list . . . . . . . . . . . . . . . . . H Availability . . . . . . . . . . . . . . . . . . . . . . . . I 'cFos' and CompuServe with DOSCIM/WINCIM . . . . . . . . . . J 1. Introduction 'cFos' is a FOSSIL driver / BIOS INT 14h Emulator which works on a basis of a modem emulator and a CAPI driver V1.1, Profil A. 'cFos' allows you to make use of a variety of existing software even for ISDN. As ISDN is more than a net for high speed data transfer, our goal is to make most of the features of ISDN accessable by the use of 'cFos'. 'cFos' comes in different flavours: - 'cFos' (without any extension): This is the shareware version of our driver. You may use this version for an evaluation period of up to 90 days, in order to determine whether the program meets your needs before purchasing it. Once the evaluation period ends, you agree to either stop using it, or to purchase the Professional Version of cFos ('cFos/Pro'). - 'cFos/Lite': This version has mainly the same functionality as 'cFos/Shareware' has, but is not time-limited and features the +++-sequence. - 'cFos/Pro': This is the Professional Version of 'cFos'. It has ALL features discussed in this documentation and comes with an interactive configuration utility (CFOSCFG.EXE). Features that are only available in the 'cFos/Pro' version are marked with a '{++}'. Features of the different 'cFos' flavours: | Feature | cFos | cFos/Lite | cFos/Pro | +----------------------------+------+-----------+-----------+ | FOSSIL rev. 5 | yes | yes | yes | | BIOS INT 14h Emulator | yes | yes | yes | | Modem Emulator | yes | yes | yes | | Configuration program | yes | yes | yes/ext. | | +++ Hangup-sequence | | yes | yes | | MultiPort Mode | | | yes | | Time-synchronization | | | yes | | SPV-Support (1.TR.6 only) | | | yes | | "Knocking" (*) | | | yes | | Leased line support (Teles)| | | yes | | cFos Channel Bundling | | | yes | | dyn. cFos Channel Bundling | | | yes | | V.42bis data compression | | | yes | | Memory saving version | | | yes | | NetWare Time-sync. | | | yes | | Charge-Timer/Remaining Time| | | yes | | Charge messages | | | yes | | Charge/Time-limited calls | | | yes | | CPS-O-Meter | | | yes | | Variable CONNECT delay | | | yes | | FOSSIL data dump | | | yes | | Logging (*) | | | yes | | Baudrate evaluation | | | yes | | Hangup by command | | | yes | | EAZ evaluation | | | yes | | CallerId evaluation | | | yes | | Updates | yes | dealer | yes | | Printed documentation | | | yes | | Unlimited usage |90days| yes | yes | +----------------------------+------+-----------+-----------+ * not yet implemented To obtain 'cFos/Pro' read and fill out the order form ORDER.ENG and send it to the address mentioned in the form. To run 'cFos' an 286 AT class computer is at least required. 'cFos' quick installation: In most cases you can simply load 'cFos' by "CFOS i" and use it with the modem string AT&F. 'cFos' comes with the interactive configuration utility CFOSCFG.EXE to ease the installation and to change the PROFILE file from outside 'cFos'. It may also be used for quick configuration. Just get into the Hardware setup and select all those ISDN-hardware you use. On exit, save the profile. After that select the Software setup and tag all software products you plan to use. The CFOSCFG utility will modify the profile in a way that all of them will run well. At the end of the configuration CFOSCFG will ask if it shall generate a report file. CFOSCFG will also create a STARTFOS.BAT and STOPFOS.BAT file for quick startup (and quick unload) of the configured 'cFos'. They will reflect your Hard- and Software setup. You should use ATZ as the modem init string so that the parameters stored in PROFILE get effective. {++} Users of 'cFos/Pro' can also select "extended settings" that allows you to configure 'cFos' Channel Bundling and preset the ISDN protocol, EAZs, charge-/time limited calls, the outdial prefix for telephone equipment and 'cFos' status line easily. For every selection a help text and some hints are displayed. 'cFos' and the different national ISDN networks: The manufacturer of ISDN hardware supplies drivers for his ISDN equipment, including a CAPI driver, Version 1.1, Profil A. Among others these drivers are used to do the ISDN D channel protocol. In Germany the D channel protocol is either 1.TR.6 or DSS1 (EuroISDN). The CAPI V1.1 standard was designed for the 1.TR.6 protocol. Therefore there exist such values as "Additional Service Indicator" and "EAZ", which normally do not occur in other ISDN networks. In addition to the 1.TR.6 drivers manufacturers of ISDN hardware normally offer drivers for other different D channel protocols. These drivers then translate information from the national ISDN network to values of the 1.TR.6 specification. As an example if you use a DSS1 (EuroISDN) D channel driver the "Multiple Subscriber Numbers", MSNs, are mapped to EAZs (the last digit of a phone number). The same is done for LLC, BA values which are translated into values for the Service and Additional Service Indicator and vice versa. 'cFos' can be used in different ISDN networks under the assumption that the manufacturer has realized this translation from/to national D channel information to/from 1.TR.6. In this documentation we therefore talk about "EAZ", "Service Indicator" and "Additional Service Indicator", independant of what is actually transmitted in the respective ISDN network. At this time 'cFos' is used successfully with 1.TR.6 and DSS1 (EuroISDN) in many different countries. The CAPI 2.0 standard overcomes the limitation to 1.TR.6. We will be able to offer a 'cFos' version for CAPI 2.0 soon. 2. Features at a Glance * 'cFos' runs with any card that has an ISDN CAPI V1.1. Profil A (not 'cFos/Lite') * 'cFos'supports FOSSIL spec. Revision 5 (according to FSC-0015) with several extensions. {++} * 'cFos' supports several B-channels simultaneously, for choice with automatic ringdown in MultiPort mode. * 'cFos' runs stand-alone or in co-operation with standard RS-232 FOSSILs. * 'cFos' has a built in BIOS-Emulator so that you can also run programs that only support INT 14h. * 'cFos' is fast. Having windowsizes >= 2 you achieve transfer rates with X.75 of 7900 cps per channel and even more. * 'cFos' has a built in Modem-Emulator. With this you can imitate all modem messages. You can also set/adjust all ISDN specific parameters and save them. By the support of our 'cFos built-in modem emulator' you can make use of all ISDN paramters. * 'cFos' can display a status line that shows you all ISDN connecting parameters plus Modem LEDs for carrier detect, Off Hook, transmitted and received data. {++} The professional version also displays the remaining seconds per charging unit (toll saver) and a CPS-O-METER, which shows the thruput of the last seconds. * Support of almost every B2 and B3 protocol, e.g. X.75 and V.110. {++} * 'cFos' has its own built in CHANNEL BUNLDING! 'cFos' Channel Bundling (CCB) operates independently of your ISDN card. It supports up to 4 B-channels - also with several ISDN boards simultaneously. Besides that you can arbitrarily combine 'cFos' MutliPort Mode with CCB. E.g. you can bundle 2 ports simultaneously with 2 channels each. 'cFos' achieves 15800 CPS with 2 B-channels, 22500 CPS with 3 B-Channels and more than 30000 CPS with 4 channels. {++} * 'cFos' supports SPV's (Germany, 1.TR.6: semipermanent con- nections) * Support of TELES channel bundling (128kbps with 2 B-channels). * Savety, inactivity and connect timers to avoid toll explosion. 'cFos' has a special code to deal with possible malfunctions of the CAPI/ISDN net. {++} * You can evaluate the Time/Date information of the ISDN network and set the local computer time. You can also set the time of a NetWare Server. * 'cFos' can hold its buffers in DOS and XMS UMBs. 3. 'cFos' Command line parameters 'cFos' offers the following commands: i Install Installs 'cFos' as TSR in PC memory. It requires that a CAPI driver is already loaded (warning message if not loaded). All switches have to be set. Later setting will only be possible with specific commands. d Deinstall Deinstalls 'cFos' and frees all memory used by 'cFos'. Please deinstall 'cFos' first, then the CAPI driver. When deinstalling 'cFos' all existing connections run by 'cFos' will be disconnected. r Reregister Re-register 'cFos' with CAPI. Thereby the CAPI driver can be initalized anew. All existing connections will be disconnected and the internal CAPI structures will be initalized. {++} t Tranx Syncronize the computer's clock with the time that is made available by ISDN. For further information see the explanation below. If no -jn is set on the commandline a possible Network server is synchronized as well. {++} bps:<portnb> (bits per second) The Environment Variable BPSRATE is set to the value of the baudrate of the current connection. This can be useful for later evalution in batch files (for example in calling BBS software). You can specify a port number with this command, for example "cfos bps:2", if none is specified, zero is assumed. {++} callerid:<portnb> The environment variable CALLERID is set to the caller ID of the current or last caller on port <portnb>. This may be useful for callback, logging or verification of the caller. {++} eaz:<portnb> The requested EAZ of the last or current call is written to the environment variable EAZ, so it can be checked within e.g. batch files. This may be useful for selecting which application to spawn from a mailer system, e.g. Mailbox or answering machine. reboot The FOSSIL Definition requires a reboot function, which is also available on the command line. Before the computer reboots all open files of DOS applications will be closed, then the following disk caches will be flushed: QCache, Super PC Kwik, PC Tools PC-Cache 5.x & 6.x, Qualitas Qcache 4.00, Norton Utilities NCACHE, SMARTDRV v4.00+ and Hyperdisk 4.50+. After that the computer is booted. init:<portnb> This initializes the COM-Port <portnb> for FOSSIL use. Sometimes (e.g. after a HS/Link session) the COM-port is de-init'ed and some programs may have problems with this, so you can init it manually. hangup:<portnb> Drops the carrier on port <portnb>. statusline:<portnb>:<linenb> Sets the statusline to line nb. <linenb>. Note that the linenumbers start with line 0 as the top line on screen. and the follwoing switches -b maximum B2-Framelength maximum B2-Framelength you can choose with the modem-emulator, default = 2048 bytes -w maximum windowsize Maximum B2-windowsize you can choose in modem-emulator These two functions also reserve the amount of memory necessary for registering at the CAPI. By using ATS22=xxxx and ATS26=x you can certainly set a smaller value for the next connection, but not a bigger one. -c Portnumber (default all ports) 0=COM1, 1=COM2, ... -c can be set several times. The setting of the ports allows the co-operation of 'cFos' with an RS232 FOSSIL on a single computer. 'cFos' checks every INT 14h call, whether it should support this port number. If not, 'cFos' will issue the original INT 14h, so that an underlying driver or the original BIOS code is executed. -e Enable BIOS emulator 0 = off, 'cFos' works as a FOSSIL only 1 = on, 'cFos' works as a FOSSIL as well as BIOS INT 14h. Thereby you can run programs for ISDN that do not use a FOSSIL but BIOS INT 14h 2 = Force on, 'cFos' operates only as a BIOS emulator. Recommendations for programs that use BIOS INT 14h on PS/2 computers or other INT 14h functions. The INT 14h functions 4-21h are de-activated. The FOSSIL signatuer of 'cFos' is overwritten in memory. Note: The INT 14h function 'set baudrate' is used to terminate a call when the BIOS emulator is not turned off, you specified the -jk switch and the port is NOT init'ed for FOSSIL use (ie. no -ji was set on commandline). Besides FOSSIL function 0x06 (raise/lower DTR) and the "+++ATH0<cr>" sequence it is the only non-interactive possibility to hangup. -r rxbufsize, size of the FOSSIL's receiver buffer. Default size is 1024 bytes. Increasing this size is mainly only useful if connecting with machines that send with windowsize 1. -t txbufsize, size of the FOSSIL's transmitter buffer. Default is B2-framelength * (windowsize + 1) bytes. -v CAPI interrupt number, default 0xf1 = 241. {++} -a auxiliary port including controller number (e.g. -a1). The professional 'cFos' version offers you the possibility of activating so called auxiliary ports for 'cFos' channel bundling (CCB), that means data transfer on serveral ISDN B-channels simultaneously. For details see chapter 12. -m Maximum time difference for the TRANX function (see below). If the timediff is more than that, it is ignored. Postfixing a number with a "k" has the effect of multiplying this number by 1024. "-r4k" means for example 4096 bytes receiver buffer. In addition to that all values can be specified in hexadecimal by prefixing them with 0x, for example 0x800 = 2048. Additional -j flags: -j0 Enable Caller-ID repair. If the local area code doesn't start with a '0' append one in front of it (E-DSS1). -j3 disable 386 CPU support. -jb Reboot on an emergency_stop() condition. This is a severe error condition and normally 'cFos' only loggs out all active connections, but setting this option will increase safety. -jc enable carrier detect LED. The Scroll-Lock LED is used as a carrier detect LED. During a connection the LED in on. As long as an incoming call is neither accepted nor rejected the LED flashes. Warning for programs using the Scroll-Lock LED for different purposes (for example the FrontDoor terminal). They will react to the activity of the Scroll-Lock LED. You may specify -jc1 to use the NumLock of -jc2 to use the CapsLock LED. {++} -jd Data dump. When this flag is set 'cFos' logs all received and transmitted data into a file called FOSSDUMP. FOSSDUMP is located in the same directory as CFOS.EXE. Teh data dump can only be stopped by de-installing the the FOSSIL driver. The data dump function requires 10k Bytes additional memory. This Option is not included in the No-Debug Version of 'cFos'. -je Disable environment deallocation. This switch may help in case of a system crash or a severe DOS error immediately after loading 'cFos'. -jf Ignore flush_output() FOSSIL function calls. This may be useful e.g. for QuickBBS, which sometimes sends a flush_output() after each character sent. -jg Disable all XMS functioncalls. -jh Ignore the high byte of DX in FOSSIL function calls that use DX for the portnumber. Some programs (e.g. D'Bridge) trash the upper part of DX. Use this switch if your program works without a -c switch, but not if you specify one. -ji Loads 'cFos' with initalized COM ports. This is for software which neglects to initialize COM ports before use. This initializes the ports for FOSSIL use. So some BIOS functions won't run (e.g. the +++-hangup-sequence), because 'cFos' thinks you're using the FOSSIL interface. So only use this parameter with FOSSIL applications. -jk Enable Set_Baudrate() carrier drop. If 'cFos' is using the BIOS emulator, the carrier is high, the COM-port is not used via FOSSIL (i.e. not FOSSIL init'ed) and this switch has been set, the current connection will be disconnected. -jm Disable alternate monitor support. Only possible in the debug version. {++} -jn Disable NetWare Support. If this switch is set 'cFos' does not attempt to find or to support NetWare. -jo Disable far CALLs and use "real INTs" instead to call CAPI. This is only useful in Protected mode environments that catch interrupts. OS/2 is deteced automatically. -jp Activates passive layer B3 setup in order to fulfill the specific requirements of ISDN Blaster FOSSIL PCIF V5.78. (Recommendation for AVM only - not for Teles). It might not be neccessary any more if the remote site uses PCIF V5.81 or higher. -jr Disable CAPI re-register function (neccessary for SOLIS boards). If your CAPI crashes after some calls, try this switch (but only use it, if it helps). {++} -js Ignore seconds in ISDN date/time info. For further informa- tion see Tranx. -ju Do not use UMB memory. Otherwise 'cFos' tries to allocate UMB memory first before using conventional memory. -jv Disable V.110. By setting -jv 'cFos' knows that the respec- tive CAPI does not support V.110 and upon the ATB1 and ATB2 commands 'cFos' issues the "ERROR" message. Also incoming calls which indicate V.110 by the additional service indicator are rejected. The purpose of this feature is to save the caller phone charges. For further information see chapter 6. -jx pretend to be the X00 FOSSIL. This switch forces to return the same values in CX and DX after having executed function 0x1b as X00 does. This is required for older versions of XBTX. -jy By default, 'cFos' ignores any modem input if DTR is low. This is for enhanced modem compatibility. If you have problems with some software that does not rise DTR, load 'cFos' with -jy. Note that this may cause problems when dropping the carrier. -d[d] debugging trace: If this switch is set at load time 'cFos' will log all CAPI messages into a trace file, called CTRACE located in the same directory as CFOS.EXE. This requires 10k bytes of buffer space in addition. That file can easily consume large quantities of disk space. Therefore this function should only be used in rare cases. -d turns on the logging function. -dd results in a hex dump of CAPI messages. In case 'cFos' does not properly run on your computer or does not accept incoming calls, etc... you can send us a CTRACE of your problem. You should load 'cFos' with CFOS i -dd and you should in any case deinstall 'cFos' with CFOS d before you pack or mail the CTRACE file. The debug trace functionality is not included in the No-Debug version of 'cFos'. {++} Tranx: The ISDN network provides the actual time/date to the calling party during connection setup and clearence. 'cFos' compares the ISDN time with the clock of the computer and calculates the difference. 'cFos' does not change the clock of the computer immediately, only on request: By calling 'cFos t' the computer's clock will be corrected by the average difference calculated before. This can also be accomplished by the modem command AT&T. This way of setting the time is much saver than setting up a connection. If you constantly want to set the time place AT&T into the modem init string. Note: In some areas the ISDN network provides the time without seconds. 'cFos' is designed in a way that it automatically approximates the correct time within several connections. This mode can be enforced (-js switch). If so the seconds are ignored, even if they are provided. This can be useful when using local telephone equipment which simulates the seconds. You may set the maximum minutes the ISDN time may be off from your systems time with the -m switch. So, setting -m90 (default) will only accept and set your systems (and networks) time, if the difference between actual and isdn time is less or equal 90 minutes. {++} If a NetWare server is detected, its time will be set unless -jn switch is set. The user has to be a file server console operator, however. 4. AT command emulator: As this driver is designed to enable the user to use existing modem software with ISDN, 'cFos' emulates a modem that uses commands such as ATD for dialing and AT&V to display the configuration. The entire control of the CAPI driver and the behaviour of 'cFos' is operated by the modem emulator. The emulator offers help which can be displayed with the AT? command. You can find a complete list of all modem commands and registers in MODEM.DOC. There is a listing of the numerical result codes as well (we designed them as like the USR HST modem gives them back (codes 0 to 11) and extended them for ISDN requirements). The receiver buffer has to be big enough to store the respective output of the modem emulator. For example the buffer should have the size of 2k bytes to store a complete AT? screen. If the receiver buffer is too small (caused by -rxxx switch) then the error message "rx-buffer too small, output lost" will be displayed. It is sometimes difficult to relate a recent and much more complex technology as ISDN to the terminology of a standard analogous modem. Therefore a brief explanation what the modem messages mean: - NO ANSWER The call came through but the called party does not answer the phone. CAPI cause: 0x34ba: No user responding - NO DIALTONE 'cFos' could not come through the ISDN network. CAPI causes: 0x3301: D channel layer 1 setup error 0x3302: D channel layer 2 setup error 0x3305: D channel layer 1 shutdown 0x3307: D channel layer 3 shutdown 0x348a: No channel available 0x34a0: Outgoing calls barred 0x34a3: Nonexistent CUG 0x34d9: Network congestion 0x34f0: Local procedure error - BUSY The call reached the destination but it could not answer or rejected the call. CAPI causes: 0x34a1: User access busy 0x34bb: User busy 0x34bd: Incoming calls barred 0x34be: Call rejected - NO CARRIER All other causes result in a NO CARRIER message from the modem emulator. If you think that a certain cause belongs to the messages above please mail us. 0x3483: This network error is issued if you try to call a party with a non supported service, e.g. an analogous phone. We could issue a VOICE message, but this is not yet implemented. 0x34b5: Destination not obtainable; you placed a call with an invalid number or an invalid service. This may be due to bad connection parameters. See CFOS.FAQ. 0x34f1: Remote procedure error; the calling party provided unsupported parameters, such as an invalid Additional Servive Indicator. In addition to that the modem emulator is capable of serveral other commands. For an explanation please refer to the AT command chart in MODEM.DOC. Apart from that here a detailed explanation of the ATIn commands. They are used to display information about the last connection. - ATI0 product info - ATI1 status line (see chapter 7) - ATI2 link information: "Last inbound call": contains caller id, requested service indicator and additional service indicator of the last caller as well as his EAZ. "Last outbound call": contains the charges of the last outbound call. "Last disconnect": contains the reason and the CAPI cause for the last disconnect. The reason can assume the following values: Active: the application requested 'cFos' to terminate the connection. Passive: The remote end or the CAPI driver disconnected. Disconnect B3 timeout: The respective safety timer has been timed out. Disconnect D timeout: The respective safety timer has been timed out. CAPI reset: All timers timed out and 'cFos' re-registered at the CAPI driver. This is an emergency stop condition. Connect timeout: the time needed to establish a connection exceeded the value specified in register S7. Inactivity timeout: There was no data to be transmitted/received longer than the time specified in register S19. Appendage reset: The connection was terminated due to a reset function of the 'cFos' ISDN appendage. - ATI4: Message dump: Dump of the last 10 CAPI messages containing w-elements (1.TR.6), except charging info and time/date info. As an example this can be used to display the last caller-IDs of users who called during the last connection. Profile saving: In an ordinary modem all settings can be written into a battery buffered RAM by the AT&W command. Since 'cFos' has no such RAM the settings are stored on disk in a file called PROFILE. With DOS 3.1+ this file is located in the directory of CFOS.EXE, otherwise in the directory, which was default when 'cFos' was loaded. The file contains all modem profiles, stored by an AT&Wn command (n=0..9). The respective ATZn commands restore and activate a profile. If no number is given the AT&W and ATZ commands operate on profile 0. The profile 0 is loaded at 'cFos' startup and therefore contains 'power on' defaults. You should save a simple and working configuration to profile 0. As DOS sometimes does not allow reading and writing of files 'cFos' checks DOS's critical error flag to determine if read/write operations are allowed. If you try to read/write a profile at a time these file operations are not allowed, 'cFos' returns ERROR. ERROR is also returned if the file PROFILE is not valid (e.g. if it was created by a quite old version of 'cFos'). If 'cFos' cannot find a PROFILE, an ATZ command is equivalent to an AT&F command and is answered by OK. Note: If 'cFos' is used for multiple ports, all ports can be easily used with the same profile (for example by using ATZ on all ports). To avoid that you can use different profile numbers for different ports (ATZ0..ATZ9). In MultiPort Mode the registers S41 info-mask low S42 info-mask high are "mirrored". That means a change of one of these registers for one port automatically changes the value of the profile for all other ports. 5. Placing outbound calls: Besides the phone number ISDN enables you to set up a variety of parameters, such as the kind of service and transmission protocols. For 'cFos' the default service is 'data transmission' using X.75 as B2 protocol and transparent (that means non-existent) B3 protocol. All neccessary parameters for the different protocols, the respective CAPI supports, can be set by the registers S16-S18, S20-S36, S39 and S40. To ease the choice of the most important transmission protocols you can use simple AT commands to select the following protocols: ATB0 Data transmission using X.75 and transparent B3 protocol. In contrast to the CAPI default, the X.75 window- and frame-size are set to the values specified when 'cFos' was loaded (by switches -b and -w). An Additional Service Indicator of 0 is used for outgoing calls. ATB1 Data transmission using V.110 with 38400,8,n,1, ansynchronous and transparent B2/B3 protocol. An Additional Service Indicator of 64 (40 hex) is used. ATB2 Data transmission using V.110 with 19200,8,n,1, ansynchronous and transparent B2/B3 protocol. An Additional Service Indicator of 199 (C7 hex) is used. ATB3 Like ATB0, but with channel bundling (128k bps). Only TELES's channel bundling is currently supported. This is only possible if BUNDLE.EXE is loaded by STARTS0. Note that TELES's channel bundling is not compatible with 'cFos' Channel Bundling (CCB), which is actived by AT&Bn (explained below). ATB4 Elink compatiblity mode, data transmission using X.75 and transparent B3 protocol. In contrast to the CAPI default, an X.75 windowsize of 7 and a framesize of 256 bytes is used. This mode is only available if 'cFos' was loaded at least with -b256. Otherwise ATB4 results in an ERROR. An Additional Service Indicator of 146 is used. ATB5 German BTX mode; BTX uses a variant of X.75 with Windowsize 7, so 'cFos' should be loaded with -w7. {++} ATB6 Like ATB5, but sends VT-100 sequence right after the connection has been established, so you may use BTX with VT-100. {++} ATB7 Analogue modem support, if you ISDN-board features that. We recommend that you use these commands for placing calls. However you can also set the individual registers manually for special applications. For example some called parties do not accept calls if the Additional Service Indicator is not 0 (e.g. CompuServe). In addition here are some settings for special calls, e.g. with TELIX-Int14 or Terminate: for CompuServe und Datex-P Gateways V110, 9600,async,7,E,1 ATB0S20=8S27=237 but for DOSCIM or WINCIM ATB0S20=8S27=197S10.4=1 V110, 9600,async,8,N,1 6. Handling incoming calls / protocol selection: First you have to tell the CAPI driver which ISDN services and EAZs it should listen to. This is done by setting the "Serviced SI Mask" and the "EAZ Mask". The services are specified by setting register S14. For example the service "data transmission" is selected by setting bit 7 = 1. Bit 1 = 1 and Bit 2 = 1 enables incoming calls with service "telephony/voice calls" or "a/b/ services". You may set these bits with the AT&I command as well. 'A' stands for analog, 'D' for data. The active EAZs are specified by setting the appropriate bits of register S13 or by the AT&Lxxxx command. AT&L* activates all EAZs. AT&123 activates EAZs 1, 2 and 3. 'cFos' currently supports the services "data transmission" and "telephony". If other services are activated, 'cFos' uses the protocols and parameters given by registers S20-S36 to answer a call. On incoming calls with service "telephony" 'cFos' uses the B2 protocol 'bittransparent' and the b3 protocol 'transparent'. This results in a constant data stream of 8000 cps of digitized analog-samples to the application. However the service activated by default is "data transmission" only. Due to the design of CAPI it is not possible to select a protocol on the basis of a negotiation between both parties. Thus 'cFos' selects the protocols for incoming calls with the service "data transmission" according to the "Additional Service Indicator". A later change of the protocol is not possible, since there is no way the CAPI driver can indicate the protocols available to the remote party nor its parameters. The B3 protocol is always chosen due to registers S21 and S30-36. We recommend to use 'transparent', since the CAPI default of 1 (= T70 NL) is very rarely used by any system, but is required for the german BTX. The B2 protocol is selected according to the "Additional Service Indicator" regarding 1.TR.6. For V.110, 38400 bps, asynch. no value for additional service indicator is specified by 1.TR.6. However callers can activate this protocol by using a value of 64 or 128. Specification for the Additional Service Indicator : 0000 0000 caller requests X.75, 64000 bps 1000 0000 caller requests V.110, 38400,8,n,1,asynch. 01-- -000 caller requests V.110, 38400, asynch. 1010 ---- caller requests V.110, X.30 (ECMA 102), synch. 1011 ---- caller requests V.120, synch. 11-- ---- caller requests V.110, X.30 (ECMA 102), asynch. the most important : 1100 0111 caller requests V.110, 19200,8,n,1,asynch. 0100 0000 caller requests V.110, 38400,8,n,1,asynch. Whether these protocols are supported by the respective CAPI driver depends on the manufacturer of the CAPI driver. For V.110 'cFos' uses "V.110 with transparent B2-protocol" (8). Callers who do not support this specification or use telephone equipment, which filters the Additional Service Indicator, might activate another protocol for the called 'cFos' than expected. To overcome the trouble with the protocol selection, we implemented a few "specials" in 'cFos': If the additional service indicator is unknown, 'cFos' uses register S43 to select the protocol. The high byte specifies the protocol and the low byte the V.110 user rate, if applicable. Default for S43 is V.110, 38400,8,n,1,asynch., because this mode seems to cause often most of the trouble. In addition each individual EAZ can be fixed to a certain protocol, used if the additional service indicator equals 0. This is done by registers S50-S59 for EAZ 0 to EAZ 9. If the low byte of the respective register is nonzero the feature is activated for this EAZ and the value is used as a V.110 user rate. The high byte then specifies the protocol selected. However an additional service indicator of nonzero activates the above protocol selection according to 1.TR.6. By default this feature is disabled. Example: Let S51 = 0x0 and S52 = 0x0840 and S53 = 0x08C7 and the Serviced EAZ Mask = 14 (you thus listen to EAZ 1-3); then the following protocols are selected: EAZ AddSi = 0 AddSi <> 0 1 X.75 according to 1.TR.6 2 V.110,38400 according to 1.TR.6 3 V.110,19200 according to 1.TR.6 Thus: Callers, requesting X.75, can call EAZ 1. Callers, using 1.TR.6 conform hardware/software, reques- ting V.110 can call all EAZs. Callers using hardware/software nonconform to 1.TR.6 can call EAZ 2 for V.110, 38400 and EAZ 3 for V.110, 19200. See Appendix B for an exact specification of the Additional Service Indicator. 7. Status Line: For the purpose of a look and feel of a modem or for debugging purposes, 'cFos' can display a status line on the screen. AT&D0 status line off AT&D1 status line on, when the COM port is initialized AT&D2 status line on, when a connection is active ATS11=xx display row of the status line (0 = top of screen) Its layout is as follows: # of frames not fully received | | # of frames 'cFos' is sending | | {++} | | remaining sec's of current charging unit | | | {++} | | CPS-O-METER of last 8 sec's | | | | | cFos> C-B3 ACOD 0R:64 0T:1024 C:12 7680 V110 19200 9111041 39 | | |||| | | | | | | connect/ | |||| | | Charging | | Caller ID/ disconnect | |||| | | Units | | dialed number indicator | |||| | | | | (*) | |||| | | | bps rate bei V110 level |||| | | B2 protocol (e.g. X75) |||| | last transmitted block length, TX-"LED" |||| last received block length, with RX-"LED" Auto-Ans||| ||DTR-"LED" Carrier Detect| Offhook-"LED", on = reject calls (different to a modem) (*) during an active connection the number of active B channels used is displayed here ("B3-1") {++} with 'cFos' Channel Bundling (CCB) "B3-2" can appear for example. 8. Safety/Debug features: Starting out with ISDN it might appear unusual to you that you don't always know if you still hold the connection or hopefully hung up. 'cFos' can prevent a charge explosion in several ways: 1. 'cFos' modem emulator has an inactivity timer which can be activated by setting register S19 to the time in minutes which may pass without transmission or reception of data before 'cFos' disconnects. 2. In the process of disconnecting watchdog timers are started. For example 'cFos' waits 5 sec. for the respective DISCONNECT_B3_INDs and DISCONNECT_INDs before it re-tries the disconnect request. It tries first to disconnect the B3 level twice, then the D channel twice and as a last attempt to disconnect, it re-registers with CAPI. Then all connections should be terminated. 3. In the connection phase 'cFos' uses a timer to wait for a "carrier". If the connection cannot be established within the time specified by register S7 it will be disconnected. This avoids a "hang" while connecting the B3 layer. 4. In the debug version 'cFos' supports an alternate screen. You can monitor the flow of messages to/from CAPI and other debug information on this screen. 9. Blocksizes and Memory Requirements: This FOSSIL driver offers a confusing variety of blocks and buffers. Therefore we try explain all of them. B2-Framelength: X.75 sends data on layer 2 in frames. These frames (= packages) are limited to a maximum length. That is what we call B2-Framelength. The CAPI specifactions limit the B2-framelength to a maximum of 2048 bytes. Receiving bigger lengths may cause loss of data and disconnection. Therefore ISDN boards that send bigger B2 framelengths are incomatible with CAPI applications !!! B3-Framelength: Data are sent in frames on layer 3 as well. If layer 3 is transparent (it has no protocol) B3 frames have the same size as B2 frames. But if a protocol is in use on level 3 , for example T70.NL (CAPI default but not 'cFos' default) then this protocol requires several bytes overhead. The B2 layer considers these bytes as raw data and therefore they are stored in a corresponding buffer. B3-Framelength is also the maximum amount of bytes a DATA_B3-IND can signal on reception. B2-Windowsize: B2-windowsize is the maximum amount of B2 data blocks that the CAPI can send without the necessity to confirm the reception of data by the counterpart. To enable a full-streamed data transfer (data blocks will be continously sent without the delay of waiting for confirmation of data receive) B2 windowsize should at least be set on 2 unless the counterpart is not able to choose at least the same value (if it is not possible you may overrun your counterpart). Buffer for API_REGISTER: CAPI requires at least a buffer for incoming B3 datablocks. This buffer has to be able to accept at least one B2 data block including the B3 overhead. If B2 is set to X.75 and B3 is to T.70.NL and a requested maximum B3 framelength of 128, CAPI requires a B2 framelength of 130 bytes, thus 130 bytes per block are necessary for this buffer. A buffer must be made available to CAPI to store the maximum B3 frames, which in turn depends of the B2 windowsize and the number of simultaneous connections. CAPI also requires memory for its message queues. Our example leads to the following memory requirements used for API_REGISTER (we assume that 10 messages can be queued) : (10 * 180) + (# of B3 connections * B2-windowsizes * 130) Buffer for FOSSIL Functions: A FOSSIL also requires memory for its ringbuffers. The receiver buffer should at least have the size of the B3 framelength. Otherwise 'cFos' can not fully accept the received data block from CAPI. The data block will then be splitted into several parts. These parts are written into the FOSSIL receiver buffer. This procedure may cause slight delays of the handling of the received data. 'cFos' can also queue up to 8 messages received from CAPI and copy them into the receiver buffer, if the receiver buffer provides enough memory. This is more than the maximum B2- windowsize by CAPI standards. But it requires that CAPI has sufficient receiver memory. While sending 'cFos' tries to send data immediately and in biggest blocks possible (and also as many as possible :-) only limited by the maximum B2-windowsize). The way CAPI transmits data imposes that data located near the limits of the FOSSIL transmitter buffer can not always be grouped to blocks of a maximum B3 framelength. The size of the transmitter buffers should be around B2-Framelength * (windowsize + 1) to avoid the effect described above. {++} Using Channel Bundling the size/value should be multiplied as well by the amount of B channels. 10. Windowsize, the ultimate speed You can try to increase the speed by using B3 datablocks as big as possible. This method might not be succesful, due to the way data is transmitted using X.75. As it was explained above B2-windowsize is the amount of frames that are allowed to be on transmission without the necessity of confirming them. For example: If windowsize is 3, three blocks can be sent one by one (without any delay) without waiting for the receiver's confirmation. Therefore 'cFos' has to wait for a confirmation for each block if windowsize is 1 before it can send a new one. The confirmation can not be signaled before the application of the ISDN board of the counterpart has accepted the block. (*) (This is very useful because it enables a way of flow-control between the counterparts. ISDN does not offer a RTS/CTS handshake :-)). With a windowsize of 1 the result is that only one block is on the way and ISDN transfer gains exactly the same time behaviour as X-Modem has. This is stone age telecommunication !!! But if windowsize is 2 'cFos' can already send a second block while the first one is on the way. The counterpart can confirm the acceptance of the first block while accepting the second one. By this way data blocks can be continuously sent without any delays. Therefore you actually gain quite some speed. Our tests achieved more than 7900 cps (theoretical maximum of 8000 cps) using an average blocksize of 2048 bytes. We used Z-Modem for mailer protocol. We increased the windowsize to 3 without any improvements. Our Recommendation: Even though 'cFos' transfer routines are designed for high speed we do not care much about the CPS war. By a closer look the actual transfer time is what really matters. That is what costs your money. Transfering a 2 MB file with 7500 cps instead of 7900 cps makes a difference of 15 seconds. In the worst possible case it costs 1 charging unit for a domestic call. Another important factor concerning transfer rates is the protocol overhead (you should not overestimate it - more crucial is the timing discribed above). To minimize the overhead we recommend B3 protocol = 4, that means transparent. Therefore the overhead will be 0. To minimize the B2 protocol overhead as well we recommend a B2 framelength of 2048 bytes. All ISDN boards should be able to handle this framelength while receiving; at least because of the reason to be compatible to CAPI. Setting ISDN boards to bigger framelengths leads to imcompatibility to other cards. ISDN-Blaster unfortunately sends 16k byte frames by default. That's the reason why there is no transfer possible with this card without changes. But there is a simple trick: As an owner of a Blaster just set an ATS75=0x800 in the init-string and Blaster will send a maximum of 2k byte frames. Anyone who cannot accomplish a connect with an ISDN-Blaster should try V.110. He should then write to the owner to set his B2 framelength on sensible values via ATS75=0x800, otherwise he is only compatible to other ISDN Blaster boards - but incom- patible to the rest of the world. If CRC errors often occur while sending the reason for this might be that the counterpart receives with a windowsize of only 1. In this case you can also decrease the windowsize to 1 with 'cFos' by ATS26 = 1. But most boards can handle a windowsize of 2 or more. Therefore we recommend a windowsize of 2. Stonage Telecommuni- cation hopefully does not reconquer FidoNet. For the present time ISDN does anything else but working properly with FidoNet. One reason is that a mutual ISDN B2 and B3 protocol standard has not been agreed upon yet. When two boards with different protocol parameters connect sooner or later transfer problems and aborted connections occur. Sooner or later an agreement is necessary what the ISDN flags in the nodelist should exactly mean. Here is our proposal (and 'cFos' default setup) B2-Protokoll : X.75 (of course :-) ) B2-Framelength : 2048 (see explanation above) Link-Address A : 3 (CAPI default) Link-Address B : 1 (CAPI default) Modulo Mode : 8 (CAPI default) Windowsize : 2 (see explanation above) higher values consume too much memory at 2048 framesize B3-Protokoll : transparent, this means none. We think that this might be the best chance for a good transfer. (*) With active ISDN boards the confirmation can be signaled sooner. {++}11. 'cFos' as a Multiport FOSSIL: Theoretically 'cFos' can support up to 255 different ports. We would like see a computer with such a performance and the adequate ISDN equipment (8 S2M-Busses :-). This 'cFos'-Version is compiled for up to 4 COM ports. Buffer memory and data storage memory will be reserved for each COM port when installing. On installation you can select -c0 and -c1 to support COM1 and COM2, for example. There are then 2 modem emulators accordingly. At the same time you can either call two different systems or you can be called by one or two systems and/or answer a ring on the other port. But this feature requires either software that can operate multiple ports, or a multitasker. In multiport mode you can specify the EAZs and services 'cFos' should listen to for each port separately. If EAZs or services overlap there will be an automatic ringdown from the first port specified by the -c parameter to the next ports specified. {++}12. 'cFos' Channel Bundling (CCB): Static Channel Bundling: 'cFos' channel bundling was designed to operate independantly of any respective CAPI producer/manufacturer. Every 'cFos' user can do channel bundling with every other user of 'cFos', even though they use different ISDN hardware. 'cFos' channel bundling is not a protocol, it is an operation mode. You can either bundle with X.75 or with any other packet oriented protocol. CCB requires that the ISDN equipment can operate several B channels simultaneously with the service "data transmission". Following cards fulfil the requirement: TELES, AVM (but not the old A1 board, ELSA (starting with CAPI 1.43). Stollmann boards TINA DS and TINA D (with the exeption of TINA DD) are not fit for CCB because one of the two B channels is used for the A/B Adapter on a hardware basis. A further requirement is that 'cFos' is loaded for several ports. That is the case for example when it is loaded in multiport mode, that means when several ports are activated by using the parameter -c. If 'cFos'is supposed to support only one COM port -aX can activate so called auxiliary ports. 'cFos' uses these ports internally, but they cannot be accessed from outside for example by INT 14h calls. Parameter X indicates on which controller (ISDN board) the according B channel ought to run. 'cFos' is able to carry out channel bundling on several ISDN boards simultaneously provided that CAPI supports this. Examples: cfos i -c0 -c1 'cFos' is loaded in multiport mode. 'cFos' supports the ports COM1 and COM2. CCB is possible with 2 channels. cfos i -c2 -a0 'cFos' only supports COM3. CCB is still possible with 2 channels by using a second (auxiliary) channel on the ISDN board 0. This will be most often the case. cfos i -c0 -c2 -a1 'cFos' supports COM1 and COM3. CCB is possible with 2 or 3 channels. If you want to bundle with only 2 channels 'cFos' uses the "main port" (COM1 or COM3) and the auxiliary port. Only in case that 3 channels ought to be bundled the second main port is needed provided it is not used at the time the connection is established. Unfortunately things have became a little complicated but this enables that channel bundling and multiport mode do not exclude each other. Any combination of both of them is possible. Basically 'cFos' prefers to select auxiliary ports rather than main ports. Only in case all auxiliary ports are busy 'cFos' uses additional main ports for channel bundling. If 'cFos' uses an additional main port for channel bundling the modem emulater will always send the message 'OK' on all modem commands. This could be the case with 2 mailer tasks run under DesQView. No modem command will be executed but the mailer still knows that its "modem" is still there. The establishing of a connection for outgoing or incoming calls while doing channel bundling, especially the choice of transfer protocols, does not differ from the establishing of only one channel. Auxiliary ports share the same profile as the corresponding main channel with the exeption of the controller bytes (register S40). This will be determined by the value of the -a parameter. The modem command AT&Bn determines how many channels should be used for CCB. The ATD <nummer> command builds up the channels. If you try to use more channels than made available at 'cFos' load time 'cFos' responds with the message 'ERROR'. If there are enough channels but some are in use for other purposes 'cFos' will execute CCB with the channels that are available. The same procedure applies to incoming calls. When calls are coming in 'cFos' checks whether there is a connect for the respective caller id and EAZ/SI/AddSI, and, if possible, switches to bundle mode. If you call 'cFos' with the same caller ID/EAZ simultaneously and twice 'cFos' will asume CCB. Therefore 'cFos' requires that the caller transfers his Caller ID. If you'd like to test now, here is a quicky: cfos i -a0 ; load cfos with defaults for ; COM1 + 1 Aux.Port start you terminal software for COM1 AT &F &B2 D +49-228-9111041 ; call Zaphods BBS ^ Insert your int'l prefix here There is no specific CONNECT string for channel bundling because 'cFos' does not have any information about the amount of the bundled channels at the moment it issues the connect message. CCB is possible with up to 4 channels. On customers request we can compile special versions with more than 4 channels. CCB is also possible with several S0 busses of different telephone numbers. As this feature might be of any interest only for a few users see for further informatin appendix F. Dynamic Channel Bundling: With 'cFos' dynamic channel bundling it is possible to connect or disconnect B-channels with respect the the current thoughput. If the throughput is below a certain limit you can save the additional costs of a further B-channels not necessary then. Otherwise, if you call with only one B-channel another channel will be automatically connected if the thoughput reaches a certain limit. In oder to use the current charging unit optimally channels are disconnected a few seconds before it ends. As with static channel bundling the maximum number of channels to use is selected by the AT&Bn modem command. Static channel bundling is selected by AT&M0 (which is the default), while dynamic channel bundling is selected by AT&M1. In dynamic mode 'cFos' connects one B-channel only on an ATD... command and estabishes further channels during the connection. The following modem S registers allow you to control the behaviour of the dynamic channel bundling for maximum throughput with minimal phone costs: S64 = Lower limit in cps per channel. If the throughput of a connection falls below this limit a channel will be disconnected with the end of the current charging unit. S65 = Upper limit in cps per channel. If the throughput of a connection exceeds this limit a further channel will be connected. We recommend a difference of at least 1000 cps in the values of both registers. 'cFos' has a 'CPS-O-METER' in its status line, so that you can monitor the throughput of the last 8 seconds. The following modem registers are provided for further fine tuning purposes: S67 = Pre-off time in seconds. A channel is only disconnected, when the remaining seconds of the current charging unit of this channel are less than the seconds in this register. The default value of 5 for example means that a channel will be disconnected 5 seconds before end of the current charging unit. 5 seconds is also the minimum time. S66 = Charging unit simulation time in seconds. Some users don't have the ISDN network provide charging information during a connection. In this case no B-channels are disconnected, since the current charging unit never ends. The users can let 'cFos' generate charging information every n seconds, where n can be specified in this register. 0 disables this feature. S68 = Dynamic bundling tries. This registers determines the number of times 'cFos' tries to connect an additional B-channel. Default is 1. S69 = Delay (in seconds) before 'cFos' tries to connect another channel. Default is 0. In addition to that an outgoing call can be configured to be time- or charge limited. This can be selected for main ports and auxiliary ports independantly. Registers S60-S63 are used for this purpose. S60 = charge limit for main port. S61 = charge limit for aux. ports. S62 = time limit in seconds for main port. S63 = time limit in seconds for aux. ports. Time and charge limits can also be configured when no channel bundling is used. They operate independant of each other, so that you can specify a time and a charge limit at the same time. Default is 0 for these registers, which disables this feature. Clearly disconnection of the main port/channels results in disconnecting all respective auxiliary ports 'cFos' Channel Bundling example: You are a mailbox user and after log in you first check all new files and tag those, you want to download. You then can use the following 'cFos' initialization: AT&B2 &M1 S64=5000 S65=7000 Which results in tagging the new files with only one channel but, when the bandwith is needed, downloading them with two, getting more than 15000 cps! WARNING: 'cFos' Channel Bundling (CCB) of Version 1.01a is not compatible with that of earlier versions, since we had to change a few things to get dynamic channel bundling to work. The newer version can deal with CCB of the older versions, but dynamic CCB works only if you call a newer 'cFos' version. 13. 'cFos' Compatibility with Current Software We tested 'cFos' with a variety of applications and ISDN hardware and software. A few programs could lead to difficulties with the high baud rates (most programs offer a signed int, a value of 32767 reaches the upper end of the scale.) FOSSIL spec. suggests to test the ability of your FOSSIL by running it with current software. Some programs have no fast FOSSIL support, especially if they receive data by using the get_status and receive_char functions instead of using the receive_block function. This way of dealing with FOSSIL produces at least 2 INTs and 2 IRETs per character (sums up to 2000 clocks working with a 386 class computer with QEMM or EMM386) neglecting all other call overhead. We tried hard to enable a data transfer with a decent speed even with such an application. But such a FOSSIL support does not allow a data transmission with a good transfer rate on slow computers (especially 386 class computers with memory managers). It is task of the programmers of the terminal software to look for better ways to support FOSSIL. In other words to transfer datas in bigger blocks with receive_block and transmit_block instead of sending byte by byte. Many FOSSIL supporting software needs to know a baud rate with which the software is able to communicate with the modem via RS232 serial port. This baud rate is also required to lock this port on. This baud rate is very import for communicatiom with the modem but for our solution of no importance at all (as without RS232 and external modem). You should write a baud rate of 38400 or 19200 in those fields to stay on the save side. FrontDoor FidoNet-Mailer written by Absolute Solutions (JoHo). Mailer and terminal programm run well with FOSSIL. That is the reason why this programm still achieves transfer rates of more than 7300 cps even with slow computers (386 DX with 6 mhz) and passive ISDN boards. FD on fast computers is one of the best terminal programs we could find (at least concerning transfer speed). Problem 1: Peculiar about FD is that this programm is only able to recognize "canned" CONNECT strings. (In FD versions < 2.11 there is no connect string for 64000, but for 38400.) Therefore you should simply use another unused connect string. That leads to the result that FD miscalculates the transfer time estimations, but at least it works. Solution 1: a) Using FD 2.20/c or FD 2.11/nc the problem does not arise. b) You can use other CONNECT messages for the new bps rates or c) If you do not use a FD >= 2.11 then set ATS9.1 = 0 so that the "CONNECT 9600" message always appears. For logging purposes 'cFos' appends the B2 protocol to the connect string, thus you get CONNECT 9600/X75. This works with FD. Problem 2: The Caller ID delivered by ISDN. 'cFos' can display the caller id behind the "RING" message. Solution 2: If you configured the "RING" message with FD to "RING|" to avoid the "RING"/"RINGING" confusion you should disable this feature by ATS9.2=1. Otherwise FD cannot detect a "RING". You may also enable a 2-line RING message with ATS10.3=1. FrontDoor requires about 250 kb memory. So you should not run into memory problems (even though using DesQView). InterMail As with FrontDoor, 'cFos' runs well with InterMail. The usage of memory is similar, too. BinkleyTerm Binkley uses very fast and skillfully written routines to access a FOSSIL. Even on slow computers high transfer rates can be achieved. Problem: Binkley 2.50 (and 2.50 EE up to Beta D incl.) uses (as far as we know) a signed int for baud rates. That causes errors with a CONNECT of 64000 bps. Solution: An ATS9.1 = 1 always leads to a report of the baud rate of 9600. Then they work properly together. But the timings are wrong. Binkley requires about 300 kb of memory. No memory problems should occur either. D'Bridge D'Bridge (DB) is a mailer written by Chris Irwin from the sunny Miami. To get 'cFos' to run with DB select CONFIG, Comm/Modem Setup in the menu. You find there a setup screen. You have to use one of the DATA/1 ... DATA/3 lines to enter "CFOS" in the column "MCF name". Then you also have to create a file called CFOS.MCF, located in the DB system-directory with at least the following contents: MCF CFOS ISDN-board + cFos BAUD 64000 LOCKED DELAY 0 INIT ATZ OFFHOOK ATH1 ANSWER ATA DIAL 300 ATD DIAL 19200 ATD DIAL 38400 ATD DIAL 64000 ATD TRANSLATE 9600 CONNECT 9600 TRANSLATE 38400 CONNECT 38400 TRANSLATE 64000 CONNECT 64000 The CONNECT strings of 'cFos' must exactly match with one of the above strings. Otherwise DB reports a baud rate of 0. Therefore you should use ATS9.4=0 to suppress the "/X75" in the connect string. If you know another solution for DB please mail us. We recommend to use DB version 1.54 or higher, since the author improved the FOSSIL support in that version. It is possible that you have to use the -jh switch with DB. Yuppie! Yuppie is a 3d pointprogram. We tested version 2.10. Its transfer routines are based on Binkley. Therefore it works fairly well. But it cannot handle a 'CONNECT 64000'. Set "ATS9.1=0" so that it recognizes that a call was succesful. Yuppie requires much memory (it's written in CLIPPER), if possible load CAPI and/or FOSSIL into UMBs. Portal of Power PoP Version 0.62 seems to run good with 'cFos'. Elder versions of PoP had some problems, so use at least v0.62. You have to watch not to load X00 automatically. In case a change of POP.BAT file may help. McMail A new Mailer from Germany with some nice features and good 'cFos' ISDN appendage support (e.g. it gets the real ISDN charges from the FOSSIL and you may interactively add or remove channels in CCB mode). CrossPoint Starting with version 2.92, XP fully supports FOSSIL, for example the termial program etc. Just switch on the topic FOSSIL in the communication/modem menu. Earlier versions of XP had only a partial FOSSIL support. Maximus Maximus is a BBS program written by Scott J. Dudley. As we use this program we tested it thoroughly. It is possible that the Maximus WFC Interface and SpawnBBS do not like baudrates higher that 32767. Menus and textfiles are sent character by character. Therefore ISDN cannot reach its highest speed. But that does not matter much. When downloading Maximus sends datas in 128 byte blocks to the FOSSIL. This way it achieves good transfer rates. Unfortunately Maximus does not use the receive_block() function of FOSSIL for receiving data. Maximus rather accepts byte by byte with the function receive_char(). That leads to a huge overhead. Slow computers cannot reach the highest transfer rates possible. As we wrote the functions receive_char() and get_status() in assembler we obtained an acceptable throughput. Maximus will always be faster downloading than uploading. RemoteAcces RemoteAcces is BBS software written by Andrew Milner. Our tests proved that RemoteAcces runs well without any problems. RemoteAcces can handle transfer rates of more than 7300 cps. It is able to accept calls independently. At least version 2.00 should not have any problems handling baud rates of 38400 or 64000. Unfortunately RemoteAcces can only accept "canned" CONNECT strings. They need to be set in RACONFIG. Version 2.00 offers all strings necessary for ISDN. Only the RING string has to be set to "RING" (if you use ATX3 or above) so that "RING CallerID" will not be mixed up with "RINGING". PCBoard A PCBoard/M version is required to support FOSSIL. 'cFos' runs without any bigger problems with this version. But you have to set "ATS9.4=0" to limit the CONNECT message to 'CONNECT <bps>' because PCBoard uses the last number of the CONNECT string as a baud rate. In addition you can not use the 'cFos' BIOS emulator (-e2) with 'cFos'. In case of problems try using the -ji switch. Wildcat 4.0 Wildcat works with 'cFos' if FOSSIL support is activated and the baudrate is set to 38400. Unfortunately the interal file transfer protocols are not the fastest. We recommend to use external protocols. GS-Mailbox Use at least version 1.90 and the update from may 1995. The internal protocols are not very fast, we heard. Maybe you like to run external ones. TERMINATE _The_Final_Terminal_ Terminate is one of the most advanced DOS-communications programs ever written. It offers fast file transfers using fast FOSSIL block functions and allows you to bundle channels with 'cFos' while you are in a file transfer. Furthermore a special cFos menu is included in versions later than 1.51 that allow you to connect/disconnect b-channels, view FOSSIL options, show last callerid or called number, call charges and to completely reset the driver. Terminate has been tested on slow computers with fast results even with channel bundling without any problems. Even more Terminate is prepared for the cFos status line in the dialer, point system, chatter and file transfer. Terminate was tested and tuned together by the authors of both products. In version 1.52 Terminate requires about 300 kb memory. TeleMate TeleMate is one of the most famous and widespread terminal programs on the PC market. TeleMate supports FOSSIL for quite some time. TeleMate offers the very special feature of internal multitasking, that means you can download a file and edit a text at the same time. But multitasking consumes a vast amount of transfer speed if your computer is not fast enough. A 386 DX is at least required to keep up an acceptable transfer speed. Telemate requires 430 kb memory which is quite a lot. Therefore try to do without as many drivers and resident programs as possible. Important: If you configure TeleMate to support FOSSIL the baud rate *must not* exceed 38400. Otherwise TeleMate would not accept FOSSIL support. If 'cFos' does not respond to AT commands, please check if FOSSIL support is still enabled. Telix for Windows Start 'cFos' with the -r6k switch. If you do so, Telix for Windows will run quite ok, as we heard. HS/Link HS/Link deinitializes the COM-port after use and some programs will barf at that (e.g. the FrontDoor Terminal). Load 'cFos' with the -ji switch or issue a 'CFOS INIT:<portnb>' command to re-init the port. Warning: HS/Link will eventually disconnect your connection if 'cFos' is loaded with the -jk switch. XBTX XBTX is a BTX decoder written by Juergen Buchmueller. XBTX supports FOSSIL starting with version 1.50. As you can also run BTX via ISDN, and the Datex-J ports of German TELEKOM are capable of ISDN, we added BTX support to 'cFos' (ATB5). XBTX checks the ports 0-7 for a the presence of the X00 FOSSIL only. Therefore you need the the -jx switch to let 'cFos' pretend it were X00. XBTX requires 490 kb. Therefore all TSRs should be reduced to an absolute minimum necessary. DoorWay It works. But it is strongly recommended to switch off the 'cFos' status line. Otherwise DoorWay will always transmit the changes of the status line (it does not cause any problems but it bothers). Be sure DoorWay uses FOSSIL mode; the comport-name must be postfixed with an 'F', e.g. 'COM3F' to do this. MS-Kermit You have to switch Kermit in INT 14 mode (for example with "SET PORT BIOS1"). Then use "C" to access 'cFos'. When problems arise a "SET BELL OFF" often helped (nobody knows why). pcANYWHERE for DOS Configure pcANYWHERE for DOS to INT14, set the Modem to {++} "manual settings" and set the Initstring to "ATZS10.4=1S0=1". The hangup string MUST be exactly "+++ATH0". If you do this, AW will run fine and Zmodem transfers will run at 7500 cps. 'cFos' can be loaded with "cfos i". If pcANYWHERE modem settings requires some other string use the AT&H command to change the string to the desired form (see MODEM.DOC). PROCOMM PLUS for Windows Set the Port to INT14 in the "Setup" Menu (ALT-S), "Advanced", "Port". cc:Mail for DOS cc:Mail remote and the cc:Mail router run in version 5.1 fine with 'cFos'. You have to enable the INT 14 functionality, see the cc:Mail documentation for details. FX UUCP You have to add/change the following items in file STATIC: driver: fossil uu.driver: fossil NCBMail A complete mailbox package incl. ZConnect/Fido-Mailer by Fricke EDV-Beratung, Wolfenbuettel. NCBMail is optimized, so even on a 286-16 you get transmission rates >7300 CPS. Furthermore, NCBMail supports all standard transfer protocols (X, Y, Z-Modem and Kermit). cFos-appendage support is a specialty of NCBMail. With this, you may select to start arbitrary programs depending on the incoming caller-id, EAZ/MSN, service indicator, ring counter and date and time. This is very useful for answering machines like cFosTALK. DesQView We tested 'cFos' working with DesQView as a MultiPort FOSSIL. You have to load 'cFos' BEFORE DesQView with serveral -c parameters so that several tasks can access different "modems". Running DesQView we called one FrontDoor from another FrontDoor. We achieved transfer rates of more than 7500 cps (386DX-40). MS-Windows If you want to run 'cFos' with MS-Windows you have to load 'cFos' prior to MS-Windows. Some Windows programs do not support FOSSIL but they can use INT 14h. If so 'cFos' can operate with them. OS/2 DOS-Box As far as we tested, 'cFos' should now run OK in the OS/2 DOS Box. The allocation of DOS UMB's is turned off, because OS/2 behaves strangely in this matter ('cFos' loads with an effective commandline of cfos i -jo -jg -ju if OS/2 is detected). See Appendix H for a compatibility list. 14. ISDN Hardware/Software 'cFos'is based on CAPI which is an official German standard ISDN interface. But there are still some questions unanswered. Therefore it is necessary to test an application with the given hardware. Here we present a report of our experience (and other users' on the subject of ISDN boards): TELES Creatix S0 'cFos' was developed and tested on a TELES.S0 ISDN board. TELES AG, Berlin kindly supported and still supports the development 'cFos' by their developers of their CAPI. 'cFos' recognizes TELES CAPI and checks whether the modules are loaded for V.110 or bundle protocol. 'cFos' then enables the use of either V110 or channel bundling and therefore ATB1...ATB3. If you have problems with the OS/2 CAPI in a DOS-Box be sure to use a new version, like 2.95. AVM 'cFos' runs well on both the passive AVM A1+ and the active AVM B1. The rather abnormal behaviout of the X.75 ISDN Blaster board could cause problems. Meanwhile AVM has a new version of their drivers to solve the problems when calling a Blaster with an AVM board (version 2.07-10 or higher). If you want to call a Blaster that uses FOSSIL PCIF V5.78 it is recommended to set 'cFos' -jp flag (for further details see chapter 3). In parts AVM CAPI does not include V.110. If it is the case the error message "ERROR/B2" will be displayed after a connect message when you try to call. A new version of AVM CAPI fixed the problem. But there are still old A1 boards that lack a V.110 driver. {++} The AVM B1 (with an additional module by AVM) can be used to plcae outbound analogue 2400bps, V.22bis calls using the init-string "ATB7". You should run at least CAPI 2.09 to do this. CPV Stollmann 'cFos' runs well on the active boards Tina D and Tina DS. Even on slow computers 'cFos' is fast. Stollmann CAPI cannot execute V.110 until now but Stollmann anounced to work it out soon. Our mailbox offers the latest versions of drivers for Stollmann boards (TINACAPI.ZIP and TINAETSI.ZIP). We recommend to use them by all means. And we recommend to follow the instructions for executing a call with TICAPI -b to avoid problems with ISDN Blaster when placing calls. There is a COM-port emulation that unfortunateley when loaded prevents that 'cFos' succesfully registers in CAPI. When you want to use 'cFos' make sure that this module is not loaded. CPV Stollmann kindly made us a TINA DS available for testing. Therefore 'cFos' should work with this board without any problems. {++} Unfortunately channel bundling is not possible with a TINA D or a TINA DS board (but it functions with a TINA DD) because the second B-channel is connected to the integrated A/B adapter on a hardware basis and therefore is not available for CAPI. mbp SOLIS SOLIS boards produced by the company mbp work well with 'cFos' when you follow certain instructions: Set switch -jr when loading 'cFos'. Solis supplies a COM port emulation. We recommend to switch it off. This COM emulator listens to EAZ 9 by default. This can be changed with Util ICOMONF. The COM emulator and 'cFos' may not listen to the same EAZs at the same time. We suggest to use the latest mbp CAPI version in any case because older ones might cause problems. We heard that the SOLIS board does not report charging infos while a connection is active, only at the end of the connection. ITK iX1 'cFos' works well with iX1-basic, we had the opportunity to test the board version 1.2 with CAPI 2.41. {++} The iX1-basic may be switched to do outgoing analogue modem calls with up to 14.400 bps, but without error correction using the init-string "ATB7". Thanx to ITK for sending us a test board. ELSA Microlink ISDN/PC, ISDN/PCC, ISDN/PCF, ISDN/PCF-Pro ELSA kindly made us available an ISDN/PC and PCF-Pro plug-in-board including CAPI 1.43 for testing. 'cFos' runs well with this configuration. ELSA CAPI needs only few memory and is fast. Unfortunately it is not (yet) able to execute V.110. But ISDN/PC offers a COM-port with a 16550 "for compensation". {++} 'cFos' can execute channel bundling starting with ELSA CAPI version 1.43. {++} ISDN/PCF has a built in modem-chip. It which can be activated for outgoing calls with 2400 bps (ISDN/PCF) resp. V.34 (ISDN/PCF-Pro) with fall-back by using ATB7. 'cFos' channel-bundling is possible. Sedlbauer S0-BOX and S0-plug-in board The S0-BOX is an external equipment that needs to be plugged on the printer port. All data between ISDN and the computer are exchanged via printer port. For the presence the S0-BOX can operate only one channel. Sedlbauer announced to change that. Therefore channel bundling will be possible in the near future. CAPI version before 4.00 maybe had some problems with windowsizes < 7. CAPI's from verion 4.00 on should run ok. If in doubt, get a new CAPI version from the Sedlbauer server. The S0-BOX only supports windowsize 7 so far. Therefore load 'cFos' with "cfos i -w7" and set ATS26=7. When you observe our recommendations the S0-BOX will run well with 'cFos'. All said about the S0-Box also applies to the S0 plug-in board. We thank Sedlbaur for making us an S0-BOX available for testing. Diehl Diehl Diva is an active ISDN board. 'cFos' runs fast on Diva boards especially on slow computers. In the near future the "at run time" loadable firmware will also support V.110. We thank Diehl for making us a Diva board available. According to information by Diehl 'cFos' works well with the following boards without modem features: SCOM, SX/n, S2M (Primary Rate), Quadro (4xSo), Diva, Diva PC-Card (PCMCIA) and Diva Piccola. Furthermore does it run well with these boards with modem features: Maestra, Diva Pro und Diva Pro PC-Card (PCMCIA). Dr. Neuhaus Dr. Neuhaus kindly tested 'cFos' with their ISDN Boards and reported that is runs at least with their passive NICCY 1000, 1016 and active 3008, 3009 and 5000 CTX boards. Since all these boards have two b-channels, you can run CCB with them. KSI SA-1 Digiteam Digiboard As far as we tested it, 'cFos' is running with the SA-1. Thanks to KSI for supplying us with a test board. The SA-1 CAPI uses 180kb of memory, so you should run 'cFos' with smallest buffers possible. It seems not to support V.110. IBM PCMCIA Active 2000 IBM Employees told us that this board runs well with 'cFos'. JanusSoft/HST Saphir 'cFos' runs well on the Saphir ISDN board. This board has a very small CAPI driver for both E-DSS1 and 1.TR.6, with or without V.110 and ISO8208. There area versions that support Novell's DPMS as well. The board is capable of CCB. Thanx to HST for their test board. It looks like it is not possible to connect to ISDN-Blaster boards. NCP ISDN P-8 / P-16 'cFos' runs well on NCP cards with the HST CAPI. Thanks to HST for sending us a baord for testing purposes. The card features an extremely small CAPI with optional V.110 and ISO 8208 and is able to run multiple channels at the same time. It looks like it is not possible to connect to ISDN-Blaster boards. BinTec BIANCA The BinTec BIANCA is an active ISDN board with V.22bis (2400 {++} bps) modem emulation. 'cFos' supports the analogue modem if you select it with ATB7. The board is quite nice and comes with very good documentation. The BIANCA board supports the V.110 protocol. According to user responses the following cards run with 'cFos': Siemens Hicom 300 PC Miro P1 Other Boards If problems arise with ISDN hardware/boards not mentioned above check first if there is a more recent CAPI version available. If so try it first. Otherwise send mail to us. We would like to take the chance to say thanks to the manufacturers of ISDN boards for the good cooperation, we especially like to mention TELES, but also CVP/Stollmann, ELSA, Diehl and Sedlbauer. 15. Miscellaneous: - Disconnect Reasons 'cFos' reports to the remote party: 0x00 : normal disconnect (also 0x80) 0xbe : call rejected 0xbb : user busy 0xb9 : out of order The disconnect reason arrives at the remote party as 0x34?? cause. However some causes are filtert/translated by the telephone switching equipment. - Service Indicator (SI) not equal 7 If you enable other services than "data transmission" by register S14, 'cFos' issues a "CONNECT VOICE" message, if the service indicator (SI) = 1 or SI = 2 and selects the B2 protocol "bittransparent", if register S44 = 0. This enables you to run an answering machine software, such as cFosTalk, with 'cFos'. If register S44 = 1 and the manufacturer of your ISDN board supports a modem protocol in it's CAPI implementation, 'cFos' selects this protocol. This allows you for example to service modem callers with your ISDN mailbox. If SI <> 7 and SI <> 1, 'cFos' issues a "CONNECT ?" message and selects the protocols given by registers S20-S36. If you place a call, you can choose the service indicator by setting register S16 in the same way you choose the additional service indicator as well as the B2 and B3 protocol by registers S17, S20 and S21. - For further study Here is some literature (including programs) references to anyone who is further interested in the subject of ISDN: CAPI Dokumentation COMMON-ISDN-API, Einheitliche Schnittstelle zwischen Applikationsprogrammen und ISDN-Adaptern, Spezifikation, Version 1.1, Profil A, Editorisches Datum: 07.09.90 e.g. at Zaphods BBS as ISDNAPI.ZIP, 24k (german) or CAPI_ENG.ZIP, 20k (english) or CAPI11.ZIP, 62k (german, WORD-Format) 1.TR.6 Dokumentation The 1.TR.6 documentation is available at the following address: DBP Telekom FA Bad Kreuznach Projekt Roland Arbeitskreis CAPI/PCI z. Hd. Herrn Kreuzer Postfach 9100 W-6550 Bad Kreuznach Germany PAPI Source PAPI is an ISDN paket driver for TCP/IP, which uses CAPI. e.g. at Zaphods BBS as PAPI*.ZIP, about 38k each If you are interested in the FOSSIL specs, there is FSC-0015 available. THE original FOSSIL Doc by Rick Moore. As FSC-0015.A?? in every good FIDO BBS available. 25k. X00REF.DOC The function refence by Ray Gwinn for FOSSIL developer contains many good and important comments. e.g. at Zaphods BBS as X00150.ZIP, 105k. - If you should ever use the "V.110 inband negotiation", you get a "CONNECT 9600" message from 'cFos', since 'cFos' can not know which baudrate was actually negotiated. 16. Addresses, Authors, Availability: - License Terms see our license in COPYING.CF. - Authors Lueders/Winkler GbR Heerstr. 8 53111 Bonn, Germany Fidonet: martin winkler, 2:2453/30 Internet: winkler@zaphod.infox.com .-- Voice: (Read paragraph below!) +49-228-650389 | | | Voice phone calls: | |-- Phone us for commercial purposes only, please. | {++} | Users of 'cFos/Pro' are provided phone support by their | respective suppliers/vendors. Please don't ask questions | treated in this documentation. | | We also started a Fido echomail conference, called CFOS_HELP. | In addition you can write a mail to SysOp at Zaphods BBS (ISDN | 0228-9111041, V32b 0228-262894). This can often help you | faster than calling somebody voice. | `-> Before support can be given, we'd appreciate that the caller has carefully read CFOS.ENG, WHATSNEW, MODEM.DOC, CFOS.FAQ and already experimented with 'cFos'. You can call us, if you use ISDN equipment not mentioned in this documentation. If you have problems with the configuration of your applica- tion software, it is always a good idea to contact the respective "Help-Sites". Mail/Bug-Reports: We are always interested in - obvious bugs in 'cFos' or the documentation. - experiences with software or ISDN hardware unkown to us. - suggestions of features to include in 'cFos'. - What else can be done with 'cFos'. Interesting ISDN phone numbers, for example, are always welcome. A Mail to us should at least contain: - your name and (if it's a bug report or you have an ISDN board not mentioned in the documentation) your voice number so that we can call back (and the hours you're reachable under that number). - The version number of 'cFos'. - Used Computer, Software, CAPI driver and ISDN board, please always include their version numbers. - New Versions: The most recent version of 'cFos' is always available at our own BBS, called Zaphods BBS, in Bonn, Germany. In addition we try to spread the 'cFos' archive as fast as possible via Fido BBSes, Internet servers and MAUS BBSes. For future versions we plan - to improve the readability of the ATIn displays. - to support Ralf Brown's AMISL Alternate Multiplex Interrupt Specification for resident programs. {++} - to include serveral logging features to evalutate phone costs, incoming calls, etc. 17. Credits: The order does not imply any preference ;-) Andreas Illg, Alexander Bell, Eberhard Mattes, Dietmar Friede, Uwe Engelmann, Scott J. Dudley, Robert Bergermann, Jens Osterwohldt, Markus Kessler, Olaf Droege, Tobias Erichsen, Jan Ceuleers, Kalle Braun, Roland Steinmeyer, Oliver von Bueren, Rainer Schuetze, Thorsten Winkler, Manfred Recla, Joern Bardewyck, Heiko Meyer. 18. End of Documentation; Thanx for using 'cFos'. Practice random kindness and senseless acts of beauty! ---------------------------------------------------------------- APPENDICES ---------------------------------------------------------------- A. CAPI Error messages: Here is a list of the CAPI error messages of the "Arbeitskreis CAPI", extended by V.110 error messages, 1.TR.6 causes and manufacturer specific messages: 0x0000 No error 0x1001 Error on API_REGISTER 0x1002 Illegal application-id 0x1003 Illegal message 0x1004 Illegal command or subcommand 0x1005 Queue is full 0x1006 Queue is empty 0x1007 Queue overflow 0x1008 Deinstall error 0x1009 Wrong message operation 0x2001 Illegal Controller 0x2002 Illegal PLCI 0x2003 Illegal NCCI 0x2004 Illegal type 0x3101 B-channel erroneous 0x3102 Infomask erroneous 0x3103 Serviced-EAZ-mask erroneous 0x3104 Serviced-SI-mask erroneous 0x3105 Illegal B2 protocol 0x3106 Illegal DLPD 0x3107 Illegal B3 protocol 0x3108 Illegal NCPD 0x3109 Illegal NCPI 0x310A Illegal flags 0x3201 General controller error 0x3202 non-unique LISTEN_REQs 0x3203 function not supported 0x3204 PLCI inactive 0x3205 NCCI inactive 0x3206 B2 protocol not supported 0x3207 can't select B2 protocol now 0x3208 B3 protocol not supported 0x3209 can't select B3 protocol now 0x320A illegal DLPD parameters 0x320B illegal NCPD parameters 0x320C illegal NCPI parameters 0x320D data length not supported 0x3301 D channel layer 1 setup error 0x3302 D channel layer 2 setup error 0x3303 B channel layer 1 setup error 0x3304 B channel layer 2 setup error 0x3305 D channel layer 1 shutdown 0x3306 D channel layer 2 shutdown 0x3307 D channel layer 3 shutdown 0x3308 B channel layer 1 shutdown 0x3309 B channel layer 2 shutdown 0x330A B channel layer 3 shutdown 0x330B B channel layer 2 reestablished 0x330C B channel layer 3 reestablished 0x3400 Normal disconnect 0x3480 Normal disconnect 0x3481 Invalid call reference value 0x3483 Bearer service not implemented 0x3487 Call identity doesn't exist 0x3488 Call identity in use 0x348a No channel available 0x3490 Requested facility not implemented 0x3491 Requested facility not subscribed 0x34a0 Outgoing calls barred 0x34a1 User access busy 0x34a2 Negative CUG-match 0x34a3 Nonexistent CUG 0x34a5 SPV not allowed 0x34b5 Destination not obtainable 0x34b8 Number changed 0x34b9 Out of order 0x34ba No user responding 0x34bb User busy 0x34bd Incoming calls barred 0x34be Call rejected 0x34d9 Network congestion 0x34da Remote user initiated 0x34f0 Local procedure error 0x34f1 Remote procedure error 0x34ff User info discarded locally 0x4001 stollmann: too many applications 0x4002 stollmann: block size too large 0x4003 stollmann: error on init of message queue 0x4004 stollmann: no PLCI cntl block available 0x40ff stollmann: function not allowed in current context 0x4101 Loss of Frame-Synchronisation 0x4201 stollmann: can't deinstall, not on top of int chain 0x4202 stollmann: can't deinstall, application still active B. Format of the V.110 user rate (S27) and Additional Service Indicator (S17): Bit 76 01 Extension for asynchr. transmission Bit 5 Bit 4 Bit 3 0 8 data bits 0 1 stopbit 0 no parity 1 7 data bits 1 2 stopbits 1 even parity Bit 210 000 38400 bit/s 11 Asynchr. transmission with bit rate adaption acc. CCITT V.110 Bit 5 Bit 4 Bit 3 0 8 data bits 0 1 Stopbit 0 no parity 1 7 data bits 1 2 Stopbits 1 even parity Bit 210 user rate in bit/s 000 1200 001 1200/75 010 75/1200 011 2400 100 4800 101 9600 110 14400 111 19200 10 Synchronous transmission with bit rate adaption acc. CCITT V.110 Bit 54 10 never change Bit 3210 User Rate in bit/s 0000 1200 0001 1200/75 0010 75/1200 0011 2400 0100 4800 0101 9600 0110 14400 V.32bis 0111 19200 1000 48000 1001 56000 1010 56000 USA 1111 in band negatiation C. B2-Frames and windowsizes with X.75: For all, who still believe 16k byte frames and windowsize 1 are good for high transfer speeds, we include a few diagrams here, which show the different timing at different frames and window- sizes: The windowsize specifies how many frames may be sent until the sender needs a confirmation before sending further frames. Windowsize 1, 2k Byte Frames: sender -<2kb data>-------<2kb data>-------<2kb ... receiver ------------<conf>-----------<conf>---- ... delay ------------!!!!!!-----------!!!!!!---- ... time ------------------------------------------> With 1 MB transmitted data you thus have 512 times a time consuming delay. With 16k bytes frames you still have 64 delays. We see that we cannot achieve the maximum CPS rates by this transmission mode. Now Windowsize 2 und 2kb Frames: sender --<2kb data1>-<2kb data2>-<2kb data3>-<2kb data4>-- receiver --------------<conf1>-----<conf2>-----<conf3>------- time ---------------------------------------------------> delay: None! A Windowsize of 1 can be compared with data transmission of X-Modem, whereas windowsizes greater 1 are comparable with the full streamed data transmission of Z-Modem. Allthough the overhead of Z-Modem is bigger than that of X-Modem, it is still faster. CRC errors during transmission: In Germany the Telekom garanties an error rate smaller than 1:1,000,000 on ISDN phone lines. Thus the worst case is one error per transmitted MB, resulting in one frame resend. With 16k frames the resend costs 2 seconds (at 64000 bps). In case of an error you therefore lose about 300 CPS per MB - but with 2k byte frame only 40 CPS ! D. Connect problems with ISDN Blaster (X.75): Even if the Blaster is set up to 2k bytes frames it is still possible that problems occur with Stollmann and AVM boards. These problems always occur if you place a call to a Blaster board - not if you are called by it. The reason is a bug in the implementation of the Blaster FOSSIL PCIF 5.78 and 5.80. The bug however is fixed in PCIF 5.82. To solve the problem users of CPV/Stollmann boards should obtain the most recent CAPI driver from Stollmann or from our BBS. This driver has the ability to run in LAP B mode (TICAP -b) and thereby avoiding the problems. AVM now also provides a driver for all of their ISDN boards with a work-around for this problem. For PCIF 5.78 you can also load 'cFos' with the -jp switch. But this does not work with PCIF 5.80. In any case you can place calls to a Blaster using V.110, 38400, async. and then tell the Blaster user to set up the frame size to 2k bytes (by placing ATS75=0x0800 in the init string) and install PCIF 5.82. E. Connect problems to ELINK "Modems": Some Elink user set up their "modems" in a way that can cause connect problems or the Elink does not answer calls at all. To solve this problem here we include the Elink settings which make it compatible with other ISDN hardware/software. V.110-Subkanal (S18): 000 Betriebsart &B16 : 64kbps,sync Protokollmodus \N6 : X.75 Extended mode \X0 : aus SIN unbekannt \S1 : Ruf annehmen SIN <> abgehend \S3 : Ruf annehmen SIN abgehend \S5\S7 : herst.spez. Rate adjust \J1 : ein Blocklaenge \A3 : 256 Bytes XID-Prozedur : aus Please let the owners of Elinks know of these settings and inform them to use EPROM release 2.12 or higher, since some bugs were fixed since then. F. CCB with several S0-Busses of different phone numbers: outgoing calls: In order to call several S0-Busses with different phone numbers you can specify serveral phone numbers, seperated by ':' or '|' in the ATD command. For example ATD 123456:234567. They are used in the following way: Channels Dial Channel 1 Channel 2 Channel 3 Channel 4 AT&B2 ATD A A A - - ATD A:B A B - - AT&B3 ATD A A A A - ATD A:B A A B - ATD A:B:C A B C - AT&B4 ATD A A A A A ATD A:B A A B B ATD A:B:C A A B C ATD A:B:C:D A B C D Of cause 'A', 'B', 'C', 'D' name phone numbers. We admit that dialing several number at the same time is a rare case. But this provides a way of calling a person, who offers 4 channels for CCB on two different S0-busses, by operating two ISDN boards in one computer. Sometimes these two S0-Busses have different phone numbers. Incoming calls: To allow CCB with caller ids which are similiar, 'cFos' has register S49. The value in this registers specifies how many digits in the caller id are ignored (from right to left), when deciding if this is a CCB call. Default is 0. Example: You are called by a user with the S0-busses of the phone number 12345-01 and 12345-67. If you set S49 to the value of 2 then 'cFos' ignores the digits '01' and '67' when comparing the caller ids. Notice that the lengths of the caller ids have to be the same. However the normal case is that both S0-busses have the same phone number, because they are connected by a ringdown (or similar) circuit. G. 'cFos' modem error message: ERROR The last modem command has an incorrect format or the values given were out of the allowed range. ERROR/B2: The selection of the B2-protocol resulted in an error generated by the CAPI driver. In most cases this means that the respective CAPI driver does not support the selected protocol. (Some older German CAPIs do not support V.110. 'cFos' then disables V.110 as if a -jv switch was given). ERROR/B3: The selection of the B2-protocol resulted in an error generated by the CAPI driver. In most cases this means that the respective CAPI driver does not support the selected protocol. ERROR/LISTEN: The selection of the kind of calls the CAPI/cFos should listen was invalid. In this case you should check the values specified in the S registers for Serviced SI Mask, Info Mask and Serviced EAZ Mask (Registers S13, S14, S41, S42). ERROR/CAUSE=xxxx During call setup the CAPI indicated an error. For a list of errors refer to appendix A. In many cases this problem can be solved by checking the modem S registers. H. Software compatibility list: Among others 'cFos' runs with the following software: Product Manufacturer Program-Type ------- ---------- ------------ FrontDoor Absolute Solutions, Fido-Mailer Joaquim H. Homrighausen Intermail Peter Stewart Fido-Mailer BinkleyTerm Vince Perriello/Bob Hartman Fido-Mailer D'Bridge Chris Irwin Fido-Mailer (*) McMail Gordian Schuermann/ Fido-Mailer Albert Freriks Portal of Power Soren Ager & The Portal Team Fido-Mailer Xenia Lentz Software Development Fido-Mailer Dutchie >=3.00 Applied Computer Sciences, Fido-Mailer Ede Yuppie! V2.10+ YEAsoft, Aachen Fido-Point System CrossPoint V2.14+ Peter Mandrella Fido-Point System Maximus Scott J. Dudley BBS Software RemoteAccess Andrew Milner BBS Software PCBoard/M Clark Development BBS Software SuperBBS Risto Virkkala & Aki Antman BBS Software Wildcat 4.0 Mustang Software, Inc. BBS Software GS-Mailbox 1.90 Gandke und Schubert BBS Software (*) NCBMail Fricke EDV-Beratung BBS Software/ Mailer Dialog Daniel Raseghi Terminal Prg TeleMate V4.12+ White River Software Terminal Prg Terminate V1.40+ Bo Bendtsen, Daenemark Terminal Prg Telix INT14 EXIS Inc. / ELSA Terminal Prg Telix for Windows ? Terminal Prg Unicom Data Graphics Terminal Prg PCPLUS/Procomm Plus Datastorm Technologies, Inc Terminal Prg MS-Kermit Trustees of Columbia Univers. Terminal Prg DN 3270 Lange Communication Terminal Prg COMM90 Bausch Datacom Terminal Prg VipCOM Telesoft GmbH Terminal Prg Reflection >= 4.21 WRQ Terminal Prg GLINK Atlantis, Erftstadt Terminal Prg HS/Link Samuel H. Smith Transmission protocol Engine CEXYZ Cutting Edge Computing Transmission protocol Engine SDPFL Streamline Design Transmission protocol Engine PC-Anywhere 5.0 Symantec, Inc. Remotecontrol Software DoorWay Marshall Dudley Remotecontrol Software FernTerm Remotecontrol Software OzCIS 2.x Steve Sneed CompuServe Navigator OzWIN Steve Sneed CompuServe Navigator DOS-CIM Compuserve, Inc. CompuServe Info.Manager WIN-CIM Compuserve, Inc. CompuServe Info.Manager cc:Mail Lotus eMail System XBTX Juergen Buchmueller, BTX Decoder Bonn, Germany (*) CFOSTALK Michael Grube Answering Machine Waffle Darkside International UUCP BBS Prg FX UUCP Jorge Cwik UUCP BBS Prg 'cFos' is compatible with DesQView, MS-Windows, PAPI 0.16, X00, ISDN-Talk and OS/2. Thanks to the people who helped us testing the software. Products marked with an asterik (*) support the 'cFos' ISDN appendage (see APPEND.DOC). Note: We can not be held responsible that the above mentioned software works with 'cFos'. We only say, that we, or someone else, tested them and that they seem to work under our test conditions. I. Availability: We release 'cFos' as a ZIP archive, but beware that it may be repacked to some other archive style by other sites. The original name of the archive is CFOSnnnn.ZIP, where 'nnnn' is some kind of version numbering, like CFOS095.ZIP for version 0.95. The most recent version of cFos may be obtained at... Our home BBS : Zaphods BBS, Bonn/Germany, Sysop Chris Lueders +49-228-262894 14400bps, HST/V32b (fido 2:2453/30) +49-228-9111041 64000bps, X75/V110 (fido 2:2453/33) We try to keep the following sites up to date: FIDO: Cuckoo's Nest, Vienna/Austria, Sysop Werner Schlagnitweit +43-1-4941019 V32B,V42B,V34,H16,VFC,X75 (fido 2:310/0) +43-1-4854330 V32B,V42B,V34,H16,VFC (fido 2:310/2) +43-1-4941019 V32B,V42B,V34,H16,VFC,X75 (fido 2:310/3) German CompuServe: See the ISDN forum, area #9 ISDN Applications or, see the GERNET forum, area Telecommunication. Internet fileservers (Europe): Directory : FTP.FUNET.FI ? Europeans: please avoid calling over the Atlantic. Get your files from one of the above or some SIMTEL/Garbo mirror site. The network will appreciate that ;-) Internet fileservers (North America): Directory : OAK.OAKLAND.EDU [141.210.10.117] ? J. 'cFos' und CompuServe mit DOSCIM/WINCIM CompuServe Information Service (CIS) and the ISDN Access with 'cFos', (Thanks to Manfred Recla for this description): Before you start DosCIM (or WinCIM), you have to check if V.110 support was loaded with the CAPI driver. Please check your CAPI manual for V.110 support in your CAPI. With TELES (or CREATIX) S0 boards the module V110.EXE is loaded in STARTS0.BAT batch. Then you are ready to use the nost recent release of DosCIM V2.2.3 or WinCIM V1.3.1 (with Int-14h/LAN support!) with 'cFos'. 'cFos' should simply be loaded after the CAPI driver with parameter "i". It should be loaded before starting Windows. CompuServe's WinCIM is available in an English or a German Version. If you don't have a version, please download it for example from ZAPHODS BBS. In addition to that you can also download an updated version of the modem database for DosCIM/WinCIM with a modem init string for "cFos - ISDN CAPI Modem Emulation". This can be used to configure 'cFos' for the CompuServe requuirements (e.g. calling with an Additional Service Indicator of 0, since CompuServe uses Dr. Neuhaus NICCY 3000 terminal apadptors, which can not evaluate the Additional Service Indicator. Replace the pre-installed file "MODEM.DB" with the updated version from Zaphods BBS. If you installed WinCIM in the default directories, the file is located in \CSERVE\SCRIPTS. Now follow the configuration defaults for the English or German version. After that you are ready for your first online-session. Now follows an installation example for DosCIM v2.2.3: █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█ █ ┌──────────────────────┐ █ █ Session: │ cFOS │ ┌─────────┐ █ █ └──────────────────────┘ │ New │ █ █ ┌───────────────────────────────────────────────────────────┐ └─────────┘ █ █ │ Your Name: Manfred Recla___________ │ █ █ │ User ID: 100042,1170___ │ ┌─────────┐ █ █ │ Password: ▒▒▒▒▒▒▒▒▒▒▒▒▒▒ Phone: 0049-89-66530130 │ │ Delete │ █ █ │ │ └─────────┘ █ █ │┌Baud Rate──┐ ┌Comm Port───┐ ┌Network─────┐ ┌Dial Type───┐ │ █ █ ││ 9600 │ │ INT 14 │ │ CompuServe │ │ Tone │ │ ╔═════════╗ █ █ │└───────────┘ └────────────┘ └────────────┘ └────────────┘ │ ║ OK ║ █ █ │ │ ╚═════════╝ █ █ │┌Alternate Session─────┐ ┌──────────┐┌─────────┐┌─────────┐│ █ █ ││ cFOS │ │ Modem... ││ LAN... ││ More... ││ ┌─────────┐ █ █ │└──────────────────────┘ └──────────┘└─────────┘└─────────┘│ │ Cancel │ █ █ └───────────────────────────────────────────────────────────┘ └─────────┘ █ █▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█ █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█ █ Modem Control Strings █ █ █ █ ┌ Modem Type ──────────────────────────────┐ █ █ │ cFOS - ISDN CAPI Modem Emulation │ █ █ └──────────────────────────────────────────┘ █ █ Initialize: ATB0S20=8S27=197S10.4=1^M █ █ Prefix: AT_______________ █ █ Reset: &F_____________ [ ] Speaker Off █ █ Dial Tone: DT_____________ █ █ Dial Pulse: DP_____________ ╔══════════╗ █ █ Hang Up: H0_____________ ║ OK ║ █ █ Suffix: ^M_______________ ╚══════════╝ █ █ Escape: +++______________ ┌──────────┐ █ █ Modem Acknowledge: OK_______________ │ Security │ █ █ Connect Message: CONNECT__________ └──────────┘ █ █ Connect Failure: NO CARRIER_______ ┌──────────┐ █ █ [ ] Error Correction: _________________ │ Cancel │ █ █ [ ] Data Compression: _________________ └──────────┘ █ █ █ █ * Modified from Default █ █▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█ If you have installed DosCIM (v2.2.3) or WinCIM (v1.3.1) already, but you don't have an updated "MODEM.DB", you can change it as follows: [Version] Version=3.5.2 (10/23/94) [Modems] cFos - ISDN CAPI Modem Emulation=cFOS [cFos] Init=AT B0 S20=8 S27=197 S10.4=1 &D2 S11=24^M an updated "MODEM.DB" file with changes for 'cFos' is available at ZAPHODS BBS. CompuServe new user login: If you are not already a user of CompuServe and don't have a CompuServe user ID you have to edit your Session Settings as illustrated above. Please fill in your name and as your user ID a 0. After that use menu "Special" to choose the terminal emulation. Klick the button "Manual Connect" and then "OK". You are now in the terminal emulation. Now supply the following dial string: AT B0 S20=8 S27=197 S10.4=1 AT D 0049-89-66530-130 After a few seconds a "CONNECT 9600" message will be displayed. Now press RETURN (or ENTER) once which initiates transfer of your login data to the CompuServe host. The prompts are answered as follows: Host-Name: CIS USER ID: 177000,5603 Password: NEUE/WELT Agreement-Number: BTX92D Serial-Number: 92283 You are also asked for name, address, credit card no. or bank account. CompuServe then assigns you your own user ID and a temporary password, valid for 2 weeks. Withing that time CompuServe informs you about your final password via mail. For now write down your user ID and the temporary password and answer the CompuServe command prompt with the word "OFF", thus terminating the connection to the host. Close the terminal emulation window and enter your user ID and password in the menu "Session Settings". Now DosCIM/WinCIM is ready to login at CompuServe automatically. You only need to "klick" on a desired service. Note: DOSCIM, WINCIM and OS2CIM cannot be downloaded from our BBS. You must get them from CompuServe. -------------------- End of Documentation -----------------------