[asterisk-bugs] [Asterisk 0018274]: atxfer fails to read data if Dial exetes macro or gosub

Asterisk Bug Tracker noreply at bugs.digium.com
Mon Nov 8 04:59:36 CST 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18274 
====================================================================== 
Reported By:                jmharris
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18274
Category:                   Core/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.2.13 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-11-08 04:54 CST
Last Modified:              2010-11-08 04:59 CST
====================================================================== 
Summary:                    atxfer fails to read data if Dial exetes macro or
gosub
Description: 
We wish to execute commands after a call has connected, so testing using
the M() and U() options to the Dial command. However if either of these are
used (even if the the subroutine only issues NoOps) the inbuilt transfer
functionality can seemingly no longer read the DTMF tones correctly.

This appears to the callee as:
* Phone rings, and the call is connected.
* Asterisk successfully executes the subroutine.
* Call recipient issues https://issues.asterisk.org/view.php?id=1 (or
https://issues.asterisk.org/view.php?id=2) which are defined as the blind
transfer
and attended transfer features codes respectively.
* Caller hears MOH.
* Call recipient hears 'extension?' prompt and dialtone.
* Call recipient presses first digit of the extension.
* Asterisk plays beeper error tone and reconnects the call immediately.
* Asterisk log contains ''

Varying the speed of typing the digits does not matter. It should be noted
that the feature digit timeout and transfer digit timeouts are set, and
that the transfers work just as expected so long as we do not add an M() or
U() to the Dial options.
====================================================================== 

---------------------------------------------------------------------- 
 (0128687) jmharris (reporter) - 2010-11-08 04:59
 https://issues.asterisk.org/view.php?id=18274#c128687 
---------------------------------------------------------------------- 
In the description it was meant to say that the asterisk log reports
'features.c:1444 builtin_atxfer: Did not read data.' 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-11-08 04:59 jmharris       Note Added: 0128687                          
======================================================================




More information about the asterisk-bugs mailing list