mirror of
https://github.com/asterisk/asterisk.git
synced 2025-09-04 11:58:52 +00:00
4ec301360c
This patch includes a number of changes to the indications API. The primary motivation for this work was to improve stability. The object management in this API was significantly flawed, and a number of trivial situations could cause crashes. The changes included are: 1) Remove the module res_indications. This included the critical functionality that actually loaded the indications configuration. I have seen many people have Asterisk problems because they accidentally did not have an indications.conf present and loaded. Now, this code is in the core, and Asterisk will fail to start without indications configuration. There was one part of res_indications, the dialplan applications, which did belong in a module, and have been moved to a new module, app_playtones. 2) Object management has been significantly changed. Tone zones are now managed using astobj2, and it is no longer possible to crash Asterisk by issuing a reload that destroys tone zones while they are in use. 3) The API documentation has been filled out. 4) The API has been updated to follow our naming conventions. 5) Various bits of code throughout the tree have been updated to account for the API update. 6) Configuration parsing has been mostly re-written. 7) "Code cleanup" The code is from svn/asterisk/team/russell/indications/. Review: http://reviewboard.digium.com/r/149/ git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@176627 65c4cc65-6c06-0410-ace0-fbb531ad65f3
110 lines
5.4 KiB
Plaintext
110 lines
5.4 KiB
Plaintext
===========================================================
|
|
===
|
|
=== Information for upgrading between Asterisk 1.6 versions
|
|
===
|
|
=== 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
|
|
=== modules or patches. These files also includes advance
|
|
=== notice of any functionality that has been marked as
|
|
=== 'deprecated' and may be removed in a future release,
|
|
=== along with the suggested replacement functionality.
|
|
===
|
|
=== UPGRADE-1.2.txt -- Upgrade info for 1.0 to 1.2
|
|
=== UPGRADE-1.4.txt -- Upgrade info for 1.2 to 1.4
|
|
=== UPGRADE-1.6.txt -- Upgrade info for 1.4 to 1.6
|
|
===
|
|
===========================================================
|
|
|
|
From 1.6.1 to 1.6.2:
|
|
|
|
* The res_indications module has been removed. Its functionality was important
|
|
enough that most of it has been moved into the Asterisk core.
|
|
Two applications previously provided by res_indications, PlayTones and
|
|
StopPlayTones, have been moved into a new module, app_playtones.
|
|
|
|
From 1.6.0.1 to 1.6.1:
|
|
|
|
* The ast_agi_register_multiple() and ast_agi_unregister_multiple()
|
|
API calls were added in 1.6.0, so that modules that provide multiple
|
|
AGI commands could register/unregister them all with a single
|
|
step. However, these API calls were not implemented properly, and did
|
|
not allow the caller to know whether registration or unregistration
|
|
succeeded or failed. They have been redefined to now return success
|
|
or failure, but this means any code using these functions will need
|
|
be recompiled after upgrading to a version of Asterisk containing
|
|
these changes. In addition, the source code using these functions
|
|
should be reviewed to ensure it can properly react to failure
|
|
of registration or unregistration of its API commands.
|
|
|
|
* The ast_agi_fdprintf() API call has been renamed to ast_agi_send()
|
|
to better match what it really does, and the argument order has been
|
|
changed to be consistent with other API calls that perform similar
|
|
operations.
|
|
|
|
From 1.6.0.x to 1.6.1:
|
|
|
|
* The following core commands dealing with dialplan have been deprecated: 'core
|
|
show globals', 'core set global' and 'core set chanvar'. Use the equivalent
|
|
'dialplan show globals', 'dialplan set global' and 'dialplan set chanvar'
|
|
instead.
|
|
|
|
* In the dialplan expression parser, the logical value of spaces
|
|
immediately preceding a standalone 0 previously evaluated to
|
|
true. It now evaluates to false. This has confused a good many
|
|
people in the past (typically because they failed to realize the
|
|
space had any significance). Since this violates the Principle of
|
|
Least Surprise, it has been changed.
|
|
|
|
* While app_directory has always relied on having a voicemail.conf or users.conf file
|
|
correctly set up, it now is dependent on app_voicemail being compiled as well.
|
|
|
|
* SIP: All of the functionality in SIPCHANINFO() has been implemented in CHANNEL(),
|
|
and you should start using that function instead for retrieving information about
|
|
the channel in a technology-agnostic way.
|
|
|
|
* If you have any third party modules which use a config file variable whose
|
|
name ends in a '+', please note that the append capability added to this
|
|
version may now conflict with that variable naming scheme. An easy
|
|
workaround is to ensure that a space occurs between the '+' and the '=',
|
|
to differentiate your variable from the append operator. This potential
|
|
conflict is unlikely, but is documented here to be thorough.
|
|
|
|
* The "Join" event from app_queue now uses the CallerIDNum header instead of
|
|
the CallerID header to indicate the CallerID number.
|
|
|
|
From 1.6.1 to 1.6.2:
|
|
|
|
* The default console now will use colors according to the default background
|
|
color, instead of forcing the background color to black. If you are using a
|
|
light colored background for your console, you may wish to use the option
|
|
flag '-W' to present better color choices for the various messages. However,
|
|
if you'd prefer the old method of forcing colors to white text on a black
|
|
background, the compatibility option -B is provided for this purpose.
|
|
|
|
* SendImage() no longer hangs up the channel on transmission error or on
|
|
any other error; in those cases, a FAILURE status is stored in
|
|
SENDIMAGESTATUS and dialplan execution continues. The possible
|
|
return values stored in SENDIMAGESTATUS are: SUCCESS, FAILURE, and
|
|
UNSUPPORTED. ('OK' has been replaced with 'SUCCESS', and 'NOSUPPORT'
|
|
has been replaced with 'UNSUPPORTED'). This change makes the
|
|
SendImage application more consistent with other applications.
|
|
|
|
* skinny.conf now has separate sections for lines and devices.
|
|
Please have a look at configs/skinny.conf.sample and update
|
|
your skinny.conf.
|
|
|
|
* Queue names previously were treated in a case-sensitive manner,
|
|
meaning that queues with names like "sales" and "sALeS" would be
|
|
seen as unique queues. The parsing logic has changed to use
|
|
case-insensitive comparisons now when originally hashing based on
|
|
queue names, meaning that now the two queues mentioned as examples
|
|
earlier will be seen as having the same name.
|
|
|
|
* The SPRINTF() dialplan function has been moved into its own module,
|
|
func_sprintf, and is no longer included in func_strings. If you use this
|
|
function and do not use 'autoload=yes' in modules.conf, you will need
|
|
to explicitly load func_sprintf for it to be available.
|