<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi Doug,<div><br></div><div>I was afraid that would be your response..</div><div><br></div><div>Oh well. I will "educate" the offending node owner. Maybe turn on the rxtimeout since it's running a version that's capable of it.</div><div><br></div><div>73,</div><div><br></div><div>Lito KI9H<br><br><div><hr id="stopSpelling">To: arm-allstar@hamvoip.org<br>Date: Fri, 19 Aug 2016 17:36:19 -0400<br>Subject: Re: [arm-allstar] node lockups<br>From: arm-allstar@hamvoip.org<br>CC: doug@crompton.com<br><br>
<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">Lito,<br><br> This is a common problem and we have helped a bit in the new code with an rxtimeout command that limits the amount of COS time. However this new code would have to be installed at each node connected to you and it would only limit the duration of the event to whatever the timeout was set to and not eliminate it entirely.<br><br>The best thing to do is educate those who connect and if there are repeat offenders ban them from connecting. The problem is almost always a person that has turned off or physically disconnected their radio while connected to you. Radios that go high on COS would be the worst offenders. If you have carrierfrom=usb then a high signal will mimic COS. The COS line is pulled high internally in the cm108/119 chip. Simply pulling out the radio side of the interface would make COS go valid as would in most cases turning off the radio.<br><br>Whenever you are connected to somewhere you need to be aware of this. Never turn off or physically disconnect a radio. Disconnect (*76) from everywhere first.<br><br>Doing this on the server (hub) side is a little more difficult. We briefly looked into it and may have a better solution in the future but for now education is your best tool.<br><br></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">http://www.crompton.com/hamradio</font></b><font style="font-size:16pt;" size="4"><br></font><br><br><div><hr id="ecxstopSpelling">To: arm-allstar@hamvoip.org<br>Date: Fri, 19 Aug 2016 13:38:12 -0700<br>Subject: [arm-allstar] node lockups<br>From: arm-allstar@hamvoip.org<br>CC: tolitski@hotmail.com<br><br>
<style><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}
--></style>
<div dir="ltr">I have a hub running on a virtual server and that's where most of the Pi nodes connect to. <div>A couple of times now I wake up and one of the nodes that connected would be "locked up"</div><div>Is there a dial plan or anything I can do to automate "muting" or disconnecting the offending node?</div><div><br></div><div>Any help is appreciated.</div><div><br></div><div>73,</div><div><br></div><div>Lito KI9H</div><div>formerly KK6OOS</div> </div>
<br>_______________________________________________
arm-allstar mailing list
arm-allstar@hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
Visit the BBB and RPi2 web page - http://hamvoip.org</div> </div>
<br>_______________________________________________
arm-allstar mailing list
arm-allstar@hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
Visit the BBB and RPi2 web page - http://hamvoip.org</div></div> </div></body>
</html>