[Asterisk-Users] X100P stopped working

[Rich Adamson]

> I recompiled Asterisk with the aggressive echo cancellation on.  That's
> all I changed, honest.  After recompiling, it refused to run.  I tried
> updating the source, etc, and eventually went back to no echo
> cancellation.  Every time, I got this error while starting Asterisk. 
> Please help!  I have no idea what went wrong.
> 
> Oh, and yes, wcfxo and zaptel are loaded, I checked with lsmod.  I
> rebooted a few times too, to make sure everything had been cleared out.
> 
> ===================================================================
> 
> [chan_zap.so] => (Zapata Telephony w/PRI)
>   == Parsing '/etc/asterisk/zapata.conf': Found
> WARNING[1074404064]: File chan_zap.c, Line 6986 (load_module): Ignoring
> rxwink
> WARNING[1074404064]: File chan_zap.c, Line 626 (zt_open): Unable to
> specify channel 1: No such device or
> address
> ERROR[1074404064]: File chan_zap.c, Line 4949 (mkintf): Unable to open
> channel 1: No such device or address
> here = 0, tmp->channel = 0, channel = 1
> ERROR[1074404064]: File chan_zap.c, Line 6730 (load_module): Unable to
> register channel '1'
> WARNING[1074404064]: File loader.c, Line 301 (ast_load_resource):
> chan_zap.so: load_module failed, returning -1
> WARNING[1074404064]: File loader.c, Line 396 (load_modules): Loading
> module chan_zap.so failed!
> Warning, flexibel rate not heavily tested!
> Ouch ... error while writing audio data: : Broken pipe

I'm probably not going to be of much help since I'm rather new at this
as well. I do have two x100p's running on RH9 though.

Check your /etc/zaptel.conf to ensure you have something like:
fxsks=1
loadzone=us

Might try:
 /usr/src/zaptel/ztcfg -vv

If I run /sbin/lsmod, I see:
Module                  Size  Used by    Not tainted
<snip>
wcfxo                   9056   2 
zaptel                180128   8  [wcfxo]
ppp_generic            24444   0  [zaptel]
<snip>

Not sure about this, but using rmmod, insmod and lsmod to unload and
reload might help as the running (old) modules vs newly compiled modules
might be causing some sort conflict. (Out of my league.)