[asterisk-bugs] [Asterisk 0010384]: When using Asterisk RealTime, processing does not continue after queue command

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10384 
====================================================================== 
Reported By:                unservices
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10384
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:            1.2.23  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!): 45332 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             08-05-2007 11:19 CDT
Last Modified:              08-05-2007 15:58 CDT
====================================================================== 
Summary:                    When using Asterisk RealTime, processing does not
continue after queue command
Description: 
I'm using asterisk realtime. The extensions db does have 3 records for each
incoming number - first is a deadagi to prepare some settings, then either
a dial or queue command, finally another deadagi to finish some
calculations.

When the instruction sequence is DEADAGI -> DIAL SIP -> DEADAGI everything
works fine. But when the sequence is DEADAGI -> QUEUE -> DEADAGI we don't
have the return to process the last agi script.

It sounds that at the end of the queue processing the control is not
coming back to the extensions information. Maybe a bug in the queue
application?
====================================================================== 

---------------------------------------------------------------------- 
 Corydon76 - 08-05-07 15:58  
---------------------------------------------------------------------- 
Both Queue and Dial will terminate (hangup) the call after a bridge occurs.
 Dial allows an additional option (g) to continue the call in the dialplan
after a hangup occurs on the bridge.  Queue does not have that option, but
the lack of that option is not a bug.

It is best to use the 'h' extension if you'd like to continue
postprocessing after the call has been hungup.  If you need to, you may set
a channel variable prior to the execution of Dial or Queue (i.e.
Set(lastexten=${EXTEN}), leaving a flag for the post hangup AGI script to
use to determine what actions to take. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-05-07 15:58  Corydon76      Note Added: 0068459                          
======================================================================