[asterisk-bugs] [Asterisk 0017235]: [patch] asterisk dsp always reports detected DTMF length to be 0ms

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17235 
====================================================================== 
Reported By:                frawd
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   17235
Category:                   Core/General
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     confirmed
Target Version:             1.6.2.9
Asterisk Version:           1.6.2.7-rc2 
JIRA:                       SWP-1337 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-04-23 10:21 CDT
Last Modified:              2010-05-04 05:00 CDT
====================================================================== 
Summary:                    [patch] asterisk dsp always reports detected DTMF
length to be 0ms
Description: 
The attached patch makes the DSP report the correct length for DTMF
detected in the audio.

Tested with DAHDI channels (FXS, FXO, ISDN PRI) and SIP channels
configured as "inband".
====================================================================== 

---------------------------------------------------------------------- 
 (0121329) frawd (reporter) - 2010-05-04 05:00
 https://issues.asterisk.org/view.php?id=17235#c121329 
---------------------------------------------------------------------- 
So far so good, I have this in 2 production servers, it resolves my bug but
the length is only multiples of 12.75ms. It's good enough for me.

This resolution could apparently be improved implementing some "sliding
goertzel" algorithm. I could try that if you believe it is needed, the only
thing is that it would represent a core change potentially affecting many
users and I don't think it would ever be committed... 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-05-04 05:00 frawd          Note Added: 0121329                          
======================================================================