|Summary:||ASTERISK-15439: [patch] Group Variables|
|Reporter:||Mark Murawski (kobaz)||Labels:||patch|
|Date Opened:||2010-01-15 10:04:53.000-0600||Date Closed:|
|Environment:||Attachments:||( 0) groupvars.diff|
|Description:||This patch allows for setting variables on a group of channels.|
First a channel is assigned a group via dialplan GROUP() or GroupSet via the ami (new command)
Then, variables can be set on that group with the GROUP_VAR() dialplan function, or GroupVarSet in the manager
This patch also adds manager events for channel group changes, and variable updates
When a group is no longer used (all channels referencing the group are hung up, or all channels referencing the group have their group changed/unset), variables are destroyed
new manager commands:
GroupSet - adds functionality to the manager to be able to set a GROUP() on a channel.
GroupsShowChannels - show each channel and it's associated groups (a channel will be repeated for each group@category it's a member of)
GroupsShowVariables - show variables in each group@category, one event per group, all variables are contained in each group@category event
GroupVarSet - set a group variable (the group has to exist)
GroupVarGet - get a group variable
new manager events:
|Comments:||By: Leif Madsen (lmadsen) 2010-01-15 13:14:42.000-0600|
I also think it might be useful to add some documentation here about one or two examples of how this could be used (or how you're using it) and why you might want to use it, in additional to how you can't or shouldn't use it.
I'd really like to start having a section that contains examples and usage of new features (and update existing features) for dialplan applications and functions.
By: John Todd (jtodd) 2010-01-15 14:19:00.000-0600
Great patch! Thanks.
By: Russell Bryant (russell) 2010-01-28 11:37:20.000-0600
Thank you very much for the patch! I'm going to temporarily suspend the review request until we have someone assigned to this issue to take care of it. At that point, we can open it back up.
By: Mark Murawski (kobaz) 2010-01-28 11:43:59.000-0600
No problem. I'll have the code cleanups ready by the end of the week.
By: Mark Murawski (kobaz) 2010-02-09 09:51:48.000-0600
So much for the end of the week. I'm still alive. I'll get back to work on this.
By: Leif Madsen (lmadsen) 2010-02-22 15:34:43.000-0600
Set to Feedback until patches are updated. Thanks!
By: Mark Murawski (kobaz) 2010-02-22 15:37:36.000-0600
Yeah... I've been crazy busy... I'll be working on it again soon
By: Leif Madsen (lmadsen) 2010-02-24 09:23:36.000-0600
Oh no problem, was just marking the bug into an appropriate state. Thanks for all the work I've seen from you lately!
By: Mark Murawski (kobaz) 2010-06-06 15:51:20
I'm still alive... I'll be back to work on this shortly
By: Paul Belanger (pabelanger) 2010-06-25 09:00:36
Suspending for now, we can re-open once your patch is complete.
Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.
Further information can be found at http://www.asterisk.org/developers/bug-guidelines
By: Mark Murawski (kobaz) 2012-03-15 15:54:40.501-0500
Readying for trunk commit.
By: Mark Murawski (kobaz) 2017-12-20 07:17:43.232-0600
I know it's been a loooong time in the making. My 2018 goal is to get my open ended items on here completed. Group variables is something I'm particularly fond of and have been using in my own production environment for years with great success. I'm looking forward to getting this into mainline.
By: Joshua C. Colp (jcolp) 2017-12-20 07:21:14.936-0600
[~kobaz] Once you're actively working feel free to assign back to yourself. I'm just doing JIRA cleanup to try to make things better reflect reality.
By: Mark Murawski (kobaz) 2017-12-20 07:24:05.316-0600
Sounds good. Cleanups are always nice.