<html>
<head>
<meta name="viewport" content="width=device-width" />
<base href="https://wiki.asterisk.org/wiki" />
<style type="text/css">
body, #email-content, #email-content-inner { font-family: Arial,FreeSans,Helvetica,sans-serif; }
body, p, blockquote, pre, code, td, th, li, dt, dd { font-size: 13px; }
small { font-size: 11px; }
body { width:100% !important; -webkit-font-smoothing: antialiased; }
body,
#email-wrapper { background-color: #f0f0f0; }
#email-wrapper-inner { padding: 20px; text-align: center; }
#email-content-inner { background-color: #fff; border: 1px solid #bbb; color: $menuTxtColour; padding:20px; text-align:left; }
#email-wrapper-inner > table { width: 100%; }
#email-wrapper-inner.thin > table { margin: 0 auto; width: 50%; }
#email-footer { padding: 0 16px 32px 16px; margin: 0; }
.email-indent { margin: 8px 0 16px 0; }
.email-comment { margin: 0 0 0 56px; }
.email-comment.removed { background-color: #ffe7e7; border: 1px solid #df9898; padding: 0 8px;}
#email-title-avatar { text-align: left; vertical-align: top; width: 48px; padding-right: 8px; }
#email-title-flavor { margin: 0; padding: 0 0 4px 0; }
#email-title-heading { font-size: 16px; line-height: 20px; min-height: 20px; margin: 0; padding: 0; }
#email-title .icon { border: 0; padding: 0 5px 0 0; text-align: left; vertical-align: middle; }
#email-actions { border-top: 1px solid #bbb; color: #505050; margin: 8px 0 0 0; padding: 0; }
#email-actions td { padding-top: 8px; }
#email-actions .left { max-width: 45%; text-align: left; }
#email-actions .right { text-align: right; }
.email-reply-divider { border-top: 1px solid #bbb; color: #505050; margin: 32px 0 8px 0; padding: 8px 0; }
.email-section-title { border-bottom: 1px solid #bbb; margin: 8px 0; padding: 8px 0 0 0; }
.email-metadata { color: #505050; }
a { color: #326ca6; text-decoration: none; }
a:hover { color: #336ca6; text-decoration: underline; }
a:active {color: #326ca6; }
a.email-footer-link { color: #505050; font-size: 11px; }
.email-item-list { list-style: none; margin: 4px 0; padding-left: 0; }
.email-item-list li { list-style: none; margin: 0; padding: 4px 0; }
.email-list-divider { color: #505050; padding: 0 0.35em; }
.email-operation-icon { padding-right: 5px; }
.avatar { -ms-interpolation-mode: bicubic; border-radius: 3px;}
.avatar-link { margin: 2px; }
.tableview th { border-bottom: 1px solid #69C; font-weight: bold; text-align: left; }
.tableview td { border-bottom: 1px solid #bbbbbb; text-align: left; padding: 4px 16px 4px 0; }
.aui-message { margin: 1em 0; padding: 8px; }
.aui-message.info { background-color: #e0f0ff; border: 1px solid #9eb6d4; }
.aui-message.success { background-color: #ddfade; border: 1px solid #93c49f; }
.aui-message.error,
.aui-message.removed { background-color: #ffe7e7; border: 1px solid #df9898; color: #000; }
.call-to-action-table { margin: 10px 1px 1px 1px;}
.call-to-cancel-container, .call-to-action-container { padding: 5px 20px; }
.call-to-cancel-container { border: 1px solid #aaa; background-color: #eee; border-radius: 3px; }
.call-to-cancel-container a.call-to-cancel-button { background-color: #eee; font-size: 14px; line-height: 1; padding: 0; margin: 0; color: #666; font-family: sans-serif;}
.call-to-action-container { border: 1px solid #486582; background-color: #3068A2; border-radius: 3px; padding: 4px 10px; }
.call-to-action-container a.call-to-action-button { background-color: #3068A2; font-size: 14px; line-height: 1; padding: 0; margin: 0; color: #fff; font-weight: bold; font-family: sans-serif; }
/** The span around the inline task checkbox image */
.diff-inline-task-overlay {
display: inline-block;
text-align: center;
height: 1.5em;
padding: 5px 0px 1px 5px;
margin-right: 5px;
/** Unfortunately, the negative margin-left is stripped out in gmail */
margin-left: -5px;
}
@media handheld, only screen and (max-device-width: 480px) {
div, a, p, td, th, li, dt, dd { -webkit-text-size-adjust: auto; }
small, small a { -webkit-text-size-adjust: 90%; }
td[id=email-wrapper-inner] { padding: 2px !important; }
td[id=email-content-inner] { padding: 8px !important; }
td[id="email-wrapper-inner"][class="thin"] > table { text-align: left !important; width: 100% !important; }
td[id=email-footer] { padding: 8px 12px !important; }
div[class=email-indent] { margin: 8px 0px !important; }
div[class=email-comment] { margin: 0 !important; }
p[id=email-title-flavor] a { display: block; } /* puts the username and the action on separate lines */
p[id=email-permalink] { padding: 4px 0 0 0 !important; }
table[id=email-actions] td { padding-top: 0 !important; }
table[id=email-actions] td.right { text-align: right !important; }
table[id=email-actions] .email-list-item { display: block; margin: 1em 0 !important; word-wrap: normal !important; }
span[class=email-list-divider] { display: none; }
}
</style>
</head>
<body style="font-family: Arial, FreeSans, Helvetica, sans-serif; font-size: 13px; width: 100%; -webkit-font-smoothing: antialiased; background-color: #f0f0f0">
<table id="email-wrapper" width="100%" cellspacing="0" cellpadding="0" border="0" style="background-color: #f0f0f0">
<tbody>
<tr valign="middle">
<td id="email-wrapper-inner" style="font-size: 13px; padding: 20px; text-align: center">
<table id="email-content" cellspacing="0" cellpadding="0" border="0" style="font-family: Arial, FreeSans, Helvetica, sans-serif; width: 100%">
<tbody>
<tr valign="top">
<td id="email-content-inner" align="left" style="font-family: Arial, FreeSans, Helvetica, sans-serif; font-size: 13px; background-color: #fff; border: 1px solid #bbb; padding: 20px; text-align: left">
<table id="email-title" cellpadding="0" cellspacing="0" border="0" width="100%">
<tbody>
<tr>
<td id="email-title-avatar" rowspan="2" style="font-size: 13px; text-align: left; vertical-align: top; width: 48px; padding-right: 8px"> <img class="avatar" src="cid:avatar_ce51dcf276530e4a4b00548e2a6d0905" border="0" height="48" width="48" style="-ms-interpolation-mode: bicubic; border-radius: 3px" /> </td>
<td valign="top" style="font-size: 13px">
<div id="email-title-flavor" class="email-metadata" style="margin: 0; padding: 0 0 4px 0; color: #505050">
<a href=" https://wiki.asterisk.org/wiki/display/~mjordan " style="color:#326ca6;text-decoration:none;; color: #326ca6; text-decoration: none">Matt Jordan</a> edited the page:
</div> </td>
</tr>
<tr>
<td valign="top" style="font-size: 13px"> <h2 id="email-title-heading" style="font-size: 16px; line-height: 20px; min-height: 20px; margin: 0; padding: 0"> <a href="https://wiki.asterisk.org/wiki/display/AST/New+in+12" style="color: #326ca6; text-decoration: none"> <img class="icon" src="cid:page-icon" alt="" style="border: 0; padding: 0 5px 0 0; text-align: left; vertical-align: middle" /> <strong style="font-size:16px;line-height:20px;vertical-align:top;">New in 12</strong> </a> </h2> </td>
</tr>
</tbody>
</table>
<div class="email-indent" style="margin: 8px 0 16px 0">
<div class="email-diff">
<div id="page-diffs" class="wiki-content">
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<p class="diff-block-target" style="font-size: 13px">It is <strong>highly</strong> recommended that anyone migrating to Asterisk 12 read the information regarding its release both in the <a href="http://svn.asterisk.org/svn/asterisk/branches/12/CHANGES" class="external-link" rel="nofollow" style="color: #326ca6; text-decoration: none"><span class="diff-html-changed" id="changed-diff-0" style="background-color: #d6f0ff;">CHANGES</span></a><span class="diff-html-changed" style="background-color: #d6f0ff;"> </span>files and in the <span class="diff-html-removed" id="removed-diff-0" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;">accompanying UPGRADE</span><span class="diff-html-added" id="added-diff-0" style="font-size: 100%; background-color: #ddfade;">accompanying </span><a href="http://svn.asterisk.org/svn/asterisk/branches/12/UPGRADE.txt" class="external-link" rel="nofollow" style="color: #326ca6; text-decoration: none"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">UPGRADE</span><span class="diff-html-changed" id="changed-diff-1" style="background-color: #d6f0ff;">.txt</span></a><span class="diff-html-changed" style="background-color: #d6f0ff;"> </span>file.</p>
<h1 id="Newin12-BuildSystem" class="diff-block-context"> <span style="line-height: 1.25;">Build System</span> </h1>
<ul class="diff-block-context">
<li style="font-size: 13px">Added build option <code style="font-size: 13px">DISABLE_INLINE</code>. This option can be used to work around a bug in gcc. For more information, see <a href="http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47816" class="external-link" rel="nofollow" style="color: #326ca6; text-decoration: none">http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47816</a> </li>
<li style="font-size: 13px">Removed the <code style="font-size: 13px">CHANNEL_TRACE</code> development mode build option. Certain aspects of the <code style="font-size: 13px">CHANNEL_TRACE</code> build option were incompatible with the new bridging architecture.</li>
<li style="font-size: 13px">Asterisk now optionally uses <code style="font-size: 13px">libxslt</code> to improve XML documentation generation and maintainability. If libxslt is not available on the system, some XML documentation will be incomplete.</li>
<li style="font-size: 13px">Asterisk now depends on <code style="font-size: 13px">libjansson</code>. If a package of <code style="font-size: 13px">libjansson</code> is not available on your distro, please see <a href="http://www.digip.org/jansson/" class="external-link" rel="nofollow" style="color: #326ca6; text-decoration: none">http://www.digip.org/jansson/</a>.</li>
<li style="font-size: 13px">Asterisk now depends on <code style="font-size: 13px">libuuid</code> and, optionally, <code style="font-size: 13px">uriparser</code>. It is recommended that you install <code style="font-size: 13px">uriparser</code>, even if it is optional.</li>
<li style="font-size: 13px">The new SIP stack and channel driver currently use a particular version of PJSIP. Please see <a href="https://wiki.asterisk.org/wiki/x/J4GLAQ" rel="nofollow" style="color: #326ca6; text-decoration: none">https://wiki.asterisk.org/wiki/x/J4GLAQ</a> for more information on configuring and installing PJSIP for usage with Asterisk.</li>
</ul>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<ul class="diff-block-target">
<li style="font-size: 13px"> <span style="line-height: 1.5;">Along with <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">AgentRequest</a>, this application has been modified to be a </span>replacement for <code style="font-size: 13px">chan_agent</code>. 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 <code style="font-size: 13px">app_agent_pool</code> module. See <a href="#Newin12-channels_chan_agent" style="color: #326ca6; text-decoration: none"><span class="diff-html-changed" id="changed-diff-2" style="background-color: #d6f0ff;">chan_agent</span></a><span class="diff-html-changed" style="background-color: #d6f0ff;"> </span>and <a href="/wiki/display/AST/New+in+12" style="color: #326ca6; text-decoration: none">AgentRequest</a> for more information.</li>
<li style="font-size: 13px">This application no longer performs agent authentication. If authentication is desired, the dialplan needs to perform this function using the <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">Authenticate</a> or <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">VMAuthenticate</a> application or through an AGI script before running AgentLogin.</li>
<li style="font-size: 13px">If this application is called and the agent is already logged in, the dialplan will continue exection with the <code style="font-size: 13px">AGENT_STATUS</code> channel variable set to <code style="font-size: 13px">ALREADY_LOGGED_IN</code>.</li>
<li style="font-size: 13px">The <em><a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">agents.conf</a></em> 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.</li>
<li style="font-size: 13px">A number of parameters from <em><a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">agents.conf</a></em> have been removed. This includes:
<ul>
<li style="font-size: 13px"> <code style="font-size: 13px">maxloginretries</code> </li>
<li style="font-size: 13px"> <code style="font-size: 13px">autologoffunavail</code> </li>
<li style="font-size: 13px"> <code style="font-size: 13px">updatecdr</code> </li>
<li style="font-size: 13px"> <code style="font-size: 13px">goodbye</code> </li>
<li style="font-size: 13px"> <code style="font-size: 13px">group</code> </li>
<li style="font-size: 13px"> <code style="font-size: 13px">recordformat</code> </li>
<li style="font-size: 13px"> <code style="font-size: 13px">urlprefix</code> </li>
<li style="font-size: 13px"> <code style="font-size: 13px">savecallsin</code> </li>
</ul>These options were obsoleted by the move from a channel driver model to the bridging/application model provided by <code style="font-size: 13px">app_agent_pool</code>.</li>
</ul>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<ul class="diff-block-target">
<li style="font-size: 13px">The channel variable <code style="font-size: 13px">CPLAYBACKSTATUS</code> may now return the value <code style="font-size: 13px">REMOTESTOPPED</code>. This occurs when playback is stopped by a remote interface, such as AMI. See the AMI action <a href="#Newin12-ami_controlplayback" style="color: #326ca6; text-decoration: none"><span class="diff-html-changed" id="changed-diff-3" style="background-color: #d6f0ff;">ControlPlayback</span></a><span class="diff-html-changed" style="background-color: #d6f0ff;"> </span>for more information.</li>
</ul>
<h2 id="Newin12-Directory" class="diff-block-context"> <span style="line-height: 1.4285715;"><a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">Directory</a></span> </h2>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<ul class="diff-block-target">
<li style="font-size: 13px"> <span style="line-height: 1.4285715;"> </span><span style="line-height: 1.4285715;">The <code style="font-size: 13px">app_parkandannounce</code> module has been removed. The application </span><span style="line-height: 1.4285715;">ParkAndAnnounce is now provided by the <code style="font-size: 13px">res_parking</code> module. See the </span><span style="line-height: 1.4285715;"><a href="#Newin12-res_parking" style="color: #326ca6; text-decoration: none"><span class="diff-html-changed" id="changed-diff-4" style="background-color: #d6f0ff;">res_parking</span></a><span class="diff-html-changed" style="background-color: #d6f0ff;"> </span>changes for more information.</span> </li>
</ul>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<ul class="diff-block-target">
<li style="font-size: 13px">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.</li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">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.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">The channel variable <code style="font-size: 13px">ATTENDED_TRANSFER_COMPLETE_SOUND</code> is no longer channel driver specific. If the channel variable is set on the transferrer channel, the sound will be played to the target of an attended transfer.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">The channel variable <code style="font-size: 13px">BRIDGEPEER</code> becomes a comma separated list of peers in </span><span style="line-height: 1.4285715;">a multi-party bridge. The <code style="font-size: 13px">BRIDGEPEER</code> value can have a maximum of 10 peers </span><span style="line-height: 1.4285715;">listed. Any more peers in the bridge will not be included in the list. {{</span><span style="line-height: 1.4285715;">BRIDGEPEER}} is not valid in holding bridges like parking since those channels </span><span style="line-height: 1.4285715;">do not talk to each other even though they are in a bridge.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;"> </span><span style="line-height: 1.4285715;">The channel variable <code style="font-size: 13px">BRIDGEPVTCALLID</code> is only valid for two party bridges </span><span style="line-height: 1.4285715;">and will contain a value if the <code style="font-size: 13px">BRIDGEPEER</code>'s channel driver supports it.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;"> </span><span style="line-height: 1.4285715;">A channel variable <code style="font-size: 13px">ATTENDEDTRANSFER</code> is now set which indicates which channel </span><span style="line-height: 1.4285715;">was responsible for an attended transfer in a similar fashion to <code style="font-size: 13px">BLINDTRANSFER</code>.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;"> </span><span style="line-height: 1.4285715;">Modules using the Configuration Framework or Sorcery must have XML </span><span style="line-height: 1.4285715;">configuration documentation. This configuration documentation is included </span><span style="line-height: 1.4285715;">with the rest of Asterisk's XML documentation, and is accessible via CLI </span><span style="line-height: 1.4285715;">commands. See the<a href="#Newin12-CLI" style="color: #326ca6; text-decoration: none"><span class="diff-html-changed" style="background-color: #d6f0ff;"> </span><span class="diff-html-changed" id="changed-diff-5" style="background-color: #d6f0ff;">CLI changes</span></a><span class="diff-html-changed" style="background-color: #d6f0ff;"> </span>for more information.</span> </li>
</ul>
<h2 id="Newin12-AMI%28AsteriskManagerInterface%29" class="diff-block-context"> <span style="line-height: 1.4285715;"> </span><span style="line-height: 1.4285715;">AMI (Asterisk Manager Interface)</span> </h2>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<ul class="diff-block-target">
<li style="font-size: 13px">Added a new action <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">ControlPlayback</a>. 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 <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">ControlPlayback</a> application or <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">CONTROL STREAM FILE</a> AGI command, the audio can be paused, stopped, restarted, reversed, or skipped forward. When initiated by other mechanisms (such as the <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">Playback</a> application), the audio can be stopped, reversed, or skipped forward.</li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">Channel related events now contain a snapshot of channel state, adding new </span><span style="line-height: 1.4285715;">fields to many of these events.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">The AMI event <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">Newexten</a> field <em>Extension</em> is deprecated, and may be removed </span><span style="line-height: 1.4285715;">in a future release. Please use the common <em>Exten</em> field instead.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">The AMI event <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">UserEvent</a> from <code style="font-size: 13px">app_userevent</code> now contains the channel state </span><span style="line-height: 1.4285715;">fields. The channel state fields will come before the body fields.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">The AMI events <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">ParkedCall</a>, <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">ParkedCallTimeOut</a>, <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">ParkedCallGiveUp</a>, and </span><span style="line-height: 1.4285715;"><a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">UnParkedCall</a> have changed significantly in the new <a href="#Newin12-res_parking" style="color: #326ca6; text-decoration: none"><code style="font-size: 13px"><span class="diff-html-changed" id="changed-diff-6" style="background-color: #d6f0ff;">res_parking</span></code><span class="diff-html-changed" style="background-color: #d6f0ff;"> </span></a> module.</span>
<ul>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">The <em>Channel</em> and <em>From</em> headers are gone.</span>
<ul>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">For the channel that was parked </span><span style="line-height: 1.4285715;">or is coming out of parking, a <em>Parkee</em> channel snapshot is issued and it </span><span style="line-height: 1.4285715;">has a number of fields associated with it. The old <em>Channel</em> header relayed </span><span style="line-height: 1.4285715;">the same data as the new <em>ParkeeChannel</em> header.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">The <em>From</em> field was ambiguous and changed meaning depending on the event. </span><span style="line-height: 1.4285715;">For most of these, it was the name of the channel that parked the call </span><span style="line-height: 1.4285715;">(the <em>Parker</em>).</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">There is no longer a header that provides this channel name, </span><span style="line-height: 1.4285715;">however the <em>ParkerDialString</em> will contain a dialstring to redial the </span><span style="line-height: 1.4285715;">device that parked the call.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">On <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">UnParkedCall</a> events, the <em>From</em> header would instead represent the channel responsible for retrieving the parkee. It receives a channel snapshot labeled <em>Retriever</em>. The <em>From</em> field is is replaced with <em>RetrieverChannel</em>.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">Lastly, the <em>Exten</em> field has been replaced with <em>ParkingSpace</em>.</span> </li>
</ul> </li>
<li style="font-size: 13px">The AMI event Parkinglot (response to <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">Parkinglots</a> command) in a similar fashion has changed the field names <em>StartExten</em> and <em>StopExten</em> to <em>StartSpace</em> and <em>StopSpace</em> respectively.</li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">The deprecated use of | (pipe) as a separator in the <code style="font-size: 13px">channelvars</code> setting in <em>manager.conf</em> has been removed.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">Channel Variables conveyed with a channel no longer contain the name of the channel as part of the key field, i.e., <code style="font-size: 13px">ChanVariable(SIP/foo): bar=baz</code> is now <code style="font-size: 13px">ChanVariable: bar=baz</code>. When multiple channels are present in a single AMI event, the various <em>ChanVariable</em> fields will contain a prefix that specifies which channel they correspond to.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">The NewPeerAccount AMI event is no longer raised. The <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">NewAccountCode</a> AMI event always conveys the AMI event for a particular channel.</span> </li>
<li style="font-size: 13px">All <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">Reload</a> events have been consolidated into a single event type. This event will always contain a <em>Module</em> field specifying the name of the module and a <em>Status</em> field denoting the result of the reload. All modules now issue this event when being reloaded.</li>
<li style="font-size: 13px">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 <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">FullyBooted</a> event.</li>
<li style="font-size: 13px"> <code style="font-size: 13px">app_fax</code> now sends the same send fax/receive fax events as <code style="font-size: 13px">res_fax</code>. The FaxSent event is now the <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">SendFAX</a> event, and the FaxReceived event is now the <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">ReceiveFAX</a> event.</li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">The MusicOnHold event is now two events: <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">MusicOnHoldStart</a> and </span><span style="line-height: 1.4285715;"><a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">MusicOnHoldStop</a>. The sub type field has been removed.</span> </li>
<li style="font-size: 13px">The JabberEvent event has been removed. It is not AMI's purpose to be a carrier for another protocol.</li>
<li style="font-size: 13px">The <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">Bridge</a> Manager action's <em>Playtone</em> header now accepts more fine-grained options. <code style="font-size: 13px">Channel1</code> and <code style="font-size: 13px">Channel2</code> may be specified in order to play a tone to the specific channel. <code style="font-size: 13px">Both</code> may be specified to play a tone to both</li>
<li style="font-size: 13px">channels. The old <code style="font-size: 13px">yes</code> option is still accepted as a way of playing the tone to <code style="font-size: 13px">Channel2</code> only.</li>
<li style="font-size: 13px">The AMI <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">Status</a> response event to the AMI <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">Status</a> action replaces the <em>BridgedChannel</em> and <em>BridgedUniqueid</em> headers with the <em>BridgeID</em> header to indicate what bridge the channel is currently in.</li>
<li style="font-size: 13px">The AMI Hold event has been moved out of individual channel drivers, into core, and is now two events: <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">Hold</a> and <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">Unhold</a>. The status field has been removed.</li>
<li style="font-size: 13px">The AMI events in <code style="font-size: 13px">app_queue</code> 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 <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">QueueCallerJoin</a> and <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">QueueCallerLeave</a>.</li>
<li style="font-size: 13px">The <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">MCID</a> AMI event now publishes a channel snapshot when available and its non-channel-snapshot parameters now use either the <em>MCallerID</em> or <em>MConnectedID</em> prefixes with Subaddr*, Name*, and Num* suffixes instead of <em>CallerID</em> and <em>ConnectedID</em> to avoid confusion with similarly named parameters in the channel snapshot.</li>
<li style="font-size: 13px">The AMI events Agentlogin and Agentlogoff have been renamed <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">AgentLogin</a> and <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">AgentLogoff</a> respectively.</li>
<li style="font-size: 13px">The <em>Channel</em> key used in the <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">AlarmClear</a>, <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">Alarm</a>, and <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">DNDState</a> has been renamed <em>DAHDIChannel</em> since it does not convey an Asterisk channel name.</li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">ChannelUpdate events have been removed.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">All AMI events now contain a <em>SystemName</em> field, if available.</span> </li>
<li style="font-size: 13px">Local channel optimization is now conveyed in two events: <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">LocalOptimizationBegin</a> and <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">LocalOptimizationEnd</a>. 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.</li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">Local channel information in events is now prefixed with <em>LocalOne</em> and <em>LocalTwo.</em></span><span style="line-height: 1.4285715;"> This replaces the suffix of '1' and '2' for the two halves of </span><span style="line-height: 1.4285715;">the Local channel. This affects the <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">LocalBridge</a>, <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">LocalOptimizationBegin</a>, </span><span style="line-height: 1.4285715;">and <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">LocalOptimizationEnd</a> events.</span> </li>
<li style="font-size: 13px">The option <code style="font-size: 13px">allowmultiplelogin</code> can now be set or overriden in a particular account. When set in the general context, it will act as the default setting for defined accounts.</li>
<li style="font-size: 13px">The BridgeAction event was removed. It technically added no value, as the <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">Bridge</a> Action already receives confirmation of the bridge through a successful completion Event.</li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">The BridgeExec events were removed. These events duplicated the events that </span><span style="line-height: 1.4285715;">occur in the Bridging API, and are conveyed now through <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">BridgeCreate</a>, </span><span style="line-height: 1.4285715;"><a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">BridgeEnter</a>, and <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">BridgeLeave</a> events.</span> </li>
<li style="font-size: 13px">The <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">RTCPSent</a>/<a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">RTCPReceived</a> 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.</li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">Added <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">BlindTransfer</a> and <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">AttendedTransfer</a> events. These events are </span><span style="line-height: 1.4285715;">raised when a blind transfer/attended transfer completes successfully. </span><span style="line-height: 1.4285715;">They contain information about the transfer that just completed, including </span><span style="line-height: 1.4285715;">the location of the transferred channel.</span> </li>
</ul>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<ul class="diff-block-target">
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">Parking has been pulled from core and placed into a separate module called </span><span style="line-height: 1.4285715;"><a href="#Newin12-res_parking" style="color: #326ca6; text-decoration: none"><span class="diff-html-changed" id="changed-diff-7" style="background-color: #d6f0ff;">res_parking</span></a>. Configuration for </span><span style="line-height: 1.4285715;">parking should now be performed in <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none"><em>res_parking.conf</em></a>. Configuration for </span><span style="line-height: 1.4285715;">parking in <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none"><em>features.conf</em> </a> is now unsupported.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">Core attended transfers now have several new options. While performing an </span><span style="line-height: 1.4285715;">attended transfer, the transferer now has the following options:</span>
<ul>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;"><code style="font-size: 13px">*1</code> - cancel the attended transfer (configurable via <code style="font-size: 13px">atxferabort</code>)</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;"><code style="font-size: 13px">*2</code> - complete the attended transfer, dropping out of the call </span><span style="line-height: 1.4285715;">(configurable via <code style="font-size: 13px">atxfercomplete</code>)</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;"><code style="font-size: 13px">*3</code> - complete the attended transfer, but stay in the call. This will turn </span><span style="line-height: 1.4285715;">the call into a multi-party bridge (configurable via <code style="font-size: 13px">atxferthreeway</code>)</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;"><code style="font-size: 13px">*4</code> - swap to the other party. Once an attended transfer has begun, this </span><span style="line-height: 1.4285715;">options may be used multiple times (configurable via <code style="font-size: 13px">atxferswap</code>)</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">For DTMF blind and attended transfers, the channel variable <code style="font-size: 13px">TRANSFER_CONTEXT</code> </span><span style="line-height: 1.4285715;">must be on the channel initiating the transfer to have any effect.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">The <code style="font-size: 13px">BRIDGE_FEATURES</code> channel variable would previously only set features for </span><span style="line-height: 1.4285715;">the calling party and would set this feature regardless of whether the </span><span style="line-height: 1.4285715;">feature was in caps or in lowercase. Use of a caps feature for a letter </span><span style="line-height: 1.4285715;">will now apply the feature to the calling party while use of a lowercase </span><span style="line-height: 1.4285715;">letter will apply that feature to the called party.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">Add support for <code style="font-size: 13px">automixmon</code> to the <code style="font-size: 13px">BRIDGE_FEATURES</code> channel variable.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">The channel variable <code style="font-size: 13px">DYNAMIC_PEERNAME</code> is redundant with <code style="font-size: 13px">BRIDGEPEER</code> and is </span><span style="line-height: 1.4285715;">removed. The more useful <code style="font-size: 13px">DYNAMIC_WHO_ACTIVATED</code> gives the channel name that </span><span style="line-height: 1.4285715;">activated the dynamic feature.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">The channel variables <code style="font-size: 13px">DYNAMIC_FEATURENAME</code> and <code style="font-size: 13px">DYNAMIC_WHO_ACTIVATED</code> are set </span><span style="line-height: 1.4285715;">only on the channel executing the dynamic feature. Executing a dynamic </span><span style="line-height: 1.4285715;">feature on the bridge peer in a multi-party bridge will execute it on all </span><span style="line-height: 1.4285715;">peers of the activating channel.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">You can now have the settings for a channel updated using the <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">FEATURE()</a> </span><span style="line-height: 1.4285715;">and <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">FEATUREMAP() </a>functions inherited to child channels by setting <code style="font-size: 13px">FEATURE(inherit)=yes</code>.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;"><code style="font-size: 13px">automixmon</code> now supports additional channel variables from <code style="font-size: 13px">automon</code> including: <code style="font-size: 13px">TOUCH_MIXMONITOR_PREFIX</code>, <code style="font-size: 13px">TOUCH_MIXMONITOR_MESSAGE_START</code>, and <code style="font-size: 13px">TOUCH_MIXMONITOR_MESSAGE_STOP</code>.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">A new general <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none"><em>features.conf</em> </a> option <code style="font-size: 13px">recordingfailsound</code> has been added which </span><span style="line-height: 1.4285715;">allows setting a failure sound for a user tries to invoke a recording feature </span><span style="line-height: 1.4285715;">such as <code style="font-size: 13px">automon</code> or <code style="font-size: 13px">automixmon</code> and it fails.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">It is no longer necessary (or possible) to define the <code style="font-size: 13px">ATXFER_NULL_TECH</code> in <code style="font-size: 13px">features.c</code> </span><span style="line-height: 1.4285715;">for <code style="font-size: 13px">atxferdropcall=no</code> to work properly. This option now just </span><span style="line-height: 1.4285715;">works.</span> </li>
</ul>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<ul class="diff-block-target">
<li style="font-size: 13px">Added support for <a href="http://tools.ietf.org/html/rfc3327" class="external-link" rel="nofollow" style="color: #326ca6; text-decoration: none">RFC 3327 "Path"</a> headers. This can be enabled in <em>sip.conf</em> using the <code style="font-size: 13px">supportpath</code> setting, either on a global basis or on a peer basis. This setting enables Asterisk to route outgoing out-of-dialog requests via a set of proxies by using a pre-loaded route-set defined by the Path headers in the <code style="font-size: 13px">REGISTER</code> request. See <a href="#Newin12-Realtime" style="color: #326ca6; text-decoration: none"><span class="diff-html-changed" id="changed-diff-8" style="background-color: #d6f0ff;">Realtime</span></a><span class="diff-html-changed" style="background-color: #d6f0ff;"> </span>updates for more configuration information.</li>
<li style="font-size: 13px"> <p style="font-size: 13px"> <span style="line-height: 1.4285715;">The <code style="font-size: 13px">SIP_CODEC</code> family of variables may now specify more than one codec. Each </span><span style="line-height: 1.4285715;">codec must be separated by a comma. The first codec specified is the </span><span style="line-height: 1.4285715;">preferred codec for the offer. This allows a dialplan writer to specify both </span><span style="line-height: 1.4285715;">audio and video codecs, e.g., </span> </p>
<table class="diff-macro" style="background-color: #f0f0f0;border: 1px solid #dddddd;margin: 10px 1px;padding: 0 2px 2px;width: 100%;">
<thead>
<tr>
<th class="diff-macro-title" style="background-color: transparent; text-align: left; font-weight: normal;padding: 5px;; font-size: 13px"><span class="icon macro-placeholder-icon" style="background-color: ;line-height: 20px;"><img src="https://wiki.asterisk.org/wiki/s/en_GB-1988229788/4252/6ac85e9b14675c5514a674e1aecae99c9505ed36.48/_/images/icons/macrobrowser/dropdown/noformat.png" style="padding-right: 5px; vertical-align: text-bottom;" /> </span>No Format</th>
</tr>
</thead>
<tbody>
<tr>
<td class="diff-macro-body" style="background-color: #fff;border: 1px solid #dddddd;padding: 10px;; font-size: 13px"> <pre style="font-size: 13px">same => n,Set(SIP_CODEC=ulaw,h264)</pre> </td>
</tr>
</tbody>
</table> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">The <code style="font-size: 13px">callevents</code> parameter has been removed. <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">Hold</a> AMI events are now raised </span><span style="line-height: 1.4285715;">in the core, and can be filtered out using the <code style="font-size: 13px">eventfilter</code> parameter </span><span style="line-height: 1.4285715;">in <em>manager.conf</em>.</span> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">Added <code style="font-size: 13px">ignore_requested_pref</code>. When enabled, this will use the preferred </span><span style="line-height: 1.4285715;">codecs configured for a peer instead of the requested codec.</span> </li>
</ul>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
</div>
</div>
</div>
<table id="email-actions" class="email-metadata" cellspacing="0" cellpadding="0" border="0" width="100%" style="border-top: 1px solid #bbb; color: #505050; margin: 8px 0 0 0; padding: 0; color: #505050">
<tbody>
<tr>
<td class="left" valign="top" style="font-size: 13px; padding-top: 8px; max-width: 45%; text-align: left"> <span class="email-list-item"><a href="https://wiki.asterisk.org/wiki/display/AST/New+in+12" style="color: #326ca6; text-decoration: none">View Online</a> </span> <span class="email-list-divider" style="color: #505050; padding: 0 0.350em">·</span> <span class="email-list-item"><a href="https://wiki.asterisk.org/wiki/plugins/likes/like.action?contentId=26476750" style="color: #326ca6; text-decoration: none">Like</a> </span> <span class="email-list-divider" style="color: #505050; padding: 0 0.350em">·</span> <span class="email-list-item"><a href="https://wiki.asterisk.org/wiki/pages/diffpagesbyversion.action?pageId=26476750&revisedVersion=7&originalVersion=6" style="color: #326ca6; text-decoration: none">View Changes</a> </span> <span class="email-list-divider" style="color: #505050; padding: 0 0.350em">·</span> <span class="email-list-item"><a href="https://wiki.asterisk.org/wiki/display/AST/New+in+12?showComments=true&showCommentArea=true#addcomment" style="color: #326ca6; text-decoration: none">Add Comment</a> </span> </td>
<td class="right" width="50%" valign="top" style="font-size: 13px; padding-top: 8px; text-align: right"> <span class="email-list-item"><a href="https://wiki.asterisk.org/wiki/users/removespacenotification.action?spaceKey=AST" style="color: #326ca6; text-decoration: none">Stop watching space</a> </span> <span class="email-list-divider" style="color: #505050; padding: 0 0.350em">·</span> <span class="email-list-item"><a href="https://wiki.asterisk.org/wiki/users/editmyemailsettings.action" style="color: #326ca6; text-decoration: none">Manage Notifications</a> </span> </td>
</tr>
</tbody>
</table> </td>
</tr>
</tbody>
</table> </td>
</tr>
<tr>
<td id="email-footer" align="center" style="font-size: 13px; padding: 0 16px 32px 16px; margin: 0"> <small style="font-size: 11px"> This message was sent by <a class="email-footer-link" style="color:#505050;font-size:11px;text-decoration:none;; color: #326ca6; text-decoration: none; color: #505050; font-size: 11px" href="http://www.atlassian.com/software/confluence">Atlassian Confluence</a> 5.1.5, <a class="email-footer-link" style="color:#505050;font-size:11px;text-decoration:none;; color: #326ca6; text-decoration: none; color: #505050; font-size: 11px" href="http://www.atlassian.com/software/confluence/overview/team-collaboration-software?utm_source=email-footer">Team Collaboration Software</a> </small> </td>
</tr>
</tbody>
</table>
</body>
</html>