Subsections


1.1 OPT_MTGCAPRI - ISDN-Remote-CAPI For fli4l

1.1.1 Introduction

OPT_MTGCAPRI provides an ISDN remote-CAPI for fli4l enabling ISDN-CAPI based applications on network clients to use a CAPI without having the need for an ISDN card in each client with fli4l's ISDN card being shared over the network.
OPT_MTGCAPRI is only the integration of the Linux CAPRI-Server by mtG (http://www.mtg.de/de/) into fli4l's infrastructure.

1.1.2 Copyright

The installation manual for clients is taken from the original documentation of the mtG-Capriserver and is Copyrighted by mtG.

1.1.3 Precondition

1.1.4 Configuration

OPT_MTGCAPRI

Default Setting: OPT_MTGCAPRI='no'

'yes' activates the Capri server.

MTGCAPRI_PORT

Default Setting: MTGCAPRI_PORT='20000'

This may be configured freely but should not be under 10000 in normal use cases to avoid possible conflicts. It has to be known by the client resp. entered in the client's capri.ini.


Important: Please pay attention to not open this port for connections from the Internet in base.txt!

MTGCAPRI_TRACELEVEL

Default Setting: MTGCAPRI_TRACELEVEL='1'

The trace level sets the logging scope. Possible values are:


Important: Setting the trace level to a high value should only be used in the event of an error, since relatively large files may arise and thus the performance of mtG-CAPRI decreases. This may interfere with time-critical applications (eg fax).

MTGCAPRI_TRACEFILE

Default Setting: MTGCAPRI_TRACEFILE='/var/log/capri.trc'

The trace file serves for logging the activities of the server. Name and path to the file may be choosen freely.

Alternatively you may specify 'auto' here and the file will be created in the systems folder for persistent data automatically. Please pay attention to configure FLI4L_UUID accordingly, because the file might become really big and /boot or even the Ramdisk may overflow.

MTGCAPRI_LOGFILE

Default Setting: MTGCAPRI_LOGFILE='/var/log/caprilog.txt'

Define the name of the logfile here.

Alternatively you may specify 'auto' here and the file will be created in the systems folder for persistent data automatically. Please pay attention to configure FLI4L_UUID accordingly, because the file might become really big and /boot or even the Ramdisk may overflow.

MTGCAPRI_MULTIPLEBIND

Default Setting: MTGCAPRI_MULTIPLEBIND='no'

Allows passive binding of several clients to one phone number on the server. With MTGCAPRI_MULTIPLEBIND='yes' more clients can wait for incoming calls on the same phone number. With MTGCAPRI_MULTIPLEBIND='no' only one phone number can be assigned per client.

MTGCAPRI_USER_N

Default Setting: MTGCAPRI_USER_N='1'

Specify the number of users here.

MTGCAPRI_USER_x_NAME

This variable holds the username. It has to be the same as the user account on the Windows client on which the mtg-CAPRI-Client is installed.

MTGCAPRI_USER_x_SERVICE

Default Setting: MTGCAPRI_USER_x_SERVICE='all'

Specify the services here the user can get access to. Possible values are: all, fax23, fax4, data64, telefon.
You can specify multiple services separated by a space.
Example: MTGCAPRI_USER_x_SERVICE='telefon fax23'

MTGCAPRI_USER_x_OWN_NUMBERS

Default Setting: MTGCAPRI_USER_x_OWN_NUMBERS='all'

Here it is determined to which phone numbers the user is allowed to bind passively. Possible values are:

MTGCAPRI_USER_x_OWN_NUMBERS_LIST

Default Setting: MTGCAPRI_USER_x_OWN_NUMBERS_LIST=''

For the setting MTGCAPRI_USER_x_OWN_NUMBERS='partial' define the numbers here which the user is allowed to access. Multiple numbers have to be separated by spaces.
Example: MTGCAPRI_USER_x_OWN_NUMBERS_LIST='12345 12346'

MTGCAPRI_USER_x_INCOMING_NUMBERS

Default Setting: MTGCAPRI_USER_x_INCOMING_NUMBERS='all'

This determines which numbers can connect to the server from outside. Possible values are:

MTGCAPRI_USER_x_INCOMING_NUMBERS_LIST

Default Setting: MTGCAPRI_USER_x_INCOMING_NUMBERS_LIST=''

When using MTGCAPRI_USER_x_INCOMING_NUMBERS='partial' define here the numbers that are allowed to connect to the server from outside. Multiple numbers have to be separated by spaces. Only the specified digits from the beginning of the number are compared.
Example: MTGCAPRI_USER_x_INCOMING_NUMBERS_LIST='0172123456 0511'

This setting allows only connections from the phone number '0172123456 'and from all numbers from the area code '0511 '.

MTGCAPRI_USER_x_OUTGOING_NUMBERS

Default Setting: MTGCAPRI_USER_x_OUTGOING_NUMBERS='all'

This determines which numbers are LOCKED for a connection to the outside.

Possible values are:

MTGCAPRI_USER_x_OUTGOING_NUMBERS_LIST

Default Setting: MTGCAPRI_USER_x_OUTGOING_NUMBERS_LIST=''

When using MTGCAPRI_USER_x_OUTGOING_NUMBERS='partial' define here the numbers that are LOCKED for a connection to the outside. Multiple numbers have to be separated by spaces. Only the specified digits from the beginning of the number are compared.

Example: MTGCAPRI_USER_x_OUTGOING_NUMBERS_LIST='0900 0180'

This setting denies all connections to phone numbers starting with '0900' or '0180'.

MTGCAPRI_USER_x_TIME_XX

Default Setting: MTGCAPRI_USER_x_TIME_XX='0:0 0:0'

Specify the times here at which the user is allowed to use the CAPI (Monday-Sunday).
here some examples:

            '0:0 0:0'     - no time restrictions
            '9:0 17:30'   - usage only from 09:00 to 17:30
            '24:00 24:00' - no usage

1.1.5 Installation Of The mtG-CAPRI-Client-Software

The Client-Installation differs for a Windows95- and a WindowsNT-based system, due to system architecture different files are needed.

When setting up the mtG-CAPRI client the following important point has to be noted:
If there is or was already a CAPI application installed on the computer (in other words, a local ISDN card) and still one of the following dll files is located on the hard disk, these must be removed before mtG-CAPRI installation: CAPI20.DLL and CAPI2032.DLL; both of which are normally located in the system directory.

If this is the case, one of the two following ways has to be followed:

a) Deinstallation of the ISDN card and check if the files capi20.dll and capi2032.dll have been removed.
b) Renaming of these dlls if they are needed again later for the activation of the local ISDN card and hence deactivation of the mtG-CAPRI. Renaming deactivates the drivers of the builtin card.

