Summary:	ASTERISK-11961: Agent cannot unlock a channel after transfer calls
Reporter:	Rodrigo R Passos (rodrigopassos)	Labels:
Date Opened:	2008-05-02 11:51:11	Date Closed:	2011-06-07 14:08:00
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Applications/app_queue
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Hi all, I have the following problem: When one agent transfer one call to another extension, the agent not change the status of the In Use. To solve this problem, I put the agent to ring in use on my queues.conf, but all calls ring on my agent and this is not available to be connected and the queues_log show RINGNOANSWER to this agent. When a put ringinuse  = no, and the agent transfer a call to another extension, the call cannot be connect while this transfered call is disconnected (hangup). This is a bug? Have a patch to solve this problem?
Comments:	By: Russell Bryant (russell) 2008-05-02 17:17:20 Is this issue marked private for a reason? By: Rodrigo R Passos (rodrigopassos) 2008-05-05 07:18:22 for no reason.. you it could move for public? By: Rodrigo R Passos (rodrigopassos) 2008-05-06 07:02:30 Ok. I go to modify my structure not to use more dynamic members in my queue structure. This issue can move to closed. By: Mark Michelson (mmichelson) 2008-05-06 08:58:16 rodrigopassos: I will close this issue as you recommended. You may have noticed that last night I linked this issue to ASTERISK-11085. If you check that issue, you'll see the difficulties involved with reporting device state accurately for queue members which are mapped to Local channels. You will also see the solution that was designed there. Unfortunately the fix that was made only went into trunk (and now is also in the 1.6.0 beta releases) and not into 1.4.