[Asterisk-Users] TDM04B and T100P driver loading issue

[Rich Adamson]

Just spent the better part of two days trying to identify why
a new RH ES3 system with current cvs is unstable. The stability
relates to the TDM04B (4-port fxo) arbitraly failing after "some"
period of time, and when it fails, the iax2 links fail to a
one-way data flow (as observed with a sniffer). No log messages
or CLI indications as to it failing.

After it fails, there does not seem to be any way to restart the
system, including rebooting.

By changing the order in which the drivers are installed (in the
/etc/rc.d/init.d/zaptel script), it now functions correctly. Time
will tell if early failures are still an issue, but at least now
the "service zaptel stop" and "service zaptel start" will
recover the asterisk box.

I changed the loading order in the zaptel script to be:
MODULES="torisa tor2 wct4xxp wcte11xp wctdm wct1xxp wcfxo wcusb"
RMODULES="wcusb wcfxo wct1xxp wctdm wcte11xp wct4xxp tor2 torisa"

where the wctdm appears "before" the wct1xxp, and it seems to
work reliably. (The two cards are on different interrupts.)

Anyone have any thoughts as to why the loading order seems to be
an issue????

Rich