Page 100 - Asterisk™: The Future of Telephony

[globals]
[general]
autofallthrough=yes

[default]
[incoming_calls]

[internal]
[phones]
include => internal

In the [general] section, we have set autofallthrough=yes, which tells
Asterisk to continue when an extension runs out of things to do. If you
set this to no, then Asterisk will sit and wait for input after all priorities
have executed. This is most prevalent if the Background() application is
the last application executed in an extension. If set to yes (which is now
the default in 1.4), Asterisk will drop the call after Background() finishes
executing (at the end of the prompt(s) supplied to it). In order to force
Asterisk to wait for input after the Background() application finishes
playing the voice prompts supplied to it, we use the WaitExten()
application.
Do not be afraid if what we’ve just written doesn’t make a whole lot of
sense, as we haven’t explored the dialplan, applications, priorities, or
extensions yet (that is coming up in the next chapter). So for now, just
set autofallthrough=yes. It is safest to use the autofallthrough=yes
command as we don’t want Asterisk hanging around waiting for input
unless we explicitly tell it to do so.

There is nothing else for now, but we’ll be using this file as we go through this chapter
to build a test dialplan so we can ensure that all of our devices are working. Also, be
sure to run the dialplan reload command from the Asterisk CLI to update to the latest
changes. Verify your changes by running the CLI command dialplan show:
*CLI> dialplan show
[ Context 'phones' created by 'pbx_config' ]
Include => 'internal' [pbx_config]

[ Context 'internal' created by 'pbx_config' ]
[ Context 'incoming_calls' created by 'pbx_config' ]

[ Context 'default' created by 'pbx_config' ]
[ Context 'parkedcalls' created by 'res_features' ]
'700' => 1. Park((null)) [res_features]

-= 1 extension (1 priority) in 5 contexts. =-

72 | Chapter 4: Initial Configuration of Asterisk