[asterisk-bugs] [JIRA] (ASTERISK-21517) API Improvements: refactor app_queue to listen for a Transfer stasis message and update the Queue Log appropriately

Matt Jordan (JIRA) noreply at issues.asterisk.org
Wed Apr 17 18:22:05 CDT 2013


     [ https://issues.asterisk.org/jira/browse/ASTERISK-21517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan updated ASTERISK-21517:
-----------------------------------

    Status: Open  (was: Triage)
    
> API Improvements: refactor app_queue to listen for a Transfer stasis message and update the Queue Log appropriately
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-21517
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-21517
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Applications/app_queue, Core/Stasis
>            Reporter: Matt Jordan
>              Labels: Asterisk12
>
> Currently {{app_queue}} has a masquerade callback that it uses to try and update the queue log. Masquerades are (for the most part) going the way of the DoDo (poor bird with a funny name)
> However, {{app_queue}} still does have to know that a transfer occurred. It should do this by subscribing to bridge topics that are it's Queue bridges. When a message comes across for that bridge that says a channel transferred out of it, it should update the queue log.

--
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



More information about the asterisk-bugs mailing list