Summary: | ASTERISK-19242: AMI QUEUESTATUS not working correctly in 10.0.1 (CLI queue show not working correct as well) | ||
Reporter: | Jeff Hoppe (jhoppebugs) | Labels: | |
Date Opened: | 2012-01-24 17:06:53.000-0600 | Date Closed: | 2012-01-30 12:08:41.000-0600 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | |
Versions: | 10.0.1 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | Attachments: | ||
Description: | I currently store queues in a realtime database. I have 261 queues. I am trying to upgrade from 1.6.2 to 10.0.1 and have run into issues regarding the queues. When I do a "queue show" at the CLI in 1.6.2, I will get information on all queues I have stored in the database (261) and when I run QUEUESTATUS action from an external app, I will get all queues in Asterisk (261). However, in 10.0.1, when I run "queue show" at the CLI, I will only get information on 1 queue (this queue is the ONLY one that has queue members defined in the realtime database). However, I need to get all queues back to the external app using AMI, whether or not they have queue members currently defined. Also, when I run the QUEUESTATUS action, I will get that one queue that has queue members back to my application approximately 100 times. I don't believe the change in the "CLI> queue show" has changed functionality since 1.6.2, from my reading of the upgrade logs from 1.6.2 to 1.8 and from 1.8 to 10. | ||
Comments: | By: Richard Mudgett (rmudgett) 2012-01-24 18:02:36.297-0600 This appears to be a duplicate of ASTERISK-19170. By: Jeff Hoppe (jhoppebugs) 2012-01-25 13:13:44.632-0600 Sorry, I thought Asterisk-19170 was fixed and closed but was still an issue, but I see now that the target release for the fix is for 10.1.0 and I am currently using 10.0.1 By: Matt Jordan (mjordan) 2012-01-27 08:21:34.748-0600 Please test with 10.1.0-rc2 (or when it becomes available) and let us know if that resolves this issue. By: Jeff Hoppe (jhoppebugs) 2012-01-30 12:03:48.204-0600 I tested it with 10.1.0 and seems to be fixed. Thanks. |