[asterisk-bugs] [DAHDI-linux 0009096]: [patch] DTMF CID without polarity reversal implementation in wctdm for Denmark, Brazil, etc

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=9096 
====================================================================== 
Reported By:                fleed
Assigned To:                murf
====================================================================== 
Project:                    DAHDI-linux
Issue ID:                   9096
Category:                   NewFeature
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for review
Target Version:             2.2.0
====================================================================== 
Date Submitted:             2007-02-18 19:02 CST
Last Modified:              2009-01-22 16:26 CST
====================================================================== 
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...
====================================================================== 

---------------------------------------------------------------------- 
 (0098504) nivio (reporter) - 2009-01-22 16:26
 http://bugs.digium.com/view.php?id=9096#c98504 
---------------------------------------------------------------------- 
I applied patch 9096.nopolaritypatch on dahdi-linux, but I had errors:

patching file drivers/dahdi/wctdm.c
Hunk http://bugs.digium.com/view.php?id=1 succeeded at 226 (offset -2 lines).
Hunk http://bugs.digium.com/view.php?id=2 succeeded at 292 (offset -1 lines).
Hunk http://bugs.digium.com/view.php?id=3 succeeded at 385 (offset -1 lines).
Hunk http://bugs.digium.com/view.php?id=4 FAILED at 424.
Hunk http://bugs.digium.com/view.php?id=5 succeeded at 822 with fuzz 2.
Hunk http://bugs.digium.com/view.php?id=6 FAILED at 840.
Hunk http://bugs.digium.com/view.php?id=7 succeeded at 2530 (offset 1 line).

2 out of 7 hunks FAILED -- saving rejects to file
drivers/dahdi/wctdm.c.rej

patching file drivers/dahdi/wctdm24xxp/wctdm24xxp.h
Hunk http://bugs.digium.com/view.php?id=1 FAILED at 230.

1 out of 1 hunk FAILED -- saving rejects to file
drivers/dahdi/wctdm24xxp/wctdm24xxp.h.rej

patching file drivers/dahdi/wctdm24xxp/base.c
Hunk http://bugs.digium.com/view.php?id=1 succeeded at 224 (offset 12 lines).
Hunk http://bugs.digium.com/view.php?id=2 succeeded at 853 (offset 12 lines).
Hunk http://bugs.digium.com/view.php?id=3 succeeded at 900 (offset 12 lines).
Hunk http://bugs.digium.com/view.php?id=4 FAILED at 1194.
Hunk http://bugs.digium.com/view.php?id=5 FAILED at 1223.
Hunk http://bugs.digium.com/view.php?id=6 succeeded at 4140 with fuzz 2 (offset
113 lines).

2 out of 6 hunks FAILED -- saving rejects to file
drivers/dahdi/wctdm24xxp/base.c.rej

Please, I need work it. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-22 16:26 nivio          Note Added: 0098504                          
======================================================================