[Asterisk-Users] TDM400 hardware problems?

John Morris
Wed, 03 Mar 2004 22:55:24 -0000

Hi!  I didn't get an answer on this, so I'm going to be annoying and
try again.  For some reason, it looks like two of my channels on my
TDM400 stopped working for no good reason.

Asterisk stopped working on my main extension today (it does this
every week or so).  I usually remedy this by stopping asterisk,
removing the kernel modules, reinstall them, and restart asterisk,
everything's good again.  I did this today, but at the step where I
install the modules, the kernel hung, with this in /var/log/messages:

Feb 29 00:51:01 squid kernel: Found a Wildcard FXO: Wildcard X101P
Feb 29 00:51:01 squid kernel: Found a Wildcard FXO: Wildcard X101P
Feb 29 00:51:01 squid kernel: PCI: Enabling device 00:0c.0 (0000 -> 0003)
Feb 29 00:51:01 squid kernel: Freshmaker version: ff
Feb 29 00:51:01 squid kernel: 00 != ff
Feb 29 00:51:01 squid kernel: 01 != ff
[....]
Feb 29 00:51:01 squid kernel: 0e != ff
Feb 29 00:51:01 squid kernel: 0f != ff

So I reboot, and try to bring things back up again.  But now the first
two channels on my TDM400 aren't working, a new one.  The light on
them isn't glowing, and installing the module I get this:

Feb 29 01:09:15 squid kernel: Zapata Telephony Interface Registered on major
19\6
Feb 29 01:09:18 squid kernel: Freshmaker version: 62
Feb 29 01:09:28 squid kernel: Freshmaker passed register test
Feb 29 01:09:28 squid kernel: Timeout waiting for calibration of module 0
Feb 29 01:09:28 squid kernel: ProSlic died on Calibration.
Feb 29 01:09:28 squid kernel: Module 0: Not installed
Feb 29 01:09:28 squid kernel: Timeout waiting for calibration of module 1
Feb 29 01:09:28 squid kernel: ProSlic died on Calibration.
Feb 29 01:09:28 squid kernel: Module 1: Not installed
Feb 29 01:09:28 squid kernel: Module 2: Initialized
Feb 29 01:09:28 squid kernel: Module 3: Initialized
Feb 29 01:09:28 squid kernel: Found a Wildcard FXS: Wildcard S400P Prototype (4\
modules)

Luckily, at least the last two are working, so I plugged my extensions
into those, modified extensions.conf to reflect the change, and I'm
working again for the moment.

Anyone see something I'm missing here?  Another similar thread on the
list, someone said maybe it's a bad module, but I don't understand why
*two* would suddenly stop working at the same time after many months.

I am running a rather old asterisk version, 0.4.0, and whatever
zaptel/zapata modules were current then, with kernel 2.4.20.

Thanks for any help!

        John

--
John Morris
+1-512-480-0200x1002