<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Ok, I've answered my own question. 
      Your do have to comment out the section in rpt.conf.<br>
      <br>
      LaRoy McCann, K5TW<br>
      <br>
      <br>
      On 1/22/2016 8:43 AM, LaRoy McCann wrote:<br>
    </div>
    <blockquote cite="mid:56A2401B.2050208@dtisp.com" type="cite">
      <meta content="text/html; charset=windows-1252"
        http-equiv="Content-Type">
      <div class="moz-cite-prefix">Doug,<br>
        Thanks,  I'll give it a try this weekend.<br>
        <br>
        What if the telemetry sections were in both .conf files?<br>
        Would the settings in the custom file redefine the variables
        since it would be read after rpt.conf?<br>
        <br>
        LaRoy McCann, K5TW<br>
        <br>
        <br>
        On 1/21/2016 6:59 PM, Doug Crompton wrote:<br>
      </div>
      <blockquote cite="mid:BLU171-W6738583C82B85EC58E3A89BAC40@phx.gbl"
        type="cite">
        <style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style>
        <div dir="ltr"><font style="" color="#000000"
            face="Tahoma,sans-serif">OK, here is a reasonable way to do
            it that seems to work well. There is a little setup but it
            should not take too long. Follow these steps -<br>
            <br>
            Put the attached script in /etc/asterisk/local<br>
            <br>
            Make it executable<br>
            <br>
            chmod 750 change_telemetry.sh<br>
            <br>
            Backup your rpt.conf file<br>
            <br>
            Make a new directory if it does not already exist in
            /etc/asterisk called custom<br>
            <br>
            Edit the primary rpt.conf file and copy (cut and paste or
            whatever) the telemetry section in entirety.<br>
            <br>
            Save the telemetry section you copied out of rpt.conf to
            /etc/asterisk/custom/telemetry.conf<br>
            <br>
            Also copy it to /etc/asterisk/custom/telemetry1    and  
            telemetry2 <br>
            <br>
            This assumes you will have two telemetry changes. If you
            will have more copy to more telemetry files telemetry3,
            telemetry4, etc.<br>
            <br>
            Go back to the rpt.conf file and either delete or comment
            (your choice) ALL lines in the telemetry section you just
            copied out. When you are done there should be no active
            telemetry section in rpt.conf<br>
            <br>
            Go to the end of the rpt.conf file and change the last line
            to this -<br>
            <br>
            #includeifexists custom/telemetry.conf<br>
            <br>
            Go to the /etc/asterisk/custom directory and edit the files
            for the different telemetry settings you want.
            telemetry.conf and telemetry1 should not be edited - they
            will be the stock files. Edit telemetry2, 3, 4 etc. however
            many different tone groups you want to define. You can have
            as many as you want, just give them consecutive numbers and
            remember them by number.<br>
            <br>
            Once the files are saved run the change_telemetry program.
            It is set at start to only accept  two files - telemetry1
            and 2 - change the MAX_FILE parameter in the script to the
            number of definitions you have (telemetryx files in the
            custom directory.) <br>
            <br>
            You can run the script manually to see how it works. It does
            not effect Allstar operation. You can change at any time.<br>
            <br>
            change_telemetry x        - where x equals the file number<br>
            <br>
            Once this is all working you can call the script either
            directly from a function, via the autopatch, cron, etc.<br>
            <br>
            function section example....<br>
            <br>
            811=cmd,/etc/asterisk/local/change_telemetry 1<br>
          </font><font style="" color="#000000" face="Tahoma,sans-serif">812=cmd,/etc/asterisk/local/change_telemetry

            2</font><br>
          <font style="" color="#000000" face="Tahoma,sans-serif"><font
              style="" color="#000000" face="Tahoma,sans-serif">813=cmd,/etc/asterisk/local/change_telemetry

              3<br>
              etc.<br>
              <br>
              then DTMF <br>
              <br>
              *811  - default telemetry<br>
              *812  - Telemetry values 2<br>
              etc.<br>
              <br>
              What this does.<br>
              <br>
               The telemetry section is removed from rpt.conf. rpt.conf
              is then setup to call telemetry.conf in the
              /etc/asterisk/custom directory. The change_telemetry.sh
              then copies different definition files to telemetry files
              to telemetry.conf based on a number. It then reloads
              rpt.conf and sends an audible message to the user.<br>
              <br>
              Things to remember - <br>
              <br>
              if you run setup again the rpt.conf file will be
              overwritten. You will have to delete the telemetry section
              and add the last line again.<br>
              <br>
              Always leave at least one file - preferably telemetry1 -
              as the default stock values.<br>
              <br>
              The mapping in rpt.conf should not need to be changed. For
              instance if unlinkct=ct2  and you wanted to change it you
              would change the ct2 definition in the telemetry section
              in one of the files.<br>
              <br>
              The change_telemetry script announces the change locally
              on the primary node given in the environment variable
              NODE1. If you want it to speak on a different node you
              need to change the node in the voice lines in the
              change_telemetry script.<br>
              <br>
              I hope this helps or at least gives you ideas of how to do
              it. Let me know how it works for you and if you have any
              questions I would be glad to answer them.<br>
              <br>
            </font></font><b><font style="font-size:16pt;" size="4">73
              Doug</font><font style="font-size:16pt;" size="4"><br>
            </font><font style="font-size:16pt;" size="4">WA3DSP</font><font
              style="font-size:16pt;" size="4"><br>
            </font><font style="font-size:16pt;" size="4"><a
                moz-do-not-send="true" class="moz-txt-link-freetext"
                href="http://www.crompton.com/hamradio"><a class="moz-txt-link-freetext" href="http://www.crompton.com/hamradio">http://www.crompton.com/hamradio</a></a></font></b><font
            style="font-size:16pt;" size="4"><br>
          </font><br>
          <br>
          <div>
            <hr id="stopSpelling">To: <a moz-do-not-send="true"
              class="moz-txt-link-abbreviated"
              href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
            From: <a moz-do-not-send="true"
              class="moz-txt-link-abbreviated"
              href="mailto:lmccann@dtisp.com">lmccann@dtisp.com</a><br>
            Date: Wed, 20 Jan 2016 15:29:57 -0600<br>
            Subject: Re: [arm-allstar] Courtesy tones<br>
            <br>
            <div class="ecxmoz-cite-prefix">Is there any way to
              dynamically change the courtesy tones?<br>
              Maybe thru the event management subsystem?<br>
              <br>
              Or is the only way to read the definitions from rpt.conf?<br>
              I know I could always use a script to edit rpt.conf and
              then reload, but was just hoping of some other way to do
              it.<br>
              <br>
              LaRoy McCann, K5TW<br>
              <br>
              <br>
              <br>
              On 1/20/2016 11:41 AM, LaRoy McCann wrote:<br>
            </div>
            <blockquote cite="mid:569FC6B6.4020409@dtisp.com">
              <div class="ecxmoz-cite-prefix">Doug,<br>
                <br>
                <b><i>remotetx</i></b>  That was what I was looking for.<br>
                <br>
                Thanks<br>
                <br>
                LaRoy McCann, K5TW<br>
                <br>
                On 1/20/2016 11:29 AM, Doug Crompton wrote:<br>
              </div>
              <blockquote
                cite="mid:BLU171-W76C0978975FC7576531C57BAC20@phx.gbl">
                <style><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}

