[asterisk-commits] mjordan: branch 12 r397870 - /branches/12/CHANGES
SVN commits to the Asterisk project
asterisk-commits at lists.digium.com
Wed Aug 28 15:43:07 CDT 2013
Author: mjordan
Date: Wed Aug 28 15:43:03 2013
New Revision: 397870
URL: http://svnview.digium.com/svn/asterisk?view=rev&rev=397870
Log:
Update CHANGES file for Asterisk 12
This updates the Asterisk 12 CHANGES file with the things that were missed
during the development cycle.
Review: https://reviewboard.asterisk.org/r/2795/
Modified:
branches/12/CHANGES
Modified: branches/12/CHANGES
URL: http://svnview.digium.com/svn/asterisk/branches/12/CHANGES?view=diff&rev=397870&r1=397869&r2=397870
==============================================================================
--- branches/12/CHANGES (original)
+++ branches/12/CHANGES Wed Aug 28 15:43:03 2013
@@ -7,30 +7,175 @@
=== and the other UPGRADE files for older releases.
===
==============================================================================
+
------------------------------------------------------------------------------
--- Functionality changes from Asterisk 11 to Asterisk 12 --------------------
------------------------------------------------------------------------------
+Overview
+------------------
+
+Asterisk 12 is a standard release of the Asterisk project. As such, the
+focus of development for this release was on core architectural changes and
+major new features. This includes:
+ * A more flexible bridging core based on the Bridging API
+ * A new internal message bus, Stasis
+ * Major standardization and consistency improvements to AMI
+ * Addition of the Asterisk RESTful Interface (ARI)
+ * A new SIP channel driver, chan_pjsip
+In addition, as the vast majority of bridging in Asterisk was migrated to the
+Bridging API used by ConfBridge, major changes were made to most of the
+interfaces in Asterisk. This includes not only AMI, but also CDRs and CEL.
+
+Specifications have been written for the affected interfaces. These
+specifications are available on the Asterisk wiki:
+ * AMI - https://wiki.asterisk.org/wiki/x/dAFRAQ
+ * CEL - https://wiki.asterisk.org/wiki/x/4ICLAQ
+ * CDRs - https://wiki.asterisk.org/wiki/x/pwpRAQ
+
+It is *highly* recommended that anyone migrating to Asterisk 12 read the
+information regarding its release both in this file and in the accompanying
+UPGRADE.txt file. More detailed information on the major changes can be found
+on the Asterisk wiki at https://wiki.asterisk.org/wiki/x/0YCLAQ.
+
+
+Build System
+------------------
+ * Added build option DISABLE_INLINE. This option can be used to work around a
+ bug in gcc. For more information, see
+ http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47816
+
+ * Removed the CHANNEL_TRACE development mode build option. Certain aspects of
+ the CHANNEL_TRACE build option were incompatible with the new bridging
+ architecture.
+
+ * Asterisk now optionally uses libxslt to improve XML documentation generation
+ and maintainability. If libxslt is not available on the system, some XML
+ documentation will be incomplete.
+
+ * Asterisk now depends on libjansson. If a package of libjansson is not
+ available on your distro, please see http://www.digip.org/jansson/.
+
+ * Asterisk now depends on libuuid and, optionally, uriparser. It is
+ recommended that you install uriparser, even if it is optional.
+
+ * The new SIP stack and channel driver uses a particular version of PJSIP.
+ Please see https://wiki.asterisk.org/wiki/x/J4GLAQ for more information on
+ configuring and installing PJSIP for usage with Asterisk.
+
+
Applications
------------------
AgentLogin
------------------
- * The application no longer does agent authentication. The dialplan needs to
- perform this function before running AgentLogin. If the agent is already
- logged in, dialplan will continue with the AGENT_STATUS channel variable
- set to ALREADY_LOGGED_IN.
+ * Along with AgentRequest, this application has been modified to be a
+ replacement for chan_agent. The act of a channel calling the AgentLogin
+ application places the channel into a pool of agents that can be
+ requested by the AgentRequest application. Note that this application, as
+ well as all other agent related functionality, is now provided by the
+ app_agent_pool module. See chan_agent and AgentRequest for more information.
+
+ * This application no longer performs agent authentication. If authentication
+ is desired, the dialplan needs to perform this function using the
+ Authenticate or VMAuthenticate application or through an AGI script before
+ running AgentLogin.
+
+ * If this application is called and the agent is already logged in, the
+ dialplan will continue exection with the AGENT_STATUS channel variable set
+ to ALREADY_LOGGED_IN.
+
+ * The agents.conf schema has changed. Rather than specifying agents on a
+ single line in comma delineated fashion, each agent is defined in a separate
+ context. This allows agents to use the power of context templates in their
+ definition.
+
+ * A number of parameters from agents.conf have been removed. This includes
+ maxloginretries, autologoffunavail, updatecdr, goodbye, group, recordformat,
+ urlprefix, and savecallsin. These options were obsoleted by the move from
+ a channel driver model to the bridging/application model provided by
+ app_agent_pool.
+
+AgentRequest
+------------------
+ * A new application, this will request a logged in agent from the pool and
+ bridge the requested channel with the channel calling this application.
+ Logged in agents are those channels that called the AgentLogin application.
+ If an agent cannot be requested from the pool, the AGENT_STATUS dialplan
+ application will be set with an appropriate error value.
AgentMonitorOutgoing
------------------
- * Application removed. It was a holdover from when AgentCallbackLogin was
- removed.
+ * This application has been removed. It was a holdover from when
+ AgentCallbackLogin was removed.
+
+AlarmReceiver
+------------------
+ * Added support for additional Ademco DTMF signalling formats, including
+ Express 4+1, Express 4+2, High Speed and Super Fast.
+
+ * Added channel variable ALARMRECEIVER_CALL_LIMIT. This sets the maximum
+ call time, in milliseconds, to run the application.
+
+ * Added channel variable ALARMRECEIVER_RETRIES_LIMIT. This sets the
+ maximum number of times to retry the call.
+
+ * Added a new configuration option answait. If set, the AlarmReceiver
+ application will wait the number of milliseconds specified by answait
+ after the channel has answered. Valid values range between 500
+ milliseconds and 10000 milliseconds.
+
+ * Added configuration option no_group_meta. If enabled, grouping of metadata
+ information in the AlarmReceiver log file will be skipped.
+
+BridgeWait
+------------------
+ * A new application in Asterisk, this will place the calling channel
+ into a holding bridge, optionally entertaining them with some form of
+ media. Channels participating in a holding bridge do not interact with
+ other channels in the same holding bridge. Optionally, however, a channel
+ may join as an announcer. Any media passed from an announcer channel is
+ played to all channels in the holding bridge. Channels leave a holding
+ bridge either when an optional timer expires, or via the ChannelRedirect
+ application or AMI Redirect action.
ConfBridge
------------------
* All participants in a bridge can now be kicked out of a conference room
by specifying the channel parameter as 'all' in the ConfBridge kick CLI
- command, i.e., "confbridge kick <conference> all"
+ command, i.e., 'confbridge kick <conference> all'
+
+ * CLI output for the 'confbridge list' command has been improved. When
+ displaying information about a particular bridge, flags will now be shown
+ for the participating users indicating properties of that user.
+
+ * The ConfbridgeList event now contains the following fields: WaitMarked,
+ EndMarked, and Waiting. This displays additional properties about the
+ user's profile, as well as whether or not the user is waiting for a
+ Marked user to enter the conference.
+
+ * Added a new option for conference recording, record_file_append. If enabled,
+ when the recording is stopped and then re-started, the existing recording
+ will be used and appended to.
+
+ControlPlayback
+------------------
+ * The channel variable CPLAYBACKSTATUS may now return the value
+ 'REMOTESTOPPED'. This occurs when playback is stopped by a remote interface,
+ such as AMI. See the AMI action ControlPlayback for more information.
+
+Directory
+------------------
+ * Added the 'a' option, which allows the caller to enter in an additional
+ alias for the user in the directory. This option must be used in conjunction
+ with the 'f', 'l', or 'b' options. Note that the alias for a user can be
+ specified in voicemail.conf.
+
+DumpChan
+------------------
+ * The output of DumpChan no longer includes the DirectBridge or IndirectBridge
+ fields. Instead, if a channel is in a bridge, it includes a BridgeID field
+ containing the unique ID of the bridge that the channel happens to be in.
ForkCDR
------------------
@@ -47,13 +192,15 @@
the state of the channel and cannot be altered.
* The 'D' option has been removed. Who the Party B is on a CDR is a function
- of the state of the respective channels, and cannot be altered.
+ of the state of the respective channels involved in the CDR and cannot be
+ altered.
* The 'r' option has been changed. Previously, ForkCDR always reset the CDR
such that the start time and, if applicable, the answer time was updated.
Now, by default, ForkCDR simply forks the CDR, maintaining any times. The
'r' option now triggers the Reset, setting the start time (and answer time
- if applicable) to the current time.
+ if applicable) to the current time. Note that the 'a' option still sets
+ the answer time to the current time if the channel was already answered.
* The 's' option has been removed. A variable can be set on the original CDR
if desired using the CDR function, and removed from a forked CDR using the
@@ -64,39 +211,67 @@
* The 'v' option now prevents the copy of the variables from the original CDR
to the forked CDR. Previously the variables were always copied but were
- removed from the original. Removing variables from a CDR can have unintended
- side effects - this option allows the user to prevent propagation of
- variables from the original to the forked without modifying the original.
+ removed from the original. This was changed as removing variables from a CDR
+ can have unintended side effects - this option allows the user to prevent
+ propagation of variables from the original to the forked without modifying
+ the original.
MeetMe
-------------------
-* Added the 'n' option to MeetMe to prevent application of the DENOISE function
- to a channel joining a conference. Some channel drivers that vary the number
- of audio samples in a voice frame will experience significant quality problems
- if a denoiser is attached to the channel; this option gives them the ability
- to remove the denoiser without having to unload func_speex.
+ * Added the 'n' option to MeetMe to prevent application of the DENOISE
+ function to a channel joining a conference. Some channel drivers that vary
+ the number of audio samples in a voice frame will experience significant
+ quality problems if a denoiser is attached to the channel; this option gives
+ them the ability to remove the denoiser without having to unload func_speex.
+
+MixMonitor
+------------------
+ * The 'b' option now includes conferences as well as sounds played to the
+ participants.
+
+ * The AUDIOHOOK_INHERIT function is no longer needed to keep a MixMonitor
+ running during a transfer. If a MixMonitor is started on a channel,
+ the MixMonitor will continue to record the audio passing through the
+ channel even in the presence of transfers.
NoCDR
------------------
* The NoCDR application is deprecated. Please use the CDR_PROP function to
disable CDRs.
+
* While the NoCDR application will prevent CDRs for a channel from being
propagated to registered CDR backends, it will not prevent that data from
being collected. Hence, a subsequent call to ResetCDR or the CDR_PROP
function that enables CDRs on a channel will restore those records that have
not yet been finalized.
+ParkAndAnnounce
+-------------------
+ * The app_parkandannounce module has been removed. The application
+ ParkAndAnnounce is now provided by the res_parking module. See the
+ res_parking changes for more information.
+
Queue
-------------------
- * Add queue available hint. exten => 8501,hint,Queue:markq_avail
- Note: the suffix '_avail' after the queuename.
- Reports 'InUse' for no logged in agents or no free agents.
- Reports 'Idle' when an agent is free.
+ * Added queue available hint. The hint can be added to the dialplan using the
+ following syntax: exten,hint,Queue:{queue_name}_avail
+ For example, if the name of the queue is 'markq':
+ exten => 8501,hint,Queue:markq_avail
+ This will report 'InUse' if there are no logged in agents or no free agents.
+ It will report 'Idle' when an agent is free.
+
+ * Queues now support a hint for member paused state. The hint uses the form
+ 'Queue:{queue_name}_pause_{member_name}', where {queue_name} and {member_name}
+ are the name of the queue and the name of the member to subscribe to,
+ respectively. For example: exten => 8501,hint,Queue:sales_pause_mark.
+ Members will show as In Use when paused.
* The configuration options eventwhencalled and eventmemberstatus have been
removed. As a result, the AMI events QueueMemberStatus, AgentCalled,
AgentConnect, AgentComplete, AgentDump, and AgentRingNoAnswer will always be
sent. The "Variable" fields will also no longer exist on the Agent* events.
+ These events can be filtered out from a connected AMI client using the
+ eventfilter setting in manager.conf.
* The queue log now differentiates between blind and attended transfers. A
blind transfer will result in a BLINDTRANSFER message with the destination
@@ -104,49 +279,88 @@
ATTENDEDTRANSFER message. This message will indicate the method by which
the attended transfer was completed: "BRIDGE" for a bridge merge, "APP"
for running an application on a bridge or channel, or "LINK" for linking
- two bridges together with local channels.
-
- * Queues now support a hint for member paused state. The hint uses the form
- 'Queue:{queue_name}_pause_{member_name}', where {queue_name} and {member_name}
- are the name of the queue and the name of the member to subscribe to,
- respectively. For example: exten => 8501,hint,Queue:sales_pause_mark.
- Members will show as In Use when paused.
+ two bridges together with local channels. The queue log will also now detect
+ externally initiated blind and attended transfers and record the transfer
+ status accordingly.
+
+ * When performing queue pause/unpause on an interface without specifying an
+ individual queue, the PAUSEALL/UNPAUSEALL event will only be logged if at
+ least one member of any queue exists for that interface.
+
+ * Added the 'queue_log_realtime_use_gmt' option to have timestamps in GMT
+ for realtime queue log entries.
ResetCDR
------------------
* The 'e' option has been deprecated. Use the CDR_PROP function to re-enable
CDRs when they were previously disabled on a channel.
+
* The 'w' and 'a' options have been removed. Dispatching CDRs to registered
backends occurs on an as-needed basis in order to preserve linkedid
propagation and other needed behavior.
+SayAlphaCase
+------------------
+ * A new application, this is similar to SayAlpha except that it supports
+ case sensitive playback of the specified characters. For example,
+ SayAlphaCase(u,aBc) will result in 'a uppercase b c'.
+
SetAMAFlags
------------------
- * This application is deprecated in favor of the CHANNEL function.
+ * This application is deprecated in favor of CHANNEL(amaflags).
+
+SendDTMF
+------------------
+ * The SendDTMF application will now accept 'W' as valid input. This will cause
+ the application to delay one second while streaming DTMF.
+
+Stasis
+------------------
+ * A new application in Asterisk 12, this hands control of the channel calling
+ the application over to an external system. Currently, external systems
+ manipulate channels in Stasis through the Asterisk RESTful Interface (ARI).
UserEvent
------------------
* UserEvent will now handle duplicate keys by overwriting the previous value
- assigned to the key. UserEvent invocations will also be distributed to any
- interested res_stasis applications.
-
-
-Build System
-------------------
- * Asterisk now optionally uses libxslt to improve XML documentation generation
- and maintainability. If libxslt is not available on the system, some XML
- documentation will be incomplete.
+ assigned to the key.
+
+ * In addition to AMI, UserEvent invocations will now be distributed to any
+ interested Stasis applications.
+
+VoiceMail
+------------------
+ * The voicemail.conf configuration file now has an 'alias' configuration
+ parameter for use with the Directory application. The voicemail realtime
+ database table schema has also been updated with an 'alias' column.
+
+
+Codecs
+------------------
+ * Pass through support has been added for both VP8 and Opus.
+
+ * Added format attribute negotiation for the Opus codec. Format attribute
+ negotiation is provided by the res_format_attr_opus module.
Core
------------------
- * Redirecting reasons can now be set to arbitrary strings. This means
- that the REDIRECTING dialplan function can be used to set the redirecting
- reason to any string. It also allows for custom strings to be read as the
- redirecting reason from SIP Diversion headers.
-
- * For DTMF blind and attended transfers, the channel variable TRANSFER_CONTEXT
- must be on the channel initiating the transfer to have any effect.
+ * Masquerades as an operation inside Asterisk have been effectively hidden
+ by the migration to the Bridging API. As such, many 'quirks' of Asterisk
+ no longer occur. This includes renaming of channels, "<ZOMBIE>" channels,
+ dropping of frame/audio hooks, and other internal implementation details
+ that users had to deal with. This fundamental change has large implications
+ throughout the changes documented for this version. For more information
+ about the new core architecture of Asterisk, please see the Asterisk wiki.
+
+ * Multiple parties in a bridge may now be transferred. If a participant in a
+ multi-party bridge initiates a blind transfer, a Local channel will be used
+ to execute the dialplan location that the transferer sent the parties to. If
+ a participant in a multi-party bridge initiates an attended transfer,
+ several options are possible. If the attended transfer results in a transfer
+ to an application, a Local channel is used. If the attended transfer results
+ in a transfer to another channel, the resulting channels will be merged into
+ a single bridge.
* The channel variable ATTENDED_TRANSFER_COMPLETE_SOUND is no longer channel
driver specific. If the channel variable is set on the transferrer channel,
@@ -161,36 +375,40 @@
* The channel variable BRIDGEPVTCALLID is only valid for two party bridges
and will contain a value if the BRIDGEPEER's channel driver supports it.
- * The channel variable DYNAMIC_PEERNAME is redundant with BRIDGEPEER and is
- removed. The more useful DYNAMIC_WHO_ACTIVATED gives the channel name that
- activated the dynamic feature.
-
- * The channel variables DYNAMIC_FEATURENAME and DYNAMIC_WHO_ACTIVATED are set
- only on the channel executing the dynamic feature. Executing a dynamic
- feature on the bridge peer in a multi-party bridge will execute it on all
- peers of the activating channel.
-
* A channel variable ATTENDEDTRANSFER is now set which indicates which channel
was responsible for an attended transfer in a similar fashion to
BLINDTRANSFER.
-
-Codecs
-------------------
- * Added pass through support for VP8 and Opus
-
- * Added format attribute negotiation for the Opus codec. Format attribute
- negotiation is provided by the res_format_attr_opus module.
-
+ * Modules using the Configuration Framework or Sorcery must have XML
+ configuration documentation. This configuration documentation is included
+ with the rest of Asterisk's XML documentation, and is accessible via CLI
+ commands. See the CLI changes for more information.
AMI (Asterisk Manager Interface)
------------------
- * The SIPshowpeer action will now include a 'SubscribeContext' field for a peer
- in its response if the peer has a subscribe context set.
-
- * The SIPqualifypeer action now acknowledges the request once it has established
- that the request is against a known peer. It also issues a new event,
- 'SIPQualifyPeerDone', once the qualify action has been completed.
+ * Major changes were made to both the syntax as well as the semantics of the
+ AMI protocol. In particular, AMI events have been substantially improved
+ in this version of Asterisk. For more information, please see the AMI
+ specification at https://wiki.asterisk.org/wiki/x/dAFRAQ
+
+ * AMI events that reference a particular channel or bridge will now always
+ contain a standard set of fields. When multiple channels or bridges are
+ referenced in an event, fields for at least some subset of the channels
+ and bridges in the event will be prefixed with a descriptive name to avoid
+ name collisions. See the AMI event documentation on the Asterisk wiki for
+ more information.
+
+ * The CLI command 'manager show commands' no longer truncates command names
+ longer than 15 characters and no longer shows authorization requirement
+ for commands. 'manager show command' now displays the privileges needed
+ for using a given manager command instead.
+
+ * The SIPshowpeer action will now include a 'SubscribeContext' field for a
+ peer in its response if the peer has a subscribe context set.
+
+ * The SIPqualifypeer action now acknowledges the request once it has
+ established that the request is against a known peer. It also issues a new
+ event, 'SIPQualifyPeerDone', once the qualify action has been completed.
* The PlayDTMF action now supports an optional 'Duration' parameter. This
specifies the duration of the digit to be played, in milliseconds.
@@ -198,13 +416,8 @@
* Added VoicemailRefresh action to allow an external entity to trigger mailbox
updates when changes occur instead of requiring the use of pollmailboxes.
- * CLI Command 'Manager Show Commands' no longer truncates command names longer
- than 15 characters and no longer shows authorization requirement for commands.
- 'Manager Show Command' now displays the privileges needed for using a given
- manager command instead.
-
- * Added new action "ControlPlayback". The ControlPlayback action allows an AMI
- client to manipulate audio currently being played back on a channel. The
+ * Added a new action 'ControlPlayback'. The ControlPlayback action allows an
+ AMI client to manipulate audio currently being played back on a channel. The
supported operations depend on the application being used to send audio to
the channel. When the audio playback was initiated using the ControlPlayback
application or CONTROL STREAM FILE AGI command, the audio can be paused,
@@ -258,71 +471,71 @@
* The NewPeerAccount AMI event is no longer raised. The NewAccountCode AMI
event always conveys the AMI event for a particular channel.
- * All "Reload" events have been consolidated into a single event type. This
+ * All 'Reload' events have been consolidated into a single event type. This
event will always contain a Module field specifying the name of the module
and a Status field denoting the result of the reload. All modules now issue
this event when being reloaded.
- * The "ModuleLoadReport" event has been removed. Most AMI connections would
+ * The 'ModuleLoadReport' event has been removed. Most AMI connections would
fail to receive this event due to being connected after modules have loaded.
AMI connections that want to know when Asterisk is ready should listen for
- the "FullyBooted" event.
+ the 'FullyBooted' event.
* app_fax now sends the same send fax/receive fax events as res_fax. The
- "FaxSent" event is now the "SendFAX" event, and the "FaxReceived" event is
- now the "ReceiveFAX" event.
-
- * The MusicOnHold event is now two events: MusicOnHoldStart and
- MusicOnHoldStop. The sub type field has been removed.
-
- * The JabberEvent event has been removed. It is not AMI's purpose to be a
+ 'FaxSent' event is now the 'SendFAX' event, and the 'FaxReceived' event is
+ now the 'ReceiveFAX' event.
+
+ * The 'MusicOnHold' event is now two events: 'MusicOnHoldStart' and
+ 'MusicOnHoldStop'. The sub type field has been removed.
+
+ * The 'JabberEvent' event has been removed. It is not AMI's purpose to be a
carrier for another protocol.
- * The Bridge Manager action's Playtone header now accepts more fine-grained
- options. "Channel1" and "Channel2" may be specified in order to play a tone
- to the specific channel. "Both" may be specified to play a tone to both
- channels. The old "yes" option is still accepted as a way of playing the
+ * The Bridge Manager action's 'Playtone' header now accepts more fine-grained
+ options. 'Channel1' and 'Channel2' may be specified in order to play a tone
+ to the specific channel. 'Both' may be specified to play a tone to both
+ channels. The old 'yes' option is still accepted as a way of playing the
tone to Channel2 only.
* The AMI 'Status' response event to the AMI Status action replaces the
- BridgedChannel and BridgedUniqueid headers with the BridgeID header to
+ 'BridgedChannel' and 'BridgedUniqueid' headers with the 'BridgeID' header to
indicate what bridge the channel is currently in.
* The AMI 'Hold' event has been moved out of individual channel drivers, into
- core, and is now two events: Hold and Unhold. The status field has been
+ core, and is now two events: 'Hold' and 'Unhold'. The status field has been
removed.
* The AMI events in app_queue have been made more consistent with each other.
Events that reference channels (QueueCaller* and Agent*) will show
- information about each channel. The (infamous) "Join" and "Leave" AMI
- events have been changed to "QueueCallerJoin" and "QueueCallerLeave".
-
- * The MCID AMI event now publishes a channel snapshot when available and
+ information about each channel. The (infamous) 'Join' and 'Leave' AMI
+ events have been changed to 'QueueCallerJoin' and 'QueueCallerLeave'.
+
+ * The 'MCID' AMI event now publishes a channel snapshot when available and
its non-channel-snapshot parameters now use either the "MCallerID" or
- "MConnectedID" prefixes with Subaddr*, Name*, and Num* suffixes instead
- of "CallerID" and "ConnectedID" to avoid confusion with similarly named
+ 'MConnectedID' prefixes with Subaddr*, Name*, and Num* suffixes instead
+ of 'CallerID' and 'ConnectedID' to avoid confusion with similarly named
parameters in the channel snapshot.
- * The AMI events "Agentlogin" and "Agentlogoff" have been renamed
- "AgentLogin" and "AgentLogoff" respectively.
-
- * The "Channel" key used in the "AlarmClear", "Alarm", and "DNDState" has been
+ * The AMI events 'Agentlogin' and 'Agentlogoff' have been renamed
+ 'AgentLogin' and 'AgentLogoff' respectively.
+
+ * The 'Channel' key used in the 'AlarmClear', 'Alarm', and 'DNDState' has been
renamed "DAHDIChannel" since it does not convey an Asterisk channel name.
- * "ChannelUpdate" events have been removed.
-
- * AMI events now contain a SystemName field, if available.
+ * 'ChannelUpdate' events have been removed.
+
+ * All AMI events now contain a 'SystemName' field, if available.
* Local channel optimization is now conveyed in two events:
- LocalOptimizationBegin and LocalOptimizationEnd. The Begin event is sent
+ 'LocalOptimizationBegin' and 'LocalOptimizationEnd'. The Begin event is sent
when the Local channel driver begins attempting to optimize itself out of
the media path; the End event is sent after the channel halves have
successfully optimized themselves out of the media path.
- * Local channel information in events is now prefixed with "LocalOne" and
- "LocalTwo". This replaces the suffix of "1" and "2" for the two halves of
- the Local channel. This affects the LocalBridge, LocalOptimizationBegin,
- and LocalOptimizationEnd events.
+ * Local channel information in events is now prefixed with 'LocalOne' and
+ 'LocalTwo'. This replaces the suffix of '1' and '2' for the two halves of
+ the Local channel. This affects the 'LocalBridge', 'LocalOptimizationBegin',
+ and 'LocalOptimizationEnd' events.
* The option 'allowmultiplelogin' can now be set or overriden in a particular
account. When set in the general context, it will act as the default
@@ -336,25 +549,20 @@
occur in the Briding API, and are conveyed now through BridgeCreate,
BridgeEnter, and BridgeLeave events.
-
-AGI (Asterisk Gateway Interface)
-------------------
- * The manager event AGIExec has been split into AGIExecStart and AGIExecEnd.
-
- * The manager event AsyncAGI has been split into AsyncAGIStart, AsyncAGIExec,
- and AsyncAGIEnd.
-
- * The CONTROL STREAM FILE command now accepts an offsetms parameter. This
- will start the playback of the audio at the position specified. It will
- also return the final position of the file in 'endpos'.
-
- * The SAY ALPHA command now accepts an additional parameter to control
- whether it specifies the case of uppercase, lowercase, or all letters to
- provide functionality similar to SayAlphaCase.
+ * The 'RTCPSent'/'RTCPReceived' events have been significantly modified from
+ previous versions. They now report all SR/RR packets sent/received, and
+ have been restructured to better reflect the data sent in a SR/RR. In
+ particular, the event structure now supports multiple report blocks.
+
+ * Added 'BlindTransfer' and 'AttendedTransfer' events. These events are
+ raised when a blind transfer/attended transfer completes successfully.
+ They contain information about the transfer that just completed, including
+ the location of the transfered channel.
CDR (Call Detail Records)
------------------
- * Significant changes have been made to the behavior of CDRs. For a full
+ * Significant changes have been made to the behavior of CDRs. The CDR engine
+ was effectively rewritten and built on the Stasis message bus. For a full
definition of CDR behavior in Asterisk 12, please read the specification
on the Asterisk wiki (wiki.asterisk.org).
@@ -371,16 +579,34 @@
included in the resulting CDR. If both parties have the same variable, only
the Party A value is provided.
+ * Added a new option to cdr.conf, 'debug'. When enabled, significantly more
+ information regarding the CDR engine is logged as verbose messages. This
+ option should only be used if the behavior of the CDR engine needs to be
+ debugged.
+
+ * Added CLI command 'cdr set debug {on|off}'. This toggles the 'debug' setting
+ normally configured in cdr.conf.
+
+ * Added CLI command 'cdr show active {channel}'. When {channel} is not
+ specified, this command provides a summary of the channels with CDR
+ information and their statistics. When {channel} is specified, it shows
+ detailed information about all records associated with {channel}.
+
CEL (Channel Event Logging)
------------------
+ * CEL has undergone significant rework in Asterisk 12, and is now built on the
+ Stasis message bus. Please see the specification for CEL on the Asterisk
+ wiki at https://wiki.asterisk.org/wiki/x/4ICLAQ for more detailed
+ information.
+
* The 'extra' field of all CEL events that use it now consists of a JSON blob
with key/value pairs which are defined in the Asterisk 12 CEL documentation.
- * AST_CEL_BLINDTRANSFER events now report the transferee bridge unique
+ * BLINDTRANSFER events now report the transferee bridge unique
identifier, extension, and context in a JSON blob as the extra string
instead of the transferee channel name as the peer.
- * AST_CEL_ATTENDEDTRANSFER events now report the peer as NULL and additional
+ * ATTENDEDTRANSFER events now report the peer as NULL and additional
information in the 'extra' string as a JSON blob. For transfers that occur
between two bridged channels, the 'extra' JSON blob contains the primary
bridge unique identifier, the secondary channel name, and the secondary
@@ -388,12 +614,84 @@
and a channel running an app, the 'extra' JSON blob contains the primary
bridge unique identifier, the secondary channel name, and the app name.
- * AST_CEL_LOCAL_OPTIMIZE events have been added to convey local channel
+ * LOCAL_OPTIMIZE events have been added to convey local channel
optimizations with the record occurring for the semi-one channel and
the semi-two channel name in the peer field.
+ * BRIDGE_START, BRIDGE_END, BRIDGE_UPDATE, 3WAY_START, 3WAY_END, CONF_ENTER,
+ CONF_EXIT, CONF_START, and CONF_END events have all been removed. These
+ events have been replaced by BRIDGE_ENTER/BRIDGE_EXIT. The BRIDGE_ENTER
+ and BRIDGE_EXIT events are raised when a channel enters/exits any bridge,
+ regardless of whether or not that bridge happens to contain multiple
+ parties.
+
+CLI
+-------------------
+ * When compiled with '--enable-dev-mode', the astobj2 library will now add
+ several CLI commands that allow for inspection of ao2 containers that
+ register themselves with astobj2. The CLI commands are 'astobj2 container
+ dump', 'astobj2 container stats', and 'astobj2 container check'.
+
+ * Added specific CLI commands for bridge inspection. This includes 'bridge
+ show all', which lists all bridges in the system, and 'bridge show {id}',
+ which provides specific information about a bridge.
+
+ * Added CLI command 'bridge destroy'. This will destroy the specified bridge,
+ ejecting the channels currently in the bridge. If the channels cannot
+ continue in the dialplan or application that put them in the bridge, they
+ will be hung up.
+
+ * Added command 'bridge kick'. This will eject a single channel from a bridge.
+
+ * Added commands to inspect and manipulate the registered bridge technologies.
+ This include 'bridge technology show', which lists the registered bridge
+ technologies, as well as 'bridge technology {suspend|unsuspend} {tech}',
+ which controls whether or not a registered bridge technology can be used
+ during smart bridge operations. If a technology is suspended, it will not
+ be used when a bridge technology is picked for channels; when unsuspended,
+ it can be used again.
+
+ * The command 'config show help {module} {type} {option}' will show
+ configuration documentation for modules with XML configuration
+ documentation. When {module}, {type}, and {option} are omitted, a listing
+ of all modules with registered documentation is displayed. When {module}
+ is specified, a listing of all configuration types for that module is
+ displayed, along with their synopsis. When {module} and {type} are
+ specified, a listing of all configuration options for that type are
+ displayed along with their synopsis. When {module}, {type}, and {option}
+ are specified, detailed information for that configuration option is
+ displayed.
+
+ * Added 'core show sounds' and 'core show sound' CLI commands. These display
+ a listing of all installed media sounds available on the system and
+ detailed information about a sound, respectively.
+
+ * 'xmldoc dump' has been added. This CLI command will dump the XML
+ documentation DOM as a string to the specified file. The Asterisk core
+ will populate certain XML elements pulled from the source files with
+ additional run-time information; this command lets a user produce the
+ XML documentation with all information.
+
Features
-------------------
+ * Parking has been pulled from core and placed into a separate module called
+ res_parking. See Parking changes below for more details. Configuration for
+ parking should now be performed in res_parking.conf. Configuration for
+ parking in features.conf is now unsupported.
+
+ * Core attended transfers now have several new options. While performing an
+ attended transfer, the transferer now has the following options:
+ - *1 - cancel the attended transfer (configurable via atxferabort)
+ - *2 - complete the attended transfer, dropping out of the call
+ (configurable via atxfercomplete)
+ - *3 - complete the attended transfer, but stay in the call. This will turn
+ the call into a multi-party bridge (configurable via atxferthreeway)
+ - *4 - swap to the other party. Once an attended transfer has begun, this
+ options may be used multiple times (configurable via atxferswap)
+
+ * For DTMF blind and attended transfers, the channel variable TRANSFER_CONTEXT
+ must be on the channel initiating the transfer to have any effect.
+
* The BRIDGE_FEATURES channel variable would previously only set features for
the calling party and would set this feature regardless of whether the
feature was in caps or in lowercase. Use of a caps feature for a letter
@@ -402,8 +700,14 @@
* Add support for automixmon to the BRIDGE_FEATURES channel variable.
- * Parking has been pulled from core and placed into a separate module called
- res_parking. See Parking changes below for more details.
+ * The channel variable DYNAMIC_PEERNAME is redundant with BRIDGEPEER and is
+ removed. The more useful DYNAMIC_WHO_ACTIVATED gives the channel name that
+ activated the dynamic feature.
+
+ * The channel variables DYNAMIC_FEATURENAME and DYNAMIC_WHO_ACTIVATED are set
+ only on the channel executing the dynamic feature. Executing a dynamic
+ feature on the bridge peer in a multi-party bridge will execute it on all
+ peers of the activating channel.
* You can now have the settings for a channel updated using the FEATURE()
and FEATUREMAP() functions inherited to child channels by setting
@@ -417,90 +721,16 @@
allowssetting a failure sound for a user tries to invoke a recording feature
such as automon or automixmon and it fails.
+ * It is no longer necessary (or possible) to define the ATXFER_NULL_TECH in
+ features.c for atxferdropcall=no to work properly. This option now just
+ works.
+
Logging
-------------------
- * When performing queue pause/unpause on an interface without specifying an
- individual queue, the PAUSEALL/UNPAUSEALL event will only be logged if at
- least one member of any queue exists for that interface.
-
- * Added the 'queue_log_realtime_use_gmt' option to have timestamps in GMT
- for realtime queue log entries.
-
-Parking
--------------------
- * Parking is now implemented as a module instead of as core functionality.
- The preferred way to configure parking is now through res_parking.conf while
- configuration through features.conf is not currently supported.
-
- * res_parking uses the configuration framework. If an invalid configuration is
- supplied, res_parking will fail to load or fail to reload. Previously parking
- lots that were misconfigured would generally be accepted with certain
[... 463 lines stripped ...]
More information about the asterisk-commits
mailing list