Connections are what make Asterisk useful. If there are no connections to Asterisk, you wouldn’t be able to
connect a phone or use a link to the outside, which really limits the things you can do with it. Asterisk, when
first installed, actually has a connection to a demonstration server hosted by Digium.This connection shows
how calls can be transferred via VoIP to a completely different server as easily as dialing a number, and
gives you a taste of what can be accomplished.This connection, however, is a nice demonstration, but
doesn’t really have any use besides showing off what can be done with Asterisk. If you want to actually
accomplish tasks, you will need to set up your own connections with the outside world.
Connections, Connections, Connections!
Numerous files control the various protocols for Asterisk. Some protocols are commonly used in today’s VoIP setups, while some are quite vestigial and are likely not to be used unless you have specialty hardware. Let’s take a look at the various protocols supported by Asterisk (see Table 3.5).
Each protocol is controlled by a different file. Multiple connections can be set up in a single file, or the files
can be broken down and linked via include statements. What you opt to do is a choice of personal
preference. Each file has certain specific configuration options that are used only for the protocol the file
governs, and they also have options that are common across all files. Let’s go over some of the conventions:
Configuration File Conventions
All Asterisk configuration files have certain conventions that run throughout them. We went through some of them when we were talking about extensions.conf. However, some differences exist in the terminology and layout when comparing extensions.conf to another file.
Much like how extensions.conf is broken down into contexts, most configuration files are broken down into sections. Context and sections have the same syntax— namely, that the headers are surrounded by brackets, as shown in the following example.
Each configuration file often has a [general] section as well, which functions more or less the same way as
the [general] section in extensions.conf: settings in that section are applied to each section unless they are
overridden within the specific section.
connect a phone or use a link to the outside, which really limits the things you can do with it. Asterisk, when
first installed, actually has a connection to a demonstration server hosted by Digium.This connection shows
how calls can be transferred via VoIP to a completely different server as easily as dialing a number, and
gives you a taste of what can be accomplished.This connection, however, is a nice demonstration, but
doesn’t really have any use besides showing off what can be done with Asterisk. If you want to actually
accomplish tasks, you will need to set up your own connections with the outside world.
Connections, Connections, Connections!
Numerous files control the various protocols for Asterisk. Some protocols are commonly used in today’s VoIP setups, while some are quite vestigial and are likely not to be used unless you have specialty hardware. Let’s take a look at the various protocols supported by Asterisk (see Table 3.5).
can be broken down and linked via include statements. What you opt to do is a choice of personal
preference. Each file has certain specific configuration options that are used only for the protocol the file
governs, and they also have options that are common across all files. Let’s go over some of the conventions:
Configuration File Conventions
All Asterisk configuration files have certain conventions that run throughout them. We went through some of them when we were talking about extensions.conf. However, some differences exist in the terminology and layout when comparing extensions.conf to another file.
Much like how extensions.conf is broken down into contexts, most configuration files are broken down into sections. Context and sections have the same syntax— namely, that the headers are surrounded by brackets, as shown in the following example.
Each configuration file often has a [general] section as well, which functions more or less the same way as
the [general] section in extensions.conf: settings in that section are applied to each section unless they are
overridden within the specific section.
No comments:
Post a Comment