Copyright: Copyright © 1993-1996 TELES AG Berlin


Contents

Abstract

Installation

CAPI Installation

Configuration file CAPI.INI

CAPI tests and error diagnostics

Hardware Test

Callback Test

BRI Statistics

CAPI Trace (Recording CAPI messages)

Error messages  and trouble shooting

CAPI driver error messages

CAPI error messages

Troubleshooting for callback test

Glossary

ISDN & CAPI Terms


Hardware Tests

There is no hardware test for the TELES.S0/16.3PnP Card.


BRI Statistics

This Windows program belongs to the CAPI drivers and reveals useful information about the status of your ISDN adapter.

BRI statistics offers three different kinds of information:

- Controller Statistics

- Software Statistics

- BRI Packet Statistics


Callback Test

The Windows program Callback Test checks the efficiency of the CAPI drivers together with the installed ISDN hardware.

After clicking on the button Call a connection to your own program will be established, some data will be transmitted and then checked for a correct reception.

- If the test finishes successfully, your hardware and software configuration is OK.

- If the callback test fails, please follow the trouble shooting.

- If all trouble shooting has no effect, use the integrated trace tool and please contact our hotline.


CAPI Installation

If the 32 Bit CAPI drivers are not already installed during the software installation, this can be done afterwards with the CAPI Setup program.

If the option 32 Bit CAPI is checked, the program installs the VxD CAPI and modifies the Windows configuration files WIN.INI and SYSTEM.INI. Restart Windows for changes to take effect.


Trace Layers

The group Layers displays a list of protocols for which the trace tool can be activated.

The list divides into the following layers:

- BRI: hexadecimal output of packets from and to the BRI interface

- H.221: internal messages from the H.221 driver

- B channel:  internal driver messages

- D channel:  internal driver messages

- CAPI functions: all CAPI functions except API_PUT_MESSAGE and API_GET_MESSAGE

- CAPI messages: all CAPI messages except all DATA_B3 messages

- DATA_B3: all DATA_B3 messages

NOTE: Especially the BRI output will slow down the computer's performance.


CAPI Trace

For software developers and interested users the CAPI Trace tool provides the opportunity to follow the protocol running between CAPI drivers and the application.

After starting the trace program all CAPI messages are recorded automatically and displayed in a trace window. The buttons Start and Stop begin and end the recording procedure at any time.

Choose among several trace layers and trace modes.

The displayed information can be removed from the buffer (button Clear buffer) or saved to another file (button Save buffer).

NOTE: If the trace tool is active it may reduce the speed (depending on the selected layers). The CAPI trace should not be in use for regular work.


CAPI driver errror messages

If CAPI errors are detected during the Windows start (loading the CAPI drivers) a short error message appears on the screen.

All error messages with possible causes and solutions are listed below:

Wrong I/O address specified.

Wrong memory address specified.

Wrong controller specified.

Wrong IRQ specified.

Couldn´t map memory.

Couldn´t virtualize IRQ.

Cannot initialize ISDN adapter correctly.

Another CAPI is active and cannot be deinstalled.

Wrong adapter type specified.

Cannot open CAPI.INI or no controller specified.

Cannot open CAPI.INI or no D channel protocol specified.

Cannot open CAPI.INI or no IRQ specified.

Cannot open CAPI.INI or no adapter type specified.

No adapter found.

Cannot open CAPI.INI or no I/O address specified.

Cannot open CAPI.INI or no memory address specified.

Cannot open WIN.INI or no entry for CAPI.INI.


CAPI errors

CAPI errors:	Message:

Mode of operation not supported by hardware:

3201	General controller error

3202	Non-unique LISTEN_REQ

3203	Function not supported

3204	PLCI inactve

3205	NCCI inactive

3206	B channel protocol, layer 2 (B2) not supported

3207	Can´t select B2 protocol now

3208	B channel protocol, layer 3 (B3) not supported

3209	Can´t select B3 protocol now

320A	Illegal DLPD parameters

320B	Illegal NCPD parameters

