[asterisk-bugs] [JIRA] (ASTERISK-21781) on reload app_queue should check/prune queue members against associated devices in configuration

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-21781:
-----------------------------------------

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.
                
> on reload app_queue should check/prune queue members against associated devices in configuration
> ------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21781
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21781
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Applications/app_queue, Resources/res_sip
>    Affects Versions: 1.8.20.1
>         Environment: Debian 6, Asterisk, Dahdi
>            Reporter: André Emerich
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira