;
; Static and realtime external configuration
; engine configuration
;
; Please read doc/extconfig.txt for basic table
; formatting information.
;
[settings]
;
; Static configuration files: 
;
; 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,hosted-database
;extensions.conf => sqlite,asterisk,hosted-database
;sip.conf => odbc,hosted-database,sip_confs_1
extensions.conf => odbc,hosted-database,exten_confs_5
;voicemail.conf => odbc,hosted-database,voicemail_confs_1
;queues.conf => odbc,hosted-database,ast_queue_confs_1
;features.conf => odbc,hosted-database,feature_confs_1
res_parking.conf => odbc,hosted-database,parking_confs_5
;musiconhold.conf => odbc,hosted-database,music_on_hold_confs_1
;meetme.conf => odbc,hosted-database,conference_room_confs
;
; 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
;
;
; 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
;
;example => odbc,asterisk,alttable
;example2 => ldap,"dc=oxymium,dc=net",example2
;
; "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
;
;iaxusers => odbc,asterisk
;iaxpeers => odbc,asterisk
;sipusers => odbc,hosted-database,sipfriends
;sippeers => odbc,hosted-database,sipfriends
;sipregs => odbc,asterisk
voicemail => odbc,hosted-database,voicemail_realtime_confs_5
;extensions => odbc,asterisk
;meetme => odbc,general
queues => odbc,hosted-database,ast_queue_realtime_confs_5
queue_members => odbc,hosted-database,ast_queue_member_realtime_confs_5
musiconhold => odbc,hosted-database,music_on_hold_realtime_confs_5
;acls => odbc,hosted-database,acltable
;queue_log => odbc,general
;
;
; 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.
ps_endpoints => odbc,hosted-database,ps_endpoints_5
ps_auths => odbc,hosted-database,ps_auths_5
ps_aors => odbc,hosted-database,ps_aors_5
;ps_resource_lists =>  odbc,hosted-database,ps_resource_lists_5
;ps_contacts => odbc,pjsip-contacts,ps_contacts
;ps_domain_aliases => odbc,hosted-database,ps_domain_aliases
;ps_endpoint_id_ips => odbc,hosted-database,ps_endpoint_id_ips
;ps_contacts => odbc,hosted-database,ps_contacts
ps_globals => odbc,hosted-database,ps_globals
;ps_acls => odbc,hosted-database,ps_acls
