;
; Static and realtime external configuration
; engine configuration
;
; See https://wiki.asterisk.org/wiki/display/AST/Realtime+Database+Configuration
; for basic table formatting information.
;
[settings]
;
; Static configuration files:
;
; file.conf => driver,database[,table[,priority]]
;
; 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
;extensions.conf => sqlite,asterisk,ast_config
;
; 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,1
;example => mysql,asterisk,alttable,2
;example2 => ldap,"dc=oxymium,dc=net",example2
;
; Additionally, priorities are now supported for use as failover methods
; for retrieving realtime data.  If one connection fails to retrieve any
; information, the next sequential priority will be tried next.  This
; especially works well with ODBC connections, since res_odbc now caches
; when connection failures occur and prevents immediately retrying those
; connections until after a specified timeout.  Note:  priorities must
; start at 1 and be sequential (i.e. if you have only priorities 1, 2,
; and 4, then 4 will be ignored, because there is no 3).
;
; "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
;    curl ... res_config_curl
;    ldap ... res_config_ldap
;
iaxusers => odbc,asterisk1,iaxfriends,1
iaxpeers => odbc,asterisk1,iaxfriends,1
iaxusers => odbc,asterisk2,iaxfriends,2
iaxpeers => odbc,asterisk2,iaxfriends,2
sipusers => odbc,asterisk1,sipfriends,1
sippeers => odbc,asterisk1,sipfriends,1
sipusers => odbc,asterisk2,sipfriends,2
sippeers => odbc,asterisk2,sipfriends,2
;sipusers => mysql,asterisk,sipfriends
;sippeers => mysql,asterisk,sipfriends
sipregs => odbc,asterisk1,sipregs_srv02,1
sipregs => odbc,asterisk2,sipregs_srv02,2
voicemail => odbc,asterisk1,voicemail,1
voicemail => odbc,asterisk2,voicemail,2
;extensions => odbc,asterisk1,extensions,1
;extensions => odbc,asterisk2,extensions,2
;hints => odbc,asterisk1,hints,1
;hints => odbc,asterisk2,hints,2
meetme => odbc,asterisk1,meetme,1
meetme => odbc,asterisk2,meetme,2
queues => odbc,asterisk1,queue,1
queues => odbc,asterisk2,queue,2
queue_members => odbc,asterisk1,queue_member,1
queue_members => odbc,asterisk2,queue_member,2
musiconhold => odbc,asterisk1,musiconhold,1
musiconhold => odbc,asterisk2,musiconhold,2
queue_log => odbc,asterisk1,queue_log,1
queue_log => odbc,asterisk2,queue_log,2
followme => odbc,asterisk1,followme,1
followme => odbc,asterisk2,followme,2
followme_numbers => odbc,asterisk1,followme_numbers,1
followme_numbers => odbc,asterisk2,followme_numbers,2

ps_endpoints => odbc,asterisk1,ps_endpoints,1
ps_endpoints => odbc,asterisk2,ps_endpoints,2
ps_auths => odbc,asterisk1,ps_auths,1
ps_auths => odbc,asterisk2,ps_auths,2
ps_aors => odbc,asterisk1,ps_aors,1
ps_aors => odbc,asterisk2,ps_aors,2
ps_domain_aliases => odbc,asterisk1,ps_domain_aliases,1
ps_domain_aliases => odbc,asterisk2,ps_domain_aliases,2
ps_endpoint_id_ips => odbc,asterisk1,ps_endpoint_id_ips,1
ps_endpoint_id_ips => odbc,asterisk2,ps_endpoint_id_ips,2
ps_contacts => odbc,asterisk1,ps_contacts_srv02,1
ps_contacts => odbc,asterisk2,ps_contacts_srv02,2
ps_asterisk_publications => odbc,asterisk1,ps_asterisk_publications,1
ps_asterisk_publications => odbc,asterisk2,ps_asterisk_publications,2
ps_outbound_publishes => odbc,asterisk1,ps_outbound_publishes,1
ps_outbound_publishes => odbc,asterisk2,ps_outbound_publishes,2
ps_inbound_publishes => odbc,asterisk1,ps_inbound_publishes,1
ps_inbound_publishes => odbc,asterisk2,ps_inbound_publishes,2



;sla => odbc,asterisk1,testsla,1

;sip.conf => odbc,asterisk1,ast_config

;
;
; 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.