.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}

--></style>
                <div dir="ltr"><font style="" color="#000000"
                    face="Tahoma,sans-serif">LaRoy,<br>
                    <br>
                      linkunkeyct  when connected and someone on the
                    network unkeys.  But your local radio unkey is set
                    by the remotetx tone group in the telemetry stanza.<br>
                    <br>
                    So if you change linkunkeyct you would not hear the
                    change unless someone else on the connected network
                    unkeys. You could test this by connecting two locals
                    nodes together.  That is why I mentioned it is
                    confusing because you expect it to change when you
                    are connected and unkey and it doesn't. Also always
                    remember to 'reload rpt' in the client after a
                    change.<br id="ecxFontBreak">
                  </font><br>
                  <b><font style="font-size:16pt;" size="4">73 Doug</font><font
                      style="font-size:16pt;" size="4"><br>
                    </font><font style="font-size:16pt;" size="4">WA3DSP</font><font
                      style="font-size:16pt;" size="4"><br>
                    </font><font style="font-size:16pt;" size="4"><a
                        moz-do-not-send="true"
                        class="moz-txt-link-freetext"
                        href="http://www.crompton.com/hamradio"><a class="moz-txt-link-freetext" href="http://www.crompton.com/hamradio">http://www.crompton.com/hamradio</a></a></font></b><font
                    style="font-size:16pt;" size="4"><br>
                  </font><br>
                  <br>
                  <div>
                    <hr id="ecxstopSpelling">To: <a
                      moz-do-not-send="true"
                      class="moz-txt-link-abbreviated"
                      href="mailto:arm-allstar@hamvoip.org"><a class="moz-txt-link-abbreviated" href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a></a><br>
                    From: <a moz-do-not-send="true"
                      class="ecxmoz-txt-link-abbreviated"
                      href="mailto:lmccann@dtisp.com">lmccann@dtisp.com</a><br>
                    Date: Wed, 20 Jan 2016 10:47:58 -0600<br>
                    Subject: [arm-allstar] Courtesy tones<br>
                    <br>
                    Ok, I've been racking my brain trying to figure this
                    out.<br>
                    <br>
                    The courtesy tone on a single node when a users
                    unkeys is <b><i>unlinkedct</i></b>.<br>
                    <br>
                    The courtesy tone changes when this node connects to
                    another node via the internet.<br>
                    What courtesy tone variable is used when the local
                    user unkeys and the two nodes are linked together?<br>
                    <br>
                    <br>
                    LaRoy McCann, K5TW<br>
                    <table style="border-top:1px solid #aaabb6;">
                      <tbody>
                        <tr>
                          <td style="width:105px;padding-top:15px;"> <a
                              moz-do-not-send="true"
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient"
                              target="_blank"><img
                                moz-do-not-send="true"
                                src="https://ipmcdn.avast.com/images/logo-avast-v1.png"
                                style="width:90px;height:33px;"></a> </td>
                          <td
                            style="width:470px;padding-top:20px;color:#41424e;font-size:13px;font-family:Arial,

                            Helvetica, sans-serif;line-height:18px;">This

                            email has been sent from a virus-free
                            computer protected by Avast. <br>
                            <a moz-do-not-send="true"
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient"
                              target="_blank" style="color:#4453ea;">www.avast.com</a>
                          </td>
                        </tr>
                      </tbody>
                    </table>
                    <br>
                    _______________________________________________
                    arm-allstar mailing list <a moz-do-not-send="true"
                      class="ecxmoz-txt-link-abbreviated"
                      href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>
                    <a moz-do-not-send="true"
                      class="ecxmoz-txt-link-freetext"
                      href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar"
                      target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a>
                    Visit the BBB and RPi2 web page - <a
                      moz-do-not-send="true"
                      class="moz-txt-link-freetext"
                      href="http://hamvoip.org"><a class="moz-txt-link-freetext" href="http://hamvoip.org">http://hamvoip.org</a></a></div>
                </div>
                <br>
                -- <br>
                This message has been scanned for viruses and <br>
                dangerous content by the <a moz-do-not-send="true"
                  href="http://www.dtisp.com/" target="_blank"><b>DTISP
                    MailScanner</b></a>, and is <br>
                believed to be clean. <br>
                <fieldset class="ecxmimeAttachmentHeader"></fieldset>
                <br>
                <pre>_______________________________________________

