asterisk users - Jul 2008 - zap not getting callerid any more

I have a wildcard 100 xp on my pots line and all was working just fine
up until a few days ago when all of a sudden it stopped receiving caller
id on incoming calls.  I know caller id is being presented on the line
as the analog set on the same line always gets it.

What is strange is that this all of a sudden started happening out of
the blue.  It was working one day and then not the next.  No asterisk
changes at all in that time frame.

I have the following in my zapata.conf:

signalling=fxs_ks                     
usecallerid=yes
cidsignalling=bell
cidstart=ring
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=yes
rxgain=10.9
txgain=0.0
group=1
callgroup=1
pickupgroup=1
immediate=no
callerid=asreceived
channel => 1

Any ideas what could have happened, or how to go about troubleshooting
this?  Is there some amount of debug I can enable to see why it's
failing?

b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20080713/29c25e44/attachment.pgp

On Sun, 2008-07-13 at 10:22 -0400, Brian J. Murrell
wrote:
> I have a wildcard 100 xp on my pots line and all was working just fine
> up until a few days ago when all of a sudden it stopped receiving caller
> id on incoming calls.  I know caller id is being presented on the line
> as the analog set on the same line always gets it.
...
> rxgain=10.9
> txgain=0.0
To add more information, I tried setting my rxgain back to 0.0 and CID
now seems more reliable.  So again I went through the process of setting
rxgain using a milliwatt number (not at all local however as I can't
find one near me) and ztmonitor and had to adjust it down by 4 points to
10.5 to get it close to the magical 14844.  CID was again, 100%
unreliable.

One thing I have noticed is that in the cases where the wildcard cannot
determine the CID (i.e. because the rxgain is up around 10.5), I get
this in my asterisk console:

[Jul 15 08:04:09] NOTICE[26696]: chan_zap.c:6670 ss_thread: Got event 18 (Ring
Begin)...

And indeed, Asterisk seems to take longer to pass the call to the
destination extensions, exactly as if it's struggling to get the CID on
the analog line.

Does that message from Asterisk mean anything to anyone?

b.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20080715/ab32e8c5/attachment.pgp