[asterisk-bugs] [Zaptel 0009096]: [patch] DTMF CID without polarity reversal implementation in wctdm for Denmark, Brazil, etc
noreply at bugs.digium.com
noreply at bugs.digium.com
Sat Jun 21 12:52:29 CDT 2008
The following issue requires your FEEDBACK.
======================================================================
http://bugs.digium.com/view.php?id=9096
======================================================================
Reported By: fleed
Assigned To: murf
======================================================================
Project: Zaptel
Issue ID: 9096
Category: NewFeature
Reproducibility: always
Severity: minor
Priority: normal
Status: feedback
Zaptel Version: 1.4.10
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: Yes
Request Review:
======================================================================
Date Submitted: 02-18-2007 19:02 CST
Last Modified: 06-21-2008 12:52 CDT
======================================================================
Summary: [patch] DTMF CID without polarity reversal
implementation in wctdm for Denmark, Brazil, etc
Description:
Caller id signaling in Denmark, Brazil and other places is done through
DTMF tones before the first ring, without polarity reversal to indicate the
start of incoming data. Currently wctdm can only detect dtmf callerid if
there is a polarity reversal before the dtmf digits, so it's not working in
some countries.
This uses the idea reported in bug id 9 for wcfxo, but implements it in
wctdm. It fakes a polarity reversal so that the code already in chan_zap
can take that and pass it through the dtmf bit.
To use, patch and build the zaptel part, load the module with option
dtmf=1. Then use the following in zapata.conf:
callerid=asreceived
usecallerid=yes
cidsignalling=dtmf
hidecallerid=no
cidstart=polarity
Works fine in Brazil, on a Telemar line.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0000009 [patch] DTMF CLIP not supported by Aste...
related to 0012658 [patch] DTMF issues on Zap
related to 0009201 Problem with caller ID detection when D...
======================================================================
----------------------------------------------------------------------
murf - 06-21-08 12:52
----------------------------------------------------------------------
Perhaps I'm jumping the gun, but with fleed not responding, I went ahead
and took the one patch I could inspect, and applied those changes to the
new dahdi equivalents. Then I back-extrapolated those same changes into
the wctdm.c file.
For those of you who haven't switched over to the dahdi drivers from the
zaptel drivers, you will need to do an svn checkout of
http://svn.digium.com/svn/dahdi/linux
and
http://svn.digium.com/svn/dahdi/tools
my patch applies to the stuff in the dahdi/linux dir.
Since I don't have the ability to test any of this, I need everyone
hoping to have these changes merged into the drivers to test the
patch and verify that it works both in the wctdm and 24xxp versions.
I looked at the fxo (wilcard) driver, and I didn't get a warm
and fuzzy feeling that these changes would apply there.
Issue History
Date Modified Username Field Change
======================================================================
06-21-08 12:52 murf Note Added: 0089055
06-21-08 12:52 murf Status assigned => feedback
======================================================================
More information about the asterisk-bugs
mailing list