[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:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17235
Category:                   Core/General
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     ready for testing
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-04-28 13:49 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".
====================================================================== 

---------------------------------------------------------------------- 
 (0121083) frawd (reporter) - 2010-04-28 13:49
 https://issues.asterisk.org/view.php?id=17235#c121083 
---------------------------------------------------------------------- 
"immediately" is around 50ms after the last digit.

I will try first to do a correct duration report in the dsp since it
coincidently fixes my problem, it could be a start for me to learn
something (it's also quite irritating to see those 0ms in debug mode).

I would like to avoid using ast_tvnow() every time I have some hit or miss
in digit detection if possible. Is reporting the number of "hits" and
multiplying that with the goertzel block duration really impossible? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-04-28 13:49 frawd          Note Added: 0121083                          
======================================================================