2008-11-19 12:42:19 +00:00
|
|
|
===========================================================
|
2008-11-21 20:42:37 +00:00
|
|
|
===
|
2010-06-03 18:53:24 +00:00
|
|
|
=== Information for upgrading between Asterisk versions
|
2008-02-08 16:49:19 +00:00
|
|
|
===
|
2008-11-21 20:42:37 +00:00
|
|
|
=== These files document all the changes that MUST be taken
|
|
|
|
|
=== into account when upgrading between the Asterisk
|
|
|
|
|
=== versions listed below. These changes may require that
|
|
|
|
|
=== you modify your configuration files, dialplan or (in
|
|
|
|
|
=== some cases) source code if you have your own Asterisk
|
2011-01-04 16:38:28 +00:00
|
|
|
=== modules or patches. These files also include advance
|
2008-11-21 20:42:37 +00:00
|
|
|
=== notice of any functionality that has been marked as
|
|
|
|
|
=== 'deprecated' and may be removed in a future release,
|
|
|
|
|
=== along with the suggested replacement functionality.
|
2008-02-08 16:49:19 +00:00
|
|
|
===
|
|
|
|
|
=== UPGRADE-1.2.txt -- Upgrade info for 1.0 to 1.2
|
|
|
|
|
=== UPGRADE-1.4.txt -- Upgrade info for 1.2 to 1.4
|
2008-11-19 12:42:19 +00:00
|
|
|
=== UPGRADE-1.6.txt -- Upgrade info for 1.4 to 1.6
|
2010-07-23 19:17:30 +00:00
|
|
|
=== UPGRADE-1.8.txt -- Upgrade info for 1.6 to 1.8
|
2013-08-30 18:38:00 +00:00
|
|
|
=== UPGRADE-10.txt -- Upgrade info for 1.8 to 10
|
|
|
|
|
=== UPGRADE-11.txt -- Upgrade info for 10 to 11
|
|
|
|
|
=== UPGRADE-12.txt -- Upgrade info for 11 to 12
|
2014-08-08 01:33:18 +00:00
|
|
|
=== UPGRADE-13.txt -- Upgrade info for 12 to 13
|
2008-11-19 12:42:19 +00:00
|
|
|
===========================================================
|
|
|
|
|
|
2015-03-06 20:24:58 +00:00
|
|
|
Channel Drivers:
|
|
|
|
|
|
|
|
|
|
chan_dahdi:
|
|
|
|
|
- For users using the FXO port (FXS signaling) distinctive ring detection
|
|
|
|
|
feature, you will need to adjust the dringX count 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.
|
res_http_websocket: Close websocket correctly and use careful fwrite
When a client takes a long time to process information received from Asterisk,
a write operation using fwrite may fail to write all information. This causes
the underlying file stream to be in an unknown state, such that the socket
must be disconnected. Unfortunately, there are two problems with this in
Asterisk's existing websocket code:
1. Periodically, during the read loop, Asterisk must write to the connected
websocket to respond to pings. As such, Asterisk maintains a reference to
the session during the loop. When ast_http_websocket_write fails, it may
cause the session to decrement its ref count, but this in and of itself
does not break the read loop. The read loop's write, on the other hand,
does not break the loop if it fails. This causes the socket to get in a
'stuck' state, preventing the client from reconnecting to the server.
2. More importantly, however, is that the fwrite in ast_http_websocket_write
fails with a large volume of data when the client takes awhile to process
the information. When it does fail, it fails writing only a portion of
the bytes. With some debugging, it was shown that this was failing in a
similar fashion to ASTERISK-12767. Switching this over to ast_careful_fwrite
with a long enough timeout solved the problem.
Note that this version of the patch, unlike r417310 in Asterisk 11, exposes
configuration options beyond just chan_sip's sip.conf. Configuration options
to configure the write timeout have also been added to pjsip.conf and ari.conf.
#ASTERISK-23917 #close
Reported by: Matt Jordan
Review: https://reviewboard.asterisk.org/r/3624/
........
Merged revisions 417310 from http://svn.asterisk.org/svn/asterisk/branches/11
........
Merged revisions 417311 from http://svn.asterisk.org/svn/asterisk/branches/12
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@417317 65c4cc65-6c06-0410-ace0-fbb531ad65f3
2014-06-26 12:21:14 +00:00
|
|
|
|
2015-03-13 01:12:35 +00:00
|
|
|
Core:
|
2015-04-17 07:16:59 +00:00
|
|
|
- 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.
|
2015-03-13 01:12:35 +00:00
|
|
|
|
2015-05-06 13:31:33 +00:00
|
|
|
- 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=yes in asterisk.conf. Any other option set on the
|
|
|
|
|
command-line will now override the equivalent setting from asterisk.conf.
|
|
|
|
|
|
git migration: Refactor the ASTERISK_FILE_VERSION macro
Git does not support the ability to replace a token with a version
string during check-in. While it does have support for replacing a
token on clone, this is somewhat sub-optimal: the token is replaced
with the object hash, which is not particularly easy for human
consumption. What's more, in practice, the source file version was often
not terribly useful. Generally, when triaging bugs, the overall version
of Asterisk is far more useful than an individual SVN version of a file. As a
result, this patch removes Asterisk's support for showing source file
versions.
Specifically, it does the following:
* Rename ASTERISK_FILE_VERSION macro to ASTERISK_REGISTER_FILE, and
remove passing the version in with the macro. Other facilities
than 'core show file version' make use of the file names, such as
setting a debug level only on a specific file. As such, the act of
registering source files with the Asterisk core still has use. The
macro rename now reflects the new macro purpose.
* main/asterisk:
- Refactor the file_version structure to reflect that it no longer
tracks a version field.
- Remove the "core show file version" CLI command. Without the file
version, it is no longer useful.
- Remove the ast_file_version_find function. The file version is no
longer tracked.
- Rename ast_register_file_version/ast_unregister_file_version to
ast_register_file/ast_unregister_file, respectively.
* main/manager: Remove value from the Version key of the ModuleCheck
Action. The actual key itself has not been removed, as doing so would
absolutely constitute a backwards incompatible change. However, since
the file version is no longer tracked, there is no need to attempt to
include it in the Version key.
* UPGRADE: Add notes for:
- Modification to the ModuleCheck AMI Action
- Removal of the "core show file version" CLI command
Change-Id: I6cf0ff280e1668bf4957dc21f32a5ff43444a40e
2015-04-12 02:38:22 +00:00
|
|
|
AMI:
|
|
|
|
|
- The 'ModuleCheck' Action's Version key will no longer show the module
|
|
|
|
|
version. The value will always be blank.
|
|
|
|
|
|
|
|
|
|
CLI:
|
|
|
|
|
- The 'core show file version' command 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.
|
|
|
|
|
|
2015-03-13 01:12:35 +00:00
|
|
|
Logging:
|
|
|
|
|
- The first callid created is now 1 instead of 0. The value 0
|
|
|
|
|
is now reserved to represent a lack of callid.
|
|
|
|
|
|
2015-04-17 03:34:59 +00:00
|
|
|
AMI:
|
|
|
|
|
- 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.
|
|
|
|
|
|
2015-12-21 03:33:02 +00:00
|
|
|
app_amd:
|
|
|
|
|
- The 'maximum_number_of_words' configuration 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 previos value, if your previous value
|
|
|
|
|
was working well for you.
|
|
|
|
|
|
2010-07-23 19:17:30 +00:00
|
|
|
===========================================================
|
|
|
|
|
===========================================================
|
