; Module loading for the lab.
;
; The image ships `autoload=yes`, which loads every module Asterisk was built
; with. On a headless container that produces a lot of startup noise for
; hardware and backends that do not exist here — measured at ~74 ALSA lines
; plus a dozen module-load ERRORs per restart, all of it in Loki. None of it
; was harmful; all of it made the log harder to read.
;
; autoload stays on: this is a lab, and an explicit allow-list would break
; quietly every time a scenario needs a module nobody remembered to add. The
; noload lines below are only for modules that *cannot* work in this container.
[modules]
autoload=yes

; --- Audio hardware -------------------------------------------------------
; No sound card in a container. chan_alsa/chan_oss probe for one and emit
; ~74 lines of ALSA config errors on every start. The media path is RTP via
; PJSIP, never a local device.
noload => chan_alsa.so
noload => chan_oss.so
noload => chan_console.so

; --- CDR/CEL backends for databases we do not run -------------------------
; Each logs "declined to load" or a config error at startup. Call records live
; in Hold Slayer's own Postgres, written by the gateway, not by Asterisk.
noload => cdr_pgsql.so
noload => cdr_sqlite3_custom.so
noload => cdr_custom.so
noload => cdr_csv.so
noload => cel_pgsql.so
noload => cel_sqlite3_custom.so
noload => cel_custom.so

; --- Realtime config backends we do not use -------------------------------
; The lab's configuration is the mounted .conf files. LDAP/ODBC/PgSQL realtime
; each complain about missing connection details on every start.
noload => res_config_ldap.so
noload => res_config_odbc.so
noload => res_config_pgsql.so
noload => res_config_sqlite3.so

; --- Codecs and formats that fail to initialise ----------------------------
; format_ogg_vorbis errors on load. The lab plays .sln (signed linear) and
; negotiates ulaw/alaw, so nothing here needs Vorbis.
noload => format_ogg_vorbis.so
noload => format_ogg_speex.so