[asterisk-bugs] [Asterisk-GUI 0015166]: Features.conf edits to [featuremap] context
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed May 20 08:39:35 CDT 2009
The following issue has been SUBMITTED.
======================================================================
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: assigned
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:
======================================================================
Date Submitted: 2009-05-20 08:39 CDT
Last Modified: 2009-05-20 08:39 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.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2009-05-20 08:39 meseptiamus New Issue
2009-05-20 08:39 meseptiamus Status new => assigned
2009-05-20 08:39 meseptiamus Assigned To => awk
2009-05-20 08:39 meseptiamus Asterisk GUI Version => SVN
2009-05-20 08:39 meseptiamus Asterisk Version => 1.4.23
2009-05-20 08:39 meseptiamus SVN Branch (only for SVN checkouts, not tarball
releases) => 1.4
2009-05-20 08:39 meseptiamus SVN Revision (number only!) => 4786
======================================================================
More information about the asterisk-bugs
mailing list