Only internal cards that plug into an ISA or PCI slot are
supported. ISA Plug&Play cards are also supported, but need some additional
manual configuration by means of the isapnptools
. For details on the
configuration see question
config_pnp.
Internal cards may be active, semi-active, or passive. Unless you have paid big money, assume you have a passive card. More about the difference: see question hardware_activepassive.
Right now there is a driver for all passive card with certain Siemens
chipsets (HiSax driver). Have a look at the README.HiSax
that comes with
the driver for the most up to date information on supported cards and which
parameter to pass to Hisax.
Here the status from 4th September 1999 (constantly improving):
cat /proc/pci
. You have HFC-PCI if you have a line
saying "Master capable" for your card.The following cards are definitely not supported and will probably never be supported, since the manufacturers have not released the specifications for their very proprietary hardware/protocols:
An active ISDN card handles most of the ISDN connection protocols (dialing, accepting calls, etc.) itself. The card includes a kind of minicomputer with its own software (firmware). With a passive card, the computer in which the card is installed has to perform these functions.
In principle, both types are supported by isdn4linux. However, since active cards have non-standard interfaces, a driver can only be made when the producer publishes the specifications for the interface. Also, the card's firmware needs to be made freely available. In contrast, many passive cards share the same chipset. Therefore many passive cards can be supported once a driver supports this one chipset.
These active cards are currently supported by an individual driver:
The developers suggest using ELSA cards. ELSA has made their specifications available to the developers, and provided a lot of support, resulting in an excellent driver. Also, their cards are certified for usage in Germany, see question country_certified.
If you want to buy an active card, then the developers would recommend the PCI Server from Eicon. The reason is that it can fax on both channels with AT class 2 commands, and includes a V.90 modem. The AVM B1 works also very well, but can only fax on one channel. The Hypercope cards have also been reported to work very well, servicing all available channels for faxing. However, they require a hardware update for faxing and their linux driver is fairly new.
If faxing is important for you, but you don't want to spent the money for an active card, then a card with ISAR chipset may work well for you, e.g. Sedlbauer Speedfax+ (in Germany you may be able to buy it at Conrads).
No, but it doesn't need to. Terminal adapters are designed to behave either like a modem or like a network card. Linux already supports both modems and network cards without isdn4linux - so no special ISDN driver is necessary (which usually greatly simplifies the configuration).
For any details in this direction have a look at the excellent cable FAQ, which can be found at least in a German version at: http://www.in-berlin.de/User/scorpio/faqkabel.html.
On many PCI boards, interrupt 12 is often used by a PS/2 mouse (even though you may not have any or the IRQ is not activated for it). It may be used even when you have no PS/2 port. Interrupt 15 is also often used by the second IDE bus (even when you are not using it or the IRQ is not activated for it). Even though one thinks that some IRQs are available they are still somehow reserved by the BIOS. Good IRQs to try are always IRQ 5 and IRQ 9. Without mice or modems you could also try 4 and 3, which works even on very exotic boards.
At least these S2M cards have been reported to work:
At least these PCMCIA cards have been reported to work:
Yes, this works nicely. However, make sure to compile the kernel and all
modules with option SMP
. If you run into problems when both CPUs try to
handle the same IRQ, try to boot with noapic
.
Yes, most cards should run with isdn4linux on a DEC Alpha. Many cards have been reported to work with the HiSax driver. Also the active ICN card has been reported to work.
In principle, hisax works with the built-in ISDN adapter of a Sparc-Station-LX and a Sparc-Station-10, with development kernels version 2.3.x. The code for Sun is only available there. Please be aware that the code of the latest developments can not be compiled for 32 bit machines like all sun-4m machines.
Audio works, but not well; ISDN works, but randomly crashes the machine. The author of dbri.c has stopped active work on it, but made a copy of the DBRI data sheet available at: http://www.freesoft.org/Linux/DBRI for anyone who wants to fix the remaining glitches (status as of Jan 10, 2000).
Yes, most cards should work. However, at least the AVMFritz!PCI card won't work, due to the different Endian format for 32bit B-channel data on the PPC.
In any case, you may also get a terminal adapter (= external ISDN "modem"). Since then you don't need isdn4linux (see question hardware_external), this is not covered here any further.
It depends on the availability of slots, interrupts/IO addresses in your computer as well as the possibilities of the ISDN card. Most passive cards are limited by the supported IO addresses (e.g.: Teles 16.x: only 3 addresses are legally possible: 0xf80, 0xd80, 0xe80), and the total usage of interrupts (every card needs one).
To use more cards, the ICN card may be your choice. It has no interrupts, a more flexible port configuration and the driver places the shared memory area of all ICN cards at the same address. The card memory is shown only as needed. Therefore, one can use as many cards are there are slots.
If you really need a lot of ports, then eventuelly, a S2M card might be interesting for you, see question hardware_s2m.
See question config_manycards about the specialities for the configuration of more than one card.
Cards with an HFC-PCI chip allow some specialities that are not possible with other ISDN cards. So it is possible to run the card in NT mode (requires crossing the ISDN connection and change by software) - this means you can simulate to another ISDN card that your card is an NTBA. Also, it is possible to give up one B-channel in exchange for reading the complete D-channel protocol, which is great for isdnlog. The later can also be done with a reversed card (see question isdnlog_reversedcard) but with HFC chips this works much more reliably and cleanly. You can activate this special echo mode by calling:
hisaxctrl <driver_name> 10 1 hisaxctrl <driver_name> 12 1
hisaxctrl <driver_name> 12 0 hisaxctrl <driver_name> 10 2
Generally, ELSA supports the ISDN4LINUX developers quite well with documentation on how to access their cards. Thus, these cards are well supported and very recommendable for use under ISDN4LINUX. Also, the ELSA Quickstep 1000 PCI (new name Microlink PCI) is one of the only brands of cards that are officially certified for use in Germany, and therefore in EC (see question country_certified for more information on certification).
However, there is a speciality with some non-PCI-conformal mainboards and
the ELSA Quickstep 1000pro-PCI. These mainboards set the IO address to
incorrect values (they need to be on 0x100 boundaries, and in a higher
area). This may create an error message like
"You may have the wrong PCI bios" and hang the system. The best fix
is a Bios upgrade. If this is not feasible, you can get the module
pcitest
from Karsten Keil
keil@isdn4linux.de
. It will initialize the card correctly,
then exit with an intentional error (thus not occupying any memory).
To interface from ELSA's RJ11 plug to an RJ45 cable, use the following cabling scheme:
RJ11 - RJ45 pins 1234 12345678 Cable abcd --abcd--
It is a semiactive card based on the ISAR chipset which supports sending/receiving faxes. It is special in that you use it with HiSax which normally works only for passive cards. However, as all active card you have to load its firmware (in this case after loading HiSax) from the file ISAR.BIN, which is part of the isdn4k-utils.
Please note that compression (V42bis, MNP) are not implemented in firmware,
and therefore not supported. The ideal init string for the card to allow
modem dialin is AT%C0\N0
.
First the latest news: The Teles card 16.3c has a crippled FIFO, therefore
it is required to use AT&B1024
when using the ttyI* devices (if the
remote side still send packets with more than 1024 bytes it will not work
- unfortunately many CAPIs use 2048 bytes as default).
The latest Teles PCI card needs the netjet
driver, the teles driver
will NOT work (that card identifies itself as 'TigerJet Tiger300' when doing a
cat /proc/pci
).
Now some comments about Teles in general (these are the personal opinions of the author of this FAQ, please blame nobody else than me):
Teles' business practices are very customer- and developer-unfriendly when compared to those of other companies. Naturally, the developers give priority to cards for which support is available, and where the specifications are freely available.
So far, Teles has had a very unfriendly attitude towards the i4l developers. No support has ever been received from them, and they don't publish any information about how to access their card. The developers have invested a lot of private effort into getting this card to work from the beginning without receiving any support. The driver has been a complete private effort. Yet, Teles has bragged on their web site that their cards run under Linux, without giving proper credit.
Even companies that buy Teles cards and resell them under their own name have not been able to improve the support. This has lead to the situation where a re-branding company (!) itself had to go through the effort of obtaining approval to legally use i4l in Germany on a Teles card.
From a customer point of view, check out the prices for their hotline before you buy any hardware from them! The author of the FAQ refuses to use any hotline that charges 216,- DM per hour. Reports about quality and waiting time have not always been favorable.
And this company doesn't even give away drivers for other operating systems, like Windows, for free. You have to dial up a very expensive number (0190) where you have to pay about DM 1,20 per minute in Germany to download the driver. Not that it's advisable to use Windows anyway, but just to let you know...
Warning: Teles has often changed their cards without notice, while still using the same name. When you buy a Teles card, you may find out that your brand-new card can not be supported by i4l! (As is currently the case...)
The developers will try to support new Teles cards when information about how to access it becomes available, and when they have no other priorities. Of course you can always send a patch.
This card supports many special features in its firmware and is very well supported by its Linux driver. It's currently one of the only ISDN cards that you can use to fax under ISDN4LINUX, or which supports the CAPI 2.0 interface. You can get the newest driver from: ftp://calle.in-berlin.de/pub/linux/avmb1 or ftp://ftp.avm.de/cardware/b1/linux/. The firmware is available on: ftp://ftp.avm.de/cardware/b1/linux/firmware. The latest firmware will also allow D channel traces with isdnlog without usage of a reversed card.
To use the AVM on a point-to-point connection ("Anlagenanschluss") add "DSS1 P2P" to the load command for the firmware, like:
avmcapictrl load /usr/lib/isdn/b1.t4 0 DSS1 P2P
There is also a mailing list for problems with the AVM B1 available on:
linux-avmb1@calle.in-berlin.de (send an email to majordomo@calle.in-berlin.de
with subscribe linux-avmb1 <your email address>
in its body).
These cards support several special features in their firmware. They are newly supported by a Linux driver. They are currently one of the only ISDN cards that support the CAPI 2.0 interface. Also, you can use them very well for faxing under ISDN4LINUX (after upgrade with a fax card - possible for HYSDN Ergo2 and HYSDN Metro4).
More information on company and hardware is available on: http://www.hypercope.de Configuration is similar to that of an AVM B1.
This was the first active card supported by isdn4linux. The manufacturer has
always supported i4l developers (
http://www.think.de/
).
The ICN does not need any interrupt (polling), therefore a PC can be equipped
with many of them without any interrupt conflicts. The newest firmware should
be available at
ftp://ftp.think.de/pub/isdn4linux/icn/firmware/
.
Unfortunately, the ICN is not produced any more.
This behavior is typical for a cable with confused a/b wiring. Some NT from Quante had a wrong labeling. They caused exactly the mentioned behavior if the PBX was connected to the plug of the NT and the ISDN card to the pins of the NT. As soon as some device activates the bus the other one can no longer get through.
This question assumes that you are connected by an internal bus that you installed, attached directly to the NT (without using an RJ45 cable).
The easiest way to test it is to buy a little cable tester (the author of this FAQ got one from Conrad Electronics in Germany for 29,- DM - just follow the simple instructions).
Otherwise you have a bit more work. Switch line a1 and b1. If it doesn't work, put them back and switch a2 and b2. If it still doesn't work, try switching them both. As long as {a|b}1 and {a|b}2 are kept, nothing can break. If you want to be sure, before plugging it in measure between pins 4 and 5 and between Pins 2 and 6 on the socket; there should be no current, but between 3 and 4 and between 6 and 5 should be 40 V, 6 and 3 positive.
With the Western plug this works similar. 4 lines are used:
| | | | | | | | 1 2 3 4Then you can try to switch (1 with 4) or (2 with 3) or both. Never switch the outer with the inner lines - this would cross the RX and TX lines and nothing will work.
Check the Cable FAQ for more details on which line should be connected how.
If both devices are attached via RJ45, then one of the cables has been twisted. That usually happens if one of the RJ45 plugs has been attached upside-down (a1/b1 are inside, a2/b2 are outside, so the order of the sending/receiving pairs is maintained), then you just need a new plug and of course pliers for the RJ45, old plug off, and new plug (in the right direction) on.
Many PBX run non-standard ISDN protocolls on their internal bus. This may cause
i4l to print warnings like "Unexpected discriminator 0xZZ" (where ZZ is a
hexadecimal number) when it encounters unexpected frames (some old versions
even crash). This can increase your message file by as much as 1 MB in 3 days.
The PBX Ackermann Euracom 181
(discriminator 0xaa) as well as
Ascom
(discriminator 0x44/0x47) seem to be notorious for this.
You can avoid the warning by adjusting the switch/case code for isdnlog in
function processctrl(...)
in processor.c
and recompiling
isdnlog.
Please be aware, that the PBX may hang if the ISDN card does not respond to
the PBX requests - bypass the PBX in such a case.
Also, a PBX may run 1TR6 protocoll on the internal bus by default, rather than Euro ISDN. You have to configure i4l (or the PBX) accordingly, best is you try to configure both on the same or similar protocolls.
Also the MSN may be different than you expect. Check several versions, no
digit (then use 0
, which i4l will require in such a case), one digit, or
two digits, or the whole MSN. Best is you call some device (e.g. ISDN
telephone) on the internal bus and check what i4l writes into the log file.
Last, remember that you may have to configure your PBX to 'route' incoming calls onto the internal ISDN bus.
If you have a point-to-point configuration ('Anlagenanschluss') then you cannot connect your card directly to the S0 bus in parallel to the PBX (otherwise nothing will work). You have to connect to an internal ISDN bus. Your MSN is usually the extension at the end of your telefon number.
It's probably not a Plug 'n Play card at all - even though Teles now prints PNP on all their card and packaging. The difference is easy to recognize: a real Teles PNP card no longer has the (tiny) Dip switches on the card to set the IO addresses.
These blinking LEDS are often caused by a bad cable or a too long or unterminated SO bus.
This is normal. The ELSA Quickstep 1000 ISA card has a hardware timer on the
card which can not be disabled by software. You have to modify the card
hardware to get rid of it. Check with Karsten Keil for this:
keil@isdn4linux.de