[asterisk-bugs] [Zaptel 0012531]: UK CallerID on TDM400P not reliable
Asterisk Bug Tracker
noreply at bugs.digium.com
Sun Sep 28 12:24:59 CDT 2008
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: 2008-09-28 12:24 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
======================================================================
----------------------------------------------------------------------
(0092922) sruffell (administrator) - 2008-09-28 12:24
http://bugs.digium.com/view.php?id=12531#c92922
----------------------------------------------------------------------
I committed the changes to the wctdm driver, but not the wctdm24xxp since
there are now changes to support Neon MWI in that same place of the code,
and any fix will need to be tested more than I can currently. If someone
wants to make a new patch for the wctdm24xxp driver, I probably can arrange
to test it with Neon.
Issue History
Date Modified Username Field Change
======================================================================
2008-09-28 12:24 sruffell Note Added: 0092922
======================================================================
More information about the asterisk-bugs
mailing list