Professional Documents
Culture Documents
Asterisk 16 Configuration - Features - Asterisk Project - Asterisk Project Wiki
Asterisk 16 Configuration - Features - Asterisk Project - Asterisk Project Wiki
Features Configuration
This configuration documentation is for functionality provided by features.
features.conf
globals
https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+Configuration_features 1/5
22/07/2022, 18:18 Asterisk 16 Configuration_features - Asterisk Project - Asterisk Project Wiki
atxferdropcall
When this option is set to no, then Asterisk will attempt to re-call the transferrer if the call to the transfer target fails. If
the call to the transferrer fails, then Asterisk will wait atxferloopdelay milliseconds and then attempt to dial the transfer
target again. This process will repeat until atxfercallbackretries attempts to re-call the transferrer have occurred.
When this option is set to yes, then Asterisk will not attempt to re-call the transferrer if the call to the transfer target
fails. Asterisk will instead hang up all channels involved in the transfer.
xfersound
This sound will play to the transferrer and transfer target channels when an attended transfer completes. This sound is
also played to channels when performing an AMI Bridge action.
atxferabort
This option is only available to the transferrer during an attended transfer operation. Aborting a transfer results in the
transfer being cancelled and the original parties in the call being re-bridged.
atxfercomplete
This option is only available to the transferrer during an attended transfer operation. Completing the transfer with a
DTMF sequence is functionally equivalent to hanging up the transferrer channel during an attended transfer. The result
is that the transfer target and transferees are bridged.
atxferthreeway
This option is only available to the transferrer during an attended transfer operation. Pressing this DTMF sequence will
result in the transferrer, the transferees, and the transfer target all being in a single bridge together.
https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+Configuration_features 2/5
22/07/2022, 18:18 Asterisk 16 Configuration_features - Asterisk Project - Asterisk Project Wiki
atxferswap
This option is only available to the transferrer during an attended transfer operation. Pressing this DTMF sequence will
result in the transferrer swapping which party he is bridged with. For instance, if the transferrer is currently bridged with
the transfer target, then pressing this DTMF sequence will cause the transferrer to be bridged with the transferees.
pickupexten
In order for the pickup attempt to be successful, the party attempting to pick up the call must either have
a namedpickupgroup in common with a ringing party's namedcallgroup or must have a pickupgroup in common with a
ringing party's callgroup.
featuremap
DTMF options that can be triggered during bridged calls
atxfer
The transferee parties will be placed on hold and the transferrer may dial an extension to reach a transfer target.
During an attended transfer, the transferrer may consult with the transfer target before completing the transfer. Once
the transferrer has hung up or pressed the atxfercomplete DTMF sequence, then the transferees and transfer target
will be bridged.
blindxfer
The transferee parties will be placed on hold and the transferrer may dial an extension to reach a transfer target.
During a blind transfer, as soon as the transfer target is dialed, the transferrer is hung up.
disconnect
Entering this DTMF sequence will cause the bridge to end, no matter the number of parties present
parkcall
The parking lot used to park the call is determined by using either the PARKINGLOT channel variable or a configured
value on the channel (provided by the channel driver) if the variable is not present. If no configured value on the
channel is present, then "default" is used. The call is parked in the next available space in the parking lot.
https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+Configuration_features 3/5
22/07/2022, 18:18 Asterisk 16 Configuration_features - Asterisk Project - Asterisk Project Wiki
automon
This will cause the channel that pressed the DTMF sequence to be monitored by the Monitor application. The format
for the recording is determined by the TOUCH_MONITOR_FORMAT channel variable. If this variable is not specified,
then wav is the default. The filename is constructed in the following manner:
prefix-timestamp-suffix.fmt
where prefix is either the value of the TOUCH_MONITOR_PREFIX channel variable or auto if the variable is not set.
The timestamp is a UNIX timestamp. The suffix is either the value of the TOUCH_MONITOR channel variable or the
callerID of the channels if the variable is not set.
automixmon
This will cause the channel that pressed the DTMF sequence to be monitored by the MixMonitor application. The
format for the recording is determined by the TOUCH_MIXMONITOR_FORMAT channel variable. If this variable is not
specified, then wav is the default. The filename is constructed in the following manner:
prefix-timestamp-suffix.fmt
where prefix is either the value of the TOUCH_MIXMONITOR_PREFIX channel variable or auto if the variable is not
set. The timestamp is a UNIX timestamp. The suffix is either the value of the TOUCH_MIXMONITOR channel variable
or the callerID of the channels if the variable is not set.
applicationmap
Section for defining custom feature invocations during a call
featuregroup
Groupings of items from the applicationmap
https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+Configuration_features 4/5
22/07/2022, 18:18 Asterisk 16 Configuration_features - Asterisk Project - Asterisk Project Wiki
https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+Configuration_features 5/5