Features and work currently in the queue for implementation:
============================================================

- Implement a CAPI device driver for the active Eicon DIVA Server boards. The
  daic driver was a first step in this direction. A lot of code should be
  reusable. But at least the same amount must be added.



Work currently in progress by other people:
===========================================

- Jan Stocker: Make hylafax work on FreeBSD and its CAPI manager. See
  <http://www.shellbang.org>.
- Jan Stocker: Make Asterisk work on FreeBSD and its CAPI manager.



Features and work currently not planned:
========================================
Note: Some of these points are very important. But either no (hardware and/or
      time) resources or knowledge is available for them.

- libcapi20: Add a Linux compatibility layer for easy porting of Linux
  applications. This layer will provide the same function prototypes as the
  Linux CAPI specification and the library will provide the necessary
  compatibility functions. Note that this will not introduce binary
  compatibility, but only source code compatibility.

- Implement a CAPI driver for passive ISDN boards, e.g. the AVM Fritz! boards.
  This driver should implement the necessary B-channel protocols transparent,
  HDLC and X.75. T.90 and ISO 8208 may be implemented later. The X.75 protocol
  should be implemented as a loadable extension module for the CAPI manager.
  So other drivers may also make use of this B-channel protocol. This should
  lead to a general interface to register B-channel protocol modules for all
  three layers. These modules could be selected by CAPI driver modules to form
  the B-channel protocol stack and even extend the protocols natively
  supported by active boards.

- Implement support for DTMF recognition for the daic driver (or better the
  driver for passive boards), the boards do not provide support for this
  feature. DTMF support should be implemented as a loadable extension module
  for the CAPI manager. This should also result in a general interface for the
  CAPI manager to register arbitrary data filter modules. These modules could
  be selected by CAPI driver modules as a reaction on specific CAPI messages.
  But this is not to confuse with an interface to register B-channel protocol
  modules.

- Complete CAPI trace decoding in "capitrace". Not all CAPI message constructs
  are currently decoded. This is especially true for the whole bunch of
  supplementary services, line interconnect and echo cancellation structures.

- Divide some of the existing manual pages into multiple smaller ones. Namely
  capi20.3, kcapi.9 and kcapi-drv.9 should be splitted into separate files for
  each CAPI function.

- Test the AVMAIC driver with the boards AVM-T1 ISA and AVM-T1 PCI.
  Unfortunately the author has no access to these types of active AVM boards.

- Implement the S2m part for the daic driver for the Eicon (Diehl in original)
  boards S, Sx, SCom, Quadro and S2m. Its logical interface is very similar to
  the S0 boards, but its physical interface is different.

- Write device drivers for other active hardware (e.g. Hypercope boards).

- Implement B-channel protocol extension modules for T.90 and ISO 8208. This
  should be done after the implementation of a CAPI driver for passive boards
  and of an X.75 stack that will provide an implementation example for
  B-channel protocol extension modules.

- Create an euro file transfer program similar to AVM connect or Fritz!Data.

- Create another LAN-CAPI to provide CAPI support to other machines without
  ISDN hardware of their own. Clients should include all MS-Windows variants
  and BSD systems (list is not closed here). If possible the protocol should be
  compatible with Bintecs remote CAPI. But it may also implement better
  separation of the connections, e.g. if one PLCI/NCCI is blocked, the
  CAPI_PUT_MESSAGE call shall not block other calls running between the same
  client and server.

- Implement fax-g3 support for passive boards or active boards without built-in
  support for it. Don't known if someone has enough knowledge for this, most
  likely not.