320C	Illegal NCPI parameters

320D	Data length not supported

Network errors:

3301	D channel layer 1 setup error

3302	D channel layer 2 setup error

3303	B channel layer 1 setup error

3304	B channel layer 2 setup error

3305	D channel layer 1 shutdown

3306	D channel layer 2 shutdown

3307	D channel layer 3 shutdown

3308	B channel layer 1 shutdown

3309	B channel layer 2 shutdown

330A	B channel layer 2 shutdown

330B	B channel layer 2 reestablished

330C	B channel layer 3 reestablished

3400, 3480	Normal disconnect, no cause given by network

3401, 3481	Invalid CR (Call Reference) value

3403, 3483	Bearer service not implemented

3407, 3487	Unknown caller identity

3408, 3488	Caller identity already suspended

340A, 348A	No channel available

340F, 348F	Disconnect

3410, 3490	FAC code unknown in this network

3411, 3491	Requested service rejected

3420, 34A0	Outgoing calls barred

3421, 34A1	User access busy

3422, 34A2	CUG mismatch

3423, 34A3	Nonexistent CUG

3425, 34A5	Invalid or unknown destination

3429, 34A9	Temporarily not available

3435, 34B5	Destination not obtainable

3438, 34B8	Number changed

3439, 34B9	Out of order

343A, 34BA	No user responding

343B, 34BB	User busy

343D, 34BD	Incoming calls barred

343E, 34BE	Call rejected

3458, 34D8	Invalid destination address

3459, 34D9	Network congestion

3460, 34E0	Call ID incomplete

3470, 34F0	Local procedure error

3471, 34F1	Remote procedure error

3472, 34F2	Remote suspended

347F, 34FF	Local reject of User to User info


ISDN & CAPI Terms

1TR6 protocol

B channel

Basic access

Bundle

CAPI (Common ISDN API)

D channel

DSS1

ETSI

EAZ (Endgeräteauswahlziffer)

H.221

HDLC

ISDN (Integrated Services Digital Network)

ISO 8208

MSN (Multiple Subscriber Number)

Primary rate access

S2M

BRI

V.110


Configuration file CAPI.INI

The CAPI configuration file is in its size corresponding to known Windows *.INI files.

All applicable entries incl. valid and default parameters are listed below:

[BRI/CAPI]

Controller = ...	(necessary)

Version = ...	(optional)

Interrupt = ...	(optional)

DChannel = ...	(necessary)

IgnoreCardService =...	(optional)

LoadVxDCAPI = ...	(optional)

LoadBundle = ...	(optional)

LoadH221 = ...	(optional)

LoadISO8208 = ...	(optional)

LoadV110 = ...	(optional)

OwnNumber = ...	(optional)

OwnEAZ = ...	(optional)

[ControllerX]

CardType = ...	(necessary)

IRQ = ...	(possibly necessary)

IOAddr = ...	(possibly necessary)

MemAddr = ...	(possibly necessary)

NOTE: The CAPI drivers access the Windows configuration file WIN.INI to locate the CAPI.INI. Therefore the following section has to be included in WIN.INI, if the software has been installed into the directory C:\TELESCOM:

[ISDN Applications]

capi=c:\telescom\capi.ini

These setttings were made during the installation of the software.


Wrong card type specified.

Wrong adapter type specified.

An unknown adapter type has been detected in the configuration file CAPI.INI.

Valid parameters for

CardType=	BRI/16	for the TELES BRI/U


No card found.

The ISDN adapter defined in the CAPI configuration file CAPI.INI cannot be detected.

Please check the adapter configuration: memory address, I/O address and IRQ.

In case there is a memory conflict make sure no other hardware is using the configured addresses for the ISDN adapter.

The memory section excluded for this adapter should not be used by a memory manager like EMM386 or activated in the BIOS setup as shadow RAM.


Cannot open CAPI.INI or no D channel protocol specified.

