[asterisk-bugs] [Asterisk 0017626]: [patch] Dialplan execution stops after awhile on an attended transfer by the calling party (with use of Dial 'g' option)

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17626 
====================================================================== 
Reported By:                ramonpeek
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17626
Category:                   PBX/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.33 
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-07-12 06:42 CDT
Last Modified:              2010-07-12 09:56 CDT
====================================================================== 
Summary:                    [patch] Dialplan execution stops after awhile on an
attended transfer by the calling party  (with use of Dial 'g' option)
Description: 
Dialplan execution stops after awhile on an attended transfer by the
calling party  (with use of Dial() command 'g' option) 
This applies to systems with large dialplans (which we use), small
dialplans do not seem to encounter much problems, due to the delay in SIP
messaging.

If traced, you can see the after Asterisk receives a SIP BYE message, the
dialplan execution is immediately stopped even though there are other
priorities to evaluate in the dialplan.

SEE STEPS TO REPRODUCE (in advanced view mode)
====================================================================== 

---------------------------------------------------------------------- 
 (0124495) ramonpeek (reporter) - 2010-07-12 09:56
 https://issues.asterisk.org/view.php?id=17626#c124495 
---------------------------------------------------------------------- 
Mmm... weird behavior on my side..
Last Friday and this Monday morning I was able to reproduce the problem
easily time after time (see the trace..)
But this afternoon I'm not able to reproduce it anymore.
I'm afraid it has to do with the phones too and the way they respond.
Anyway... I'm not letting go so easily ;-)
I'll try again tomorrow..

In the meantime, who can explain the behavior shown in the debug_log2
file?
(At least that was taken when the error was occurring.)

Please note: 
On the CLI things do seems to stop responding. (at least at my system)
But I've seen that behavior before and its a console issue, since the full
log in /var/log/asterisk/ shows clearly that every priority as been
executed. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-07-12 09:56 ramonpeek      Note Added: 0124495                          
======================================================================