<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/1987/">https://reviewboard.asterisk.org/r/1987/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On June 14th, 2012, 2:24 p.m., <b>Mark Michelson</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;">The only thing I think might be missing here is a compatibility callback for the format. Say for instance that Asterisk is offered an H.263 stream with attributes A, B, and C by endpoint 1. So Asterisk would in turn offer an H.263 stream to endpoint 2 with attributes A, B, and C as well. Now, say that Asterisk receives an SDP answer from endpoint 2 where only attributes A and C are present in the H.263 stream.
With what we have right now, I imagine we'd just send an answer to endpoint 1 with attributes A and C. However, if there were some way for the format to say that a stream with A, B, and C is compatible with a stream with only A and C, then Asterisk could respond to endpoint 1 with an answer of attributes A, B, and C. Would this be desirable?</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;">It already exists in the existing API, yarrrrrr.</pre>
<br />
<p>- Joshua</p>
<br />
<p>On June 12th, 2012, 11:42 a.m., Joshua Colp 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 Joshua Colp.</div>
<p style="color: grey;"><i>Updated June 12, 2012, 11:42 a.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;">I've put together two small wiki pages at the following URLs:
https://wiki.asterisk.org/wiki/display/~jcolp/Additional+Media+Attributes
https://wiki.asterisk.org/wiki/display/~jcolp/Media+Attribute+Knowledge
They describe the attributes needed to ensure pretty rockin' video calls and also to move format attribute knowledge out of chan_sip into a separate module. The framework is pretty much there, it just needs to be extended slightly.
Since these are small I don't expect that many comments.</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;">
</ul>
<p><a href="https://reviewboard.asterisk.org/r/1987/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>