[asterisk-bugs] [Asterisk 0018039]: Small extconfig/CLI change
Asterisk Bug Tracker
noreply at bugs.digium.com
Mon Oct 4 10:59:55 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18039
======================================================================
Reported By: Raffles
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18039
Category: General
Reproducibility: always
Severity: text
Priority: normal
Status: feedback
Asterisk Version: 1.6.2.13
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-09-23 10:50 CDT
Last Modified: 2010-10-04 10:59 CDT
======================================================================
Summary: Small extconfig/CLI change
Description:
Since the extconfig.conf has now changed - the CLI command 'core show
config mappings' needs to follow suit.
*CLI> core show config mappings
Config Engine: mysql
===> meetme (db=general, table=meetme)
===> queue_members (db=general, table=queue_members)
===> queues (db=general, table=queues)
===> voicemail (db=general, table=voicemail)
===> sippeers (db=general, table=sipusers)
===> sipusers (db=general, table=sipusers)
===> extensions (db=general, table=extensions)
Should now read ...(context=general, table=...
This is for the most pedantic of us :)
======================================================================
----------------------------------------------------------------------
(0127651) tilghman (administrator) - 2010-10-04 10:59
https://issues.asterisk.org/view.php?id=18039#c127651
----------------------------------------------------------------------
What we did was correct a problem with the mysql backend interface, not a
problem with extconfig. All of the other backends refer to the entry name,
which may or may not be the same as the database name, but it's the db
entry in that backend. Changing this is really not something we want to
do.
Issue History
Date Modified Username Field Change
======================================================================
2010-10-04 10:59 tilghman Note Added: 0127651
======================================================================
More information about the asterisk-bugs
mailing list