[asterisk-bugs] [Asterisk 0012556]: [patch] Realtime queue callers

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12556 
====================================================================== 
Reported By:                atis
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12556
Category:                   Applications/NewFeature
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 114874 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             04-30-2008 06:23 CDT
Last Modified:              05-01-2008 04:38 CDT
====================================================================== 
Summary:                    [patch] Realtime queue callers
Description: 
This patch adds new realtime family for queue callers. app_queue will do a
realtime store for new caller, and destroy for one left. 

This allows better monitoring of queue callers from multiple clients at
same time, as there is no need for caching of AMI commands, all is kept in
Realtime, and multiple clients are handled by database engine.


====================================================================== 

---------------------------------------------------------------------- 
 vieri - 05-01-08 04:38  
---------------------------------------------------------------------- 
I am currently using a custom AMI script which runs a "show queues" each
time it detects an Agent* event and parses the output (active calls, wait
time, etc). I don't have too many queues or too many calls so I guess the
AMI script won't overload asterisk but still, a database backend would
handle this more efficiently.

Also, parsing "show queues" isn't that simple because if I wanted to get
the caller IDs of all the active callers I guess I would need to grab the
caller channels and then run yet another command such as "zap show channel
XX" for each channel and parse the output for the caller ID.

A native AMI command that queries channels in a queue or all queues and
yields easily parseable information would be nice. However, having
app_queue store this data directly into a database (thus reducing potential
deadlocks by excessive AMI queries) sounds very appealing.

Couldn't we just have both? 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-01-08 04:38  vieri          Note Added: 0086246                          
======================================================================