mirror of
https://github.com/asterisk/asterisk.git
synced 2025-09-03 03:20:57 +00:00
205a31f86c
Dial events up to this point have come in two flavors * A Dial event with no status to indicate that dialing has begun * A Dial event with a status to indicate that dialing has ended With this change, Dial events have been expanded to also give intermediate events, such as "RINGING", "PROCEEDING", and "PROGRESS". This is especially useful for ARI dialing, as it gives the application writer the opportunity to place a channel into an early bridge when early media is detected. AMI handles these in-progress dial events by sending a new event called "DialState" that simply indicates that dial state has changed but has not ended. ARI never distinguished between DialBegin and DialEnd, so no change was made to the event itself. Another change here relates to dial forwards. A forward-related event was previously only sent when a channel was successfully able to forward a call to a new channel. With this set of changes, if forwarding is blocked, we send a Dial event with a forwarding destination but no forwarding channel, since we were prevented from creating one. This is again useful for ARI since application writers can now handle call forward attempts from within their own application. ASTERISK-25925 #close Reported by Mark Michelson Change-Id: I42cbec7730d84640a434d143a0d172a740995543
92 lines
4.2 KiB
Plaintext
92 lines
4.2 KiB
Plaintext
===========================================================
|
|
===
|
|
=== 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
|
|
===========================================================
|
|
|
|
ARI:
|
|
- The policy for when to send "Dial" events has changed. Previously, "Dial"
|
|
events 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 "Dial" events will always be
|
|
sent on the called channel's topic.
|
|
|
|
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.
|
|
|
|
chan_sip:
|
|
- 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.
|
|
|
|
Core:
|
|
- 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=yes in asterisk.conf. Any other option set on the
|
|
command-line will now override the equivalent setting from asterisk.conf.
|
|
|
|
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.
|
|
|
|
Logging:
|
|
- The first callid created is now 1 instead of 0. The value 0
|
|
is now reserved to represent a lack of callid.
|
|
|
|
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.
|
|
|
|
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.
|
|
|
|
===========================================================
|
|
===========================================================
|