UPGRADE.txt 7.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171
  1. ===========================================================
  2. ===
  3. === Information for upgrading between Asterisk versions
  4. ===
  5. === These files document all the changes that MUST be taken
  6. === into account when upgrading between the Asterisk
  7. === versions listed below. These changes may require that
  8. === you modify your configuration files, dialplan or (in
  9. === some cases) source code if you have your own Asterisk
  10. === modules or patches. These files also include advance
  11. === notice of any functionality that has been marked as
  12. === 'deprecated' and may be removed in a future release,
  13. === along with the suggested replacement functionality.
  14. ===
  15. === UPGRADE-1.2.txt -- Upgrade info for 1.0 to 1.2
  16. === UPGRADE-1.4.txt -- Upgrade info for 1.2 to 1.4
  17. === UPGRADE-1.6.txt -- Upgrade info for 1.4 to 1.6
  18. === UPGRADE-1.8.txt -- Upgrade info for 1.6 to 1.8
  19. ===
  20. ===========================================================
  21. from 10.12.3 to 10.12.4:
  22. * Certain dialplan functions have been marked as 'dangerous', and may only be
  23. executed from the dialplan. Execution from extenal sources (AMI's GetVar and
  24. SetVar actions; etc.) may be inhibited by setting live_dangerously in the
  25. [options] section of asterisk.conf to no. SHELL(), channel locking, and direct
  26. file read/write functions are marked as dangerous. DB_DELETE() and
  27. REALTIME_DESTROY() are marked as dangerous for reads, but can now safely
  28. accept writes (which ignore the provided value).
  29. from 10.12.0 to 10.12.1:
  30. * Asterisk would previously not output certain error messages when a remote
  31. console attempted to connect to Asterisk and no instance of Asterisk was
  32. running. This error message is displayed on stderr; as a result, some
  33. initialization scripts that used remote consoles to test for the presence
  34. of a running Asterisk instance started to display erroneous error messages.
  35. The init.d scripts and the safe_asterisk have been updated in the contrib
  36. folder to account for this.
  37. From 10.11 to 10.12:
  38. * Asterisk has always had code to ignore dash '-' characters that are not
  39. part of a character set in the dialplan extensions. The code now
  40. consistently ignores these characters when matching dialplan extensions.
  41. * Removed the queues.conf check_state_unknown option. It is no longer
  42. necessary.
  43. From 10.9 to 10.10:
  44. * Queue strategy rrmemory now has a predictable order similar to strategy
  45. rrordered. Members will be called in the order that they are added to the
  46. queue.
  47. From 10.4 to 10.5:
  48. * The complex processor detection and optimization has been removed from
  49. the makefile in favor of using native optimization suppport when available.
  50. BUILD_NATIVE can be disabled via menuselect under "Compiler Flags".
  51. From 10.3 to 10.4:
  52. * In AEL dialplans, the "h" extension will now be inherited from prior
  53. calling contexts, just as it had in 1.4. If you have created an AEL
  54. dialplan from scratch in earlier versions of 10, you may want to check
  55. that the execution of "h" extensions in earlier contexts is what you
  56. want. If you want to interrupt this functionality, simply placing an
  57. "h" extension in the macro where you want no inheritance to take place
  58. should be sufficient.
  59. From 10.2 to 10.3:
  60. * The BLINDTRANSFER channel variable is deleted from a channel when it is
  61. bridged to prevent subtle bugs in the parking feature. The channel
  62. variable is used by Asterisk internally for the Park application to work
  63. properly. If you were using it for your own purposes, copy it to your
  64. own channel variable before the channel is bridged.
  65. * If no transport is specified in sip.conf, transport will default to UDP.
  66. Also, if multiple transport= lines are used, only the last will be used.
  67. From 1.8 to 10:
  68. cel_pgsql:
  69. - This module now expects an 'extra' column in the database for data added
  70. using the CELGenUserEvent() application.
  71. ConfBridge
  72. - ConfBridge's dialplan arguments have changed and are not
  73. backwards compatible.
  74. File Interpreters
  75. - The format interpreter formats/format_sln16.c for the file extension
  76. '.sln16' has been removed. The '.sln16' file interpreter now exists
  77. in the formats/format_sln.c module along with new support for sln12,
  78. sln24, sln32, sln44, sln48, sln96, and sln192 file extensions.
  79. HTTP:
  80. - A bindaddr must be specified in order for the HTTP server
  81. to run. Previous versions would default to 0.0.0.0 if no
  82. bindaddr was specified.
  83. Gtalk:
  84. - The default value for 'context' and 'parkinglots' in gtalk.conf has
  85. been changed to 'default', previously they were empty.
  86. chan_dahdi:
  87. - The mohinterpret=passthrough setting is deprecated in favor of
  88. moh_signaling=notify.
  89. pbx_lua:
  90. - Execution no longer continues after applications that do dialplan jumps
  91. (such as app.goto). Now when an application such as app.goto() is called,
  92. control is returned back to the pbx engine and the current extension
  93. function stops executing.
  94. - the autoservice now defaults to being on by default
  95. - autoservice_start() and autoservice_start() no longer return a value.
  96. Queue:
  97. - Mark QUEUE_MEMBER_PENALTY Deprecated it never worked for realtime members
  98. - QUEUE_MEMBER is now R/W supporting setting paused, ignorebusy and penalty.
  99. Asterisk Database:
  100. - The internal Asterisk database has been switched from Berkeley DB 1.86 to
  101. SQLite 3. An existing Berkeley astdb file can be converted with the astdb2sqlite3
  102. utility in the UTILS section of menuselect. If an existing astdb is found and no
  103. astdb.sqlite3 exists, astdb2sqlite3 will be compiled automatically. Asterisk will
  104. convert an existing astdb to the SQLite3 version automatically at runtime. If
  105. moving back from Asterisk 10 to Asterisk 1.8, the astdb2bdb utility can be used
  106. to create a Berkeley DB copy of the SQLite3 astdb that Asterisk 10 uses.
  107. Manager:
  108. - The AMI protocol version was incremented to 1.2 as a result of changing two
  109. instances of the Unlink event to Bridge events. This change was documented
  110. as part of the AMI 1.1 update, but two Unlink events were inadvertently left
  111. unchanged.
  112. Module Support Level
  113. - All modules in the addons, apps, bridge, cdr, cel, channels, codecs,
  114. formats, funcs, pbx, and res have been updated to include MODULEINFO data
  115. that includes <support_level> tags with a value of core, extended, or deprecated.
  116. More information is available on the Asterisk wiki at
  117. https://wiki.asterisk.org/wiki/display/AST/Asterisk+Module+Support+States
  118. Deprecated modules are now marked to not build by default and must be explicitly
  119. enabled in menuselect.
  120. chan_sip:
  121. - Setting of HASH(SIP_CAUSE,<slave-channel-name>) on channels is now disabled
  122. by default. It can be enabled using the 'storesipcause' option. This feature
  123. has a significant performance penalty.
  124. - In order to improve compliance with RFC 3261, SIP usernames are now properly
  125. escaped when encoding reserved characters. Prior to this change, the use of
  126. these characters in certain SIP settings affecting usernames could cause
  127. injections of these characters in their raw form into SIP headers which could
  128. in turn cause all sorts of nasty behaviors. All characters that are not
  129. alphanumeric or are not contained in the the following lists specified by
  130. RFC 3261 section 25.1 will be escaped as %XX when encoding a SIP username:
  131. * mark: "-" / "_" / "." / "!" / "~" / "*" / "'" / "(" / ")"
  132. * user-unreserved: "&" / "=" / "+" / "$" / "," / ";" / "?" / "/"
  133. UDPTL:
  134. - The default UDPTL port range in udptl.conf.sample differed from the defaults
  135. in the source. If you didn't have a config file, you got 4500 to 4599. Now the
  136. default is 4000 to 4999.
  137. ===========================================================
  138. ===========================================================