; Sample configuration file for Sorcery Data Access Layer
;
; Wizards
;
; Wizards are the persistence mechanism for objects. They are loaded as Asterisk modules and register
; themselves with the sorcery core. All implementation specific details of how objects are persisted is isolated
; within wizards.
;
;
; Caching
;
; A wizard can optionally be marked as an object cache by adding "/cache" to the object type within the mapping.
; If an object is returned from a non-object cache it is immediately given to the cache to be created. Multiple
; object caches can be configured for a single object type.
;
;
; Object Type Mappings
;
; To allow configuration of where and how an object is persisted object mappings can be defined within this file
; on a per-module basis. The mapping consists of the object type, options, wizard name, and wizard configuration
; data. This has the following format:
;
; object type [/options] = wizard name, wizard configuration data
;
; For example to configure an in-memory wizard for the 'bob' object type:
;
; bob = memory
;
; Or to configure the object type 'joe' from a configuration file:
;
; joe = config,joe.conf
;
; Note that an object type can have multiple mappings defined. Each mapping will be consulted in the order in which
; it appears within the configuration file. This means that if you are configuring a wizard as a cache it should
; appear as the first mapping so the cache is consulted before all other mappings.
;
;
; The following object mappings are used by the unit test to test certain functionality of sorcery.
;
[test_sorcery_section]
test=memory
[test_sorcery_cache]
test/cache=test
test=memory
;
; The following object mapping is the default mapping of external MWI mailbox
; objects to give persistence to the message counts.
;
;[res_mwi_external]
;mailboxes=astdb,mwi_external
;
; The following object mappings set PJSIP objects to use realtime database mappings from extconfig
; with the table names used when automatically generating configuration from the alembic script.
;
;[res_pjsip]
;endpoint=realtime,ps_endpoints
;auth=realtime,ps_auths
;aor=realtime,ps_aors
;domain_alias=realtime,ps_domain_aliases
;identify=realtime,ps_endpoint_id_ips
complete console output from startup log file /var/log/asterisk/full:
[2016-06-16 13:35:58] VERBOSE[100557] asterisk.c: Asterisk cleanly ending (0).
[2016-06-16 13:35:58] VERBOSE[100557] asterisk.c: Executing last minute cleanups
[2016-06-16 13:35:58] Asterisk 13.9.1 built by root @ pbx.loc.lan on a i386 running FreeBSD on 2016-05-31 12:16:04 UTC
[2016-06-16 13:35:59] NOTICE[100083] cdr.c: CDR simple logging enabled.
[2016-06-16 13:35:59] NOTICE[100083] loader.c: 86 modules will be loaded.
[2016-06-16 13:36:00] WARNING[100083] res_phoneprov.c: Unable to find a valid server address or name.
[2016-06-16 13:36:00] NOTICE[100083] confbridge/conf_config_parser.c: Adding default_menu menu to app_confbridge
[2016-06-16 13:36:00] VERBOSE[100083] asterisk.c: Asterisk Ready.
I was not able to reproduce that specific issue on Linux using the configuration provided against Asterisk 13.9.1. It’s possible that something in FreeBSD is compiling it differently causing issues…