[asterisk-dev] app_queue.c PAUSALL/UNPAUSEALL reason

Richard Mudgett rmudgett at digium.com
Fri Oct 21 19:48:11 CDT 2016


On Fri, Oct 21, 2016 at 5:46 PM, Troy Bowman <troy at lump.net> wrote:

>
> I always need to apply this patch before putting Asterisk into Production.
>
> The pauses for specific queues get the reason logged properly, but the
> pausealls don't.  I rely on pausalls and their reasons for reporting,
> though I'm trying to get away from it by keeping agents in single queues.
>
> Can we get this in the pipeline somewhere?  Do I have to submit a patch
> this tiny through gerrit?
>
> diff a/apps/app_queue.c b/apps/app_queue.c
> --- a/apps/app_queue.c
> +++ b/apps/app_queue.c
> @@ -7289,7 +7228,7 @@ static int set_member_paused(const char *queuename,
> const char *interface, const
>                                          * but since this affects all
> queues, we cannot.
>                                          */
>                                         ast_queue_log("NONE", "NONE",
> mem->membername,
> -                                               (paused ? "PAUSEALL" :
> "UNPAUSEALL"), "%s", "");
> +                                               (paused ? "PAUSEALL" :
> "UNPAUSEALL"), "%s", S_OR(reason, ""));
>                                 }
>
>                                 set_queue_member_pause(q, mem, reason,
> paused);
>
>
All patches have to go through gerrit whether you submit it or someone else
does.
However, if you wait for someone else it may take awhile.

Richard

https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process
https://wiki.asterisk.org/wiki/display/AST/Code+Review
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20161021/442a8ddd/attachment.html>


More information about the asterisk-dev mailing list