Datasets:
Squidnutz
/
extractedtest

Dataset card Data Studio Files
xet
 Community
1
text
stringlengths
0
152
/etc/asterisk/features.conf
$ sudo chown asterisk:asterisk /etc/asterisk/features.conf
features.conf
Asterisk provides several features common to most PBXs, many of which have
optional parameters. The features.conf file is where you can adjust or define the vari‐
ous feature parameters in Asterisk.
189
DTMF-Based Features
Many of the parameters in features.conf only apply when invoked on calls that have
been bridged by the dialplan applications Dial() or Queue() using one or more of the
options K, k, H, h, T, t, W, w, X, or x. Features accessed in this way are DTMF-based
(meaning they can’t be accessed via SIP messaging, but only through touch-tone
signals in the audio channel triggered by users dialing the required digits on their
dialpads).1
Transfers on SIP channels (for example, from a SIP telephone) can be handled using
the capabilities of the phone itself and won’t be affected by anything in the
features.conf file.
The [general] Section
In the [general] section of features.conf, you can define options that fine-tune the
behavior of the transfers feature in Asterisk. These have nothing to do with how SIP
telephones handle call transfers. You instead access these features by using DTMF
digits while on a call (the call must be bridged, so calls ringing or in progress will not
have access to these features).
The features.conf.sample file in your ~/asterisk/ folder contains details of the various
options, and examples of how they can be set.
These features are not as commonly used as they were in the past, mostly because
many of these things can be handled in more advanced ways than firing DTMF from
the telephone set (for example, through an external integration of some sort, or for
that matter from the telephone itself using its own internal transfer features).
The [featuremap] Section
The [featuremap] section, summarized in Table 11-1, allows you to define specific
DTMF sequences that will trigger features on channels that have been bridged via
options in the Dial() or Queue() application. The two options you are most likely to
use are parkcall and automixmon.
1 Yes, we realize that a SIP INFO message is in fact a SIP message and not technically part of the audio channel,
but the point is that you can’t use the “transfer” or “park” button on your SIP phone to access these features
while on a call. You’ll have to send DTMF.
190
|
Chapter 11: PBX Features, Including Parking, Paging, and Conferencing
Table 11-1. features.conf [featuremap] section
Option
Value/example Notes
blindxfer
#1
disconnect *0
automon
*1
atxfer
parkcall
*2
#72
automixmon *3
Invokes a blind (unsupervised) transfer
Hangs up the call
Starts recording of the current call using the Monitor()
application (pressing this key sequence a second time stops the
recording)
Performs an automated transfer
Parks a call
Starts recording of the current call using the MixMonitor()
application (pressing this key sequence again stops the recording)
Dial()/Queue()
flags
T, t
H, h
W, w
T, t