Summary:	ASTERISK-08072: [Patch] unable to specify "no groups" for groups in config files
Reporter:	gkloepfer (gkloepfer)	Labels:
Date Opened:	2006-11-06 13:12:28.000-0600	Date Closed:	2007-01-15 23:57:37.000-0600
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/Configuration
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:	( 0) group-none-ast12.patch ( 1) group-none-trunk.patch
Description:	In configuration files, there is no clean way to specify no groups (ie. you cannot specify no groups without encountering an error message).  This currently affects chan_zap (zapata.conf) because once a group is specified (callgroup, for example) there is then no way to indicate that any channels following are not in any callgroup.  Specifying an empty group defaults to group 0 (groups are a bitmask and can set bits from 0 to 63). The included patch allows "none" as a valid option in group entry, and affects group, callgroup, and pickupgroup in any configuration file. Note that this issue affects both 1.2, 1.4, and trunk. Patches for 1.2 and trunk are attached. ****** ADDITIONAL INFORMATION ****** It is not entirely clear whether or not this will also affect "realtime" database configuration files if one of the columns is callgroup, pickupgroup, etc.  It is possible (but I have not verified) that a blank entry in that column will force group 0. SVN version for trunk is 47189 See also http://bugs.digium.com/view.php?id=7877 for related work on chan_zap configuration problems.
Comments:	By: Serge Vecher (serge-v) 2006-11-09 13:36:36.000-0600 as this is a new feature, the consideration is for trunk only. By: Joshua C. Colp (jcolp) 2007-01-15 23:57:37.000-0600 Fixed in 1.2 as of revision 51085, 1.4 as of revision 51087, and trunk as of revision 51090. Thanks!