[asterisk-bugs] [JIRA] (ASTERISK-24803) (Un)PauseQueueMember AMI action writes event to queue_log even on failure

[Matt Jordan (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-24803?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=225018#comment-225018 ] 

Matt Jordan commented on ASTERISK-24803:
----------------------------------------

That sounds reasonable.

Would you like to provide a patch?

> (Un)PauseQueueMember AMI action writes event to queue_log even on failure
> -------------------------------------------------------------------------
>
>                 Key: ASTERISK-24803
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24803
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/ManagerInterface
>    Affects Versions: 11.14.0
>            Reporter: WRP
>            Severity: Minor
>
> If you attempt to pause an interface/agent that is not in a queue from the Asterisk CLI or via the Asterisk AMI, an error is returned that the interface/agent couldn't be found and so it couldn't be paused or unpaused. When this error occurs in the Asterisk CLI, no PAUSE, PAUSEALL, UNPAUSE, or UNPAUSEALL event is written to queue_log. This makes sense, as the command wasn't successful, so it shouldn't be logged.
> This behavior differs when this error situation arises via the Asterisk AMI. If the PauseQueueMember or UnpauseQueueMember command is run and an error is returned, an event is still logged to queue_log. This creates issues downstream when other applications try to process queue_log. They see these pause and unpause events and falsely believe that they actually occurred.
> My proposal to a solution is to eliminate writing to the queue_log when PauseQueueMember or UnpauseQueueMember completes with an error.



--
This message was sent by Atlassian JIRA
(v6.2#6252)