[asterisk-bugs] [Asterisk 0013737]: [patch] Overlap dialing blocks

[Asterisk Bug Tracker]

The following issue has been UPDATED. 
====================================================================== 
http://bugs.digium.com/view.php?id=13737 
====================================================================== 
Reported By:                smurfix
Assigned To:                jpeeler
====================================================================== 
Project:                    Asterisk
Issue ID:                   13737
Category:                   Core/Channels
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-10-18 14:00 CDT
Last Modified:              2009-01-22 13:49 CST
====================================================================== 
Summary:                    [patch] Overlap dialing blocks
Description: 
The problem: when a channel is not connected and DTMF events arrive "too
fast", they get stored in the channel buffer until (a) sufficient time has
passed and (b) a voice frame has arrived.

Unfortunately, when you're in overlap dialing and the channel's audio is
not yet connected, there _is_ no voice frame, thus dialing blocks.

A quick fix is to surround wait_for_answer() with calls to set/clear the
AST_FLAG_END_DTMF_ONLY flag (patch attached).
====================================================================== 

---------------------------------------------------------------------- 
 (0098474) jpeeler (administrator) - 2009-01-22 13:48
 http://bugs.digium.com/view.php?id=13737#c98474 
---------------------------------------------------------------------- 
After looking at this issue and the way DTMF is handled now, this should no
longer be an issue. The commit that changed this behavior was in 163448. If
you find that there is still a problem, please reopen. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-22 13:49 jpeeler        Note Added: 0098474                          
2009-01-22 13:49 jpeeler        Status                   assigned => closed  
2009-01-22 13:49 jpeeler        Resolution               open => fixed       
======================================================================