Page 499 - Asterisk™: The Future of Telephony

extconfig.conf

Asterisk can write configuration data to and load configuration data from a database
using the external configuration engine (also known as realtime). This enables you to
map external configuration files (static mappings) to a database, allowing the infor-
mation to be retrieved from the database. It also allows you to map special runtime
entries that permit the dynamic creation and loading of objects, entities, peers, and so
on without a reload. These mappings are assigned and configured in the
extconfig.conf file, which is used by both res_odbc and realtime.

extensions.conf

At the center of every good universe is a dialplan. The extensions.conf file is the means
by which you tell Asterisk how you want calls to be handled. The dialplan contains a
list of instructions that, unlike traditional telephony systems, is entirely customizable.
The dialplan is so important that rather than defining it in this appendix, we have
dedicated all of Chapters 5 and 6, as well as Appendix B, to this topic. Go forth, read,
and enjoy!

extensions.ael

This file is the equivalent of extensions.conf, only it’s for dialplans written in the AEL
language. When Asterisk loads the dialplan, it reads the AEL dialplan from exten
sions.ael and merges it with the dialplan from extensions.conf.

features.conf

features.conf, the file formally known as parking.conf, contains configuration informa-
tion related to call parking and call transfers. Call parking configuration options
include:
• The extension to dial to park calls (parkext =>)
• The extension range to park calls in (parkpos =>)
• Which context to park calls in (context =>)
• How long a call can remain parked for before ringing the extension that parked it
(parkingtime =>)
• The sound file played to the parked caller when the call is removed from parking
(courtesytone =>)
• ADSI parking announcements (asdipark=yes|no)

extconfig.conf | 471