System information

The [files] Section
This section of asterisk.conf includes options related to the Asterisk control socket. It
is primarily used by remote consoles (asterisk -r). The available options are listed in
Table 4-3.
Table 4-3. asterisk.conf [files] section
Option Value/Example Notes
astctlpermissions 0660 Sets the permissions for the Asterisk control socket.
astctlowner root Sets the owner for the Asterisk control socket.
astctlgroup apache Sets the group for the Asterisk control socket.
astctl asterisk.ctl Sets the filename for the Asterisk control socket. The default is asterisk.ctl.
The [compat] Section
Occasionally the Asterisk development team decides that the best way forward involves
making a change that is not backward-compatible. This section contains some options
(listed in Table 4-4) that allow reverting behavior of certain modules back to previous
behavior.
Table 4-4. asterisk.conf [compat] section
Option Value/Example Notes
pbx_realtime 1.6 In versions earlier than Asterisk 1.6.x, the pbx_realtime module would automatically
convert pipe characters into commas for arguments to Asterisk applications. This is no
longer done by default. To enable this previous behavior, set this option to 1.4.
res_agi 1.6 In versions earlier than Asterisk 1.6.x, the EXEC AGI command would automatically convert
pipe characters into commas for arguments to Asterisk applications. This is no longer done
by default. To enable this previous behavior, set this option to 1.4.
app_set 1.6 Starting with the Asterisk 1.6.x releases, the Set() application only allows setting the
value of a single variable. Previously, Set() would allow setting more than one variable
by separating them with a &. This was done to allow any characters in the value of a
variable, including the & character, which was previously used as a separator. MSet() is
a new application that behaves like Set() used to. However, setting this option to
1.4 makes Set() behave like MSet().
modules.conf
This file is not strictly required in an Asterisk installation; however, without any mod-
ules Asterisk won’t really be able to do anything, so for all practical purposes, you need
a modules.conf file in your /etc/asterisk folder. If you simply define autoload=yes in your
modules.conf file, Asterisk will search for all modules in the /usr/lib/asterisk/modules
folder and load them at startup.
modules.conf | 75