[asterisk-bugs] [Asterisk 0012778]: [patch] Incorect duration values in INFO messages when emulation occurs

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12778 
====================================================================== 
Reported By:                tsearle
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   12778
Category:                   Core/Channels
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 119891 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             06-03-2008 02:45 CDT
Last Modified:              06-09-2008 08:05 CDT
====================================================================== 
Summary:                    [patch] Incorect duration values in INFO messages
when emulation occurs
Description: 
Here is the scenario I was doing

Sip user A (dtmfmode=rfc2833) calls Sip User B (dtmfmode=info)

sip user A sends a very brief dtmf (less than 80) ms,  the INFO message
sent to the other side has a very long duration!!!
====================================================================== 

---------------------------------------------------------------------- 
 russell - 06-09-08 08:05  
---------------------------------------------------------------------- 
I have uploaded a different patch which I think will address this issue.

I think that the block of code that you have changed shouldn't be executed
at all in the case that END_DTMF_ONLY is set (the other side is using
INFO).  It doesn't make any sense to do the emulation in that case.

Please test this patch and see if it still fixes your issue. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
06-09-08 08:05  russell        Note Added: 0088471                          
======================================================================