arm-allstar mailing list
<a moz-do-not-send="true" class="ecxmoz-txt-link-abbreviated" href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>
<a moz-do-not-send="true" class="ecxmoz-txt-link-freetext" href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a>

Visit the BBB and RPi2 web page - <a moz-do-not-send="true" class="ecxmoz-txt-link-freetext" href="http://hamvoip.org" target="_blank">http://hamvoip.org</a></pre>
              </blockquote>
              <br>
              <table style="border-top:1px solid #aaabb6;">
                <tbody>
                  <tr>
                    <td style="width:105px;padding-top:15px;"> <a
                        moz-do-not-send="true"
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient"
                        target="_blank"><img moz-do-not-send="true"
                          src="https://ipmcdn.avast.com/images/logo-avast-v1.png"
                          style="width:90px;height:33px;"></a> </td>
                    <td
                      style="width:470px;padding-top:20px;color:#41424e;font-size:13px;font-family:Arial,

                      Helvetica, sans-serif;line-height:18px;">This
                      email has been sent from a virus-free computer
                      protected by Avast. <br>
                      <a moz-do-not-send="true"
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient"
                        target="_blank" style="color:#4453ea;">www.avast.com</a>
                    </td>
                  </tr>
                </tbody>
              </table>
              <br>
              -- <br>
              This message has been scanned for viruses and <br>
              dangerous content by the <a moz-do-not-send="true"
                href="http://www.dtisp.com/" target="_blank"><b>DTISP
                  MailScanner</b></a>, and is <br>
              believed to be clean. <br>
              <fieldset class="ecxmimeAttachmentHeader"></fieldset>
              <br>
              <pre>_______________________________________________

