| Summary: | ASTERISK-21943: Bridge API Enhancements - handle AgentLogin/AgentLogout in the Queue Log using Stasis | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | Asterisk12 |
| Date Opened: | 2013-06-21 11:45:24 | Date Closed: | 2013-08-22 13:56:01 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_queue Core/Bridging |
| Versions: | 12 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | With the rework of {{chan_agent}} (and by re-work, I mean it's dead Jim), the new Agent bridge and application will need a way of informing the Queue Log that an agent has logged in/logged out.
Directly accessing the queue log through a publicly exported function is to be avoided. Instead, Stasis should convey the fact that an Agent has logged in. {{app_queue}} should subscribe for notifications that an Agent has logged in and update the Queue Log appropriately. For this to happen, the following has to occur: * Agent message types needs to be moved to {{stasis_channels}} or a similar public location * The agent bridge and/or application should publish a message when an agent logs in or logs out. * {{app_queue}} should subscribe to that message type on module load. The message handler should update the queue log. | ||
| Comments: | |||