Datasets:
Squidnutz
/
extractedtest

Dataset card Data Studio Files
xet
Community
1
text
stringlengths
0
152
Chapter 2: Asterisk Architecture
Name
res_phoneprov
res_pktccops
res_security_log
res_snmp
res_speech
res_stasis
Purpose
Provisions phones from Asterisk HTTP server
Provides PacketCable COPS resources
Enables logging of security events generated by other parts of Asterisk
Provides system status information to an SNMP-managed network
Generic speech recognition APIb
Ties together the various components of the Stasis application infrastructure
Provides XMPP resources (FKA Jabber)
res_xmpp
a While most of the ADSI functionality in Asterisk is never used, the voicemail application uses this resource.
b Requires a separately licensed product in order to be used.
Add-on Modules
Add-on modules are community-developed modules with different usage or distribu‐
tion rights from those of the main code (Table 2-13). They are kept in a separate
directory and are not compiled and installed by default. To enable these modules, use
the menuselect build configuration utility.
Table 2-13. Add-on modules
Name
chan_ooh323
Purpose
Enables making and receiving VoIP calls using the H.323 protocol Usable
Usable
Allows Asterisk to play MP3 files
res_config_mysql Uses a MySQL database as a real-time configuration backend
Useful
format_mp3
Popularity/status
Test Modules
Test modules are used by the Asterisk development team to validate new code. They
are constantly changing and being added to, and are not useful unless you are devel‐
oping Asterisk software.
If you are an Asterisk developer, however, the Asterisk Test Suite may be of interest to
you, as you can build automated tests for Asterisk and submit those back to the
project, which runs on several different operating systems and types of machines. By
expanding the number of tests constantly, the Asterisk project avoids the creation of
regressions in code. By submitting your own tests to the project, you can feel more
confident in future upgrades.
More information about building tests is available in the “Asterisk Test Suite” docu‐
ment, or you can join the #asterisk-testing channel on the Freenode IRC network.
Modules
|
19
File Structure
Asterisk is a complex system, composed of many resources. These resources make use
of the filesystem in several ways. Since Linux is so flexible in this regard, it is helpful
to understand what data is being stored, so that you can understand where you are
likely to find a particular bit of stored data (such as voicemail messages or logfiles).
Configuration Files
The Asterisk configuration files include extensions.conf, pjsip.conf, modules.conf, and
dozens of other files that define parameters for the various channels, resources, mod‐
ules, and functions that may be in use.
These files will normally be found in /etc/asterisk. You will be working in this folder a
lot as you configure and administer your Asterisk system.
Modules
Asterisk modules are usually installed to the /usr/lib/asterisk/modules folder. You will
not normally have to interact with this folder; however, it will be occasionally useful
to know where the modules are located. For example, if you upgrade Asterisk and
select different modules during the menuselect phase of the install, the old (incom‐
patible) modules from the previous Asterisk version will not be deleted, and you will
get a warning from the install script. Those old files will need to be deleted from the
modules folder. This can be done either manually or with the “uninstall” make (make
uninstall) target.
The Resource Library
There are several resources that require external data sources. For example, music on
hold (MOH) can’t happen unless you have some music to play. System prompts also
need to be stored somewhere on the hard drive. The /var/lib/asterisk folder is where
system prompts, AGI scripts, music on hold, and other resource files are stored.