[Asterisk-Users] RE: Ouch, part reset, quickly

[Steve Murphy]

        >I have exactly this problem. When it happens, I lose access to
        some FXS 
        >ports and get Geiger counter style clicking on the FXOs. I just
        opened a 
        >ticket with Digium on the subject, but given what I just read,
        perhaps I 
        >should not have high hopes.
        
        Kinda same with me; although on some of my FXS with crappy Vista
        100's I get
        crackly audio but a brand new Panasonic 2.4g cordless it's
        solid, no solid, no
        problems. Doesn't matter if I swap ports, the Panasonic is fine,
        the vista's
        sound like crap. After a reboot, everything's cool. 
        
        Dealing with the problem by cron'ing a reboot every night. 

I filed a problem report long ago with this issue. Right now, when I
boot, and modprobe the fxs, I include the arg "lowpower=1"

/sbin/modprobe wcfxs lowpower=1

This has somewhat almost eliminated this as a prob, but in recent
builds, I've had to bring down asterisk and restart it because of the
"geiger counter" affect on one or more lines.  (I have One 4-port fxs
card, and two fxo cards).

I have an old moto cordless phone hooked up, and when I drop the phone
in it's cradle, or pull it out, there is some feedback (apparently) into
the lines (what else could it be?) and I get the ouch messages.
Occasionally, the ouch message leads to the geiger affect, but not very 
often. And sometimes the ouch messages come on their own.

To recover, rebooting works, but I can also shut down asterisk, do
rmmod wcfxs
rmmod wcfxo

and then reload them

        /sbin/modprobe wcfxo
        /sbin/modprobe wcfxs lowpower=1
        ztcfg 

and restart asterisk. This has always worked for me, YMMV. It's a bit
faster than a full reboot.

When one of the lines is in a geiger state, make sure to get it's state:

echo regdumps for 3,4,5,6:

./fxstest /dev/zap/3 regdump
./fxstest /dev/zap/4 regdump
./fxstest /dev/zap/5 regdump
./fxstest /dev/zap/6 regdump

echo 
echo stats for 3,4,5,6:
echo

./fxstest /dev/zap/3 stats
echo
./fxstest /dev/zap/4 stats
echo
./fxstest /dev/zap/5 stats
echo
./fxstest /dev/zap/6 stats

fxstest is in the zaptel CVS directory. You may have to compile it.
(make fxstest).

To run the above tests, asterisk can't be running. And, of course, the
exact numbers to use will/may be different on your system. redirect the
output to a file and you'll have some data that might be useful to
Digium.

You might want to run the fxtests when the cards are working right, so
that you can compare working/non-working state. It's basically a dump of
register states, which looks amazingly like what you get from your
typical modem.

murf