[asterisk-bugs] [Asterisk 0014815]: [patch] DTMF Appears to be broken from certain sources on asterisk 1.4.24 - double digit.

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14815 
====================================================================== 
Reported By:                geoff2010
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   14815
Category:                   Core/RTP
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     feedback
Target Version:             1.4.25
Asterisk Version:           1.4.24 
Regression:                 Yes 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-04-02 15:38 CDT
Last Modified:              2009-05-04 18:36 CDT
====================================================================== 
Summary:                    [patch] DTMF Appears to be broken from certain
sources on asterisk 1.4.24 - double digit.
Description: 
I am having some trouble with 1.4.24.  This appears to be a regression
since 1.4.21.1 as I have just recently upgraded and started to experience
the problem.

When calling my asterisk box from a cell phone the system detects double
DTMF digits.  When calling from a landline or pure SIP device DTMF
detection works fine.  I have determined that the cell phone is sending the
RTP DTMF payload about 2x more than the other devices, but as far as I can
tell it should still be considered a single digit as per the RFC.

Attached are two TXT files of pcap exports which show the dump for a
working DTMF interaction, and one for a failure situation.

Please let me know if I can provide any further information.

Thanks,
Geoff
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0014460 Asterisk plays a continuous tone foreve...
related to          0015024 DTMF is not working correctly for cell ...
====================================================================== 

---------------------------------------------------------------------- 
 (0104182) dimas (reporter) - 2009-05-04 18:36
 http://bugs.digium.com/view.php?id=14815#c104182 
---------------------------------------------------------------------- 
Geoff,
at the first glance log file looks Ok.

moliveras,
well, my code does its job properly - there are lines in the log saying:

May  4 22:20:59 mikeo_asterisk1 asterisk[32616]: DEBUG[3457]: rtp.c:1329
in ast_rtp_read: TIMEOUT now=2483902209, begin=2483898769, timeout=0
May  4 22:20:59 mikeo_asterisk1 asterisk[32616]: DEBUG[3457]: rtp.c:627 in
send_dtmf: Sending dtmf: 53 (5), at 192.168.196.40


which means we did not see DTMF end within specified timeout so we forcing
it. However for some reason DTMF END message we sent were not processed by
the Asterisk core at all. The only thing I can do here is to add some more
logging to other places and ask you to re-run the test.

I will upload new patch for you in 5 minutes. Please apply it and try
again. Note: now there is no need to do "rtp debug". 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-04 18:36 dimas          Note Added: 0104182                          
======================================================================