<div><br></div><div>// My fix for the DTMF falsing problem is to make one change to the file dsp.c</div><div>// /usr/src/trunk/asterisk/main/dsp.c</div><div>// Change this line in dsp.c (find the line by searching for 26.0)</div>
<div>#define DTMF_TO_TOTAL_ENERGY ((digitmode & DSP_DIGITMODE_RELAXDTMF) ? 26.0 : 42.0)</div><div>// To look like this line</div><div>#define DTMF_TO_TOTAL_ENERGY ((digitmode & DSP_DIGITMODE_RELAXDTMF) ? 38.0 : 42.0)</div>
<div>// The result for our 2 repeaters, </div><div>// one on VHF using the USB fob, </div><div>// and the other on UHF using multiple RTCM's,</div><div>// is a reduction of DTMF falsing from hundreds per day to only 2 or 3 per day and </div>
<div>// no problems decoding DTMF.</div><div>// I do not turn off RADIO_RELAX because doing so caused problems with DTMF decode.</div><div>// The only problem with my fix is that I have to re-edit dsp.c every time I update.</div>
<div>// Remember to do the usual "makes" after editing this file.</div><div><br></div><br><div class="gmail_quote">On Sun, Jun 3, 2012 at 4:01 PM, Tim Sawyer <span dir="ltr"><<a href="mailto:tim.sawyer@me.com" target="_blank">tim.sawyer@me.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">First I would update from svn, might as well as you have to recompile anyway. The instructions to update from svn are at <a href="https://allstarlink.org/support.html#astupgrade" target="_blank">https://allstarlink.org/support.html#astupgrade</a><div>
<br></div><div>Before you do the make up grade edit /usr/src/astsrc/asterisk/menuselect.makeopts </div><div>change the line that says</div><div><br></div><div>MENUSELECT_CFLAGS=RADIO_RELAX LOADABLE_MODULES</div><div>to</div>
<div>MENUSELECT_CFLAGS=LOADABLE_MODULES</div><div><div>
<div style="word-wrap:break-word"><br></div><div style="word-wrap:break-word">then do make upgrade or make upgrade-acid as appropriate. </div><div style="word-wrap:break-word">--<br>Tim<br>:wq</div>
</div><div><div class="h5">
<br><div><div>On Jun 3, 2012, at 1:51 PM, Tim Sawyer wrote:</div><br><blockquote type="cite"><div style="word-wrap:break-word">I am one of those that found setting RADIO_RELAX off works much better. TT falsing has been reduced to near zero and decoding is still as fast as I can push the buttons. <div>
<br></div><div>One thing I found was that I had to turn on the PL filter. Before I did that TT decoding was unbearably show with RADIO_RELAX off. <br><div>
<div style="word-wrap:break-word">--<br>Tim<br>:wq</div>
</div>
<br><div><div>On Jun 3, 2012, at 12:48 PM, Jim Duuuude wrote:</div><br><blockquote type="cite"><span style="border-collapse:separate;font-family:Verdana;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;font-size:medium"><div style="font-size:10pt;font-family:Tahoma">
<div dir="ltr">This has nothing to do with the RTCM. The DTMF receiver is the same one that is used in all the other<br>channel drivers for the other types of interfaces also.<br><br>When the app_rpt stuff was first being developed (10+ years ago), the default parameters<br>
for the DTMF receiver seemed too "tight" for radio use. There were a number of combinations<br>that were found of receivers and transmitting devices (HT's mobiles, etc) that did not seem to<br>work reliably with the parameters the way they were, so we developed the "RADIO_RELAX" set<br>
of parameters, which are more "relaxed" then the normal ones.<br><br>As time has gone on, there have been cases where using these "relaxed" parameters have seemed<br>to do more harm then good. I dont know if your case is one of those. If you wish to try, I suggest<br>
re-compiling Asterisk with the RADIO_RELAX compile parameter turned off, and see if you like it<br>that way better. I can guarantee you that you will have less "falsing" if you do that. What I can not<br>guarantee is that you will get all the "real" digits decoded reliably (if you do that).<br>
<br>Jim WB6NIL<br><br><div><div></div><hr>From: <a href="mailto:adamson_alan@hotmail.com" target="_blank">adamson_alan@hotmail.com</a><br>To: <a href="mailto:app_rpt-users@ohnosec.org" target="_blank">app_rpt-users@ohnosec.org</a><br>
Date: Sun, 3 Jun 2012 15:26:06 -0400<br>Subject: [App_rpt-users] RTCM falsing DTMF<br><br><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px">
<span lang="en-us"><font face="Calibri">ok, so is it normal for the RTCM to get false DTMF when voice is doing over the link? I adjusted the RX audio so that the 2</font></span><span lang="en-us"><span> </span><font face="Calibri">lights</font></span><span lang="en-us"><font face="Calibri"><span> </span>were off with a 3khz tone generated from a service monitor.</font></span></div>
<p dir="LTR" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px"><span lang="en-us"></span></p><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px">
<span lang="en-us"><font face="Calibri">I see oh between 6-8 DTMF's detected over the voter channel during use…. How do you fix that issue?</font></span></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;padding-top:0px;padding-right:0px;padding-bottom:0px;padding-left:0px">
<span lang="en-us"><font face="Calibri">Alan</font></span><span lang="en-us"></span></div><br>_______________________________________________ App_rpt-users mailing list <a href="mailto:App_rpt-users@ohnosec.org" target="_blank">App_rpt-users@ohnosec.org</a> <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a></div>
</div>_______________________________________________<br>App_rpt-users mailing list<br><a href="mailto:App_rpt-users@ohnosec.org" target="_blank">App_rpt-users@ohnosec.org</a><br><a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a></div>
</span></blockquote></div><br></div></div>_______________________________________________<br>App_rpt-users mailing list<br><a href="mailto:App_rpt-users@ohnosec.org" target="_blank">App_rpt-users@ohnosec.org</a><br><a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
</blockquote></div><br></div></div></div></div><br>_______________________________________________<br>
App_rpt-users mailing list<br>
<a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a><br>
<a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
<br></blockquote></div><br>