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

noreply at bugs.digium.com noreply at bugs.digium.com
Thu Mar 20 14:20:15 CDT 2008


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 14:20 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.
====================================================================== 

---------------------------------------------------------------------- 
 juggie - 03-20-08 14:20  
---------------------------------------------------------------------- 
A workaround for the .call files or Manager Action Originate would be to
place your call on a local channel eg, Local/12345 at mycoolcontext

then in [mycoolcontext] you pattern match your number your dialing and do
your Dial(Zap/g1/${EXTEN},...,D()) etc. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-20-08 14:20  juggie         Note Added: 0084353                          
======================================================================




More information about the asterisk-bugs mailing list