The CAPI configuration file CAPI.INI does not contain a reference to the installed D channel protocol. The following section has to be included if, for example, the drivers should be configured for an Euro-ISDN access.

[BRICAPI]

DChannel=dss1

All applicable D channel protocols are listed in the topic CAPI.INI.


Cannot open CAPI.INI or no IRQ specified.

The CAPI configuration file CAPI.INI does not contain a reference to the configured interrupt. The following section has to be included if, for example, the drivers should be configured for a hardware interrupt 12.

[Controller0]

IRQ=12


Cannot open CAPI.INI or no memory address specified.

The CAPI configuration file CAPI.INI does not contain a reference to the excluded memory address for the ISDN adapter. The following section has to be included if, for example, the drivers should be configured for a TELES BRI/U adapter configured for the memory address d000.

[Controller0]

MemAddr=d000

The number of applicable memory addresses depends on the installed ISDN adapter. The list of valid memory addresses is included in the topic CAPI.INI.


Cannot open CAPI.INI or no controller specified.

The CAPI configuration file CAPI.INI does not contain a reference to the installed ISDN controller. The following section has to be included if, for example, the drivers should be configured for two ISDN adapters with controller numbers 0 and 1.

[S0CAPI]

Controller=0,1

[Controller0]

...

[Controller1]

...


Cannot open CAPI.INI or no card type specified.

Cannot open CAPI.INI or no adapter type specified.

The CAPI configuration file CAPI.INI does not contain a reference to the installed ISDN adapter. The following section has to be included if, for example, the drivers should be configured for a TELES BRI/U adapter.

[Controller0]

CardType=BRI/16

All applicable adapter types are listed in the topic CAPI.INI.


Cannot open WIN.INI or no entry for CAPI.INI.

The Windows configuration file WIN.INI does not contain a reference to the CAPI configuration file CAPI.INI. The following section has to be included in WIN.INI if, for example, the drivers have been installed to the directory C:\TELESCOM:.

[ISDN Applications]

capi=c:\telescom\capi.ini


Couldn´t virtualize IRQ.

The interrupt defined in the configuration file CAPI.INI is already used by another hardware device. Valid IRQs can be taken from the ISDN adapter manual.

To configure the ISDN adapter for a free interrupt, open the CAPI Setup module.


Wrong IRQ specified.

An invalid interrupt for the installed ISDN adapter has been detected in the configuration file CAPI.INI.

This IRQ depends on the installed ISDN adapter type. Valid IRQs for the appropriate adapter type can be taken from the manual.


Wrong memory address specified.

An invalid memory address for the installed ISDN adapter has been detected in the configuration file CAPI.INI.

This address depends on the installed ISDN adapter type. Valid memory addresses for the appropriate adapter type can be taken from the manual.


Wrong I/O address specified.

An invalid I/O address has been detected in the configuration file CAPI.INI.

This address depends on the installed ISDN adapter type. Valid I/O addresses for the appropriate adapter type can be taken from the manual.


Wrong controller specified.

An unknown entry for the installed ISDN adapters has been detected in the configuration file CAPI.INI.

Controller=...  must contain a list of numbers corresponding to the number of installed ISDN adapters.

Example:

Controller = 0	(one ISDN adapter installed),

Controller = 0,1	(two ISDN adapters installed)


Couldn´t map memory.

The ISDN adapter could not be mapped to the memory address defined in the configuration file CAPI.INI. This memory address depends on the installed adapter type. Valid addresses can be taken from the ISDN adapter manual.


BRI Statistics - Controller

All details of the installed ISDN adapter are summarized in the group Controller.

The ISDN adapter type, the serial number (if existent), the configured interrupt, I/O address and memory address (depending on adapter type) are displayed.


BRI Statistics - Software

The group Modules contains all drivers/protocols loaded for several ISDN applications.

The following modules can be listed:

BRI	- Hardware control,

hdlc	- Layer 2 protocols,

dss1	- Euro ISDN D channel protocol DSS1 (ETSI),

1tr6	- German D channel protocol 1TR6,

capi	- CAPI module,

