<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/1634/">https://reviewboard.asterisk.org/r/1634/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On December 19th, 2011, 4:16 p.m., <b>jrose</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;">Oh yeah, this needs to be indicated in CHANGES. Noted and put on my to do list.</pre>
</blockquote>
<p>On December 20th, 2011, 2:53 a.m., <b>Olle E Johansson</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;">I've always wanted a way to turn this off. Just a side note and a feature request that safely can be ignored.</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 saw your comment in the code actually actually, and figured you'd appreciate this patch. Maybe you need an explanation? The fact is, the feature never did anything unless you mapped the built-in automon feature to some DTMF in features.conf in the first place. With this patch in place, you can just change the general settings to use "" and then they never should never find a feature to map against, even when you've given the incoming peer the ability to use something like automon in the first place.
Alternatively, you could set up a feature that just invokes no-op or something. There really isn't any need for a more comprehensive feature to actually shut off INFO record detection if that's what you are asking for.</pre>
<br />
<p>- jrose</p>
<br />
<p>On December 19th, 2011, 4:08 p.m., jrose 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, David Vossel and Matt Jordan.</div>
<div>By jrose.</div>
<p style="color: grey;"><i>Updated Dec. 19, 2011, 4:08 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;">The reporter was was wanting to submit a feature change which would have allowed Record requests to search through dynamic features for a feature named automon rather than simply failing if it wasn't found in builtin features.
David Vossel responded to the issue suggesting he would rather see a setting added to specify the feature.
This patch goes a step beyond that by allowing the user to specify which feature to use when receiving the message separately depending on whether the incoming message contained Record: on or Record: off. These applications can be set to the same value when using the built in features like automon/automixmon, or they can be set separately so that on always triggers the recording feature while off always triggers the appropriate feature to shut the recording application off. In this case, the SNOM phone which this feature was made for will typically show the correct recording status indication after the button is pressed even if it previously fell out of sync somehow. *I would guess by the user being clumsy or mischievous and pressing record over and over again really quickly*
Thanks to this new setup, it is possible to forgo recording all together in favor of having Record: on louden the volume before blasting the other peer with weasels and then have Record: off raise the volume even more before blasting the other peer with iguanas. Glorious.
Sadly, not a single aspect of the reporter's patch has remained, though oddly enough the first chunk in chan_sip was added just a few days ago in an unrelated issue.</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;">Use of both built-in and dynamic features applied separately were performed with the settings being applied both globally and to peers individually. Testing was also done to check that the default settings applied as intended.</pre>
</td>
</tr>
</table>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Bugs: </b>
<a href="https://issues.asterisk.org/jira/browse/ASTERISK-16507">ASTERISK-16507</a>
</div>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
<li>/trunk/channels/chan_sip.c <span style="color: grey">(348210)</span></li>
<li>/trunk/channels/sip/include/sip.h <span style="color: grey">(348210)</span></li>
<li>/trunk/configs/sip.conf.sample <span style="color: grey">(348210)</span></li>
<li>/trunk/main/features.c <span style="color: grey">(348210)</span></li>
</ul>
<p><a href="https://reviewboard.asterisk.org/r/1634/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>