| Summary: | ASTERISK-07455: QueueStatus when using realtime | ||
| Reporter: | Havard Sorbo (hs) | Labels: | |
| Date Opened: | 2006-08-03 10:30:51 | Date Closed: | 2011-06-07 14:07:23 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/ManagerInterface |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | When using realtime, Queuestatus doesn't show queues that haven't been dialed after startup (of asterisk deamon), nor does it inform us of its existence when dialed to. This results in a Join event to a "non-existing" Queue. It's my opinion that Queuestatus should show the queues or a QueueParams-event should be pushed before a Join event. | ||
| Comments: | By: Serge Vecher (serge-v) 2006-09-06 10:37:42 hs: we need logs here illustrating the problem ... By: Havard Sorbo (hs) 2006-09-06 15:04:21 I'm not very sure how you want this to be logged. I can restart my asterisk and in the management interfece run Queuestatus and you will see no queues, then dial a queue which will show you a join to the Queue, run Queuestatus again an you will see that queue. Would that be satisfactory? By: Jason Parker (jparker) 2006-09-26 16:46:18 I disagree with this, and believe it was intended behavior to not do so. If they aren't loaded in memory, it shouldn't know about them - that's the whole point of using realtime queues, instead of just a static queues.conf. If you feel this should be reopened, please contact a bug marshal on freenode IRC in the channel #asterisk-bugs. | ||