As Asterisk 14 is built on the architecture introduced in Asterisk 12 and continued in Asterisk 13, users upgrading to Asterisk 14 from an older version of Asterisk should be aware of the architectural changes that were made in the previous Standard release. It is recommended that you review:
- The upgrade notes on this page
- The New in 14 information, which lists the major new features in Asterisk 14
- The notes on Upgrading to Asterisk 13 if you are upgrading from a version of Asterisk prior to Asterisk 13
- The notes on what is New in 13 if if you are upgrading from a version of Asterisk prior to Asterisk 13.
The policy for when to send
Dialevents has changed. Previously,
Dialevents were sent on the calling channel's topic. However, starting in Asterisk 14, if there is no calling channel on which to send the event, the event is instead sent on the called channel's topic. Note that for the ARI channels resource's dial operation, this means that the
Dialevents will always be sent on the called channel's topic.
- For users using the FXO port (FXS signaling) distinctive ring detection feature, you will need to adjust the
dringXcount values. The count values now only record ring end events instead of any DAHDI event. A ring-ring-ring pattern would exceed the pattern limits and stop Caller-ID detection.
- The SIP dial string has been extended past the
[!dnid]option by another exclamation mark:
[!dnid[!fromuri]. An exclamation mark in the To-URI will now mean changes to the From-URI.
- The REF_DEBUG compiler flag is now used to enable refdebug by default. The setting can be overridden in asterisk.conf by setting refdebug in the options category. No recompile is required to enable/disable it.
- Modified processing of command-line options to first parse only what is necessary to read asterisk.conf. Once asterisk.conf is fully loaded, the remaining options are processed. The -X option now applies to asterisk.conf only. To enable #exec for other config files you must set
execincludes=yesin asterisk.conf. Any other option set on the command-line will now override the equivalent setting from asterisk.conf.
ModuleCheckAction's Version key will no longer show the moduleversion. The value will always be blank.
The Command action now sends the output from the CLI command as a series of Output headers for each line instead of as a block of text with the
--END COMMAND--delimiter to match the output from other actions.
Commands that fail to execute (no such command, invalid syntax etc.) now return an Error response instead of Success.
core show file versioncommand has been removed. When Asterisk moved to Git, the source control version support was removed. As a result, the CLi command was no longer useful and was removed as well.
- The first callid created is now 1 instead of 0. The value 0 is now reserved to represent a lack of callid.
maximum_number_of_wordsconfiguration option and parameter to the AMD application previously did not match the documented functionality + variable name. In Asterisk 13, a value of '3' would mean that if '3' words were detected, the result would be detection as a 'MACHINE'. As of this version, the value reflects the maximum words that if EXCEEDED (rather than reached), would result in detection as a machine. This means that you should update this value to be one higher than your previous value, if your previous value was working well for you.