bundle	- B channel bundling,

h221	- H.221 framing,

iso8208	- EuroFiletransfer protocol,

v110	- Bitrate adaption based on V.110

For a minimum configuration, the modules BRI, hdlc, 1tr6 or dss1 and capi should be listed above. If not, the CAPI drivers are not installed completely.


BRI Statistics - BRI packets

The group BRI packets displays the counters for sent and received packets on the D and B channels.

The counters are updated every second.

 A click on the button Clear will reset all counters.


1TR6
1TR6 protocol

1TR6 is the national German D channel protocol using EAZs for different ISDN applications.

In the near future, 1TR6 will be replaced by the European standard protocol ETSI (DSS1).


ETSI

ETSI (DSS1) is the name of the European D channel standard protocol for ISDN. The 1TR6 protocol used in Germany today is currently being replaced by ETSI.

One major difference between ETSI and 1TR6, which may have implications for application programs, is the replacement of EAZ by MSNs.


DSS1
DSS1 (European Digital Subscriber Signaling Protocol No.1)

European term for the protocol ETSI.


B channel

The B channels carry all useful information. Every ISDN basic rate interface provides two B channels with 64 kBit/s bandwidth each. A primary rate interface has 23 B channels (in the US, 30 B channels in Europe) with 64 kBit/s each.


D channel

The D channel (control channel) carries all signaling and protocol information with a transmission rate of 16 kBit/s for a basic rate interface.


CAPI (Common ISDN API)

The Common ISDN Application Program Interface is a valid standard (mainly in Europe). It provides a uniform software interface for all applications to access the ISDN hardware.

Besides the current CAPI 1.1, CAPI 2.0, configured for the international market, is increasingly important.


MSN (Multiple Subscriber Number)

In Euro-ISDN with the D channel protocol ETSI (DSS1) all EAZs are replaced by MSN which does not necessarily differ in the last digit.


EAZ (Endgeräteauswahlziffer)
EAZ

EAZ is a short-cut for the german term "Endgeräteauswahlziffer", which can be translated as "Device Switching Digit". In German ISDN protocol (1TR6), each BRI number in a call is extended by a random EAZ, which is delivered to all devices with an incoming call. Devices can be configured to answer only calls for some specific EAZ.

Since the CAPI (Common ISDN API) was originally designed for 1TR6, it uses the EAZ for selecting the application to handle a particular incoming call. The EAZ however is not existent in other ISDN protocols. Multiple Subscriber Numbers (MSNs) are supported instead, which not necessarily differ only in the last digit. For this reason, CAPIs for these ISDN protocols support a mapping of entire MSNs to single digits, which in principle behave like EAZ in the 1TR6 CAPI.


Basic access
Basic Rate Interface

The ISDN basic access provides two data (B-) channels with a capacity of 64 kbt/s each and a control (D-) channel with 16 kbt/s for the transmission of protocol and signaling information.

Up to 8 devices (incl. PC) can be connected to the basic rate interface BRI.

The B channels can be bundled to a maximum capacity of 128 kbt/s.


Primary rate access
Primary rate interface

The ISDN primary rate interface has 23 data (B-) channels with a capacity of 64 kbt/s each and a control (D-) channel with 64 kBit/s as well for the transmission of protocol and signaling information.

Normally a PABX is connected to the primary rate interface S2M.

The B channels can be bundled to a maximum capacity of 1920 kbt/s.


S2M

ISDN primary rate interface including 23 B channels with 64 bit/s each and one D (control) channel with 64 kbt/s.


S0
BRI

ISDN basic rate interface including two B channels with 64 kBit/s each and one D (control) channel with 16 kbt/s.


V.110

V.110 is a standard of the CCITT and defines the protocol for adapting bit rates of 600, 1200, 2400, 4800, 7200, 9600, 12000, 14400, 19200, 48000 and 56000 bps.

V.110 is necessary for connections to other sites with transmission rates different from ISDN (e.g. WinCOM connections to modem partners).


