2004-10-05 06:46:11 +00:00
|
|
|
;
|
|
|
|
; Static and realtime external configuration
|
|
|
|
; engine configuration
|
|
|
|
;
|
2006-07-12 20:56:49 +00:00
|
|
|
; Please read doc/extconfig.txt for basic table
|
2004-10-08 05:36:23 +00:00
|
|
|
; formatting information.
|
|
|
|
;
|
2004-06-11 00:12:35 +00:00
|
|
|
[settings]
|
2004-10-05 06:46:11 +00:00
|
|
|
;
|
2009-05-28 14:39:21 +00:00
|
|
|
; Static configuration files:
|
2004-10-05 06:46:11 +00:00
|
|
|
;
|
|
|
|
; file.conf => driver,database[,table]
|
|
|
|
;
|
|
|
|
; maps a particular configuration file to the given
|
|
|
|
; database driver, database and table (or uses the
|
|
|
|
; name of the file as the table if not specified)
|
|
|
|
;
|
|
|
|
;uncomment to load queues.conf via the odbc engine.
|
|
|
|
;
|
|
|
|
;queues.conf => odbc,asterisk,ast_config
|
2007-03-13 21:22:33 +00:00
|
|
|
;extensions.conf => sqlite,asterisk,ast_config
|
2005-07-05 22:11:43 +00:00
|
|
|
;
|
|
|
|
; The following files CANNOT be loaded from Realtime storage:
|
|
|
|
; asterisk.conf
|
|
|
|
; extconfig.conf (this file)
|
|
|
|
; logger.conf
|
|
|
|
;
|
|
|
|
; Additionally, the following files cannot be loaded from
|
|
|
|
; Realtime storage unless the storage driver is loaded
|
|
|
|
; early using 'preload' statements in modules.conf:
|
|
|
|
; manager.conf
|
|
|
|
; cdr.conf
|
|
|
|
; rtp.conf
|
|
|
|
;
|
2004-10-05 06:46:11 +00:00
|
|
|
;
|
|
|
|
; Realtime configuration engine
|
|
|
|
;
|
|
|
|
; maps a particular family of realtime
|
|
|
|
; configuration to a given database driver,
|
|
|
|
; database and table (or uses the name of
|
|
|
|
; the family if the table is not specified
|
|
|
|
;
|
2005-01-11 17:05:50 +00:00
|
|
|
;example => odbc,asterisk,alttable
|
2005-12-27 06:42:29 +00:00
|
|
|
;example2 => ldap,"dc=oxymium,dc=net",example2
|
|
|
|
;
|
2007-03-13 21:22:33 +00:00
|
|
|
; "odbc" is shown in the examples below, but is not the only valid realtime
|
|
|
|
; engine. There is:
|
|
|
|
; odbc ... res_config_odbc
|
|
|
|
; sqlite ... res_config_sqlite
|
|
|
|
; pgsql ... res_config_pgsql
|
|
|
|
;
|
2005-02-10 21:14:11 +00:00
|
|
|
;iaxusers => odbc,asterisk
|
|
|
|
;iaxpeers => odbc,asterisk
|
|
|
|
;sipusers => odbc,asterisk
|
|
|
|
;sippeers => odbc,asterisk
|
2007-02-15 12:10:55 +00:00
|
|
|
;sipregs => odbc,asterisk
|
2004-10-08 05:36:23 +00:00
|
|
|
;voicemail => odbc,asterisk
|
2004-11-28 21:28:30 +00:00
|
|
|
;extensions => odbc,asterisk
|
2009-01-15 18:47:14 +00:00
|
|
|
;meetme => mysql,conferences
|
2005-06-02 21:42:49 +00:00
|
|
|
;queues => odbc,asterisk
|
|
|
|
;queue_members => odbc,asterisk
|
Adding support for realtime music on hold. The following are the main points:
1. When moh is started, we search first in memory to find the class. If we do not
find it in memory, we search realtime instead.
2. When moh is restarted (as in, it had been started on this particular channel, stopped,
and now we're starting it again), if using the "files" mode, then realtime will always
be rechecked. If you are using other modes, however, we will simply reattach to the external
running process which was playing moh earlier in the call. This is a necessary compromise so that
we don't end up with too many background processes.
3. musiconhold.conf has a general section now. It has one option: cachertclasses. If set to yes,
then moh classes found in realtime will be added to the in-memory list. This has the advantage
of not requiring database lookups each time moh is started, but it has the disadvantage of not
truly being realtime.
I have tested this for functionality, and it passes. I also tested this under valgrind and there
are no memory problems reported under typical use.
Special thanks to Sergee for implementing this feature and enduring my complaints on the bugtracker!
(closes issue #11196, reported and patched by sergee)
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@89946 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2007-11-28 00:47:22 +00:00
|
|
|
;musiconhold => mysql,asterisk
|
2009-02-17 17:28:21 +00:00
|
|
|
;queue_log => mysql,asterisk
|
2008-12-15 21:17:07 +00:00
|
|
|
;
|
|
|
|
;
|
|
|
|
; While most dynamic realtime engines are automatically used when defined in
|
|
|
|
; this file, 'extensions', distinctively, is not. To activate dynamic realtime
|
|
|
|
; extensions, you must turn them on in each respective context within
|
|
|
|
; extensions.conf with a switch statement. The syntax is:
|
|
|
|
; switch => Realtime/[[db_context@]tablename]/<opts>
|
|
|
|
; The only option available currently is the 'p' option, which disallows
|
|
|
|
; extension pattern queries to the database. If you have no patterns defined
|
|
|
|
; in a particular context, this will save quite a bit of CPU time. However,
|
|
|
|
; note that using dynamic realtime extensions is not recommended anymore as a
|
|
|
|
; best practice; instead, you should consider writing a static dialplan with
|
|
|
|
; proper data abstraction via a tool like func_odbc.
|
2004-06-11 00:12:35 +00:00
|
|
|
|