[asterisk-bugs] [Asterisk 0011603]: Queue and Transfer using Local channel

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11603 
====================================================================== 
Reported By:                acidv
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11603
Category:                   Applications/app_queue
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.15  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-19-2007 12:18 CST
Last Modified:              01-02-2008 09:16 CST
====================================================================== 
Summary:                    Queue and Transfer using Local channel
Description: 
I have setup Queue with some agents using SIP phones. I use Local channel
with /n option.

If an agent transfers an answered ACD call to another extension the
original agent remains in use and cannot receive any more ACD calls until
the transferred call is torn down.

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
has duplicate       0011604 Queue and Transfer using Local channel
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 01-02-08 09:16  
---------------------------------------------------------------------- 
I took some time on Monday to analyze this, and unfortunately, if there is
a way to fix this, it won't be easy.

Based on the scenario given, it seems like one of two potential fixes
needs to be made. Either 1) Allow local channels with the /n specified to
become available after transferring or 2) Modify app_queue so that it
actually reads the device state of the underlying channel instead of a
local channel so that the /n option is not necessary to be able to see
availability.

Of these, 1) seems like a bad idea since it contradicts the idea behind
why the /n is there to begin with.

2) seems more feasible, except that the actual channel structure for the
local channel is not available to app_queue when it is getting information
regarding device state changes.

I will look into possibility 2) more closely today and see how much of a
change it would require in order to work. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-02-08 09:16  putnopvut      Note Added: 0076208                          
======================================================================