The following steps are recommended:
ATS18=1 command to audio. Now you can get the
telephone to ring by dialing ATDxxxxxx, where xxxxxx is your own MSN./dev/ttyI0, and the other to
/dev/ttyI1. Then choose "Exit" and start the modem
emulation with "ATZ" and "AT&Exxxxxx" (where xxxxxx
is your own MSN without the area code). Then you can start. On the first
console you can dial your own number with ATDxxxxxx. On the second console you
should now see "CALLER NUMBER: xxxxxxx" and
"RING". Accept the call on the second console with
"ATA", and you should then see the message "CONNECT
64000/X.75" on both consoles. You can then send characters to the other
console by typing (to see the characters on your own console, turn on local echo).
Isdn4linux sets "digital data" as it's own service when it calls out. The switching station will not route such calls to analog devices like a telephone or a fax machine.
Yes, the following sites offer guest access for modem emulation or IP:
emoenke@gwdg.de:
ftp://ftp.gwdg.de/pub/linux/isdn/isdn4linux-gwdg/rc.isdn-Beispiel
you can test NetCall at 551-7704103 (works as is within Germany,
from outside Germany you just have to change the number).
hifi@scorpio.in-berlin.de:
There's a "gast" at +49 30 67 19 81 01 (X.75, mgetty). There's the stones-html-page with pics in postscript to test downloading. Whoever needs a target to call can use it. At ...81 03 there's a getty with HDLC. As guest you enter a kind of BBS and can read some news.
See question trouble_pap .
In this case "fuser -v /dev/isdn* /dev/ippp* /dev/cui* /dev/ttyI*" is very helpful. This helpful program shows, which processes are using those devices.
telesctrl id 3 1 --- dec module_count telesctrl id 4 1 --- inc module_count
Many PBX run non-standard ISDN protocolls on their internal bus. This may cause i4l to print warnings when it encounters unexpected frames (some old versions even crash). Also, they may run 1TR6 protocoll by default, instead of Euro ISDN on their internal bus. You have to configure i4l (or the PBX) accordingly, best is you try both on the same or similar protocolls.
Also the MSN may be different than you expect. Check several versions, one digit, or two digits, or whole MSN. Best is you call some device (e.g. ISDN telephone) on the internal bus and check what i4l writes into the log file.
These errors happen when i4l is not able to process its buffers fast
enough. They are often caused by bad sound cards or their drivers when
they disable the interrupts too long! It may also happen on old hardware
(happened to the author of this FAQ when using vbox on an old 386-25 with
only 4MB RAM). You may be able to work around it by increasing the number and
size of the buffers. Check the source code header files for definitions like:
#define HSCX_RBUF_ORDER 1 #define HSCX_RBUF_BPPS 2 #define HSCX_RBUF_MAXPAGES 3
The driver should be loaded with the command "insmod -m". The output has to be transformed somewhat to be a form similar to System.map.
Fritz Elfert
fritz@wuemaus.franken.de wrote on 17 Oct 1996:
insmod -m isdn.o | sort | sed -e 's/ / T /g' | egrep '.* T (a-z,A-Z,_)+' /etc/isdn/isdn.map cat /System.map /etc/isdn/isdn.map /iSystem.map
Check whether the reason for the hard disk activity is caused by the amount of messages written into the logfile. If this is the case, you can reduce the output by:
isdnctrl verbose 0
Andreas M. Kirchwitz
isdn4linux-mlist@zikzak.snafu.de wrote:
Instead of a "reboot" command or pressing "Ctrl-Alt-Del" try a "Hard Reset" with the reset button. With some motherboards (which is not necessarily the motherboard's fault) the cards are not completely reset with a "Soft Reset" so that some drivers will have problems finding the cards.Of course, before the hard reset you have to bring the system down correctly ("reboot" command or press "Ctrl-Alt-Del")! Only then can you hit the reset button.
When booting, a message like this will appear in the log file:
HiSax: Teles 16.3 found,irq:5 isac:a80 cfg:e80 HiSax: hscx A:280 hscx B:680 Teles3: HSCX version A: V2.1 B: V2.1HiSax is loaded if the hardware can be found and the appropriate interrupts can be generated. If not, the module is not loaded. That doesn't mean that everything will then work (e.g. twisted cables, broken cables, terminators), but that card is installed correctly in the computer and there are no hardware conflicts.
Wilhelm Schulte
schulte@wrds1.urz.uni-wuppertal.de wrote about this:
Best is you check that the interrupt is registered correctly. Check it with "cat /proc/interrupts". The following entry indicates an error: 11: 0 + hisax The 11 is correct when the card is configured on interrupt 11. However, the 0 means that the card does not accept interrupts, so it does not work. That's the well known "busy bug". Often it can be worked around by loading, unloading, and reloading the ISDN modules on bootup. The IRQ counter does have to be 0; low values also point to the same problem. You can test for it quite easily: 1. cat /proc/interrupts, note the count 2. Call the card with a telephone. 3. Again cat /proc/interrupts, the count should be quite different from the first value.See also "I always get BUSY when dialing into my ISDN mailbox". You can also check the io ports with "cat /proc/ioports".
This is normal. The ELSA Quickstep 1000 ISA card has a hardware timer on the
card which can not be disabled by software. You have to modify the card
hardware to get rid of it. Check with Karsten Keil for this:
keil@isdn4linux.de
It's probably not a Plug 'n Play card at all - even though Teles now prints PNP on all their card and packaging. The difference is easy to recognize: a real Teles PNP card no longer has the (tiny) Dip switches on the card to set the IO addresses.