arm-allstar mailing list
<a moz-do-not-send="true" class="ecxmoz-txt-link-abbreviated" href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>
<a moz-do-not-send="true" class="ecxmoz-txt-link-freetext" href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a>

Visit the BBB and RPi2 web page - <a moz-do-not-send="true" class="ecxmoz-txt-link-freetext" href="http://hamvoip.org" target="_blank">http://hamvoip.org</a></pre>
            </blockquote>
            <br>
            <table style="border-top:1px solid #aaabb6;">
              <tbody>
                <tr>
                  <td style="width:105px;padding-top:15px;"> <a
                      moz-do-not-send="true"
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient"
                      target="_blank"><img moz-do-not-send="true"
                        src="https://ipmcdn.avast.com/images/logo-avast-v1.png"
                        style="width:90px;height:33px;"></a> </td>
                  <td
                    style="width:470px;padding-top:20px;color:#41424e;font-size:13px;font-family:Arial,

                    Helvetica, sans-serif;line-height:18px;">This email
                    has been sent from a virus-free computer protected
                    by Avast. <br>
                    <a moz-do-not-send="true"
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient"
                      target="_blank" style="color:#4453ea;">www.avast.com</a>
                  </td>
                </tr>
              </tbody>
            </table>
            <br>
            _______________________________________________ arm-allstar
            mailing list <a moz-do-not-send="true"
              class="moz-txt-link-abbreviated"
              href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>
            <a moz-do-not-send="true" class="moz-txt-link-freetext"
              href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a>
            Visit the BBB and RPi2 web page - <a moz-do-not-send="true"
              class="moz-txt-link-freetext" href="http://hamvoip.org">http://hamvoip.org</a></div>
        </div>
        <br>
        -- <br>
        This message has been scanned for viruses and <br>
        dangerous content by the <a moz-do-not-send="true"
          href="http://www.dtisp.com/"><b>DTISP MailScanner</b></a>, and
        is <br>
        believed to be clean. <br>
        <fieldset class="mimeAttachmentHeader"></fieldset>
        <br>
        <pre wrap="">_______________________________________________

arm-allstar mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a>

Visit the BBB and RPi2 web page - <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://hamvoip.org">http://hamvoip.org</a></pre>
      </blockquote>
      <br>
      <table style="border-top: 1px solid #aaabb6; margin-top: 30px;">
        <tbody>
          <tr>
            <td style="width: 105px; padding-top: 15px;"> <a
                moz-do-not-send="true"
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient"
                target="_blank"><img moz-do-not-send="true"
                  src="https://ipmcdn.avast.com/images/logo-avast-v1.png"
                  style="width: 90px; height:33px;"></a> </td>
            <td style="width: 470px; padding-top: 20px; color: #41424e;
              font-size: 13px; font-family: Arial, Helvetica,
              sans-serif; line-height: 18px;">This email has been sent
              from a virus-free computer protected by Avast. <br>
              <a moz-do-not-send="true"
href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient"
                target="_blank" style="color: #4453ea;">www.avast.com</a>
            </td>
          </tr>
        </tbody>
      </table>
      <br>
      -- <br>
      This message has been scanned for viruses and
      <br>
      dangerous content by the
      <a moz-do-not-send="true" href="http://www.dtisp.com/"><b>DTISP
          MailScanner</b></a>, and is
      <br>
      believed to be clean.
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________

arm-allstar mailing list
<a class="moz-txt-link-abbreviated" href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>
<a class="moz-txt-link-freetext" href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a>

Visit the BBB and RPi2 web page - <a class="moz-txt-link-freetext" href="http://hamvoip.org">http://hamvoip.org</a></pre>
    </blockquote>
    <br>
  
 <table style="border-top: 1px solid #aaabb6; margin-top: 30px;">
        <tr>
                <td style="width: 105px; padding-top: 15px;">
                        <a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank"><img src="https://ipmcdn.avast.com/images/logo-avast-v1.png" style="width: 90px; height:33px;"/></a>
                </td>
                <td style="width: 470px; padding-top: 20px; color: #41424e; font-size: 13px; font-family: Arial, Helvetica, sans-serif; line-height: 18px;">This email has been sent from a virus-free computer protected by Avast. <br /><a href="https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient" target="_blank" style="color: #4453ea;">www.avast.com</a>
                </td>
        </tr>
 </table>
</body>
</html>