ISDN (Integrated Services Digital Network)

Communication technology providing a digital network for different services (telephony, videoconferencing, facsimile, data transfer,etc.). ISDN (and the common European standard Euro ISDN) is based on various transmission media such as coaxial cables, fiber optics, satellites and good old copper cables as well.


Trouble Shooting
Trouble Shooting for callback test

All error messages with possible causes and solutions are listed below:

Data transmission errors detected..

Requested service ´data transmission´ is not available..

The called party number has changed.

The ISDN adapter is not connected to the BRI bus.

The ISDN adapter has been disconnected from the BRI bus.

Another application already listens for incoming calls.

Wrong called party number.

Invalid number format..

Outgoing calls barred..

Incoming calls barred.

No B channel available (busy).

No B channel available (no channel).

No user responding (wrong address or one of the B channels is not available).

Network congestion.

Call rejected.


Requested service ´data transmission´ is not available.

The service data transmission is not active at your interface. No connection using that service can be established.

If you are connected to a PABX it has to be reconfigured to enable data transmission.

If you are directly connected to the ISDN please contact your local Telecom to activate this service.


Data transmission errors detected.

The data received does not correspond to the data sent.

If this error occurs constantly, your basic rate interface or the ISDN switch might be the problem. If your interface is working properly in all other cases, please contact our hotline.


Controller
Controller = ...

This entry lists all numbers corresponding to the installed ISDN adapters. The first adapter counts as "0", the second as "1". For every controller X listed above has to be defined an own section [ControllerX] with its individual parameters.

Example:

Controller = 0	(one ISDN adapter installed),

Controller = 0,1	(two ISDN adapters installed)


The called party number has changed.

The called number is not valid anymore.

Please enter your own correct number and try again.


The ISDN card is not connected to the S0 bus.
The ISDN adapter is not connected to the BRI bus.

The ISDN adapter gets no response from the BRI interface.

Check if the cable is set properly on both sides of the connection (ISDN adapter at one side and the interface on the other).

If the ISDN adapter is working properly but the test still fails, then maybe your cable is defective.


The ISDN card has been disconnected from the S0 bus.
The ISDN adapter has been disconnected from the BRI bus.

The link between ISDN adapter and BRI interface has been broken during a connection.

Check if the cable is set properly on both sides of the connection (ISDN adapter at one side and the interface on the other).

If the ISDN adapter is working properly but the test still fails, then maybe your cable is defective.


Another application already listens for incoming calls.

There is another application running that listens for incoming calls. If conflicts with other applications occur, the callback test will not work properly.

Close all other applications and try it again.


Version
Version = ...

This string displays the actual CAPI standard version (CAPI 1.1 vs. CAPI 2.0). At present the valid parameter has to be set on 11.

Valid parameters:	11	(CAPI 1.1),

20	(CAPI 2.0)

e.g.: Version = 11


Call rejected
Call rejected.

The outgoing call was rejected from the remote site.

The testing application is configured to accept every call, therefore the call number must have been wrong.

Enter the correct call number.


Network congestion.

The PABX or the ISDN switch is temporary overloaded and cannot establish a connection.

Try it again later on.


CardType
CardType = ...

CardType is a string identifying the ISDN adapter type.


DChannel
DChannel = ...

The string D Channel defines the protocol for the control (D) channel.

Valid parameters:	etsi	(Euro-ISDN access),

1tr6	(1TR6 access within Germany)

ct1	(CT1 in Belgium)

vn3	(VN3 in France)

 nt	(Northern Telecom in the USA)

at&t	(AT&T in the USA)

siemens	(Siemens in the USA)

e.g.: D Channel = etsi


Interrupt
Interrupt = ...

This parameter defines the software interrupt for accessing the CAPI out of DOS windows.

Normally the interrupt is set on 0xf1. If other applications or driver already use this interrupt and cannot be reconfigured, change the parameter above.

Valid parameters:	a hexadecimal figure defining a valid interrupt

e.g.:	Interrupt = f2	(Software interrupt 0xf2)

