[asterisk-bugs] [Asterisk-GUI 0015166]: Features.conf edits to [featuremap] context

[Asterisk Bug Tracker]

The following issue has been CLOSED 
====================================================================== 
https://issues.asterisk.org/view.php?id=15166 
====================================================================== 
Reported By:                meseptiamus
Assigned To:                awk
====================================================================== 
Project:                    Asterisk-GUI
Issue ID:                   15166
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Asterisk GUI Version:       SVN 
Asterisk Version:           1.4.23 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 4786 
Disclaimer on File?:        N/A 
Request Review:              
Resolution:                 won't fix
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-05-20 08:39 CDT
Last Modified:              2009-06-29 19:56 CDT
====================================================================== 
Summary:                    Features.conf edits to [featuremap] context
Description: 
OS: openSuse 11.0
Asterisk 1.4.23.1
Asterisk GUI 2.0 (r4786)
Menu item: Call Features then Feature Map

Summary:  On a fresh features.conf under [featuremap] there are no
entries.  If custom values are used for Blind Transfer and/or Disconnect
then blindxfer = <value> and disconnect = <value> are placed under
[featuremap].  If you then use the GUI to delete the custom values for
these two items it leaves blindxfer = and disconnect = under [featuremap]
with no values following the entries.

This is where the problem arises, after removing the custom values and
restarting the system the default "#" for transfers no longer works until
you manually edit features.conf and remove "blindxfer =" and "disconnect ="
from [featuremap].  Once these two entries are deleted and Asterisk is
restarted the default values of "#" and "*" will work again.

I am unsure if this is a feature (no pun intended) or a bug.  If you do
not want "#" to allow transfers then you need a mechinism to do so, leaving
"blindxfer =" would allow for this.  On the other hand if I do change it
and want the default values back I must manually edit features.conf to do
so as the GUI does not allow for this.

Based on the paragraph above I was unsure if this was an Asterisk or
Asterisk GUI problem.  If this is how Asterisk is intended to work
("blindxfer =" deactivating blind transfers) then this is an Asterisk GUI
issue.  If not then it may be an Asterisk issue.  I will leave that to you
to sort out.

 


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

---------------------------------------------------------------------- 
 (0107212) awk (manager) - 2009-06-29 19:56
 https://issues.asterisk.org/view.php?id=15166#c107212 
---------------------------------------------------------------------- 
meseptiamus,
This would be a feature request. If you want to restore the defaults, you
can change it back in the features page. I can see how it'd be a little
confusing seeing it empty and the "default is #" tip. That would imply that
if its empty then it'd be the default. The intention of the default tip was
to let the user know if they wanted to restore the default they'd know what
to enter. However, we need a way to disable the feature all together so we
made it consistent with the other fields (which is by setting the field to
empty).  

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-06-29 19:56 awk            Note Added: 0107212                          
2009-06-29 19:56 awk            Status                   assigned => closed  
2009-06-29 19:56 awk            Resolution               open => won't fix   
2009-06-29 19:56 awk            Description Updated                          
======================================================================