Summary: | ASTERISK-21781: on reload app_queue should check/prune queue members against associated devices in configuration | ||
Reporter: | André Emerich (aemerich) | Labels: | |
Date Opened: | 2013-05-13 16:31:28 | Date Closed: | 2013-05-21 16:04:49 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | Applications/app_queue Resources/res_pjsip |
Versions: | 1.8.20.1 | Frequency of Occurrence | |
Related Issues: | |||
Environment: | Debian 6, Asterisk, Dahdi | Attachments: | |
Description: | I have an Asterisk PBX in production which I got a strange error.
A member, SIP/1234, was in a queue. I removed the sip configs of 1234 exten from sip.conf After this, I did a "reload" on Asterisk. So, if I look at the sip peers "sip show peers" the exten isn't there anymore. But, if I take a look at the Queue "queue show" the exten is there with the last status. For example: SIP/1234 (dynamic) (Not in use) has taken no calls yet If, at least, the Asterisk put the status to Unavailable, it would help to identify a problematic exten. | ||
Comments: | By: Rusty Newton (rnewton) 2013-05-21 16:04:25.785-0500 This is expected behavior. The behavior you desire would certainly be an improvement, but the current lack of it is not a bug. If there was no change to queue configuration then app_queue is not actually reloading. You are welcome to submit a patch for this behavior or see if another developer on the dev list or IRC is interested in tackling it. http://www.asterisk.org/community/discuss If you are able to produce a patch you can ping a bug marshal on #asterisk-bugs to re-open this issue. |