<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/AstriDevCon+2013" 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;">AstriDevCon 2013</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>
<table class="diff-macro diff-block-context" 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/note.png" style="padding-right: 5px; vertical-align: text-bottom;" /> </span>Note</th>
</tr>
</thead>
<tbody>
<tr>
<td class="diff-macro-body" style="background-color: #fff;border: 1px solid #dddddd;padding: 10px;; font-size: 13px"> <p style="font-size: 13px">If your name is not on this list, please let someone know in #asterisk-dev so we can add you to this list!</p> </td>
</tr>
</tbody>
</table>
<h1 id="AstriDevCon2013-DayOne%3AAsterisk12DevelopmentDiscussion" class="diff-block-target diff-block-context"> <span class="diff-html-changed" id="changed-diff-0" style="background-color: #d6f0ff;">Day One</span> </h1>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<h1 id="AstriDevCon2013-DayOne%3AAsterisk12DevelopmentDiscussion" class="diff-block-target diff-block-context"> <span class="diff-html-added" id="added-diff-0" style="font-size: 100%; background-color: #ddfade;">: Asterisk 12 Development Discussion</span> </h1>
<p class="diff-block-context" style="font-size: 13px">Day one consisted of an in depth discussion of the features in Asterisk 12, as well as some hacking sessions with the new features in Asterisk 12. Slides used to facilitate discussion are available at the link below:</p>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<ul class="diff-block-target">
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Was PJPROJECT removed from Asterisk 12?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Yes, PJPROJECT was completely removed from Asterisk 12. The only way to use PJPROJECT is to dynamically link it using the shared object libraries.</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Does PJPROJECT have a testsuite to test for RFC compliance?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Yes, PJPROJECT itself has numerous tests that check for RFC compliance, amongst many other things.</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" id="added-diff-1" style="font-size: 100%; background-color: #ddfade;">Packaging PJPROJECT. Has anyone besides Tzafrir and Debian managed to package it while still following the distro's guidelines/rules?</span></span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Jared: no. This also impacts Asterisk - RHEL may not package or distribute Asterisk due to PJPROJECT having third party libraries</span></span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Matt: even though we actually removed PJPROJECT from Asterisk, and RHEL distributes Asterisk 11 with it?</span></span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Jared: yes</span></span> </li>
</ul> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">A discussion ensued about what it would take to package PJPROJECT. In general, the consensus was that for it to be included in the distros, the third party library folder would have to be removed</span></span>
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Note that Tzafrir already removed the folder from PJPROJECT and is distributing it with Debian without it. It should be possible for other packagers to make the same modifications.</span> </li>
</ul> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Are there license implications for PJSIP? PJSIP is licensed under the GPLv2, but </span><span style="color: rgb(34,34,34);line-height: 1.4285715;">Teluu has a dual license, similar to Digium/Asterisk. </span><span style="color: rgb(34,34,34);line-height: 1.4285715;">Does purchasing a commercial license of Asterisk come with a </span><span style="color: rgb(34,34,34);line-height: 1.4285715;">commercial license of PJSIP?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><strong>Action: Matt Jordan to provide answer</strong> <br /> </span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Implementation questions with PJSIP:</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Are we interfacing with lowest level of PJSIP stack?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Pretty much. Asterisk interfaces with the C API of PJSIP, and does not make use of PJSUA or other higher level libraries.</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Are we using</span><span style="line-height: 1.4285715;"> PJMedia</span><span style="color: rgb(34,34,34);line-height: 1.4285715;">?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Asterisk does make use of PJMedia's SDP parser, but not for any actual media handling. RTP handling is </span><span style="color: rgb(34,34,34);line-height: 1.4285715;">still done via <code style="font-size: 13px">res_rtp_asterisk</code>.</span> </li>
</ul> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Can we trigger MWI with ARI?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">ARI currently lacks the ability to raise MWI events, as well as device state. Since both of these are things that can be subscribed to, it may make sense to combine their functionality under a single resource ("blinky lights"?). This functionality is on the short list of things to do, as it would allow ARI to replace <code style="font-size: 13px">app_voicemail</code>. <strong>Action: Matt Jordan to get an issue made and a proposal out to asterisk-dev</strong></span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Sorcery is a new data abstraction layer that works with configuration and run-time data, or potentially</span><span style="line-height: 1.4285715;"> <span style="color: rgb(34,34,34);">any arbitrary data. </span></span><span style="color: rgb(34,34,34);line-height: 1.4285715;">Can any module query an object stored in any other module?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Yes, with some caveats. A module querying for an object in Sorcery must know someting about the object, i.e., it must have the definition of the struct for the object to query for it.</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Can you do a similar abstraction for DNS?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Not today. This would be a rather challenging feature to add, as DNS is supported by PJSIP and not Asterisk in the new SIP stack, and Asterisk's existing DNS support is "quirky" - integrating Sorcery into either would be quite the challenge.</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">Does</span><span style="color: rgb(34,34,34);line-height: 1.4285715;"> PJSIP support SIP SRV record lookup?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">PJSIP has full RFC 3263 support.</span><span style="color: rgb(34,34,34);line-height: 1.4285715;"> <br /> </span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Subscriptions to the state of an AoR. Does Asterisk generate state per contact on the AoR, or per AoR?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Currently Asterisk and the PJSIP stack in Asterisk will generate an aggregated state, but we could expose more detail if </span><span style="color: rgb(34,34,34);line-height: 1.4285715;">needed later on. In particular, however, the Asterisk core itself doesn't have a good way to manipulate multiple states behind a device, so this would require some heavy lifting in the device state/extension state core to be fully exploited.</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Can Endpoints have multiple auths or registrations?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Yes. <strong>Action: Mark Michelson to provide a wiki page or update an existing wiki page with those scenarios</strong></span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Since registrations are no longer defined as global "objects" or lines in a <code style="font-size: 13px">conf</code> file, what triggers an outbound registration?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">The existing configuration of a registration type section is what</span><span style="line-height: 1.4285715;"> </span><span style="color: rgb(34,34,34);line-height: 1.4285715;">triggers a registration upon Asterisk entering run-time.</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">How is documentation for new features handled?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">The Config framework requires config documentation for your new PJSIP</span><span style="line-height: 1.4285715;"> </span><span style="color: rgb(34,34,34);line-height: 1.4285715;">features or for any module that uses it (or Sorcery, by extension). Failure to provide documentation will result in the module not loading. Documentation is available in the CLI, but is also dumped to the wiki.</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">SDES, DTLS - are multiple ciphers supported?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);">Asterisk supports tag lengths of 32 and 80. However, it will only offer a single cipher in an outbound INVITE request, based either on what the inbound INVITE request offered of what Asterisk is configured with.</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"> Qualify in PJSIP, should work with outbound proxy?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Yes, outbound OPTIONS requests should respect the outbound proxy settings.</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="line-height: 1.4285715;">Questions on whether or not anyone uses features that did not make it into Asterisk 12's PJSIP stack (yet):</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Real-Time Text : no one in audience</span> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">CCSS: no one in audience</span> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">AoC: one person</span> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">SNOM ext state additions: no one in audience</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Asterisk 12 allows for new features to be added after release, subject to some constraints. See <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">Software Configuration Management Policies</a> for more information.</span> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);">Is Bridge information and other aspects of its configuration exposed through Sorcery?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">At this point in time, information about bridges is not exposed through Sorcery. In general, a bridge is created and configured through other interfaces, and state conveyed through events. Since this is a cached object in Stasis, there are possible ways in which its state could be conveyed out to Sorcery.</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">How does bridging key into the DSP subsystem?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">It uses the same APIs as channels.</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Is chan_sip still supported?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Yes, but its future depends on what</span><span style="line-height: 1.4285715;"> </span><span style="color: rgb(34,34,34);line-height: 1.4285715;">happens with chan_pjsip in the next year. Our goal is to some day </span><span style="color: rgb(34,34,34);line-height: 1.4285715;">obsolete chan_sip if possible; however, we fully expect many people to continue to use chan_sip for some time.</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Is it possible to have Stasis pub/sub distributed across servers?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">At this time, Stasis is an internal message bus only. Distribution of state across systems is still provided by interfaces built on top of Stasis, such as res_xmpp or res_corosync. It would be possible however to extend that state across systems, but a lot of thought would have to be given on how to use channel, bridge, and endpoint state in external systems.</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Can core show channels show state of stuff after it dies?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">No. The cache </span><span style="color: rgb(34,34,34);line-height: 1.4285715;">maintaining state of dead things would be a security issue - this would result in a slow leak of memory. Today, the </span><span style="color: rgb(34,34,34);line-height: 1.4285715;">cache purges itself when a call hangs up (channels), or when a bridge is destroyed.</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Is it possible for external systems to use an API to inject new messages on the Stasis message</span><span style="line-height: 1.4285715;"> </span><span style="color: rgb(34,34,34);line-height: 1.4285715;">bus?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Stasis is an internal message bus, but you could write wrapper over </span><span style="color: rgb(34,34,34);line-height: 1.4285715;">stasis to expose what you want to AMI or other API.</span> </li>
</ul> </li>
<li style="font-size: 13px"> <p style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Anyone using chan_agent? silence (except JSmith).<br /> </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/info.png" style="padding-right: 5px; vertical-align: text-bottom;" /> </span>Info</th>
</tr>
</thead>
<tbody>
<tr>
<td class="diff-macro-body" style="background-color: #fff;border: 1px solid #dddddd;padding: 10px;; font-size: 13px"> <p style="font-size: 13px">chan_agent is dead in Asterisk 12, replaced by <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">Asterisk 12 Application_AgentRequest</a> and <a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none">Asterisk 12 Application_AgentLogin</a>. No one seemed to mind.</p> </td>
</tr>
</tbody>
</table> </li>
</ul>
<ul class="diff-block-context">
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);">Anyone still using MeetMe?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);">3 or 4 in attendance admitted to using MeetMe.</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Is there still a need to add functionality to Queue for features like Skills-based routing?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Probably not. In general, you could probably use some combination of AGI/Dialplan and agent </span><span style="color: rgb(34,34,34);line-height: 1.4285715;">pool. In order to effectively use Agent pools to do skills based routing without baked in logic, you'd want an interception routine that could control whether or not an agent is dialed.</span> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">In general, business logic shouldn't be internal to Asterisk. Any solution for skills based routing or similar functionality should allow the user to define their logic outside of Asterisk.</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">CDR discussion. In general, we all admitted that CDRs may still need a bit of work, but you should have enough information to construct what occurs during a call, including various unique IDs for CDR records for tracking or</span><span style="line-height: 1.4285715;"> </span><span style="color: rgb(34,34,34);line-height: 1.4285715;">building a tree</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Who uses CEL to build CDR ? ~5 in attendance</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Origination of calls (AMI): is there a</span><span style="color: rgb(34,34,34);line-height: 1.4285715;">ny reason to add something to Originate that would create a bridge and </span><span style="color: rgb(34,34,34);line-height: 1.4285715;">connect an outbound call automatically to it?</span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;">Originate uses dialplan extension or </span><span style="color: rgb(34,34,34);line-height: 1.4285715;">application, rather than a bridge. This still should be possible, given a bridge to drop the originated call into. Alternatively, originating to an extension could accomplish this task if a dialplan application exists that adds the channel to a bridge.</span> </li>
</ul> </li>
</ul>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<ul class="diff-block-target diff-block-context">
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" id="added-diff-2" style="font-size: 100%; background-color: #ddfade;">Discussion of ARI, a new interface in Asterisk 12. ARI is </span><span class="diff-html-changed" id="changed-diff-2" style="background-color: #d6f0ff;">not a replacement for AMI or AGI. </span></span> </li>
</ul>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<ul class="diff-block-target diff-block-context">
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" id="added-diff-3" style="font-size: 100%; background-color: #ddfade;">ARI is meant as a way to replace dialplan applications with externally controlled applications - that is, </span><span class="diff-html-changed" id="changed-diff-3" style="background-color: #d6f0ff;">"write your own app_queue"</span></span>
<ul></ul> </li>
</ul>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<ul class="diff-block-target diff-block-context">
<li style="font-size: 13px">
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" id="added-diff-4" style="font-size: 100%; background-color: #ddfade;">Is it possible to </span><span class="diff-html-changed" id="changed-diff-5" style="background-color: #d6f0ff;">manipulate channel variables regardless of the state the channel is in</span></span> </li>
</ul> </li>
</ul>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<ul class="diff-block-target diff-block-context">
<li style="font-size: 13px">
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" id="added-diff-5" style="font-size: 100%; background-color: #ddfade;">?</span></span> <br />
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Yes, you can manipulate both channel variables as well as global variables through ARI.</span></span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">How about user events?</span></span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">No, we should add that capabilities. </span><strong><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Action to Matt Jordan to file an issue to add this functionality</span></strong><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">.</span></span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">How about logging messages back to Asterisk?</span></span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">No, we should add that capability as well. </span><strong><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Action to Matt Jordan to file an issue to add this functionality.</span></strong></span> </li>
</ul> </li>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">How about various dial options, indications, and DTMF?</span>
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">These should be added as well, but some thought should probably be given to how they are represented. </span><strong><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Action to Matt Jordan (or anyone, really) to have more conversation on these point on the -dev list. (Note: jcolp probably already has a patch for indications and DTMF)</span></strong> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">How does AMI compare vs ARI</span></span>
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">AMI </span><span class="diff-html-changed" id="changed-diff-6" style="background-color: #d6f0ff;">-> controlling calls in the context of dialplan</span></span> </li>
</ul> </li>
</ul> </li>
</ul>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<ul class="diff-block-target diff-block-context">
<li style="font-size: 13px">
<ul>
<li style="font-size: 13px">
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-changed" id="changed-diff-8" style="background-color: #d6f0ff;">ARI -> create a very targeted application, like </span></span> </li>
</ul> </li>
</ul> </li>
</ul>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<h1 id="AstriDevCon2013-DayTwo-Agenda" class="diff-block-target diff-block-context"> <span class="diff-html-removed" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;">Day Two - Agenda</span> </h1>
<p class="diff-block-target diff-block-context" style="font-size: 13px"> <span class="diff-html-removed" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;"> </span> </p>
<ul class="diff-block-target diff-block-context">
<li style="font-size: 13px">
<ul>
<li style="font-size: 13px">
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-changed" style="background-color: #d6f0ff;"> </span><span class="diff-html-changed" id="changed-diff-9" style="background-color: #d6f0ff;">a</span></span> </li>
</ul> </li>
</ul> </li>
</ul>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<ul class="diff-block-target diff-block-context">
<li style="font-size: 13px">
<ul>
<li style="font-size: 13px">
<ul>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" id="added-diff-6" style="font-size: 100%; background-color: #ddfade;"> dialplan application. Think of ARI as a way to write VoiceMail, Queue, or ConfBridge, while AMI controls calls outside of those applications.</span></span> </li>
</ul> </li>
</ul> </li>
</ul>
<p class="diff-block-target diff-block-context" style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Day One wrapped up with hands on labs using the server provided by BlueHost and Jared Smith. A few observations from those labs:</span></span> </p>
<ol class="diff-block-target diff-block-context">
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">PJPROJECT can still be tricky to install. The more effort we can put into getting good packages made for distros as well as making the build and install process easier, the better.</span></span>
<ol>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Common issues: installation in lib instead of lib64, various third party conflicts, pkg-config not looking in correct location</span></span> </li>
</ol> </li>
<li style="font-size: 13px"> <span style="color: rgb(34,34,34);"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">ARI is neat, but having some wrapper libraries that manage the WebSocket connection would be nice</span></span> </li>
</ol>
<p class="diff-block-context" style="font-size: 13px"> <span style="color: rgb(34,34,34);line-height: 1.4285715;"> <br /> </span> </p>
<p class="diff-block-target diff-block-context" style="font-size: 13px"> <span style="color: rgb(133,120,102);font-family: MuseoSans700 , sans-serif;font-size: 24.0px;line-height: 1.25;"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Day Two: Asterisk 12 Future and Asterisk 13 Discussion</span></span> </p>
<p class="diff-block-target diff-block-context" style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">The morning consisted of further labs and hack sessions on Asterisk 12. The afternoon consisted of a discussion regarding future development in Asterisk 12, as well as features that would be destined for the next LTS release, Asterisk 13.</span> </p>
<h2 id="AstriDevCon2013-Agenda" class="diff-block-target diff-block-context"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Agenda</span> </h2>
<ul style="list-style-type: square;" class="diff-block-target diff-block-context">
<li style="font-size: 13px"> <p style="font-size: 13px"> <span class="diff-html-changed" id="changed-diff-10" style="background-color: #d6f0ff;">Policy in general/</span><span style="line-height: 1.5;"><span class="diff-html-changed" style="background-color: #d6f0ff;">Release policy</span></span> </p> </li>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;">Expanding the ARI / rest api</span> </li>
<li style="font-size: 13px">PJSIP / chan_sip45</li>
<li style="font-size: 13px">Media negotiation adaptive stuff magic dynamic stuff
<ul style="list-style-type: square;">
<li style="font-size: 13px">Off load media handling</li>
</ul> </li>
<li style="font-size: 13px">Clustering / distributed environments
<ul style="list-style-type: square;">
<li style="font-size: 13px">Distributed conferencing</li>
</ul> </li>
<li style="font-size: 13px">Opus</li>
<li style="font-size: 13px">Kill app_queue!!!!</li>
<li style="font-size: 13px">Asteri18n - mailing list exists!</li>
<li style="font-size: 13px">Video!!!</li>
<li style="font-size: 13px">RTP / improvements</li>
<li style="font-size: 13px">Security / named ACLs mark II</li>
<li style="font-size: 13px">Dynamic configuration framework / push</li>
<li style="font-size: 13px">Review last year's list</li>
<li style="font-size: 13px">The future of Asterisk</li>
</ul>
<p class="diff-block-target diff-block-context" style="font-size: 13px"> <span class="diff-html-removed" id="removed-diff-8" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;"> </span> </p>
<h2 id="AstriDevCon2013-Releasepolicy" class="diff-block-target diff-block-context"> <span class="diff-html-changed" id="changed-diff-11" style="background-color: #d6f0ff;">Release policy</span> </h2>
<ul class="diff-block-target diff-block-context">
<li style="font-size: 13px">Asterisk 12 release policy will be different than other releases
<ul>
<li style="font-size: 13px">New features will be included after release<span class="diff-html-added" id="added-diff-7" style="font-size: 100%; background-color: #ddfade;">, subject to the constraints in </span><a class="confluence-link unresolved" href="#" style="color: #326ca6; text-decoration: none"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Software Configuration Management Policies</span></a> </li>
</ul> </li>
<li style="font-size: 13px">Release policy<span class="diff-html-removed" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;"> </span><span class="diff-html-removed" id="removed-diff-9" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;">new features change for </span><span class="diff-html-added" id="added-diff-8" style="font-size: 100%; background-color: #ddfade;">: do we allow new feature changes in Asterisk </span>13?
<ul>
<li style="font-size: 13px"> <span class="diff-html-removed" id="removed-diff-10" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;">Standalone modules ok? No changes in core</span> </li>
<li style="font-size: 13px"> <span class="diff-html-removed" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;">Disabled in menuselect</span> </li>
<li style="font-size: 13px"> <span class="diff-html-removed" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;">Approval policy for new features - benefit for the larger asterisk community</span> </li>
<li style="font-size: 13px"> <span class="diff-html-removed" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;">Action: Discussion on policy on asterisk-dev</span> </li>
</ul> <span class="diff-html-removed" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;">Version number 13 </span>
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-9" style="font-size: 100%; background-color: #ddfade;">First, as it is with Asterisk 11, standalone modules are always okay. If they are included in a release branch, they can be disabled by default, which means existing installations are insulated from the changes. There should not be changes in core.</span> </li>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Do we need an approval policy for new features? For example, there are often very minor features (new device states, new AMI events, new ARI events, etc.) that would benefit the larger asterisk community, but are currently automatically rejected. These features have a very low risk of causing an issue.</span>
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Jared: other projects have done this and had it be very successful</span> </li>
<li style="font-size: 13px"> <strong><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Action to Matt Jordan to look into a policy and start a discussion on asterisk-dev</span></strong> </li>
</ul> </li>
</ul> </li>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Should we release the next major version as 13? Should it be 14 </span>or something else? Asterisk MineSweeper 2.0? Asterisk 8+5. Marco: Asterisk XP
<ul>
<li style="font-size: 13px"> <span class="diff-html-removed" id="removed-diff-11" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;">Room in </span><span class="diff-html-added" id="added-diff-10" style="font-size: 100%; background-color: #ddfade;">The overall consensus in the room was in </span>favor of 13. <span class="diff-html-removed" id="removed-diff-12" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;">Discussion moves to </span><span class="diff-html-added" id="added-diff-11" style="font-size: 100%; background-color: #ddfade;">As we still have time for further discussion on this matter, we should bring it up again in a month or two on </span>asterisk-dev</li>
</ul> </li>
</ul>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<ul class="diff-block-target diff-block-context">
<li style="font-size: 13px">
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-12" style="font-size: 100%; background-color: #ddfade;">.</span> </li>
<li style="font-size: 13px"> <strong><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Action: revisit this decision in a month or two on asterisk-dev to solicit a wider opinion</span></strong> </li>
</ul> </li>
</ul>
<h2 id="AstriDevCon2013-ExpandingARI%2FRestfulAPI" class="diff-block-target diff-block-context"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Expanding </span><span class="diff-html-changed" id="changed-diff-12" style="background-color: #d6f0ff;">ARI/Restful API</span> </h2>
<ul class="diff-block-target diff-block-context">
<li style="font-size: 13px">Version numbering of API needs to be handled
<ul>
<li style="font-size: 13px">Current is 0.0.1<span class="diff-html-added" id="added-diff-13" style="font-size: 100%; background-color: #ddfade;">. David Lee is currently working on a versioning scheme.</span> </li>
<li style="font-size: 13px"> <strong><span class="diff-html-added" id="added-diff-14" style="font-size: 100%; background-color: #ddfade;">Action: propose a versioning scheme.</span></strong><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;"> David Lee </span><a href="http://lists.digium.com/pipermail/asterisk-dev/2013-October/063003.html" class="external-link" rel="nofollow" style="color: #326ca6; text-decoration: none"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">did reply in an e-mail to the -dev list</span></a><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;"> with a draft proposal linked here: </span><a href="https://wiki.asterisk.org/wiki/x/WwCUAQ" rel="nofollow" style="color: #326ca6; text-decoration: none"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">https://wiki.asterisk.org/wiki/x/WwCUAQ</span></a> </li>
</ul> </li>
<li style="font-size: 13px">Suggestion: Client can indicate "expected version" and server will adapt WITHIN REASON
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-15" style="font-size: 100%; background-color: #ddfade;">There was a long discussion about this proposal. The idea is that if an event is added and the version number incremented, then a client connecting supporting an earlier version number won't receive those events. Due to how messages on the Stasis bus are constructed for consumers, this is not out of the realm of possibility in both AMI and ARI, but careful thought would have to be applied - and expectations set on how far the scope of this can be extended.</span> </li>
</ul> </li>
<li style="font-size: 13px">Implementation notes to client developers may need to be published:
<ul>
<li style="font-size: 13px">Expect new events</li>
<li style="font-size: 13px">Use the version number of the API in combination with Asterisk version (Maybe not, but remember AMI)</li>
<li style="font-size: 13px">Explain the need for and use of ARI as compared with AGI, AMI, ExtIVR etc</li>
</ul> </li>
<li style="font-size: 13px">Feature requests for ARI
<ul>
<li style="font-size: 13px">Propably thousands of features missing</li>
<li style="font-size: 13px">Issue: How do we hand control of a channel back to the dialplan / or to specific app
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-16" style="font-size: 100%; background-color: #ddfade;">Currently, the channel is sent back to the dialplan, but there is not a way to send it directly to an application. This would require some careful thought, as the releasing back to the dialplan guarantees that something can still execute the channel - sending it directly to an application would almost have to guarantee that the channel is immediately destroyed when the application terminates.</span> </li>
</ul> </li>
<li style="font-size: 13px">Issue: Queue-related stuff missing - members, queue status,
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Much of this is higher level application logic that would be provided by someone implementing a replacement for app_queue</span> </li>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Question: do we need to have a RESTful interface that replaces AMI?</span>
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Answer: that would be highly desired (Jared, Dan, etc.)</span>
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Need to discuss what functionality should be carried over from AMI and put behind a REST interface; some might not make sense.</span><span class="diff-html-changed" id="changed-diff-15" style="background-color: #d6f0ff;"> </span><strong><span class="diff-html-added" id="added-diff-18" style="font-size: 100%; background-color: #ddfade;">Action - have a discussion on the asterisk-dev list about replacing AMI with a REST interface</span></strong> </li>
</ul> </li>
</ul> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;">Issue: Call states<span class="diff-html-removed" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;"> </span><span class="diff-html-removed" id="removed-diff-14" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;">- </span></span>
<ul>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Need device state resource. </span><strong><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Action - have a discussion on the asterisk-dev list about this</span></strong></span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;">Issue: User events</span>
<ul>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;"><span class="diff-html-added" id="added-diff-20" style="font-size: 100%; background-color: #ddfade;">Carried over from the previous day; action already taken</span></span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;">Issue: Generating DTMF</span>
<ul>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;"><span class="diff-html-added" id="added-diff-21" style="font-size: 100%; background-color: #ddfade;">Carried over from the previous day; action already taken</span></span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;">Suggestion: Expand ARI to handle existing apps in Asterisk</span>
<ul>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;"><span class="diff-html-added" id="added-diff-22" style="font-size: 100%; background-color: #ddfade;">Can the community create open source replacements of Queue, VoiceMail, and others? If so, where should it live?</span></span>
<ul>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Consensus seemed to rest on GitHub</span></span> </li>
</ul> </li>
</ul> </li>
<li style="font-size: 13px">How do we manage feature requests for ARI?
<ul>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;">Wiki page with feature requests / brainstorms / hot items for ARI<span class="diff-html-added" id="added-diff-23" style="font-size: 100%; background-color: #ddfade;">. </span><strong><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Action - create said wiki page for both ARI features as well as other features requested by the community</span></strong></span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;">How do we migrate more apps to ARI?</span>
<ul>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;"><span class="diff-html-added" id="added-diff-24" style="font-size: 100%; background-color: #ddfade;">Carefully!</span></span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;">Issue: Issue log items for all log channels from ARI apps</span>
<ul>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;"><span class="diff-html-added" id="added-diff-25" style="font-size: 100%; background-color: #ddfade;">Carried over from previous day; action already taken</span></span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;">Issue: Resources on the server / files - sandbox issues</span>
<ul>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;"><span class="diff-html-added" id="added-diff-26" style="font-size: 100%; background-color: #ddfade;">In general, ARI should protect the server from malicious requests. Exposing System() application like functionality should be discouraged, due to known permission elevation issues with AMI and the dialplan.</span></span> </li>
</ul> </li>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;">Issue: Dial() options that are missing from ARI</span>
<ul>
<li style="font-size: 13px"> <span style="font-size: 14.0px;line-height: 1.4285715;">Play digits</span> </li>
<li style="font-size: 13px">Ignore forwards</li>
<li style="font-size: 13px">Fake ringing</li>
<li style="font-size: 13px"> <p style="font-size: 13px"> <span class="diff-html-changed" id="changed-diff-24" style="background-color: #d6f0ff;">Play music instead of ringing</span> </p>
<table class="diff-macro diff-html-added" style="background-color: #f0f0f0;border: 1px solid #dddddd;margin: 10px 1px;padding: 0 2px 2px;width: 100%;background-color: #ddfade;border-color: #93c49f;">
<thead>
<tr>
<th class="diff-macro-title" style="background-color: transparent; text-align: left; font-weight: normal;padding: 5px;; font-size: 13px"><span class="diff-html-added" id="added-diff-27" style="font-size: 100%; background-color: #ddfade;"><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/note.png" style="padding-right: 5px; vertical-align: text-bottom;" /> </span>Note</span></th>
</tr>
</thead>
<tbody>
<tr>
<td class="diff-macro-body" style="background-color: #fff;border: 1px solid #dddddd;padding: 10px;; font-size: 13px"> <p style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Should we have a "Dial" operation that does all of this in </span><span class="diff-html-changed" id="changed-diff-25" style="background-color: #d6f0ff;">ARI</span><span class="diff-html-added" id="added-diff-28" style="font-size: 100%; background-color: #ddfade;">? Discussion now ongoing on the asterisk-app-dev list: </span><a href="http://lists.digium.com/pipermail/asterisk-app-dev/2013-October/000002.html" class="external-link" rel="nofollow" style="color: #326ca6; text-decoration: none"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">http://lists.digium.com/pipermail/asterisk-app-dev/2013-October/000002.html</span></a> </p> </td>
</tr>
</tbody>
</table> </li>
</ul> </li>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">ARI </span>options for Digium commercial modules
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-29" style="font-size: 100%; background-color: #ddfade;">Matt Jordan: probably not, or at least not right away. Digium commercial modules typically only expose inspection level commands (how many licenses do I have, etc.) - ARI is more about application control. If we end up exposing a REST interface that provides system inspection, then we may want more of this in our commercial modules</span> </li>
</ul> </li>
<li style="font-size: 13px">Issue: A bridge between ARI and AMI
<ul></ul> <span class="diff-html-removed" id="removed-diff-15" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;">Issue: USerevents from ARI</span>
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-30" style="font-size: 100%; background-color: #ddfade;">That is, is there a way to integrate AMI and ARI applications easily? This may rest heavily on the client libraries developed.</span> </li>
</ul> </li>
<li style="font-size: 13px">SDK will be released on github - python and javascript
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-31" style="font-size: 100%; background-color: #ddfade;">Digium working on the initial client library implementations that are auto-generated from the resources. </span><strong><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Update: </span></strong><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Paul Belanger working on a Python implementation as well.</span> </li>
</ul> </li>
</ul> </li>
</ul>
<h2 id="AstriDevCon2013-CHAN_PJSIP" class="diff-block-context">CHAN_PJSIP</h2>
<ul class="diff-block-target diff-block-context">
<li style="font-size: 13px">Number one issue: Get PJSIP installed
<ul>
<li style="font-size: 13px">Debian packages being built</li>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-32" style="font-size: 100%; background-color: #ddfade;">Work with/discuss options with other package maintainers</span> </li>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Other than ripping out the third party library folder, what else can we do to make the installation easier?</span>
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Auto-detection of third party libraries to aid configure script</span> </li>
</ul> </li>
</ul> </li>
<li style="font-size: 13px">PJSIP support of the "SIP/" prefix
<ul>
<li style="font-size: 13px">Configurable switch <span class="diff-html-added" id="added-diff-33" style="font-size: 100%; background-color: #ddfade;">- should we allow people to map SIP to PJSIP?</span>
<ul></ul> <span class="diff-html-removed" id="removed-diff-16" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;">Not really dialstring</span>
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-34" style="font-size: 100%; background-color: #ddfade;">Pros: easier to switch between dialplan</span> </li>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Cons: confusion as to what you're running; chan_sip to chan_pjsip nomenclature doesn't have a one to one correlation</span> </li>
</ul> </li>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Not really just dialing (which has its own issues) - things like device state, out of call messaging are also affected</span> </li>
</ul> </li>
<li style="font-size: 13px">Ability to dial any SIP URI is important - YES!!!
<ul>
<li style="font-size: 13px"> <strong><span class="diff-html-added" id="added-diff-35" style="font-size: 100%; background-color: #ddfade;">Action: create an issue to round out this functionality and/or provide sufficient documentation on how it should be configured</span></strong> </li>
</ul> </li>
<li style="font-size: 13px">SIP Outbound proxy / Predefined route set</li>
<li style="font-size: 13px">AMI and CLI commands needed
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-36" style="font-size: 100%; background-color: #ddfade;">CLI commands being worked by George Joseph - see </span><a href="https://issues.asterisk.org/jira/browse/ASTERISK-22610" class="external-link" rel="nofollow" style="color: #326ca6; text-decoration: none"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">https://issues.asterisk.org/jira/browse/ASTERISK-22610</span></a> </li>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">AMI commands being worked by Kevin Harwell - see </span><a href="https://issues.asterisk.org/jira/browse/ASTERISK-22609" class="external-link" rel="nofollow" style="color: #326ca6; text-decoration: none"><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">https://issues.asterisk.org/jira/browse/ASTERISK-22609</span></a> </li>
</ul> </li>
<li style="font-size: 13px">Integration with CHANNEL() function
<ul>
<li style="font-size: 13px"> <strong><span class="diff-html-added" id="added-diff-37" style="font-size: 100%; background-color: #ddfade;">Action: create an issue for this functionality</span></strong> </li>
</ul> </li>
<li style="font-size: 13px">Ability to dial without entity in configuration
<ul>
<li style="font-size: 13px">Set codecs and preferred codecs, DTMF mode, security properties</li>
<li style="font-size: 13px">All of the settings for an endpoint </li>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-38" style="font-size: 100%; background-color: #ddfade;">Question: should this really be allowed? In general, one can create an endpoint that acts as the outbound entity to dial, and send it SIP URIs and other options. Do we really need a default, or should we just tell people how to configure this?</span> </li>
</ul> </li>
<li style="font-size: 13px">Change properties of objects from API's and dialplan
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-39" style="font-size: 100%; background-color: #ddfade;">This would be a function that would allow a channel to override the settings inherited from its endpoint.</span> </li>
<li style="font-size: 13px"> <strong><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Action: discuss this on the asterisk-dev list, and identify an initial feature set for the function</span></strong> </li>
</ul> </li>
<li style="font-size: 13px">How much of backwards compatibility is required?</li>
<li style="font-size: 13px">Focus/prism on Security</li>
<li style="font-size: 13px">No Call Completion, AOC, SNOM extensions - needed in 12</li>
<li style="font-size: 13px">SUBSCRIBE/notify/PUBLISH STUFF</li>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-40" style="font-size: 100%; background-color: #ddfade;">How do we handle versioining of the PJPROJECT fork?</span>
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Patches are being pushed up to Teluu, but right now there is no version for PJPROJECT. Do we need a tag on the github repo so people know what to base it against in the meantime?</span> </li>
</ul> </li>
</ul>
<h2 id="AstriDevCon2013-Medianegotiation" class="diff-block-context">Media negotiation</h2>
<ul class="diff-block-target diff-block-context">
<li style="font-size: 13px">Steve invites to bar-bof<span class="diff-html-added" id="added-diff-41" style="font-size: 100%; background-color: #ddfade;">. Media negotiation is rather complex, and how it should be handled is usually a matter of opinion based on specific scenarios and requirements. For this to go forward, there should be requirements, use cases, and other proposals first discussed on the asterisk-dev list.</span>
<ul>
<li style="font-size: 13px">Draft call scenarios</li>
<li style="font-size: 13px">Draft requirements</li>
<li style="font-size: 13px">Draft solutions</li>
</ul> </li>
<li style="font-size: 13px">Continue discussion on mailing list</li>
</ul>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<p class="diff-block-context" style="font-size: 13px">Steve Murphy presenting. "gettext for saying stuff". Executive summary:</p>
<p class="diff-block-target" style="font-size: 13px"> <span class="diff-html-removed" id="removed-diff-17" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;"> </span> </p>
<ul class="diff-block-target diff-block-context">
<li style="font-size: 13px">Change all the "SAY" routines to pluggable modules</li>
<li style="font-size: 13px">The translator can not code, a solution needs to be translator-compatible</li>
<li style="font-size: 13px">The logic is now in c-code which is not very translator-friendly</li>
<li style="font-size: 13px">The logic needs to be included in the sound-file set</li>
<li style="font-size: 13px">Proposal for a new Asterisk-independent config language called "SayScript"</li>
<li style="font-size: 13px">"The fundamental unit of translation is the sentence" - context is needed</li>
<li style="font-size: 13px">A language pack will have script file, language prompts, sayscript logic</li>
<li style="font-size: 13px"> <span class="diff-html-removed" id="removed-diff-18" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;">Send to Asterisk-dev</span><span class="diff-html-added" id="added-diff-42" style="font-size: 100%; background-color: #ddfade;">As a conclusion: the proposal has strong merit but needs to be discussed further on the asterisk-dev list, as Tzafrir had some questions and concerns about its general approach. </span><strong><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Action: Steve Murphy to distribute proposal on the asterisk-dev mailing list</span></strong> </li>
</ul>
<h3 id="AstriDevCon2013-Opus" class="diff-block-context">Opus</h3>
<ul class="diff-block-target diff-block-context">
<li style="font-size: 13px">Asterisk 12 includes formats for pass-through of Opus and VP8</li>
<li style="font-size: 13px">There are patches on github.com/meetecho for Codec_opus</li>
<li style="font-size: 13px">mp3/ilbc
<ul>
<li style="font-size: 13px">mp3: use newer implementations</li>
<li style="font-size: 13px">ilbc: remove embedded source, use newer implementation from Google<span class="diff-html-added" id="added-diff-43" style="font-size: 100%; background-color: #ddfade;">. </span><strong><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Action: create an issue for versions of Asterisk to look for a library and use it if available; otherwise use embedded source. Remove embedded source in trunk.</span></strong> </li>
</ul> </li>
<li style="font-size: 13px">licensing <span class="diff-html-added" id="added-diff-44" style="font-size: 100%; background-color: #ddfade;">- Digium investigating licensing concerns with IPRs against Opus.</span>
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-45" style="font-size: 100%; background-color: #ddfade;">Current status: still working with/waiting on Xiph.</span> </li>
<li style="font-size: 13px">transcoding</li>
</ul> </li>
</ul>
<p class="diff-block-context" style="font-size: 13px"> </p>
<h2 id="AstriDevCon2013-Clustering%2Fdistributedasterisk" class="diff-block-context">Clustering/distributed asterisk</h2>
<ul class="diff-block-target diff-block-context">
<li style="font-size: 13px">No "clean way" to distribute states between asterisk servers<span class="diff-html-added" id="added-diff-46" style="font-size: 100%; background-color: #ddfade;">.</span>
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-47" style="font-size: 100%; background-color: #ddfade;">Stasis is an internal message bus. Replacing it with something that supports distributed pub/sub is theoretically possible, as Stasis is an opaque implementation and does not inspect the contents of the messages distributed on it; however, this would be quite a large project</span> </li>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Bigger question: what are the use cases for distributing state?</span>
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Full call fail over is a much larger task than just channel / channel_pvt distribution. You actually have to do something with the state once you have it.</span> </li>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">What use case is there for bridge/channel state outside of Asterisk that requires something like redis and that can't be built with AMI/ARI? Need more requirements/use cases.</span> </li>
</ul> </li>
</ul> </li>
<li style="font-size: 13px">Bar-bof Paul Belanger</li>
</ul>
<h2 id="AstriDevCon2013-Killapp_queue-ARIappsinAsterisk" class="diff-block-target diff-block-context"> <span class="diff-html-changed" id="changed-diff-36" style="background-color: #d6f0ff;">Kill app_queue - </span> </h2>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<h2 id="AstriDevCon2013-Killapp_queue-ARIappsinAsterisk" class="diff-block-target diff-block-context"> <span class="diff-html-added" id="added-diff-48" style="font-size: 100%; background-color: #ddfade;">ARI </span><span class="diff-html-changed" id="changed-diff-37" style="background-color: #d6f0ff;">apps in </span> </h2>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<h2 id="AstriDevCon2013-Killapp_queue-ARIappsinAsterisk" class="diff-block-target diff-block-context"> <span class="diff-html-added" id="added-diff-49" style="font-size: 100%; background-color: #ddfade;">Asterisk</span> </h2>
<ul class="diff-block-target diff-block-context">
<li style="font-size: 13px">There should be a replacement delivered with Asterisk, but probably initially on github
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-50" style="font-size: 100%; background-color: #ddfade;">In Asterisk might just be something that pulls from github</span> </li>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Many folks interested in creating a Queue replacement - Paul, Dan, Leif, Jared</span> </li>
</ul> </li>
<li style="font-size: 13px">Licensing of ARI applications<span class="diff-html-added" id="added-diff-51" style="font-size: 100%; background-color: #ddfade;">. </span><strong><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Action to Matt Jordan - clarify ARI licensing in the same fashion as AGI/AMI.</span></strong> </li>
<li style="font-size: 13px">How to find ARI's / Repository
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-52" style="font-size: 100%; background-color: #ddfade;">Ideally, we would have something like pip or some other package manager that would allow someone to search, install ARI applications easily</span> </li>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Has to be language agnostic</span> </li>
<li style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Could just be a wrapper around language specific functions</span> </li>
<li style="font-size: 13px"> <strong><span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;">Action: discuss more on asterisk-dev list</span></strong> </li>
</ul> </li>
</ul>
<h2 id="AstriDevCon2013-Security" class="diff-block-context">Security</h2>
<ul class="diff-block-target diff-block-context">
<li style="font-size: 13px">Fail2ban inside Asterisk
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-53" style="font-size: 100%; background-color: #ddfade;">Security event framework already exists, just need to propagate security events through interfaces (currently only a log file)</span> </li>
<li style="font-size: 13px">Named ACLs <span class="diff-html-added" id="added-diff-54" style="font-size: 100%; background-color: #ddfade;">- if these can be created and applied externally, then security events can be used to auto-ban anything coming into Asterisk</span> </li>
</ul> </li>
<li style="font-size: 13px">Security in a PRISM era
<ul>
<li style="font-size: 13px">Secure audio, secure signalling</li>
<li style="font-size: 13px">256 key length for AES encryption</li>
<li style="font-size: 13px">Upgrade to new LibSRTP on github (OpenSSL)
<ul>
<li style="font-size: 13px"> <span class="diff-html-added" id="added-diff-55" style="font-size: 100%; background-color: #ddfade;">Since Asterisk dynamically links with libSRTP, unclear right now what needs to be done. Possibly another point of discussion on asterisk-dev</span> </li>
</ul> </li>
<li style="font-size: 13px">Key lifetime, key rotation, key re-negotiation</li>
</ul> </li>
<li style="font-size: 13px">Generating certificates at install time</li>
<li style="font-size: 13px">Review TLS implementation; improve</li>
</ul>
<p class="diff-block-context" style="font-size: 13px"> </p>
<p class="diff-block-target diff-block-context" style="font-size: 13px"> <span class="diff-html-removed" id="removed-diff-21" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;"> </span> </p>
<p class="diff-block-target diff-block-context" style="font-size: 13px"> <span class="diff-html-removed" style="font-size: 100%; background-color: #ffe7e7; text-decoration: line-through;"> </span> </p>
<p class="diff-block-context" style="font-size: 13px"> <strong>Random quotes</strong> </p>
<p class="diff-block-context" style="font-size: 13px">"Asterisk is Asterisk"</p>
<p class="diff-block-context" style="font-size: 13px"> </p>
<p class="diff-context-placeholder" style="font-size: 13px">...</p>
<p class="diff-block-target diff-block-context" style="font-size: 13px"> <span class="diff-html-added" id="added-diff-56" style="font-size: 100%; background-color: #ddfade;"> </span> </p>
<p class="diff-block-target diff-block-context" style="font-size: 13px"> <span class="diff-html-added" style="font-size: 100%; background-color: #ddfade;"> </span> </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/AstriDevCon+2013" 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=26478393" 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=26478393&revisedVersion=11&originalVersion=10" 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/AstriDevCon+2013?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>