You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
92 lines
3.9 KiB
92 lines
3.9 KiB
===========================================================
|
|
===
|
|
=== Information for upgrading between Asterisk 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 include 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
|
|
=== UPGRADE-1.8.txt -- Upgrade info for 1.6 to 1.8
|
|
=== 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
|
|
=== UPGRADE-13.txt -- Upgrade info for 12 to 13
|
|
=== UPGRADE-14.txt -- Upgrade info for 13 to 14
|
|
=== UPGRADE-15.txt -- Upgrade info for 14 to 15
|
|
=== UPGRADE-16.txt -- Upgrade info for 15 to 16
|
|
===========================================================
|
|
|
|
New in 17.0.0:
|
|
|
|
chan_sip:
|
|
- The chan_sip module is now deprecated, users should migrate to the
|
|
replacement module chan_pjsip. See guides at the Asterisk Wiki:
|
|
https://wiki.asterisk.org/wiki/x/tAHOAQ
|
|
https://wiki.asterisk.org/wiki/x/hYCLAQ
|
|
|
|
func_callerid:
|
|
- The CALLERPRES() dialplan function, deprecated in Asterisk 1.8, has been
|
|
removed.
|
|
|
|
res_parking:
|
|
- The PARKINGSLOT channel variable, deprecated in Asterisk 12 in favor of the
|
|
PARKING_SPACE channel variable, will no longer be set.
|
|
|
|
res_xmpp:
|
|
- The JabberStatus application, deprecated in Asterisk 12, has been removed.
|
|
|
|
Channels:
|
|
- The core no longer uses the stasis cache for channels snapshots.
|
|
The following APIs are no longer available:
|
|
ast_channel_topic_cached()
|
|
ast_channel_topic_all_cached()
|
|
The ast_channel_cache_all() and ast_channel_cache_by_name() functions
|
|
now returns an ao2_container of ast_channel_snapshots rather than a
|
|
container of stasis_messages therefore you can't call stasis_cache
|
|
functions on it.
|
|
The ast_channel_topic_all() function now returns a normal topic,
|
|
not a cached one so you can't use stasis cache functions on it either.
|
|
The ast_channel_snapshot_type() stasis message now has the
|
|
ast_channel_snapshot_update structure as it's data.
|
|
ast_channel_snapshot_get_latest() still returns the latest snapshot.
|
|
|
|
Applications
|
|
- The JabberStatus application, deprecated in Asterisk 12, has been removed.
|
|
|
|
Bridging
|
|
- The bridging core no longer uses the stasis cache for bridge
|
|
snapshots. The latest bridge snapshot is now stored on the
|
|
ast_bridge structure itself.
|
|
- The following APIs are no longer available since the stasis cache
|
|
is no longer used:
|
|
ast_bridge_topic_cached()
|
|
ast_bridge_topic_all_cached()
|
|
- A topic pool is now used for individual bridge topics.
|
|
- The ast_bridge_cache() function was removed since there's no
|
|
longer a separate container of snapshots.
|
|
- A new function "ast_bridges()" was created to retrieve the
|
|
container of all bridges. Users formerly calling
|
|
ast_bridge_cache() can use the new function to iterate over
|
|
bridges and retrieve the latest snapshot directly from the
|
|
bridge.
|
|
- The ast_bridge_snapshot_get_latest() function was renamed to
|
|
ast_bridge_get_snapshot_by_uniqueid().
|
|
- A new function "ast_bridge_get_snapshot()" was created to retrieve
|
|
the bridge snapshot directly from the bridge structure.
|
|
- The ast_bridge_topic_all() function now returns a normal topic
|
|
not a cached one so you can't use stasis cache functions on it
|
|
either.
|
|
- The ast_bridge_snapshot_type() stasis message now has the
|
|
ast_bridge_snapshot_update structure as it's data. It contains
|
|
the last snapshot and the new one.
|
|
|