Summary:ASTERISK-14073: DTMF's are not sent to the bridge channel if they are used by any built-in or dynamic feature
Reporter:andrebarbosa (andrebarbosa)Labels:
Date Opened:2009-05-06 04:20:59Date Closed:2011-06-07 14:00:28
Versions:Frequency of
Environment:Attachments:( 0) dtmf.log
Description:I notice this when calling an outbound IVR that asked to press the "#" sign, I found that the # is not sent to the bridge channel unless you press another key after that.

This is a regression introduce by the issue ASTERISK-13435.
I have revert that patch and the problem is fixed, although the attended transfers will no work anymore.

I've tried to fix this with no luck till now, I wonder if somecone can look at it.


Here is the changelog of the commit that brokes this:

* main/channel.c: Fix bridging regression from commit 176701 This
fixes a bad regression where the bridge would exit after an
attended transfer was made. The problem was due to nexteventts
getting set after the masquerade which caused the bridge to
return AST_BRIDGE_COMPLETE. (closes issue ASTERISK-13435) Reported by:  tim_ringenbachHere
Comments:By: Joshua C. Colp (jcolp) 2009-05-06 08:21:23

This issue was already fixed in revision 191488 by jpeeler and will be in the next release.