<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="8" style="border: 1px #c9c399 solid;">
<tr>
<td>
This is an automatically generated e-mail. To reply, visit:
<a href="https://reviewboard.asterisk.org/r/1445/">https://reviewboard.asterisk.org/r/1445/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On September 19th, 2011, 1:07 p.m., <b>Tilghman Lesher</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Code looks good, but due to behavior change, I think we should hold off with this change until Asterisk 10.</pre>
</blockquote>
</blockquote>
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">I was considering adding a WARNING in 1.8 to make clear that this is not expected behavior and and option to turn on behavior as in 10, to generate an error.</pre>
<br />
<p>- Olle E</p>
<br />
<p>On September 19th, 2011, 1:07 p.m., Olle E Johansson wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: url('https://reviewboard.asterisk.org/media/rb/images/review_request_box_top_bg.png'); background-position: left top; background-repeat: repeat-x; border: 1px black solid;">
<tr>
<td>
<div>Review request for Asterisk Developers.</div>
<div>By Olle E Johansson.</div>
<p style="color: grey;"><i>Updated Sept. 19, 2011, 1:07 p.m.</i></p>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Description </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Currently, if a manager originate tries to access an extension that does not exist, pbx.c ast_pbx_start makes the call fall over to "s@default" which should *not* be the case.
We agreed on IRC to fix pbx_start later, but this patch (aimed at 1.8) fixes the manager command so that (in the manner of the SIP channel) we check for the extension before trying the call. This will affect current behaviour and should be documented properly. It may affect applications that rely on this - users may have built dialplans that use "s" this way instead of fixing a fallback within their application. We might want to have an option in manager.conf to preserve old behaviour for this reason.
Separately, we should check other originate (CLI, app) as well, but let's separate the patches.
Background: extension "s" should ONLY be used when NO extension is given. It's not a wildcard and not a fallback when things go wrong.
Side note: The bug exists in 1.4 too, so in all 1.6.x releases.
</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Testing </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Feels like the code compiles on OS/X. This review is more about if we want to fix this in 1.8 and how. After that, I'll test the code.</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
<li>/branches/1.8/main/manager.c <span style="color: grey">(336574)</span></li>
</ul>
<p><a href="https://reviewboard.asterisk.org/r/1445/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>