<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/4592/">https://reviewboard.asterisk.org/r/4592/</a>
</td>
</tr>
</table>
<br />
<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 think this change is widening the scope of the inband_progress option beyond what it was intended to do. The intended purpose of inband_progress is to determine whether AST_CONTROL_RINGING should be handled by sending a 180 (out-of-band ringing) or 183 with early media (in-band ringing) to the caller. With this change, setting inband_progress to no also prevents any early media from being sent, which is likely not what people intend when they set the option.
However, the ability to prevent early media by transforming a progress indication into a 180 Ringing makes sense as something someone may want to do. I just think this behavior should be relegated to a separate option.</pre>
<br />
<p>- Mark Michelson</p>
<br />
<p>On April 6th, 2015, 6:32 p.m. UTC, Kevin Harwell wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: url('https://reviewboard.asterisk.org/static/rb/images/review_request_box_top_bg.ab6f3b1072c9.png'); background-position: left top; background-repeat: repeat-x; border: 1px black solid;">
<tr>
<td>
<div>Review request for Asterisk Developers.</div>
<div>By Kevin Harwell.</div>
<p style="color: grey;"><i>Updated April 6, 2015, 6:32 p.m.</i></p>
<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-24835">ASTERISK-24835</a>
</div>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt;">Repository: </b>
Asterisk
</div>
<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 issue started out as early media not playing in chan_sip. However, it was then reported that once the 'progressinband' option was set to 'yes' it would work, but that the default behavior was different than that of chan_pjsip. chan_pjsip's 'inband_progress' option defaults to 'no' as well, but it still sends a 183. It turns out chan_pjsip was always sending a 183 despite whatever the 'inband_progress' option was set to. Fixed it so chan_pjsip only sends a 183 if 'inband_progress' is set to 'yes'.</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;">Duplicated the issue with chan_pjsip always sending the 183. After the patch it will only send it when 'inband_progress' is set to 'yes'</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/13/channels/chan_pjsip.c <span style="color: grey">(434021)</span></li>
</ul>
<p><a href="https://reviewboard.asterisk.org/r/4592/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>