<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Larry,<br>
    The order of the codecs in the list, in the order specified by the
    allow statements. I think the question stems from in the fact that
    at the top of the Drupal the explanation is for the general section
    of iax.conf. Further down the where the radio stanza is explained,
    the order is explained.<br>
    <br>
    73, Steve N4IRS<br>
    <br>
    <div class="moz-cite-prefix">On 03/08/2017 03:03 AM, larry wrote:<br>
    </div>
    <blockquote
cite="mid:rFMYu.2240ad5187.c8c2e3e4-286c-419e-d2d0-6dd531cb332a@n7fm.com"
      type="cite">
      <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
      Steve,<br>
      <br>
      Since the 2 links referred to have GSM - on the Drupal link listed
      as the first codec and the Github link lists GSM codec last in the
      allow sequence. <br>
      I need to ask when nodes begin negotiating is it done using the
      order of the codec in the allow list? <br>
      <br>
      Larry - N7FM<br>
      <br>
      <div class="moz-cite-prefix">On 03/07/2017 07:18 PM, Tim Sawyer
        wrote:<br>
      </div>
      <blockquote
cite="mid:CAG3ht9tJA5ttXVwW6gBroGeQV-9fdRSrfbpEcVDZTOZxfi_89g@mail.gmail.com"
        type="cite">
        <div dir="ltr">This may be of interest as well: <a
            moz-do-not-send="true"
            href="http://docs.allstarlink.org/drupal/node/15">http://docs.allstarlink.org/drupal/node/15</a></div>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Tue, Mar 7, 2017 at 10:15 AM,
            Steve Zingman <span dir="ltr"><<a moz-do-not-send="true"
                href="mailto:szingman@msgstor.com" target="_blank">szingman@msgstor.com</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">Here is
              a link to the default iax.conf in DIAL<br>
              <br>
              <<a moz-do-not-send="true"
                href="https://github.com/N4IRS/AllStar/blob/master/configs/iax.conf"
                rel="noreferrer" target="_blank">https://github.com/N4IRS/AllS<wbr>tar/blob/master/configs/iax.<wbr>conf</a>><br>
              <br>
              73, Steve N4IRS<span class="im HOEnZb"><br>
                <br>
                On 3/7/2017 12:59 PM, Benjamin L. Naber wrote:<br>
                <blockquote class="gmail_quote" style="margin:0 0 0
                  .8ex;border-left:1px #ccc solid;padding-left:1ex">
                  Interesting to learn some of the workings of iax.conf.<br>
                  <br>
                  I'm aware of the rest, however, I would encourage
                  iax.conf is modified to have the following priorities
                  for every connection stanza:<br>
                  ulaw<br>
                  g726aal2<br>
                  gsm<br>
                  <br>
                  this is to ensure audio quality is better than IRLP
                  and echo-stink. If you cannot tell the difference,
                  listen to a conversation on a local repeater, and the
                  same conversation with the convenient delay over IRLP
                  or echo-stink.<br>
                  <br>
                  You may then remember in days-past of analog cellular
                  listening to the person on the other end had more body
                  and fidelity.<br>
                  <br>
                  Regarding bandwidth, be it a DSL or mobile connection,
                  this should be a non-issue. Even 1G cellular data
                  connection will support two full-duplex uLaw streams.<br>
                  <br>
                  For hub nodes, 30 ulaw streams is right around
                  2.25Mbits. If this is a concern, perhaps the owner of
                  the hub should really consider putting the node
                  elsewhere. That's like trying to put a Pinto engine in
                  my E-350 and expecting it to work the same.<br>
                  <br>
                  Considering jitter and packet loss if it is thought a
                  higher bandwidth codec will cause this, such is not
                  the case. This is the cause of little or no
                  implementation of Qos/ToS in the WAN facing side of a
                  router. There are other external considerations, but
                  those are outside the scope of this thread.<br>
                  <br>
                  While on that subject a brief description of an
                  example is the node at my home. My connection,
                  fortunately, has maintained +25Mbps down and 5Mbps up,
                  I've have zero issues with jitter and packet loss with
                  QoS implemented, even while the kids are watching
                  netflix, skyping, and watching something on
                  youtube.... all at the same time.<br>
                  <br>
                  <br>
                </blockquote>
                <br>
              </span>
              <div class="HOEnZb">
                <div class="h5"> ______________________________<wbr>_________________<br>
                  App_rpt-users mailing list<br>
                  <a moz-do-not-send="true"
                    href="mailto:App_rpt-users@lists.allstarlink.org"
                    target="_blank">App_rpt-users@lists.allstarlin<wbr>k.org</a><br>
                  <a moz-do-not-send="true"
href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users"
                    rel="noreferrer" target="_blank">http://lists.allstarlink.org/c<wbr>gi-bin/mailman/listinfo/app_rp<wbr>t-users</a><br>
                  <br>
                  To unsubscribe from this list please visit <a
                    moz-do-not-send="true"
href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users"
                    rel="noreferrer" target="_blank">http://lists.allstarlink.org/c<wbr>gi-bin/mailman/listinfo/app_rp<wbr>t-users</a>
                  and scroll down to the bottom of the page. Enter your
                  email address and press the "Unsubscribe or edit
                  options button"<br>
                  You do not need a password to unsubscribe, you can do
                  it via email confirmation. If you have trouble
                  unsubscribing, please send a message to the list
                  detailing the problem. </div>
              </div>
            </blockquote>
          </div>
          <br>
          <br clear="all">
          <div><br>
          </div>
          -- <br>
          <div class="gmail_signature" data-smartmail="gmail_signature">
            <div dir="ltr">
              <div>
                <div dir="ltr">
                  <div>--<br>
                  </div>
                  <div>Tim</div>
                </div>
              </div>
            </div>
          </div>
        </div>
        <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">_______________________________________________
App_rpt-users mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:App_rpt-users@lists.allstarlink.org">App_rpt-users@lists.allstarlink.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a>

To unsubscribe from this list please visit <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. </pre>
      </blockquote>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
App_rpt-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:App_rpt-users@lists.allstarlink.org">App_rpt-users@lists.allstarlink.org</a>
<a class="moz-txt-link-freetext" href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a>

To unsubscribe from this list please visit <a class="moz-txt-link-freetext" href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. </pre>
    </blockquote>
    <br>
  </body>
</html>