[asterisk-bugs] [JIRA] (ASTERISK-25445) AMI QueueStatus broken

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-25445:
------------------------------------------

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> AMI QueueStatus broken
> ----------------------
>
>                 Key: ASTERISK-25445
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25445
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 11.19.0
>            Reporter: Conrad de Wet
>            Assignee: Conrad de Wet
>
> Issue the command queue show XXXX in the CLI, and you get a little report on the agents, callers, and some actual queue details.
> Issue the Action: QueueStatus on the AMI and you get, well, nothing... sometimes. Not sure why with some queues this works, and with others it doesn't. A raw, broken response looks like this:
> Asterisk Call Manager/1.3
> Response: Success
> Message: Authentication accepted
> Event: FullyBooted
> Privilege: system,all
> Status: Fully Booted
> Response: Success
> Message: Queue status will follow
> Event: QueueStatusComplete
> Response: Goodbye
> Message: Thanks for all the fish.
> There are defiantly callers and agents in this queue.



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