Summary:ASTERISK-16720: Small extconfig/CLI change
Reporter:Andrew Thomas (raffles)Labels:
Date Opened:2010-09-23 10:50:31Date Closed:2011-06-07 14:10:11
Versions:Frequency of
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 :)
Comments:By: Leif Madsen (lmadsen) 2010-09-23 10:56:50

I don't understand what has changed here and why it should be 'context' instead of 'db'.

What does your extconfig.conf file look like?

My example is showing:

; file.conf => driver,database[,table[,priority]]

By: Andrew Thomas (raffles) 2010-09-23 11:03:31

extensions => mysql,general,extensions
sipusers => mysql,general,sipusers
sippeers => mysql,general,sipusers
voicemail => mysql,general,voicemail
queues => mysql,general,queues
queue_members => mysql,general,queue_members
meetme => mysql,general,meetme

meaning :

realtime section of * => driver,context (as in res_mysql.conf),table

[general] <--- this is the middle parameter in extconfig.conf now.
dbhost =
dbname = database
dbuser = user
dbpass = password
dbsock = /var/run/mysqld/mysqld.sock
port = 3306
requirements = warn

I think this was changed in 1.6 to allow multiple servers/databases to be used.

EDIT : Just noticed, this only concerns realtime entries - not static ones.  I'm not sure how you're going to handle this one on the CLI now ;)

By: Leif Madsen (lmadsen) 2010-10-04 10:53:48

I still see nothing wrong here. You've defined 'general' for the middle value (which is the database defined in res_mysql.conf), and that is what is showing up on the CLI.

You're going to have to elaborate on what is actually wrong here because I don't see it.

By: Leif Madsen (lmadsen) 2010-10-04 10:54:57

Oh ya, I see what you're seeing now. I'll change it I guess.

By: Tilghman Lesher (tilghman) 2010-10-04 10:59:55

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.

By: Leif Madsen (lmadsen) 2010-10-04 11:00:58

Actually after looking at the files again, and talking to Tilghman, it was agreed that this was actually a change to correct a problem with the way the mysql backend worked, and not a problem with extconfig. If I change this to 'context' it's really going to be more confusing to people who aren't using MySQL backend directly as none of the configuration files reference it.