Default parameter:   f1


IRQ
IRQ = ...

IRQ defines the hardware interrupt used for the ISDN adapter.

This entry is necessary for all ISDN adapters except PCMCIA adapters working with CardCervice drivers.

Valid parameters:	a decimal figure from 2 up to 15 (depending on the ISDN adapter)

e.g.: IRQ = 12	(Interrupt 12 will be used),

        IRQ = 5	(Interrupt 5 will be used)


Callback Trace

If all attempts fail to result in a successful callback test, use the integrated trace tool to display error messages of the CAPI drivers.

For tracking down any CAPI messages, check the options CAPI Trace and/or BRI Trace.

The CAPI Trace records all messages being sent from and to the CAPI interface.

The BRI Trace records all messages being sent from and to the BRI interface.

All trace protocols are saved to the file TRACE.TXT in your installation directory. This file is needed by our hotline for further trouble shooting.


Invalid number format.

The PABX or ISDN switch does not accept the call number format. This error message indicates that maybe not all number formats are accepted.

The call number format can be set to a fixed value by editing the entry

FixedAddressType = ....

Find the number format accepted by your PABX and configure the entry above.


Outgoing calls barred.

A barrier for outgoing calls is active at your interface.

Reconfigure your access or PABX to disable the barrier and try again.


Incoming calls barred.

A barrier for incoming calls is active at your basic access.

Reconfigure your interface or PABX to disable the barrier and try again.


No B channel available (busy).

Only one B channel was available during the test.

Check if both B channels are available and try it again.


IOAddr
IOAddr = ...

This hexadecimal address defines the I/O address for the ISDN adapter. Valid parameters for the TELES BRI/U are: d80, e80, f80


No B channel available (no channel).

There are no B channels available at your interface or a temporary bottleneck in the network might be the cause.

Make sure that two B channels are available and try again.


No user responding (wrong address or one of the B channels is not available).

The outgoing call is not accepted by the remote site.

Either the call number is wrong or one of the B channels is not available.

Make sure that two B channels are available, enter your own correct call number and try again.


MemAddr
MemAddr = ...

This hexadecimal address defines the memory section excluded for the ISDN adapter. This entry is necessary for the following ISDN adapters: BRI/16, BRI/AB, BRI/MC and PCMCIA. For the last one this entry is not necessary if CardService drivers are installed.

Valid parameters:	a000, a100, a200 usw. bis df00

e.g.:  MemAddr = d000,

        MemAddr = cc00.


IgnoreCardService
IgnoreCardService = ...

This boolean parameter (true/false) defines the CardService drivers to be used for PCMCIA cards.

If this parameter is set TRUE, the hardware will be accessed directly. Not all laptops support this function, so the CardService drivers should be active.

Valid parameters:	TRUE    (Hardware is accessed directly),

FALSE  (Hardware is accessed via CardServices)

e.g.: IgnoreCardService = TRUE

Default parameter:   FALSE


LoadVxDCAPI
LoadVxDCAPI = ...

This boolean value (true/false) indicates if the Vxd CAPI drivers should be loaded or not.

Use this entry to quickly activate or deactivate the Windows CAPI without modifying the file SYSTEM.INI.

Valid parameters:	TRUE    (32 Bit CAPI is active),

FALSE  (32 Bit CAPI is deactivated)

e.g.: LoadVxDCAPI = TRUE

Default parameter:      TRUE


LoadBundle
LoadBundle = ...

This boolean (true/false) value indicates if the bundle driver should be loaded or not.

Channel bundling is necessary for data to be transferred at 128 kBit/s.

Valid parameters:	TRUE    (Bundle module is active),

FALSE  (Bundle module is deactivated)

e.g.: LoadBundle = TRUE

Default parameter:  TRUE


LoadH221
LoadH221 = ...

This boolean (true/false) value indicates if the driver module for the H.221 framing should be loaded or not.

H.221 has to be installed for audiovisual connections (e.g. VISION).

