[asterisk-bugs] [Asterisk 0011330]: [patch] CHANNELS dialplan function, get channel list in the dialplan

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11330 
====================================================================== 
Reported By:                rain
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11330
Category:                   Functions/NewFeature
Reproducibility:            always
Severity:                   feature
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.14  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             11-20-2007 15:54 CST
Last Modified:              11-21-2007 12:11 CST
====================================================================== 
Summary:                    [patch] CHANNELS dialplan function, get channel list
in the dialplan
Description: 
There is currently no clean way to get a list of active channels from
within the dialplan -- the cleanest method that's currently possible is an
AGI script, which requires the extra overhead of spawning a new process. 
Since I need to fetch the channel list for each call attempt to an agent
(from app_queue), the wasted CPU time would be substantial.
====================================================================== 

---------------------------------------------------------------------- 
 rain - 11-21-07 12:11  
---------------------------------------------------------------------- 
I created a separate function so that no argument parsing was necessary (to
avoid regexp quoting issues), and because everything CHANNEL() currently
does is oriented around the current channel.

It'd certainly be possible to merge it into CHANNEL(), but that'd require
argument parsing for CHANNEL() (which isn't done now) and probably
non-standard argument parsing (e.g. what REGEX() currently does.) 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
11-21-07 12:11  rain           Note Added: 0074146                          
======================================================================