Datasets:
Squidnutz
/
extractedtest

Dataset card Data Studio Files
xet
Community
1
text
stringlengths
0
152
while loop functionality in the dialplan
Bridging Modules
Bridging modules perform the actual bridging of channels. These modules, listed in
Table 2-2, are currently only used for (and are essential to) app_confbridge.
Table 2-2. Bridging modules
Name
bridge_builtin_features Performs bridging when utilizing built-in user features (such as those found in
Purpose
bridge_multiplexed
bridge_simple
bridge_softmix
features.conf).
Performs complex multiplexing, as would be required in a large conference room
(multiple participants). Currently only used by app_confbridge.
Performs simple channel-to-channel bridging.
Performs simple multiplexing, as would be required in a large conference room
(multiple participants). Currently only used by app_confbridge.
12
|
Chapter 2: Asterisk Architecture
Call Detail Recording Modules
The CDR modules, listed in Table 2-3, are designed to facilitate as many methods of
storing call detail records as possible. You can store CDRs to a file (the default), a
database, Remote Authentication Dial In User Service (RADIUS), or syslog.
Call detail records are not intended to be used in complex billing
applications. If you require more control over billing and call
reporting, you will want to look at channel event logging, discussed
next. The advantage of CDR is that it just works.
Table 2-3. Common call detail recording modules
Name
cdr_adaptive_odbc Allows writing of CDRs through ODBC framework with ability to add custom fields
cdr_csv
Purpose
cdr_custom
cdr_odbc
cdr_syslog
Writes CDRs to disk as a comma-separated values (CSV) file
Writes CDRs to a CSV file, but allows addition of custom fields
Writes CDRs through ODBC framework
Writes CDRs to syslog
Channel Event Logging Modules
Channel event logging (CEL) provides much more powerful control over reporting of
call activity. By the same token, it requires more careful planning of your dialplan,
and by no means will it work automatically. Asterisk’s CEL modules are listed in
Table 2-4.
Table 2-4. Channel event logging modules
Name
cel_custom
Purpose
CEL to disk/file
cel_manager CEL to AMI
cel_odbc
CEL to ODBC
Channel Drivers
Without channel drivers, Asterisk would have no way to make or receive calls. Each
channel driver is specific to the protocol or channel type it supports (SIP, ISDN, etc.).
The channel module acts as a gateway to the Asterisk core. Some of Asterisk’s more
popular channel drivers are listed in Table 2-5.
Modules
|
13
Table 2-5. Popular channel drivers
Name
chan_bridge
chan_dahdi
chan_local