Summary:	ASTERISK-25215: Differences in queue.log between Set QUEUE_MEMBER and using PauseQueueMember
Reporter:	Lorne Gaetz (lgaetz)	Labels:
Date Opened:	2015-06-30 13:25:08	Date Closed:	2015-08-19 08:42:51
Priority:	Trivial	Regression?
Status:	Closed/Complete	Components:	Applications/app_queue
Versions:	13.4.0	Frequency of Occurrence
Related Issues:	is duplicated by ASTERISK-25159 queue_log does not log PAUSE events for pause states set with QUEUE_MEMBER
Environment:	FreePBX Distro 6.12.65-28 (FreePBX 12)	Attachments:
Description:	FreePBX defines a feature code that allows queue agents to toggle between pause/unpause for all queues or individually for each queue. The dialplan that FreePBX currently uses for pausing and unpausing agents is: Set(QUEUE_MEMBER([queue_name],paused,[member_name])=0/1) Our users have pointed out that when they pause agents using the FreePBX feature code, that the pause is not logged in queue.log, but when they test by pausing agents at the Asterisk CLI pauses get logged as expected. We have tested pausing queue agents by using the dialplan commands PauseQueueMember and UnpauseQueueMember and the pauses do get logged in queue.log as expected. Questions: 1) Are the differences in logging between the two pause methods by design? 2) Is there a "preferred" method of pausing agents between the two methods noted? i.e. should FreePBX examine transitioning toward using the dialplan commands  PauseQueueMember and UnpauseQueueMember? 3) If the current state of pause logging is not by design, would it be possible to get agent paused by setting QUEUE_MEMBER logged in the same way as the dialplan commands? Cross reference to FreePBX jira ticket: http://issues.freepbx.org/browse/FREEPBX-9463 Lorne Gaetz Sangoma Technologies
Comments:	By: Asterisk Team (asteriskteam) 2015-06-30 13:25:10.158-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Philippe Lindheimer (p_lindheimer) 2015-06-30 13:48:35.705-0500 From a quick review of some dated 11.X source code on my laptop, the event is simply not being called when paused the QUEUE_MEMBER() but all the information is there to call it if the pause state is determined to have changed. By: Matt Jordan (mjordan) 2015-06-30 13:49:53.840-0500 To answer the questions: {quote} 1) Are the differences in logging between the two pause methods by design? {quote} Nope. Pretty sure the function just got missed. {quote} 2) Is there a "preferred" method of pausing agents between the two methods noted? i.e. should FreePBX examine transitioning toward using the dialplan commands PauseQueueMember and UnpauseQueueMember? {quote} I usually prefer functions to change state, as it can also be used by external APIs. So actually, {{QUEUE_MEMBER}} is kind of nice that way. That being said, there's a bug, so definitely use what works. {quote} 3) If the current state of pause logging is not by design, would it be possible to get agent paused by setting QUEUE_MEMBER logged in the same way as the dialplan commands? {quote} Sure! It is a bug :-)