<div dir="ltr"><div><div>Following from:<br><a href="http://www.en.voipforo.com/IAX/IAXvsSIP.php">http://www.en.voipforo.com/IAX/IAXvsSIP.php</a><br><br><strong>If SIP is using a server</strong> signaling messages always pass through the server but <strong>audio
messages (RTP flow) can travel end to end without passing through the
server. In IAX, signaling and data must pass always through IAX server. </strong>This increases the bandwidth need by the IAX servers when there are many simultaneous calls.<strong><br>
<br><br></strong></div>This is a big drawback of IAX it seems, especially in a mesh setup, where in many cases, the available bandwidth between clients may be higher via direct node routes compared with the bandwidth via the server route. It seems SIP will utilize the network more efficiently in a mesh topology. <br><br></div>Yesterday we were testing this on the server, and two nodes with three client. The data was being sent directly client -- node -- node -- client, and virtually no bandwidth was being used on the server. :)<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Oct 15, 2016 at 5:07 AM, Anish Mangal <span dir="ltr"><<a href="mailto:anishmg@umich.edu" target="_blank">anishmg@umich.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Will look into IAX2. Is it supported by apps on different clients? For SIP, there are usually many client options available on various platforms.<br></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Fri, Oct 14, 2016 at 9:22 PM, Sameer Verma <span dir="ltr"><<a href="mailto:sverma@sfsu.edu" target="_blank">sverma@sfsu.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">What server/service are you using? Look at IAX2 as well. Usually IAX2 does better on networks because unlike SIP, session initiation and voice call happen on the same port.</p><span class="m_-647112329684591509HOEnZb"><font color="#888888">
<p dir="ltr">Sameer</p></font></span><div class="m_-647112329684591509HOEnZb"><div class="m_-647112329684591509h5">
<div class="gmail_extra"><br><div class="gmail_quote">On Oct 14, 2016 4:48 AM, "Anish Mangal" <<a href="mailto:anishmg@umich.edu" target="_blank">anishmg@umich.edu</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi, <br><br></div>A SIP server on the XSCE will allow for VOIP services (audio, video, text). There are numerous SIP clients on various platforms so it seems a good protocol and standard to build upon. <br><br></div>I have already included a SIP server in the upcoming deployment of XSCE and mesh in Spiti, north India. <br><br></div>Thoughts?<br><div><div><div><div><br>Best, <br></div><div><div class="m_-647112329684591509m_-1099847860933295132m_-3540975107822173674gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Anish<br></div><div><br><br></div></div></div>
</div></div></div></div></div>
</blockquote></div></div>
</div></div></blockquote></div><br><br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br><div class="m_-647112329684591509gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Anish<br></div><div><br><br></div></div></div>
</font></span></div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Anish<br></div><div><br><br></div></div></div>
</div>