[asterisk-bugs] [Zaptel 0012531]: UK CallerID on TDM400P not reliable

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12531 
====================================================================== 
Reported By:                mattbrown
Assigned To:                
====================================================================== 
Project:                    Zaptel
Issue ID:                   12531
Category:                   wctdm
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     confirmed
Zaptel Version:             1.4.10 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-04-26 11:45 CDT
Last Modified:              2009-01-02 10:05 CST
====================================================================== 
Summary:                    UK CallerID on TDM400P not reliable
Description: 
Currently using Asterisk 1.4.19 and Zaptel 1.4.10

Incoming calls (most) fail to populate the CallerID resulting in the
following:

[Apr  26 16:21:13] NOTICE[12685]: chan_zap.c:6191 ss_thread: Got event  
2 (Ring/Answered)...
[Apr  26 16:21:15] WARNING[12685]: chan_zap.c:6254 ss_thread: CID timed  
out waiting for ring. Exiting simple switch

However some calls do populate the callerid.

In order to get reliable CallerID I had to regress to Zaptel 1.4.5.1 and
apply the patch submitted under the following bug report:

http://bugs.digium.com/view.php?id=9264

I note from this bug that this has now been included into Zaptel > 1.4.10
? and requires the switch in zapata.conf fwringdetect=1 however the code
fails to work reliably as it did when patched against 1.4.5.1
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0014023 UK caller ID on X100P, not working
====================================================================== 

---------------------------------------------------------------------- 
 (0097009) jedi98 (reporter) - 2009-01-02 10:05
 http://bugs.digium.com/view.php?id=12531#c97009 
---------------------------------------------------------------------- 
I investigated this problem a couple of years ago and patched chan_zap.c &
later chan_dahdi.c locally in asterisk 1.2.x-1.4.x to ignore the spurious
ring event (Got event 2 (Ring/Answered)) during v23 CID data burst. This
was really simple but whether it's the RIGHT way to do it is another
matter. 

Thing is, as far as I can see, the wctdm driver has no idea that a Ring
event is invalid at this point. chan_zap/dahdi KNOWS that there should be
no interruption. On the other hand the event IS spurious. Patch available
but I have not cluttered this issue with it since it's not for wctdm. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-02 10:05 jedi98         Note Added: 0097009                          
======================================================================