In the normal case, those files are not overwritten by the Wise installer during installation (beside the version number other manufacturer data is verified). Wise Installation System would not perform the installation correctly.

1.1.5.1 Adapting The Initialisation File capri.ini Of The mtG-CAPRI-Client

The file capri.ini serves for the initialisation of the mtG-CAPRI-Client, i.e. to identify the server to connect to and should have the following content:
[CAPRI]
SERVERNAME = Remote:Thor
PORTNUMBER = 20000
TRACELEVEL = 0
TRACEFILE = c:\tmp\capri.trc
FLOWCTRL = 7

[CAPRI]

The header of the file must not be changed.

SERVERNAME

Behind 'Remote:' the alias of the server for the TCP/IP network has to be placed (corresponding to the entry in the host file and the mtG-CAPRI server file capri.cfg).

PORTNUMBER

This entry must match the one in the capri.cfg server file.

TRACELEVEL

The value of the trace level is normally '0' for the mtG-CAPRI client.
Possible values are:


Important: Setting the trace level to a high value should only be used in the event of an error, since relatively large files may arise and thus the performance of mtG-CAPRI decreases. This may interfere with time-critical applications (eg fax).

TRACEFILE

Path and name of the trace file created by mtG-CAPRI. This entry may be edited (here: capri.trc).

FLOWCTRL

A flow control will be performed when sending data packets.
Possible values are:

Values higher than 7 are possible, but not recommended. The CAPI specification has a value of 7.

1.1.5.2 Testing The Client

The bundled software caprit32.exe (for 32bit environment) and caprit16.exe (for 16bit environment) can be started by double clicking. Normally, the message 'mtG-CAPRI test was successful' will appear. However, if the message 'mtG-CAPRI test failed' appears, the following points should be checked:

A CAPI application (such as T-Online) should only be started from the client, if this test was successfully completed.

1.1.5.3 Error Messages From CAPI Applications

The error messages from CAPI applications (such as T-Online, FritzFax etc.) are made for the case that an ISDN card with corresponding software is installed locally on the respective computer. Hence they are often misleading for mtg-CAPRI.
Examples:

The message 'driver for CAPI 2.0 not installed on this computer' means that CAPI (now in the interaction between client and server) is not functional. With mtG-CAPRI this can for example mean that anything is o.k. on the client but the network connection to the server is interrupted or the server is not running.
T-Online i.e. produces the following error message when the user was not authenticated on the server: 'Cannot initialise DDE (WSOCK32)'.

If the server name is specified incorrectly on the client, I get the message 'Result of the connection setup: ISDN CAPI drivers are missing ... '.
With such 'cryptic' messages it is recommended:

© 2001-2015 The fli4l-Team - 27 January 2015