If you like BoxMatrix then please contribute Supportdata, Supportdata2, Firmware and/or Hardware (get in touch).
My metamonk@yahoo.com is not reachable by me since years. Please use hippie2000@webnmail.de instead.
Property:CAPI (lexicon)
| BoxMatrix >> Lexicon >> Telephony-Terms >> CAPI | @ BoxMatrix - IRC-Chat - Translate: de es fr it nl pl |
| News | Selectors | Models | Accessories | Components | Environment | Config | Commands | System | Webif | Software | Develop | Lexicon | Community | Project | Media |
| Computer | FRITZ | I18N | Telephony | Smarthome | Internet | Protocols | Multimedia | Formats | Hardware | Software | Research |
 |
Name-Collision - multiple objects in this wiki use the name CAPI!
|
Term
| Term: | CAPI (lexicon) | Wiki | Freetz | IPPF | whmf | AVM | Web |
| Short for: | Common ISDN Application Programming Interface | ||||||
| Location: | Lexicon >> Telephony-Terms | ||||||
| Weblinks: | Wikipedia.int - Wikipedia.de - capi.org - CAPI-2.0-1 - CAPI-2.0-2 - CAPI-2.0-3 - CAPI-2.0-4 | ||||||
| Description: | Programming interface to ISDN hardware | ||||||
Goto: FRITZ!OS - SMW-Browser
Details
CAPI is a standardized API (programming interface) for accessing all features of ISDN hardware.
It was designed to support ISDN software to run on ISDN hardware fopm arbitary Vendors.
Each Vendor just has to provide a CAPI driver for his hardware, and all software could use it.
CAPI development started in 1989 as a collaboration of the german ISDN manufacturers AVM, Systec, Stollmann.
In 1991 they formed CAPI Association e.V. and further Vendors joined, like the german Bundespost (today Telekom).
The current version of the specification is CAPI 2.0 5th Edition (2009) and consists of 4 parts.
These cover 1) Standard / 2) Operating Systems / 3) Supplementary Services / 4) Interoperability.
For their ISDN+DSL-Cards AVM mainly offered CAPI drivers for Windows, for some models also for MS-DOS, Linux, Netware
and OS2. See the ISDN-Drivers overview.
Some dates and links (german):
FRITZ!OS
In FRITZ!OS all kinds if Telephony internally uses CAPI.
Kernel
For early FRITZ!OS AVM used their Linux ISDN-Drivers for the FRITZ!Card Classic (passive) and ISDN-Controller B1 (active):
- fcclassic.ko - fw 1.120 - 3.37
- capi.ko - fw 1.120 - 4.28
- capidrv.ko - fw 1.120 - 4.28
- capifs.ko - fw 1.120 - 4.28
- capiutil.ko - fw 1.120 - 4.27
- kernelcapi.ko - fw 1.120+
For a short time they added a CAPI4Linux driver:
- capiconn.ko - fw 4.14 - 4.45
For the 5188 they used a CAPI-over-UDP remote CAPI driver:
Today they use:
- capi_oslib.ko - fw
- capi_codec.ko - fw 4.44+ - Telephony Codecs, also used for RTP
Userspace
For some older models AVM added:
- capichan.so - fw 3.42 - 3.45
The main CAPI interface was and is libcapi20:
- libcapi20.so - fw 1.120+ - accesses /dev/capi20 or /dev/rcapi20
Current OS parts which use libcapi20:
- capiotcp_server - fw 1.120
- telefon - fw 1.120
- voipd - fw 1.120
- libfon.so - fw 4.03+
- libtamconf.so - fw 4.21+
- dtrace - fw 4-28+
- libtelcfg.so - fw 4-28+
- faxd - fw 4.44+
- libtam.so - fw 4.55+
- libfaxsend.so - fw 5.55+
Older dependencies to libcapi20:
- sip-emu - fw 1.120 - 3.14
- capichan.so - fw 3.42 - 3.45
- libdect.so - fw 4.21 - 4.77
- dect_update - fw 4.30 - 4.77
- dectwe - fw 4.30 - 4.77
- csvd - fw 4.80 - 6.110
- potscalltest - fw 5.27
- libfaxsendlua.so - fw 5.27 - 5.57
