ATTENTION! The following header is not fully valid yet!
From: dl4mhk@lrz.uni-muenchen.de (Bernhard Hailer)
Newsgroups: de.alt.comm.isdn4linux,de.answers,news.answers
Subject: ISDN4linux-FAQ
Followup-To: de.alt.comm.isdn4linux
Summary: This posting describes what every reader of de.alt.comm.isdn4linux
         ought to know about ISDN under Linux using isdn4linux.  
         This is an English translation of the original document, which is
         in German, like the Newsgroup.
Archive-name: eng-i4l-faq
Posting-frequency: monthly
Last-modified: 18-Mar-97
URL: http://www.lrz-muenchen.de/~ui161ab/www/isdn/


FAQ for isdn4linux - Version 1.3.3
(translation 3-Oct-97)

1 General information about isdn4linux

  1. What is isdn4linux?
  2. What can isdn4linux do?
  3. What can't isdn4linux do (yet)?
  4. Can I use isdn4linux in North America?
  5. What do I need for isdn4linux?
  6. How can I get isdn4linux?
  7. What documents should I read first?
  8. What helpful links are there about isdn4linux?
  9. Is there a mailing list for isdn4linux?
  10. How can I have myself removed from the mailing list?
  11. Is the mailing list mirrored to a newsgroup?
  12. Is there an archive of the isdn4linux mailing list?
  13. In which countries does isdn4linux work?
  14. Is isdn4linux approved for use by the telecommunications authorities?
  15. What is the most recent version?
  16. What hardware is NOT supported?
  17. Does isdn4linux support external terminal adapters?
  18. Which internal cards are supported?
  19. What is the new HiSax driver all about?
  20. What about the active AVM B1?
  21. Now that my AVM produces so many interrupts with the HiSax driver, which is the best passive card to use with HiSax?
  22. Does isdn4linux support external ISDN adapters?
  23. Which ISDN modes are supported?
  24. Does isdn4linux support channel bundling?
  25. What is the difference between an active and a passive ISDN card?
  26. Are there sites that offer guest access where I can test my isdn4linux setup?
  27. Can I combine isdn4linux with diald?
  28. Can I use isdn4linux as an answering machine?
  29. Can I fax with isdn4linux?
  30. Is videotex/Btx/Datex-J possible with isdn4linux?
  31. Can I connect to Compuserve with isdn4linux?
  32. Which ISDN features can not be offered by isdn4linux?
  33. I'd like to write a new hardware driver. Where can I find a description of the interfaces to the link level module?
  34. How can I access the source from the current development/what is the CVS tree all about?
  35. Can I use isdn4linux under dosemu?
  36. Is there a working ISDN card for a DEC Alpha with Linux?
  37. Can isdn4linux run in parallel to UISDN?
  38. What are AOC-x, CLIR, COLP, CVS, HDLC, HSCX, ISAC, TEI...?

2 Configuration

