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

noreply at bugs.digium.com noreply at bugs.digium.com
Mon Jun 9 09:39:54 CDT 2008


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 09:39 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 09:39  
---------------------------------------------------------------------- 
That's a good point.  I'm not sure the best way to handle it, though.

DTMF emulation relies on frames coming through Asterisk to work properly. 
If _both_ sides of the call are using SIP INFO for DTMF, then audio may not
be flowing through Asterisk even though the DTMF frames are still coming
through.  If we attempt emulation in that case, the digit will not get sent
until the next frame comes through (another DTMF frame, most likely). 

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




More information about the asterisk-bugs mailing list