<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/4328/">https://reviewboard.asterisk.org/r/4328/</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;">* "The transport type from above is used to determine which SRV record to look up. This means that the original URI *must* include the transport type for TCP and TLS types."
What if the URI is a SIPS URI? Does that have any bearing on transport selection?
* "The first configured transport matching the transport type and address family is selected"
What does this mean? Can a user influence which transport is "first" ?
* I really can't make sense of the "Multi-homed Transport Selection" section. Specifically, what is meant by "Source matches source in message" ?
* In the "connection-less protocol with maddr" section, what does "transport type" refer to? I assume it's a ;transport parameter from a URI, but which URI? Same goes for the "connection-less protocol without rport" section.
* "Configure a transport for each interface. The default transport will be the first one you choose."
I don't understand that second sentence. Does that mean the first transport in the configuration file is the default transport?
* Some "why" statements regarding the strategies for IPv4 and IPv6 would be useful. Why shouldn't an IPv6 wildcard be used, for instance?</pre>
<br />
<p>- Mark Michelson</p>
<br />
<p>On January 12th, 2015, 1:33 p.m. UTC, Joshua Colp 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 Joshua Colp.</div>
<p style="color: grey;"><i>Updated Jan. 12, 2015, 1:33 p.m.</i></p>
<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 transport selection process of PJSIP (and by extension some of our own logic) can be a dark dark thing. To help illuminate what happens I have created a wiki page[1] which goes through (based on the message type) the process by which a transport is chosen and how it can potentially change.
Stuff to look at:
1. Is this detailed enough?
2. Can you follow it? If not, how could it be made clearer?
3. Are there additional common issues that should be covered?
[1] https://wiki.asterisk.org/wiki/display/~jcolp/Transport+Selection</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;">I opened the wiki page. It opened.</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/4328/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>