[asterisk-bugs] [Asterisk 0012123]: [patch] Sending DTMF when receiving the PROGRESS status

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12123 
====================================================================== 
Reported By:                VoipForces
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12123
Category:                   Applications/NewFeature
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.18 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             03-03-2008 09:18 CST
Last Modified:              03-20-2008 11:06 CDT
====================================================================== 
Summary:                    [patch] Sending DTMF when receiving the PROGRESS
status
Description: 
Some telco account code services (like Allstream here in Canada) required
that the account code DTMF be send as soon as the PROGRESS status is
received but before the channel is considered "Answered" by Asterisk.

When dialing manually this is not an issue as the user hears the beeeep
and punch in the correct DTMF account code.

However when using call files or AMI to initiate the call, the D() flag in
app_dial does not work as D() only sends the DTMF when the channel is
answered.
====================================================================== 

---------------------------------------------------------------------- 
 VoipForces - 03-20-08 11:06  
---------------------------------------------------------------------- 
Further on this, I am hitting the same problem using call files.

I don't have a patch for this yet and would appreciate hints on how to
implement the same on the call file code which is very much different. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-20-08 11:06  VoipForces     Note Added: 0084323                          
======================================================================