[asterisk-bugs] [Asterisk 0009382]: Inband DTMF Double digits being sent.

[noreply at bugs.digium.com]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=9382 
====================================================================== 
Reported By:                remiq
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   9382
Category:                   Core/RTP
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     resolved
Asterisk Version:            1.2.14 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
Resolution:                 won't fix
Fixed in Version:           
====================================================================== 
Date Submitted:             03-26-2007 16:46 CDT
Last Modified:              08-03-2007 09:51 CDT
====================================================================== 
Summary:                    Inband DTMF Double digits being sent.
Description: 
When dtmfmode is set to inband for SIP or when using IAX2, you can hear the
DTMF digit twice in the audio stream.  This happens while Asterisk is
parsing the DTMF.  For a fraction of a second, while the end user generated
DTMF is being detected, the DTMF is passed inband.  Once the DTMF is
detected Asterisk silences it and regenerates it.  Sensitive machines like
auto attendants pick up both the brief end user generated tone as well as
the full length asterisk generated tone and ultimately perceive each digit
twice. I was able to eliminate this by not letting Asterisk silence and
regenerate the DTMF digit.  I've attached a fix, I removed some code from
channel.c and dsp.c .

====================================================================== 

---------------------------------------------------------------------- 
 file - 08-03-07 09:51  
---------------------------------------------------------------------- 
1.2 has now entered a security fixes only state. If this issue (which it
shouldn't be with our vldtmf changes) is still applicable to 1.4 please
reopen. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-03-07 09:51  file           Status                   new => resolved     
08-03-07 09:51  file           Resolution               open => won't fix   
08-03-07 09:51  file           Assigned To               => file            
08-03-07 09:51  file           Note Added: 0068368                          
======================================================================