[Home]

Summary:ASTERISK-25445: AMI QueueStatus broken
Reporter:Conrad de Wet (Conrad)Labels:
Date Opened:2015-10-05 07:04:51Date Closed:2020-01-14 11:14:04.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:
Versions:11.19.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description: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.
Comments:By: Asterisk Team (asteriskteam) 2015-10-05 07:04:53.348-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: Rusty Newton (rnewton) 2015-10-06 09:51:59.860-0500

Can you provide output showing how it works sometimes and not others?

Can you also provide the CLI command output returned for comparison with the AMI action?
By: Conrad de Wet (Conrad) 2015-10-08 11:05:31.702-0500

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.
By: Rusty Newton (rnewton) 2015-11-06 07:56:41.324-0600

I'm unable to reproduce.

To be clear.. you are no longer able to reproduce the issue correct?

So odd that changing the name of the queue resolved the behavior...
By: Asterisk Team (asteriskteam) 2015-11-20 12:00:19.864-0600

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