Troubleshooting

Troubleshooting

I. The lockdir is not writable by user executing sems!

Change lockdir param to e.g. /tmp or adjust permissions on /var/lock
(an unwriteable lockdir does not prevent isdngw from running, but other programs could interfere with isdngw)

II. ISDN devices (/dev/ttyI*) are not accessible!

adjust permissions of /dev/ttyI*

III.SER does not start!

Take a close look at syslog to determine config errors

IV. SEMS does not start!

Take a close look at syslog for reasons

V. Error message: CAPI backend not found on your system

Make shure all kernel modules are loaded.
Make shure you enabled the card/loaded the firmware
run the "capiinfo" utility from isdn4kutils package to verify
Make shure the user running sems has read/write access to /dev/capi20
If everything fails, try the procedure below.

VI. SEMS fails to start with message
Error: received wrong answer >>ERROR<< to required command >>AT+FCLASS=8<<

Make shure you enabled ISDN audio support in kernel:
/usr/src/linux/.config must contain: CONFIG_ISDN_AUDIO=y

Per card Linux setup instructions

AVM Fritz PCI V2 CAPI drivers

get the latest drivers from avm.de and compile the module if neccessary (!SuSE)
modprobe the modules: fcpci, capi, capifs, capiutil, kernelcapi, isdn, b1

AVM Fritz USB V2.x CAPI drivers:

Get the latest drivers from avm.de and compile the module if neccessary (!SuSE)
modprobe the modules: capi, fcusb2
load the firmware by running avmcapictrl load fus2base.frm

AVM C4:

native CAPI support in the kernel
load the modules: c4 capi
run avmcapictrl load c4.bin to load the firmware and start the card
the C4 offers 4 independent connectors, numbering starts at 1 (from top of card)

Isdn Card/Driver troubelshooting

We use basic commands to check the availability of isdn support. If you have a card with isdn4linux support, you can start the procedure directly -- for CAPI based drivers please first of all load isdn4linux compatibility layer by running:

modprobe capidrv

If the module is not available on your machine, please recheck your kernel configuration. If you cannot unload the module after testing, a reboot of your machine could be required.

Setting up minicom for testing:

run as any user:

ls -al /dev/ttyI*

this should display a lot of device files. If no devices show up, check your system installation. (Either devfs is not mounted, or if you dont use devfs your ttyI files must be created by running mknod command)

run as root:

minicom -s

If minicom is not installed, install it, it is included in every distro I know. Minicom drops you into configuration mode. Choose Serial Port Setup, then press A and enter /dev/ttyI1 as device name, then return, then press ESC two times. If minicom drops you out, then you have to check the reason.

Testing your isdn configuration:

Once you have minicom running, please test basic functionality by entering:

AT<RETURN>

It should answer immediatly with OK. If it does not, leave minicom (Ctrl-A, Q) and recheck your driver configuration.

If you have a OK, then enter the following commands one after another, all commands should return OK, if any does not, send an email with detailed description to the author, I will try to help, please also attach the output of the dmesg command run in another shell:

ATZ
AT&F
AT+FCLASS=8
ATS18=1
ATS14=4
AT+VSM=6
ATS13=68
ATS23=1
AT&E0

Now, check if you can call a PSTN phone by entering: ATDT

You should use a telephone number, that is available for shure and that you can pick up. If you pickup the ringing phone, in minicom you should see

ATDT03012345678
VCON

If this fails, maybe you need a prefix, like 0, to place the call. In case of error you will find an isdn4linux error code in your syslog. Call

man isdn_cause

in a shell to view possible error codes. If that does not help you, send a mail to the author along with all information you can get (card, kernel version, syslog output, what you`ve tried so far, etc.).

To leave minicom press Ctrl-A then Q and RETURN.

If you had the VCON message, your card is properly setup. If you used capidrv, remove the module by running rmmod capidrv, recheck the permissions on /dev/capi20 and run the isdngw, it should work fine now.

/* probably I should write a testing tool, that does this procedure... */