Valid parameters:	TRUE    (H221 module is active),

FALSE  (H221 module is deactivated)

e.g.:   LoadH221 = TRUE

Default parameter: TRUE


LoadISO8208
LoadISO8208 = ...

This boolean value (true/false) indicates if the driver module for the EFT based on ISO 8208 should be loaded or not.

ISO 8208 is necessary for the European standard filetransfer.

Valid parameters:	TRUE    (ISO8208 module is active),

FALSE  (ISO8208 module is deactivated)

e.g.: LoadISO8208 = TRUE

Defaul parameter:   TRUE


LoadV110
LoadV110 = ...

This boolean value (true/false) indicates if the driver module for adapting bit rates based on V.110 should be loaded or not.

V.110 is necessary for connections to remote sides with other transmission rates than ISDN .

Valid parameters:	TRUE    (V110 module is active),

FALSE  (V110 module is deactivated)

e.g.: LoadV110 = TRUE

Default parameter:   TRUE


OwnNumber
OwnNumber = ...

This string indicates your own call number without area code. OwnNumber is used for the callback test.

NOTE: If 1TR6 is installed, the EAZ will be indicated as extra figure.

Valid parameters: all strings containing figures only.

e.g.: OwnNumber = 3992800,

        OwnNumber = 5557263389


OwnEAZ
OwnEAZ = ...

If you use your own call number as EAZ (1TR6 protocol installed) the figure OwnEAZ will be added to that number.

Valid parameters: all figures

e.g.: OwnEAZ = 0

        OwnEAZ = 5


Abstract

CAPI drivers are part of every standard ISDN adapter. These drivers control the hardware and provide a standard interface for all ISDN applications (Common ISDN API).

The 32 Bit CAPI (VxD CAPI) runs in the Windows-enhanced mode, offering a range of advantages:

- the CAPI works with the 32 Bit protected mode, completely

- no need to start TSR programs under DOS

- no DOS memory needed for CAPI drivers

- the CAPI is available in all Windows applications, and in DOS applications running in DOS/Windows.

The 32 Bit CAPI supports Windows 3.1, WfW and Win 95 as well.


Bundle

Protocol for bundling the two B-channels to one data channel provides a maximum bandwidth of 128 kBit/s.


H.221

The standard H.221 defines the frame structure for audiovisual transmissions from 64 to 1920 kbt/s.


HDLC

HDLC (High Level Data Link Control) defines a layer 2 protocol for the transmission of digital information.


ISO 8208

ISO protocol standard for layer 3 connections on the B-channel. This protocol is required for EuroFileTransfer (EFT).


Trace Modes

Choose between two different modes of recording CAPI messages: buffered or direct.

In the buffered mode all recorded data will be saved to an internal buffer. After clicking on the button, Stop all messages will be displayed in the listbox. This mode is less time-critical than the other and should be used especially for BRI traces.

The direct mode displays the recorded messages simultaneously to the ongoing procedures. It will operate more slowly than the buffered mode, but all CAPI messages can be followed directly on screen.


Cannot initialize ISDN adapter correctly.

The hardware cannot be accessed properly. Please check your ISDN adapter using the test tools under DOS.

If no errors are detected, check the adapter settings, memory address, I/O address and IRQ.


Another CAPI is active and cannot be deinstalled.

While starting Windows, another CAPI driver (DOS CAPI, e.g. TSR driver) was detected. Before loading the VxD CAPI with Windows, the DOS CAPI driver has to be removed.


Cannot open CAPI.INI or no I/O address specified.

The CAPI configuration file CAPI.INI does not contain a reference to the configured I/O address. The following section has to be included if, for example, the drivers should be configured for a TELES BRI/U adapter with jumpers settled for the I/O address d80.

[Controller0]

IOAddr=d80

All applicable I/O addresses are listed in the topic CAPI.INI.


Wrong called party number.

The number dialed is invalid. This error message is similar to the phone announcement. "The dialed number is incorrect" when using the telephone.

Enter the correct own number and try again.