Common problems to avoid while installing
the T400P,E400P and related cards

Q. I'm only using one port on the card and I defined one span and I'm
having problems with the card.
Here's my configuration:

span=1,1,0,esf,b8zs

or

span=1,1,0,cas,hdb3,crc4

A. Since the card has 4 ports it tells zaptel to reserve 4 spans.
It seems that zaptel likes to have all the spans defined in spite
of the fact that you only use one, two, three. So please add the
definitions of the other spans to /etc/zaptel.conf even when other
spans are not used, eg:

span=1,1,0,esf,b8zs
span=2,2,0,esf,b8zs
span=3,3,0,esf,b8zs
span=4,4,0,esf,b8zs

or

span=1,1,0,cas,hdb3,crc4
span=2,2,0,cas,hdb3,crc4
span=3,3,0,cas,hdb3,crc4
span=4,4,0,cas,hdb3,crc4


Q. I installed the stock zaptel driver from asterisk.org and the card doesn't work.
A. Please install the driver from http://t400p.pbxhardware.com/driver/
or http://e400p.pbxhardware.com/driver/
The card doesn't work with the stock driver from Digium.

Q. I want to use the newest zaptel driver but I don't find it at
http://t400p.pbxhardware.com/driver/ or http://e400p.pbxhardware.com/driver/ ?

A. Since the driver code for the card doesn't change alot you may take the files
tor2.c and tor2-hw.h from the latest driver from my website and
overwrite them to
any stock zaptel driver. 99% of the time that will work.

Q. I installed the driver from http://t400p.pbxhardware.com/driver/ or
http://e400p.pbxhardware.com/driver/
but the driver still won't load.

A. Some boxes retain the older version of zaptel in the directories
used by modprobe dependency checker.
Check if you have the following directories/files in your system:

/lib/modules/`uname -r`/misc
/lib/modules/`uname -r`/extra

If you have both of those directories check if the old zaptel files
are there ...

ls -l /lib/modules/`uname -r`/misc/zaptel.*o
ls -l /lib/modules/`uname -r`/extra/zaptel.*o

ls -l /lib/modules/`uname -r`/misc/tor2.*o
ls -l /lib/modules/`uname -r`/extra/tor2.*o

If so please remove at least zaptel.*o and tor2.*o so that the new
driver can be used and do 'make install' again in the driver source directory.
The next modprobe should load the new driver.

A different approach that's faster is to use insmod and not modprobe.
However modprobe doens't need a path to the module and will load any modules
that the current module depends on.

Go to the directory with the driver from http://t400p.pbxhardware.com/driver/
or http://e400p.pbxhardware.com/driver/

eg: if you linked the driver to /usr/src/zaptel
cd /usr/src/zaptel

Remove the tor2 and zaptel modules
rmmod tor2 zaptel

Insmod the zaptel and then tor2
insmod zaptel.o (insmod zaptel.ko on 2.6 kernel)
insmod tor2.o (insmod tor2.ko on 2.6 kernel)
ztcfg

Now the card should be working. However this method is used to check
quickly if this is actually an issue.