[asterisk-users] zap not getting callerid any more

[Rob Hillis]

Brian J. Murrell wrote:
> 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?

It means that Asterisk has detected that the line is ringing. The fact 
that Asterisk pauses after this indicates that it is waiting to receive 
caller ID information.  The chances are that in boosting the receiving 
audio, you're causing the caller ID information to become distorted - 
enough so that Zaptel can no longer decode the caller ID properly.

X100 cards are notorious for problems.  Unless you want to invest in a 
better card, you may just have to live with the problem.