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

[Conrad de Wet (JIRA)]

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

Conrad de Wet commented on ASTERISK-25445:
------------------------------------------

I have managed to clear up the issue, but how i did this may lead to you a solution for this issue.

Firstly, the background - the queues are all in a database (mysql). The problem was that for one customer the AMI output of the QueuStatus was as described (empty) - where other queues where fine. I realized that of the possible queues, there was only the one queue that was an issue - and even after restarting the service (core restart now and service asterisk restart), the issue never resolved. This behavior meant that the problem had to be in some kind of cache (saved data)  probably in database /queue/.

To solve the issue, i stared by removing the members with the command queue remove member xxx from yyyy for all the members. still this did not resolve the issue. Then i renamed the queue (in the DB), and did an AMI call on the QueueStatus of the newly named queue - this worked! I then renamed it back, and again called the status on the old name, it now worked. I added the members again... and everything worked fine.

> 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)