<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/2183/">https://reviewboard.asterisk.org/r/2183/</a>
</td>
</tr>
</table>
<br />
<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 Mark Michelson.</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;">Have a look at the SIP project page that has been created here: https://wiki.asterisk.org/wiki/display/AST/New+SIP+channel+driver as well as its subpages.
At the moment, the content is pretty bare. This is because the project is not very far underway and so there isn't much to be able to put there right now.
A few notes:
The list of features on the project page is a list that more or less came off the top of my head and is supposed to represent a high level set of features. Feel free to let me know about things that should be added, but keep in mind that features listed there should be SIP-specific. We are not planning to do many changes to the media handling in Asterisk as of right now, so features like SRTP, STUN/TURN/ICE, and DTLS-SRTP are already provided by Asterisk's media handling and does not need to be addressed as a SIP feature (aside from potentially some SDP parsing).
The use cases are written from a *very* high level. For instance, the two-party call use case has dozens, if not hundreds, of variants. However, since these are not necessarily observable by Alice and Bob, they have not been included as separate use cases. So when evaluating use cases, information such as codecs in use, encryption of media, authentication, direct media, and NAT are irrelevant. Keep this in mind if you have additional use cases for me to document.
Please let me know what all can be added, removed, or clarified.</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/2183/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>