Tipos de modulos en Asterisk.

• Added by malcolmd, last edited by Malcolm Davenport on Sep 23, 2010  (view change)

There are many different types of modules, many of which are shown in the diagram above.

• Channel Drivers

At the top of the diagram, we show channel drivers. Channel drivers communicate with devices outside of Asterisk, and translate that particular signaling or protocol to the core.

• Dialplan Applications

Applications provide call functionality to the system. An application might answer a call, play a sound prompt, hang up a call, and so forth.

• Dialplan Functions

Functions are used to retrieve or set various settings on a call. A function might be used to set the Caller ID on an outbound call, for example.

• Resources

As the name suggests, resources provide resources to Asterisk. Common examples of resources include music on hold and call parking.

• CODECs

A CODEC (which is an acronym for COder/DECoder) is a module for encoding or decoding audio or video. Typically codecs are used to encode media so that it takes less bandwidth.

• File Format Drivers

File format drivers are used to save media to disk in a particular file format, and to convert those files back to media streams on the network.

• Call Detail Record (CDR) Drivers

CDR drivers write call logs to a disk or to a database.

• Call Event Log (CEL) Drivers

Call event logs are similar to call detail records, but record more detail about what happened inside of Asterisk during a particular call.

• Bridge Drivers

Bridge drivers are used by the bridging architecture in Asterisk, and provide various methods of bridging call media between participants in a call.

Now let's go into more detail on each of the module types.

Importan note :
Modules will not get loaded if they don't exist, which could be that they were not enabled in menuconfig, or that a required dependency was missing at build time, or because the relevant configuration file was missing or invalid.

9 Child Pages 

Reorder Pages

Page: Channel Driver ModulesPage: Dialplan Application ModulesPage: Dialplan Function ModulesPage: Resource ModulesPage: Codec ModulesPage: File Format DriversPage: Call Detail Record (CDR) DriversPage: Call Event Log (CEL) Driver ModulesPage: Bridging Modules

Podemos cargar los módulos desde la consola de Asterisk :

Asterisk-PBX*CLI> module load chan-dahdi.so

Asterisk-PBX*CLI> module load chan_sip.so

Para localizar un modulo especifico en Asterisk corremos el siguiente commando : ls /usr/lib/asterisk/modules |  grep -i modulename

Ejemplo
root@ubuntu:~# ls /usr/lib/asterisk/modules |  grep -i mysql | less
app_mysql.so
cdr_mysql.so
res_config_mysql.so


Los modulos en Asterisk residen en la ruta :
 


 /usr/lib/asterisk/modules/


tambien podemos editar el archivo /etc/asterisk/modules.conf


[modules]
autoload=yes  ; esta opcion carga los modulos de forma automatica si queremos   iniciar asterisk sin modulos solot enemos que comentarla


;aqui por ejemplo podemos quitar modulos de que no carguen en el inicio

noload => chan_dahdi.so
noload =>res_config_mysql.so
noload =>res_calendar_icalendar.so

Option	Value/Example	Notes
autoload	yes	Instead of explicitly listing which modules to load, you can use this directive to tell Asterisk to load all modules that it finds in the modules directory, with the exception of modules listed as not to be loaded using the noload directive. The default, and our recommendation, is to set this option to yes.
preload	res_odbc.so	Indicates that a module should be loaded at the beginning of the module load order. This directive is much less relevant than it used to be; modules now have a load priority built into them that solves the problems that this directive was previously used to solve.
load	chan_sip.so	Defines a module that should be loaded. This directive is only relevant if autoload is set to no.
noload	chan_alsa.so	Defines a module that should not be loaded. This directive is only relevant if autoload is set to yes.
require	chan_sip.so	Does the same thing as load; additionally, Asterisk will exit if this module fails to load for some reason.
preload-require	res_odbc.so	Does the same thing as preload; additionally, Asterisk will exit if this module fails to load for some reason.

https://wiki.asterisk.org/wiki/display/AST/Types+of+Asterisk+Modules

http://www.asteriskdocs.org/en/3rd_Edition/asterisk-book-html-chunk/additional_configuration_tasks-modules-conf-file.html