FEC Onlineservices
CAPI basic configuration of a bintec router for using Remote CAPI, effected via FCI
There are only a few steps required to configure a bintec router for CAPI applications.

Preliminary notes
CAPI 2.0 has been implemented in bintec devices since firmware release 6.3.4. In contrary to CAPI 1.1, it is now no longer necessary to assign a “CAPI” service to a MSN. The incoming call is now being transmitted to the router-internal CAPI server, if there is no adequate MSN entry available.

Starting from firmware release 7.9.1, the CAPI server can also be configured via FCI on all bintec routers. That procedure is being described using the example of a bintec RT1202, version 7.9.5 patch 3. Other bintec routers with comparable software versions can be configured identically.

Router configuration

MSN settings

For remote access, the router is able to accept all calls with its internal ISDN login if the MSN configurations stays empty. This means that if you intend to forward incoming calls from the ISDN to the CAPI server, at least one dummy-entry would be necessary.

You can add the dummy-entry at Physical Interfaces -> ISDN Ports -> MSN configuration:

CAPI server settings

The CAPI server is accessible via “local services –> CAPI server”. The tab “user” contains the login data (user name, passwords) for the CAPI clients. A standard user without password has already been created in the original state.
You can activate the server functionality at the tab “options”.

CAPI client configuration on a windows PC
In order to enable the communication of a PC (e.g. a fax server) with a router via Remote CAPI, funkwerk BRICKware must be installed. It contains the programme “CAPI configuration”.

Please click “Use these values” after entering the CAPI server address (router IP) and all other data.

Checking the functionality
All used ISDN lines have to be connected and fully functional!

Please activate the debug mode on the bintec in order to check the basic communication between PC and router. Alternatively, please select the internal protocol via FCI (“maximum message level” has to be changed to “debug”).

By clicking on “More devices (CAPI2032.DLL)", an overview of all available controllers can be shown. Then please confirm “Test….’”. The following successful messages will be shown afterwards:

rt1202:> debug capi&
12:58:40 DEBUG/CAPI: Register from port 3534
12:58:40 DEBUG/CAPI: DBG(013984210) APPL-1:04 capiclose
12:58:40 DEBUG/CAPI: Register from port 3535
12:58:40 DEBUG/CAPI: DBG(013984218) APPL02:05 capiclose


© 2013 bintec elmeg GmbH