2.1 General

  1. Where can I find scripts and other information on configuring i4l?
  2. How many ISDN cards can I stuff into my computer?
  3. Do I need a DOS setup program to setup my Teles card?
  4. Does the driver support "dial on demand"?
  5. When an IP packet should go over the link (which usually triggers a dialout), all I see in the log is: dial rejected: interface not in dialmode `auto'
  6. Does isdn4linux support PNP (Plug and Play)?
  7. Is there a trick to sometimes boot Linux with ISDN and sometimes without?
  8. Is it possible to initiate call forwarding with i4l?
  9. Has anybody routed ipx/spx over ISDN with Linux?
  10. Can I use kerneld to load the ISDN modules in the kernel as needed?
  11. How can I get a tcpdump patched for ISDN?
  12. How can I set up user permissions for the use of ISDN?

2.2 MSN

  1. What is an MSN?
  2. What is an EAZ?
  3. How many MSNs do I need if I want to do the following: * Telephone * Analogue modem (used for data, fax or voice mailbox) * Dialin for X.75 (modem emulation) * Dialin for syncPPP
  4. What is my MSN?
  5. How do I tell the modem emulation what my MSN is?
  6. How do I configure my MSN using syncPPP?
  7. Where should I configure my own MSN in order to test syncPPP by calling myself?
  8. How can I find out how my telephone number is transmitted to the calling party?
  9. Can I do the following on *THE SAME* MSN: - Telephony (voice) - VBOX (voice, of course) - X.75 login (mgetty, /dev/ttyI?) - IP interface for IP connections to other computers?
  10. How can I minimize the number of MSNs needed for dialin?
  11. How do I set the MSN in a Cisco?
  12. Why don't I always receive from the German Telekom the number of a caller ("Caller ID")?
  13. Do I receive the Caller ID from foreign calls (German Telekom)?
  14. I've heard that actually two Caller IDs are transmitted?

2.3 Teles driver

  1. I use SETUP.EXE under DOS, to configure my Teles/Creatix with memory xxxxx and IRQ yy. How do I do this under isdn4linux?
  2. I'm confused: according to the documentation, my Teles card is configured for IO address 0x180. In Linux (and also in some Windows programs) the address is shown as 0xd80?
  3. When compiling the Teles driver I get an error similar to: too many arguments to function '_get_free_pages_R5243d78b'?
  4. I'm using kernel 1.3.x, the Teles driver compiles fine, all the correct parameters are set in config.c, but the card still won't work.
  5. Is it possible to have more than 1 Teles card in one computer?
  6. How can I tell whether or not my Teles card is recognized correctly?
  7. Where can I send complaints to Teles?

2.4 HiSax driver

  1. Where can I find the HiSax driver?
  2. Which version is current?
  3. How is HiSax better as the original Teles driver?
  4. How do I install HiSax?
  5. Are there patches to the HiSax driver?
  6. What does the remark: "Known Bugs: incoming calls are only delivered, if channel == B-channel (same on teles)" mean?
  7. My ELSA card has 2 LEDs that light up like a neon sign. What does that mean?

2.5 ICN driver

  1. Where can I buy the ICN card?
  2. Where can I get the newest firmware for my ICN?
  3. Is it possible to use several ICN cards in one computer?
  4. My ICN 4B is recognized only as an ICN 2B. How is the syntax for loading icn.o with insmod for the ICN 4B?
  5. What is "lanx75i.bin" in the ICN directory?

2.6 Working together with other ISDN devices

  1. What settings does ISPA etc. (DOS, Windows) need to work with the standard settings of isdn4linux?
  2. What do I have to watch out for to connect to Windows95?
  3. Can use only syncPPP with Windows95 to connect to isdn4linux?
  4. A Windows95 user with a Fritz! Card poor transfer rates when connected with isdn4linux - what can one do?
  5. Where in Windows95 can I find the settings to get a terminal window when I log in?
  6. I'd like to exchange data with a Macintosh (Leonardo card), what do I or the Mac user have to watch out for?
  7. A Macintosh with a Leonardo card tries to call in , and wants to negotiate chap md5. How can I switch it to CHAP/PAP?
  8. How does isdn4linux work with a Cisco (HDLC) on the other side
  9. My Cisco has a Bug - which IOS is recommended?
  10. When I call in to an ASCEND, does it cost a charge unit even if I get a "BUSY"?
  11. Is there a mailing list about Ascend?
  12. How do I switch on Raw IP on the Ascend Max with Radius?
  13. How do I switch on "uihdlc" encapsulation on the Max (an Ascend) with Radius ?
  14. What settings does an ELink need to work with isdn4linux?
  15. I can I use Internet with the German T-Online with i4l?
  16. I've set up an Internet connection over T-Online as described in the groups, but the chat script fails ("Connect script failed").

2.7 Raw IP

  1. What is Raw IP?
  2. What are the advantages and disadvantages of Raw IP?
  3. How can I run a script when a raw IP connection is established?

2.8 Modem emulation (use with ttyI* devices)

  1. Does modem emulation mean that I can toss out my analog modem?
  2. Which device should I use for calls out or calls in?
  3. How to I switch the modem emulation from X.75 to HDLC?
  4. How can I poll with Taylor-UUCP using isdn4linux?
  5. What speed should I set for the modem emulation?
  6. Is 'init-chat "" ATZ OK AT&E4 OK ATS14=3 OK' correct for 1TR6 (the other side has DSS1)?
  7. Was does the register S13 exactly mean?

2.9 Async PPP

  1. pppd, ipppd, async PPP, sync PPP - what are they? Which should I use?
  2. I would like to use asynchronous PPP. Can I use the network interface from isdn4linux?
  3. How can I reduce the login time?
  4. How can I increase my transfer rates with PPP?

2.10 Sync PPP

  1. pppd, ipppd, syncPPP, asyncPPP .. what is they? What should I use?
  2. How do I compile isdn4linux with syncPPP?
  3. How does use isdn4linux with syncPPP?
  4. How should I name my network interface?
  5. How do I configure a PPP connection with ipppd?
  6. How do I get ipppd to open a PPP connection?
  7. How can I tell if a connection is unsuccessful (busy)?
  8. Where can I find the latest version of ipppd?
  9. How can I use more than one ippp* device?
  10. I want to talk to remote machines which needs different configurations. The only way I found to do this is to kill the ipppd and start a new one with another config to connect to the second machine.
  11. How does the (little-documented) "pppbind" command in isdnctrl work?
  12. I want to use dynamic IP address assignment. How must I configure the network device?
  13. According to the manpage, ipppd offers the option "dns-addr". But my ipppd refuses to take this option!
  14. How can I do IPX over ipppd?
  15. How can I reduce login delay?
  16. How can I increase my PPP data transfer rates?

2.11 ISDN4Linux in a network

  1. I've successfully used the Internet with my Linux system using isdn4linux. Now I'd like to have another computer on my Ethernet profit from the Internet as well. But how?
  2. How does this fourth possibility work, Linux + Masquerading?
  3. I have a local area network, (LAN) with computers based on several platforms - Win95, Win311, NT, Amiga (AmiTCP) and Macintosh (MacTCP) - all connected to the outside world through a Linux router. The Linux machine has an ISDN card. My ISP provides me with a dynamic IP address each time I log in. I want all the computers to reach the INTERNET not just the Linux box. How can I do this?
  4. How can I allow the users in my local network to use the ISDN card(s) in my Linux PC?
  5. Where can I find "modemd", and for which platforms are there "clients"?
  6. Where can I find COMt?
  7. How exactly does this "PERL one-liner" "modemd" look?

2.12 Isdnlog

  1. isdnlog doesn't always show the High Layer Compatibility (Speech, Video,...) as I'd like it to.
  2. Can I see the service type from an incoming call in the output from isdnrep?
  3. Why doesn't isdnlog record the number dialed by my other ISDN devices, since it records the charges?
  4. How can I get isdnlog to also show the telephone numbers for other ISDN devices?
  5. Does isdnlog also calculate the new pricing plans of the German Telecom (City Weekend, City Plus)?
  6. How can I get isdnlog to calculate the charges for the Dutch telephone company?
  7. How can I get isdnlog to calculate the charges for the Swiss telephone company?
  8. How can I display the data transfer rates graphically?

2.13 Isdnbutton

  1. What script should I use to bring down isdnbutton?
  2. What do the different states of isdnbutton mean (green, yellow, red)?

2.14 Audio

  1. What is the format of the audio messages (.msg) vbox plays when it answers a call?
  2. How can I record my own messages for vboxgetty?
  3. How can I play audio messages locally using /dev/audio?
  4. If vboxgetty has recorded a message in a format which can not be played using "cat xxx>/dev/audio" how can I still hear the message?
  5. How can I convert audio messages which where recorded by vbox to other formats (i.e. from uLaw to WAV)?
  6. How can I format WAV for uLaw (for my vbox announcement message)?

2.15 Diald

  1. How can I combine i4l with diald?
  2. Are there any example scripts for diald?

2.16 Chargeint

  1. How can I use the "chargeint" patch, so i4l will hang up before the next charge unit begins?
  2. With which drivers can I use the chargeint patch?
  3. When does it not make sense to use the chargeint patch?
  4. How does the chargeint patch work?
  5. How do I configure the chargeint patch?
  6. Where can I find more detailed instructions for the chargeint patch?
  7. How can I be sure that the chargeint patch is using the correct time?

2.17 Dial-In

  1. How can I enable others to login via ISDN?
  2. Someone would like to dial in to my mgetty with HDLC. Is ttyI1 correct, or do I have to start with ttyI0?
  3. Is it possible with mgetty to automatically start pppd when LCP frames are received?
  4. How can I have (i)pppd check passwords from /etc/passwd instead of /etc/ppp/pap-secrets when someone dials in?
  5. How can I allow several people to call in to me at once?
  6. Can I use just one MSN to serve customers both with a getty (modem emulation and with the network?
  7. Can I get the advantages of a multiple-PBX line (one MSN for all ISDN ports) with a multiple-device line [German Telekom]?
  8. When a Fritz! card calls with X.75, Linux crashes. What can I do?
  9. An AVM (A1 or B1) cannot call in to me with X.75, either under Win95 or under OS/2?
  10. How can enable a Fritz! card to call in to me?
  11. Which ISDN routers are there that are OS-independent?

2.18 Leased lines

  1. How does establishing and ending a connection work with D64S without signaling?
  2. With i4l, how can I successfully use the Teles card on a D64 leased line?
  3. Can I connect two computers with ICN cards over a D64s leased line? How? Where can I find documentation?
  4. With ISDN, can I use one channel as a leased line and other as a dialup line?
  5. I have a leased line connection to a ICN, however the ping times are too long.

2.19 SPV

  1. What is a SPV?
  2. How long will there still be SPVs?
  3. Does isdn4linux support SPVs? How?

2.20 Channel bundling

  1. What is channel bundling and how can I use it?
  2. What is raw bundling?
  3. How do I use raw bundling?
  4. What are the advantages and disadvantages of raw bundling?
  5. Is there are working example script for raw bundling?
  6. What's the current situation with raw bundling?
  7. What is MPPP?
  8. How can I use the MPPP material?
  9. What are the advantages and disadvantages of MPPP?
  10. I tried MPPP but it doesn't work. The ipppd writes in the debug log something like: ... rcvd [0][proto=0x3d] c0 00 00 00 80 fd 01 01 00 0a ... sent [0][LCP ProtRej id=0x2 00 3d c0 00 00 00 80 fd 01 ...
  11. I use MPP. Unfortunately it hangs when just one packet is lost.

3 Troubleshooting

3.1 General

  1. My isdn4linux doesn't work! How do I best go about finding the problem?
  2. I have problems compiling isdn4k-utils-2.0. "ncurses.h" or "panel.h" is not found. But curses.h does exist.
  3. Why does neither my telephone nor my fax machine ring when I call them with isdn4linux?
  4. If i4l uses one B-channel then the other one will be blocked (incoming as well as outgoing)...
  5. In the instructions for my NTBA it says that a crossed a/b cable pair has no effect on the operation?
  6. How can I test whether a a/b cable pair has been crossed?
  7. Even though I deactivated the signalling for incoming calls, an incoming caller does not get a BUSY signal, although neither i4l nor any other ISDN device is configured to use that MSN. Even when every usable B-channel is used by i4l or another user an incoming caller will not get BUSY. The same is true when I deactivate audio support for i4l.
  8. When the router is active, incoming calls from customers hear ringing, even when we're on the line with a support call. This gives the impression that our employee doesn't answer the phone.
  9. I closed all ISDN applications. Why can't I unload my ISDN modules ("isdn: Device or resource busy")?
  10. I'm now certain I've closed all ISDN applications. I still sometimes cannot unload the ISDN module ("isdn: Device or resource busy")...
  11. I still can't unload the modules. I use callback.
  12. My charge "impuls typ A" [German charge impulse at the end of a connection] is not correctly transmitted, although the Telekom says they activated it.
  13. My PBX produces a reset on the SO bus every hour, after which isdn4linux no longer accepts any calls?
  14. My Ascotel PBX crashes i4l (connected on my internal bus).
  15. My Teles 16.3 works behind a Quante IS-2 (identical to the Ackermann Euracom 181) after a reset, only when I: 1. unplug the PBX 2. turn off the PC 3. plug in the PBX 4. turn on the PC
  16. I'm connected through an old PBX. Any attempt to dial out is refused with cause 64?
  17. I can't get my PBX, a proprietary Siemens Hicom, to work?
  18. isdnctrl returns a "bus error" when I do a "isdnctrl list"?
  19. After a hangup "no routine" is printed on /dev/isdnctrl. Did it release my line or is there still some bug in the driver?
  20. I get many "HSCX RME out of buffers" messages in my syslog.
  21. My pppd or ipppd has problems with PAP/CHAP authentication.
  22. I get the error "SIOCADDRT: Invalid argument" when telling route to route to isdn0.
  23. I regularly see meesages such as:
    isdn: line0,ch1 cause: E0010
    What does this mean? Where can I find out the meaning of these causes?
  24. On my ELSA card, the LED for the loss of the TEI often blinks. My connections are also often disrupted...
  25. My isdn driver crashes my machine! Since I've configured it as a module, the addresses change each time it's loaded. How can I find out where the driver is crashing?
  26. My hard disk becomes very active when isdn4linux run. How can I turn this off?

3.2 Teles driver

  1. How can I know that my Teles card (or compatible) is recognized correctly?
  2. What is the name if my Teles driver (especially if compiled into the kernel)?
  3. On bootup I get "HSCX version A:5 B:5" but I still have the impression that my Teles card is not used correctly. What else can I check?
  4. Why should I avoid IRQ 12 and 15 for my ISDN card?
  5. My Teles card will not be recognized correctly when I use LILO with my parameters.
  6. If I first start DOS and the Teles driver included with the card, and then start Linux with Loadlin, everything works fine. However, if I start Linux directly with LILO, the Teles driver doesn't respond directly.
  7. After a reset, my card does not initialize correctly.
  8. The Teles driver recognizes my 16.3 card as a 16.0.
  9. I use i4l and the Teles driver. From time to time the driver hangs and I have to reload it.
  10. My machine often crashes. On the console I get about every few seconds l1state 4 l1state 8 l1state 13 ph_command 9 l1state 4 l1state 0 ph_command 0 l1state 7 ph_command 9
  11. My Teles driver always says "isdn0: Chargesum is 0" although I get charge information from the [German] Telekom.
  12. My Teles driver does not work in 2.1.x!
  13. I have two Teles cards in my computer but it seems that only one is used!
  14. When compiling the Teles driver I get some undefined symbols (only kernel 2.0.26)?

3.3 HiSax driver

  1. How can I tell whether my ISDN card has been corrected recognized by the HiSax driver?
  2. The Teles crashes again and again with the following error message in the log: <date> <time> foo kernel: HSCX B EXIR 10 <date> <time> last message repeated <n> times
  3. My AVM card produces very many interrupts with the HiSax driver. Is this normal or a problem with the HiSax driver?
  4. The PNP tools done work with my Teles 16.3 PNP card!

3.4 ICN driver

  1. On dialing out/in with my ICN packets get lost.

3.5 Working together with other ISDN devices

  1. I have problems connecting to an ELink.
  2. I have problems connecting to a Netblazer router.

3.6 Raw IP

  1. I get the error message "protocol error, unspecified".

3.7 Modem emulation (use with ttyI* devices)

  1. When I dial with "ATD....." I always get a "NO CARRIER".
  2. My modem emulation/pppd does not recognize an incoming call.
  3. I gave the correct MSN/EAZ, but still don't get a RING.
  4. Why can't I dial my telephone or fax with the modem emulation?
  5. I can't get a connection to my ISDN mailbox.
  6. I'm sure I used the correct parameters for my ISDN mailbox, but I still don't get a connection. I always get BUSY although I know the mailbox is not busy.
  7. My modem emulation hangs. How can I force my card to hang up?
  8. During a tty connection, I get a message from the kernel "teles_writebuf: channel not open". Then no more input is accepted for this connection.
  9. When I use UUCP with X.75, I always get transfer errors!
  10. My iprofd doesn't work any more with HiSax 2.0. I get the error message "Version of kernel modem-profile (3) does NOT match version of iprofd (1)". How can I get iprofd to work again?

3.8 Async PPP

  1. How can I get a log for pppd?
  2. Establishing the connection works fine, but pppd crashes just after that (i.e. the first bytes get through, but then everything stops)

3.9 Sync PPP

  1. How can I get a log for ipppd?
  2. My ipppd won't work, it gives the error message "PPP driver 0.0.0 is out of date".
  3. Starting ipppd I get the error message "this systems lacks ppp support".
  4. How can I switch on PPP support for my kernel 1.2.13 (needed for ipppd)?
  5. When I start ipppd, I only get error messages from the i4l driver.
  6. When I try to start ipppd it says "Can't find usable ippp device"
  7. I can't get a connect. How can I find out where the problem is?
  8. ipppd sometimes crashes (kernel 2.0.14...2.0.25)
  9. I get the message "IP frames delayed" - and I don't get a connection.
  10. I cannot dial out with "isdnctrl dial ippp0". It seems as if the route to ipppd is missing although I *did* set it ("network unreachable"). With my old kernel < 2.0 everything works fine!
  11. After ipppd dials out my default route is gone.
  12. When dialing out, I get the message "pppd: peer authentication required but no authentication files accessible." What does this mean?
  13. I cannot establish a connection - it's rejected by the other side. In the log file I find a message that's something like: "sent [0] [LCP ConfReq id=0x1 <mru 1500> <auth pap> <magic 0xcd12e9c4>"
  14. I cannot establish a connection - it's rejected by the other side. In the log file I find a message that's something like: "sent [0] [LCP ConfRej id=0x1 <auth pap>"
  15. I have problems with PAP or CHAP authentication. It does not work although I'm sure I entered passwords etc. correctly.
  16. I often get the error message "hscx_empty_fifo: incoming packet too large"
  17. The connection with ipppd seems to work, but eventually it crashes.
  18. I only have problems with ipppd when the connection is being heavily burdened. Then everything stops. What could be causing this?
  19. My ipppd works, but I keep getting the message pppd[104]: ioctl(SIOCSIFMTU): Invalid argument"?
  20. The first IP packet gets lost on automatic dialout with dynamic IP address allocation.
  21. When calling "isdnctrl mapping <line> <MSN>,..." I get the error "bad address".
  22. What does the message "No phone number, packet dropped" mean?
  23. Why does my ipppd dial one too many zeros ("isdn0: dialing 0 089XXXXXX...")? I don't have any extensions!
  24. My ISDN device is shown with HWaddr and IRQ=0 and base address = 0 when I list it with ifconfig

3.10 ISDN in a network

  1. xosview doesn't show any network activity since installing i4l.
  2. When I for example from a W95 box call up a page with Netscape, I only get the answer "unknown host".
  3. Addresses are now found, but now instead of the page I want I get the message "no route to host".
  4. After booting, my local network can no longer be reached. I use the network interface ippp0 with ifconfig 0.0.0.0; the default route points to ippp0.

3.11 Isdnlog

  1. My isdnlog 2.50 doesn't work since I installed HiSax 1.2.
  2. I've patched isdnlog, but it still won't work together with HiSax (isdnlog starts with the usual messages, but nothing happens)?
  3. Isdnlog (>=2.52) shows for a caller two telephone numbers! Which one is correct?
  4. When calling I receive a "Internal error: wrong structure".
  5. Isdnlog crashes with a "segmentation fault".
  6. I've set up a script to play sound per cat on /dev/sound or some other device. When several events occur, then there is an error: "Can't open output file '/dev/sound': Device or resource busy"
  7. Isdnlog should call a program with redirected output (e.g. "play anruf.au 2>/dev/null" ). Why does ISDN tell me "Can't start '/usr/local/bin/play anruf.au 2>/dev/null' with execvp()"?
  8. Why does isdnlog quit with "kill -1", according to the docs it should only reread isdnlog.conf.
  9. Isdnlog takes 100% of the CPU time
  10. The Telekom is paying me (according to isdnlog/isdnrep) 12 pfennigs (1 unit) for each connection...
  11. According to isdnlog every "busy" costs me 45 units?
  12. I'm having problems getting isdnlog to run with libc 5.4.7!
  13. When dialing out, the screen goes momentarily black?

3.12 Audio

  1. My vboxgetty does not answer any incoming calls.
  2. My vboxgetty answers at the first ring but the number of rings is set to 4.
  3. My vbox 1.1 does not work together with HiSax.
  4. If vboxgetty has recorded a message in a format which can not be played using "cat xxx>/dev/audio" how can I still hear the message?
  5. At the beginning of a message recorded by vboxgetty, there's often a part of my own announcement?

3.13 Dialout on demand

  1. What can cause a charge unit disaster?
  2. Ever since I installed a new kernel, my computer constantly open ISDN connections without transferring any data (expensive!).
  3. My router wants to constantly dial out (and does it too) but NO data is transferred, neither ipfwadm -A! nor tcpdump -i isdn0 show anything.
  4. After closing the line, I discover with "netstat -nt" that IP connections are still open. How can I close these manually?
  5. How can I safely turn off dialout on demand?
  6. How else can I prevent the charge unit disaster?
  7. Is it possible that even with a crashed computer a ISDN connection remains open (and the charge units accumulate)?
  8. How can track down unexplainable dialouts?
  9. Can it be that the Win95 machine on my LAN is causing automatic dialouts?
  10. I have set up a local DNS name server. Why does it cause unwanted dialouts? How can I find the cause?
  11. How can I turn off the DNS requests for WORKGROUP.xxx from my Win95 machine?
  12. How can I get sendmail to not initiate any connections without local mail being left undelivered?
  13. The samba package always triggers dialouts for me. How can I prevent this?
  14. How can I get Netscape to quit initiating dialouts when starting?

3.14 Chargeint

  1. The connection doesn't end with timeout. Possible reason: my service provider uses a Cisco router which sends a "keep alive" packet every ten seconds.
  2. My Internet provider won't switch off keep alive packets so ipppd never hangs up.
  3. The "lcp-keep-alive" patch doesn't work - ipppd still doesn't hang up.

3.15 Dialin

  1. I keep getting the message "isdn_tty: call from XXX -> YYY ignored". Why does isdn4linux (syncPPP) ignore this dialin attempt?
  2. I've configured several ippp* devices. Each incoming call "uses up" one device, until there is no device available any more.
  3. With "isdnctl pppbind" I've established an exclusive connection. But this is removed with an incoming call.
  4. A SunISDN tries to dial into my i4l system.

3.16 Callback

  1. An incoming call is rejected by i4l. i4l then calls back. The reject is not recognized by the other side which keeps on dialing to i4l.
  2. Callback isn't working. How many ippp* devices do I need (at a minimum)?
  3. Callback still doesn't work right. Can the fault lie with the Teles driver?
  4. When trying callback with Euro-ISDN the call never gets rejected.
  5. Somehow i4l can not callback a Cisco?
  6. Callback from an Ascend works only when I set "Active=Yes" in the Ascend menu; but then the Ascend keeps calling me, even when my machine is off.
  7. How can I callback a Banzai!?
  8. Some the callbacks confuse the module count. How can I now unload my ISDN modules?

3.17 MPPP

  1. SyncPPP works without problems on one channel. Unfortunately MPPP won't work due to communication problems between ipppd and the other side.

4 National Peculiarities

4.1 Germany (1TR6)

  1. Which EAZ should I use for i4l?
  2. I use 1TR6 on an extension - the extension number has more than one digit (e.g. 206). What is my EAZ?
  3. The state machine hangs with 1TR6.

4.2 Italy

  1. What does our MSN look like?

4.3 The Netherlands

  1. What does our MSN look like?
  2. How can I get isdnlog to calculate the charges for the Dutch telephone company?
  3. Are there any other peculiarities?

4.4 Austria

  1. We have neither an MSN nor an EAZ, only a normal plain telephone number. What do we have to use for i4l?
  2. Incoming and outgoing calls won't work ("incoming call without CPN")
  3. Why doesn't my getty answer the EAZ it should respond to if somebody dials the "0", the broadcast number? In the log file it says "Incoming call without CPN, assuming '0'".

4.5 Switzerland

  1. We have neither an MSN nor an EAZ, just a plain telephone number. What do we have to use for i4l?
  2. I can only keep a 184 second connection with i4l. After that the connection breaks with cause "Temporary failure" since the telephone company uses new software for its equipment.
  3. How can I get isdnlog to calculate the charges for the Swiss telephone company?

4.6 Portugal

  1. What should we use as MSN?

4.7 North America

  1. Can we use isdn4linux in North America?
  2. Why can't I use European ISDN cards in North America?
  3. Which protocol is used in North America?

5 Miscellaneous

  1. How can I set the clock of my computer with ISDN?
  2. Where can I find information on the dip switches of my NTBA?
  3. Can I connect two ISDN devices directly with a kind of "null modem cable"?
  4. Where can I get documentation on Siemens' HSCX and ISAC chips?
  5. Where can I find the "bat" book about configuration of sendmail?

FAQ for isdn4linux - Version 1.3.3
(translation 3-Oct-97)

[Translator's notes]
--5-May-97: Translation complete for 1.3.2 (except for the proofreading)!
--8-May-97: Added correction for Italy.
--25-May-97: Numerous corrections submitted by Paul Slootman
--27-May-97: Minor cleanup, noted additional countries
--27-Sep-97: Added more translator's notes for various countries and 2.0.30
--3-Oct-97: Added note for MSNs in the UK This FAQ is protected by the GNU General Public License (GPL) Version 2; (C) 1996 Volker Götz, Bernhard Hailer, Matthias Heßler, Michael Hipp and Rainer May.
Distribution under the terms of the GPL is welcome. However, we offer NO GUARANTEES for the information herein. Please read the GNU General Public License for further details. A printed version is available from
Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. An electronic version is available from the authors.

Original FAQ by Volker Goetz <volker@oops.franken.de>, (c) 1995
Comprehensive edition and additions (1996, 1997):
Matthias Hessler <hessler@wi-inf.uni-essen.de>,
Bernhard Hailer <Bernhard.Hailer@lrz.uni-muenchen.de>,
Scott Hanson <shanson@shcon.com> (English translation),
Michael Hipp <Michael.Hipp@student.uni-tuebingen.de> (many syncPPP questions)
Rainer May <r_may@khavi.desaster.heide.de> (i4l and networks)

English translation coordinated by Scott Hanson <shanson@shcon.com> with contributions from:
Sven Tervoort <sveneric@xs4all.nl>
Matthias Hessler <hessler@wi-inf.uni-essen.de>
Erik Corry <erik@arbat.com>
Paul Slootman <paul@wau.mis.ah.nl>

About the format of this FAQ:
The basis of this FAQ is the i4l mailing list. We checked the messages posted to the list and included relevant messages (usually) in the form of quotes. These quotes are not always 100% identical with the original; spelling errors have been corrected, and some messages were translated from English into German. Whoever notices that they have been incorrectly quoted, or would rather not have their Email address noted, please let us know - we'll ... in the next version of the FAQ. The same applies in cases where we have quoted someone without noting it as such. The knowledge of the FAQ authors is noted without quoting ourselves. Remarks from the FAQ authors about quotes are noted like this: [This is a remark - Ed.]
The countless links in this documents are not always complete and with time may no longer be correct. We do not have the time to check them all. If you discover a bad link, please let us know.
In the 7bit version of this FAQ, all new or rewritten questions are marked with a change bar in the left margin. (Does anyone have an idea, how we can mark this in the HTML version?)

Additions, improvements and other suggestions are always welcome (also correction of typographical errors!), preferably send "diffs" from the ASCII version to Matthias and Bernhard. Thank you very much in advance!

This FAQ can be found at:
http://www.lrz-muenchen.de/~ui161ab/www/isdn/
or:
ftp://ftp.franken.de/pub/isdn4linux/FAQ
or:
ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ


1 General information about isdn4linux



  1. What is isdn4linux?

    isdn4linux is a set of kernel modules that "teach" the Linux kernel ISDN. It consists of a main module ("isdn") and the actual hardware drivers that control the specific cards.



  2. What can isdn4linux do?

    isdn4linux controls ISDN PC cards and can emulate a modem with the Hayes command set ("AT" commands). The possibilities range from simply using a terminal program to connections via HDLC (using included devices) to full connection to the Internet with PPP to audio applications.



  3. What can't isdn4linux do (yet)?

    There is no full duplex audio connection possible. Some protocols are still missing (V.110, American protocols).



  4. Can I use isdn4linux in North America?

    See this question in the section "National Peculiarities".



  5. What do I need for isdn4linux?

    isdn4linux has been part of the Linux kernel since version 1.3.59. In addition, you need the package isdn4k-utils-2.0.tar.gz and possibly the HiSax driver.



  6. How can I get isdn4linux?

    Via FTP:
    The package is at ftp://ftp.franken.de/pub/isdn4linux and various mirrors.
    Via Modem/ISDN:
    From the Linux server of the Incubus BBS (Login gast, cd /pub/linux/isdn4linux, download via ZModem with 'sz filename') . The server can be reached at the following numbers
           +49 931   781464   Zyxel U-1496E      V.32(bis), V.42(bis), Zyxel 19200 
           +49 931   781465   Atrie 1914A        V.32(bis), V.42(bis), V32terbo
           +49 931   781467   Atrie 1914A        V.32(bis), V.42(bis), V32terbo
           +49 931   781468   Atrie 1914A        V.32(bis), V.42(bis), V32terbo
    

    New ringdown (16 Lines. First log in as 'bbs'):
           +49 931 79002055   Motorola 3400      V.32(bis), V.42(bis), V.34
    

    ISDN (also log in 'bbs') :
           +49 931  7840724   ICN                X.75    2 B channels
           +49 931  7841020   ICN                X.75    2 B channels
           +49 931  7841060   ICN                X.75    2 B channels 
           +49 931  7841070   ICN                X.75    2 B channels 
           +49 931  7841080   ICN                X.75    2 B channels 
    

    Here is a list of mirrors; thanks to Herbert Rosmanith <herp@wildsau.idv-edu.uni-linz.ac.at> for compiling it initially. Whoever knows of any mirrors not listed here, please let us know!
      ftp://ftp.cs.tu-berlin.de/pub/net/isdn/isdn4linux/
      ftp://ftp.fokus.gmd.de/pub/Linux/isdn/isdn4linux/
      ftp://ftp.franken.de/pub/isdn4linux/
      ftp://ftp.kiss.de/pub/linux/isdn4linux/
      ftp://ftp.leo.org/pub/comp/os/unix/linux/isdn/isdn4linux/
      ftp://linux.mathematik.th-darmstadt.de/pub/linux/mirrors/misc/isdn4linux/
      ftp://ftp.nvg.unit.no/pub/linux/isdn/
      ftp://ftp.pop.de/pub/linux/isdn/
      ftp://ftp.rz.fh-hannover.de/pub/linux/local/isdn4linux/
      ftp://ftp.rz.hu-berlin.de:/pub/linux/isdn4linux/  
      ftp://ftp.tu-dresden.de/pub/soft/isdn/isdn4linux/
      ftp://ftp.uni-mainz.de/pub/internet/starter-kit/isdn/isdn4linux/
      ftp://ftp.uni-wuppertal.de/pub/linux/isdn4linux/
      ftp://ftp.xlink.net/pub/mirror.ftp.franken.de/isdn4linux/
      ftp://fvkma.tu-graz.ac.at/pub/isdn4linux/ 
      ftp://wildsau.idv.uni-linz.ac.at/pub/isdn4linux/
    



  7. What documents should I read first?

       ISDN kernel subsystem:/usr/src/linux/Documentation/isdn/README
       ISDN cards:           /usr/src/linux/Documentation/isdn/README.<card>
       Synchronous PPP:      /usr/src/linux/Documentation/isdn/README.syncppp
                             /usr/src/linux/Documentation/isdn/README.syncPPP.FAQ
       Voice capability:     /usr/src/linux/Documentation/isdn/README.audio
       ISDN Utilities:       /usr/src/isdn4k-utils-<version>/README(.*)
       Many of the utilities also have man pages!
            In a Suse distribution the following information might also be
            helpful:
            Synchronous PPP:       /usr/doc/faq/faq/PPP-FAQ
            Email configuration:  /usr/doc/howto/mini/Mail-Queue.gz
    




  8. What helpful links are there about isdn4linux?

    Scripts and installation tips from several people:
    http://www.rosat.mpe-garching.mpg.de/~web/ISDN.html
    I4l, syncPPP, email, Usenet, Voicebox, this FAQ and more:
    http://www.lrz-muenchen.de/~ui161ab/www/isdn/
    Michael Hipp's page (ipppd):
    http://www.sfs.nphil.uni-tuebingen.de/~hipp/isdn/
    Chargeint instructions:
    http://www.provi.de/~gvz/chargeint.html
    Stefan Nehlsen's instructions for syncPPP:
    http://www.techfak.uni-kiel.de/~stn/i4l/
    xled (formerly xvboxled) is at:
    fb4-1112.uni-muenster.de/pub/ffwd/
    Example configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  9. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  10. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  11. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  12. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  13. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  14. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  15. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  16. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  17. Does isdn4linux support external terminal adapters?

    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),



  18. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  19. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  20. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  21. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  22. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  23. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  24. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  25. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  26. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  27. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  28. Does isdn4linux support external terminal adapters?

    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),



  29. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  30. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  31. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  32. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  33. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  34. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  35. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  36. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  37. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  38. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  39. Does isdn4linux support external terminal adapters?

    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),



  40. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  41. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  42. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  43. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  44. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  45. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  46. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  47. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  48. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  49. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  50. Does isdn4linux support external terminal adapters?

    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),



  51. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  52. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  53. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  54. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  55. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  56. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  57. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  58. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  59. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  60. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  61. Does isdn4linux support external terminal adapters?

    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),



  62. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  63. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  64. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  65. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  66. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  67. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  68. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  69. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  70. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  71. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  72. Does isdn4linux support external terminal adapters?

    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),



  73. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  74. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  75. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  76. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  77. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  78. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  79. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  80. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  81. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  82. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  83. Does isdn4linux support external terminal adapters?

    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),



  84. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  85. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  86. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  87. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  88. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  89. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  90. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  91. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  92. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  93. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  94. Does isdn4linux support external terminal adapters?

    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),



  95. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  96. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  97. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  98. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  99. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  100. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  101. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  102. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  103. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  104. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  105. Does isdn4linux support external terminal adapters?

    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),



  106. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  107. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  108. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  109. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  110. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  111. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  112. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  113. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  114. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  115. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  116. Does isdn4linux support external terminal adapters?

    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),



  117. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  118. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  119. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  120. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  121. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  122. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  123. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  124. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  125. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  126. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  127. Does isdn4linux support external terminal adapters?

    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),



  128. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  129. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  130. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  131. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  132. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  133. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  134. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  135. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  136. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  137. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  138. Does isdn4linux support external terminal adapters?

    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),



  139. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  140. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  141. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  142. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  143. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  144. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  145. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  146. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  147. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  148. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  149. Does isdn4linux support external terminal adapters?

    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),



  150. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  151. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  152. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  153. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  154. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  155. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  156. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  157. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  158. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  159. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  160. Does isdn4linux support external terminal adapters?

    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),



  161. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  162. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  163. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  164. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  165. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  166. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  167. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  168. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  169. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  170. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  171. Does isdn4linux support external terminal adapters?

    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),



  172. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  173. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  174. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  175. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  176. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  177. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  178. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  179. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  180. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  181. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  182. Does isdn4linux support external terminal adapters?

    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),



  183. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  184. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  185. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  186. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  187. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  188. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  189. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  190. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  191. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  192. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  193. Does isdn4linux support external terminal adapters?

    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),



  194. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  195. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  196. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  197. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  198. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  199. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  200. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  201. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  202. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  203. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  204. Does isdn4linux support external terminal adapters?

    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),



  205. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  206. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  207. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  208. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  209. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  210. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  211. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  212. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  213. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  214. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  215. Does isdn4linux support external terminal adapters?

    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),



  216. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  217. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  218. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  219. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  220. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  221. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  222. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  223. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  224. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  225. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  226. Does isdn4linux support external terminal adapters?

    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),



  227. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  228. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  229. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  230. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  231. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  232. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  233. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  234. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  235. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  236. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  237. Does isdn4linux support external terminal adapters?

    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),



  238. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  239. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  240. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  241. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  242. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  243. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  244. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  245. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  246. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  247. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  248. Does isdn4linux support external terminal adapters?

    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),



  249. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  250. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  251. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  252. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  253. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  254. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  255. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  256. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  257. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  258. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  259. Does isdn4linux support external terminal adapters?

    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),



  260. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  261. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  262. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  263. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  264. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  265. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  266. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  267. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  268. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  269. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  270. Does isdn4linux support external terminal adapters?

    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),



  271. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  272. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  273. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  274. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  275. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  276. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  277. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  278. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  279. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  280. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  281. Does isdn4linux support external terminal adapters?

    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),



  282. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  283. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  284. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  285. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  286. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  287. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  288. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  289. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  290. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  291. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  292. Does isdn4linux support external terminal adapters?

    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),



  293. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  294. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  295. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  296. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  297. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  298. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  299. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  300. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  301. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  302. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  303. Does isdn4linux support external terminal adapters?

    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),



  304. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  305. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  306. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  307. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  308. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  309. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  310. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  311. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  312. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  313. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  314. Does isdn4linux support external terminal adapters?

    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),



  315. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  316. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  317. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  318. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  319. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  320. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  321. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  322. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  323. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  324. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  325. Does isdn4linux support external terminal adapters?

    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),



  326. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  327. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  328. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  329. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  330. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  331. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  332. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  333. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  334. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  335. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  336. Does isdn4linux support external terminal adapters?

    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),



  337. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  338. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de> wrote on 14 Oct 1996:
         The first goal of the HiSax driver was to ample configurations for isdn4linux are said to be at:
    http://www.datenhighway.com/isdn4linux.html
    This FAQ along with isdn4linux is at:
    ftp://ftp.franken.de/pub/isdn4linux/
    This FAQ is also so:
    ftp://ftp.pop.de/pub2/linux/isdn4linux/FAQ



  339. Is there a mailing list for isdn4linux?

    Yes, there is. To subscribe, send an email message to "majordomo@hub-wue.franken.de". The subject doesn't matter. The message should read "subscribe isdn4linux <Email address>", where <Email address> is the address to which mail from the list should be sent. Currently there are about 20-50 messages per day.



  340. How can I have myself removed from the mailing list?

    To unsubscribe, send another email message to majordomo@hub-wue.franken.de - the subject doesn't matter. The message should read: "unsubscribe isdn4linux <Email address>", where <Email address> is the address to which mail messages from the mailing list had been sent.



  341. Is the mailing list mirrored to a newsgroup?

    Yes, the mailing list can also be accessed at de.alt.comm.isdn4linux - a bidirectional gateway makes sure that one can also answer postings.



  342. Is there an archive of the isdn4linux mailing list?

    Yes, the messages are saved (unsorted) at hub-wue.franken.de. They are collected by month. To access the archive, send Email to "majordomo@hub-wue.franken.de". The subject doesn't matter. The following commands are possible:
         index isdn4linux          - list which archive files are available
         get isdn4linux <filename> - retrieves the file <filename>
    

    The archives are named "archiv.<year><month>, so "archiv.9610" is the archive for October 1996. An archive of the mailing list is also available via FTP:
    !link ftp://ftp.uni-oldenburg.de/pub/unix/linux/isdn/isdn4linux/Mailing-List; Another archive is available (according to Sascha Ottolski <sascha@alzhimer.isdn.cs.tu-berlin.de>) at:
    http://wws.mathematik.hu-berlin.de/ldr/ISDN/isdn4linux/



  343. In which countries does isdn4linux work?

    [Translator's note: I've made some additions to the original list.]
    We are aware of the following countries:
         Austria
         Belgium
         Finland
         France
         Germany
         Israel
         Italy
         Norway
         Peru
         Portugal
         Spain
         Sweden
         Switzerland
         The Netherlands
         United Kingdom
         USA
    

    [Translator's note: I've also seen messages on the mailing list from isdn4linux users in Canada, Denmark, Hungary and Slovenia . I've also seen mentions of isdn4linux from Australia, the Czech Republic and Poland, but I'm not sure if it is actually in use in those countries.]



  344. Is isdn4linux approved for use by the telecommunications authorities?

    Germany:
    That depends on the driver used. For active cards, the approval covers the entire card including its firmware. Thus the approval also covers the use of these cards with isdn4linux. The Teles 16.3 and the Elsa QS1000 drivers are currently certified in Germany (and hence in most european countries). This applies to the 2.0.36 kernel version.
    Other countries:
    Besides those countries that accept a german certification, we don't have any information... does anyone know more?



  345. What is the most recent version?

    Kernel 2.0.36 contains a very up to date version of the ISDN drivers. We recommend that you use that kernel version.
    Together with the 2.0.36 kernel, a new utilities package has been released, which is a MUST (old versions of the utilities will not work with the new kernel). The utilities are available at ftp://ftp.franken.de/pub/isdn4linux/v2.0/ and the current filename is isdn4k-utils-3.0beta1.tar.gz (also available as .bz2). Check first if there is a newer version.



  346. What hardware is NOT supported?

    For not (with the exception of ICN) no active ISDN cards are supported, except the AVM B1, for which there an alpha driver as binary only.



  347. Does isdn4linux support external terminal adapters?

    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),



  348. Which internal cards are supported?

    Right now there is a driver for all card with a certain Siemens chip set (HiSax driver), that also supports Plug&Play cards. See the next question for details.
    The HiSax driver has superseded the old Teles driver, which is therefore is not being further developed. For this reason, the Teles driver has many more bugs and should not be used any longer.
    Further drivers includes that for the (active) ICN card (ICN driver), as well as that for the PCbit card (Octal, Portugal).
    There used to be a (special) driver for the ITK ix1 micro" from Frank Mohr <mohr@fhdacom2.fhrz.fh-darmstadt.de>, but that is not included in HiSax 2.0. It supports the following cards:
           * ITK ix1 micro V2.0 and V2.1
           * Cisco 200
           * ITK Columbus
    

    Finally there is also a (alpha) driver for the active AVM B1, with its own peculiarities. See the question "What about the active AVM B1?".

  349. What is the new HiSax driver all about?

    It is a new driver that should support all passive cards that are based on a certain Siemens chip set. Currently it supports:
    	* Teles 8.0/16.0/16.3 and compatible ones
    	* Teles 16.3c
    	* Teles S0/PCMCIA
    	* Teles PCI
    	* Teles S0Box
    	* Creatix S0Box
    	* Creatix PnP S0
    	* Compaq ISDN S0 ISA card
    	* AVM A1 (Fritz, Teledat 150)
    	* AVM Fritz PCMCIA
    	* AVM Fritz PnP
    	* AVM Fritz PCI
    	* ELSA Microlink PCC-16, PCF, PCF-Pro, PCC-8
    	* ELSA Quickstep 1000
    	* ELSA Quickstep 1000PCI
    	* ELSA Quickstep 3000 (same settings as QS1000)
    	* ELSA Quickstep 3000PCI
    	* ELSA PCMCIA
    	* ITK ix1-micro Rev.2
    	* Eicon.Diehl Diva 2.0 ISA and PCI
    	  (S0 and U interface, no PRO version)
    	* Eicon.Diehl Diva Piccola
    	* ASUSCOM NETWORK INC. ISDNLink 128K PC adapter
    	  (order code I-IN100-ST-D)
    	* Dynalink IS64PH
    	  (OEM version of ASUSCOM NETWORK INC. ISDNLink 128K adapter)
    	* PCBIT-DP (OEM version of ASUSCOM NETWORK INC. ISDNLink)
    	* HFC-2BS0 based cards (TeleInt SA1)
    	* Sedlbauer Speed Card (Speed Win, Teledat 100, PCI, Fax+)
    	* Sedlbauer Speed Star/Speed Star2 (PCMCIA)
    	* Sedlbauer ISDN-Controller PC/104
    	* USR Sportster internal TA (compatible Stollmann tina-pp V3)
    	* ith Kommunikationstechnik GmbH MIC 16 ISA card
    	* Traverse Technologie NETjet PCI S0 card
    	* Dr. Neuhaus Niccy PnP/PCI
    

    Note: PCF, PCF-Pro: up to now, only the ISDN part is supported PCC-8: not tested yet Teles PCMCIA is EXPERIMENTAL Teles 16.3c is EXPERIMENTAL Teles PCI is EXPERIMENTAL Teles S0Box is EXPERIMENTAL Eicon.Diehl Diva U interface not tested


    Karsten Keil <keil@temic-ech.spacenet.de>