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

[noreply at bugs.digium.com]

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:                   major
Priority:                   normal
Status:                     new
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:             04-26-2008 11:45 CDT
Last Modified:              04-26-2008 11:55 CDT
====================================================================== 
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
====================================================================== 

---------------------------------------------------------------------- 
 mattbrown - 04-26-08 11:55  
---------------------------------------------------------------------- 
I should also add that in regressing to Zaptel 1.4.5.1 distinctive ring
does not detect correct ring patterns - all calls show as 0,0,0. This is
also true with Zaptel 1.4.10 (however I assume this is a Chan_Zap issue,
not a Zaptel issue - should a separate bug be filed ?) 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
04-26-08 11:55  mattbrown      Note Added: 0086056                          
======================================================================