asterisk users - Aug 2005 - Compile ZAPTEL warning and Strange Congestion

Starting - oh - three weeks ago I started getting this when I compiled
zaptel stuff:

In file included from
/lib/modules/2.4.26smp/build/include/linux/spinlock.h:6,
                 from
/lib/modules/2.4.26smp/build/include/linux/module.h:11,
                 from wct4xxp.c:31:
/lib/modules/2.4.26smp/build/include/asm/system.h: In function
`__set_64bit_var':
/lib/modules/2.4.26smp/build/include/asm/system.h:190: warning:
dereferencing type-punned pointer will break strict-aliasing rules
/lib/modules/2.4.26smp/build/include/asm/system.h:190: warning:
dereferencing type-punned pointer will break strict-aliasing rules

Just a warning - didn't bother me too much as everything worked any way.
But it did come up in most of the source files.  I think it's just a
compiler option missing. 2.4.26 isn't exactly new 8-)

I only use my * box for a home PBX - nothing critical about it.
Then I started noticing this in the CLI:

Jul 29 13:25:54 WARNING[9075]: chan_zap.c:3696 zt_handle_event:
Ring/Off-hook in strange state 7 on channel 4
Jul 29 13:26:06 NOTICE[9078]: chan_zap.c:5797 ss_thread: Got event 2
(Ring/Answered)...
Jul 29 13:26:12 WARNING[9078]: chan_zap.c:3696 zt_handle_event:
Ring/Off-hook in strange state 7 on channel 4
Jul 29 13:26:25 NOTICE[9081]: chan_zap.c:5797 ss_thread: Got event 2
(Ring/Answered)...
Jul 29 13:26:31 WARNING[9081]: chan_zap.c:3696 zt_handle_event:
Ring/Off-hook in strange state 7 on channel 4
Jul 29 13:26:45 WARNING[9086]: chan_zap.c:5871 ss_thread: CallerID
returned with error on channel 'Zap/4-1'

I have this in my extension.conf

[default]
exten => s/6305551212,1,Congestion      ; TEST OF CONGESTION

It used to give a busy/congestion signal but now it just rings.

"","6305551212","s","default","""ILLINOIS
CALL""
<6305551212>","Zap/4-1","","Congestion","","2005-07-29
13:25:49",,"2005-07-29 13:25:57",8,0,"NO
ANSWER","DOCUMENTATION"
"","","s","default","","Zap/4-1","","Congestion","","2005-07-29
13:26:06",,"2005-07-29 13:26:14",8,0,"NO
ANSWER","DOCUMENTATION"
"","","s","default","","Zap/4-1","","Congestion","","2005-07-29
13:26:25",,"2005-07-29 13:26:33",8,0,"NO
ANSWER","DOCUMENTATION"

And it really looks like the incoming analog line is 'bouncing' or
something. I don't think my zapata.conf has changed since I got the
TDM411B.

[trunkgroups]
[channels]
context=default
switchtype=national
signalling=fxo_ls
rxwink=300              ; Atlas seems to use long (250ms) winks
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1
immediate=no
context=default
signalling=fxs_ks
channel => 4
context=local
signalling=fxo_ks
callerid="Desk Phone" <6601>
channel => 1

So anyway - I don't get it.  Any one else have anything like this
happening?

Brett