I might have a different situation here, I have full control of every node that is connected on our little private network. If I can’t have full control of the node they don’t get connected. Most of the node owners are not computer or Linux literate, so someone needs to help them out. I have a couple other Linux guys with full access to all the nodes so it’s not a one man effort. So far it is working great, 11 repeaters linked and 3 more just about to come online. We build the software for them here on the test bench and then they download the image file, put it in their pi and turn it on and the first comment is usually “the Audio is unreal!” Lol
Sent from my iPhone
So how do you identify which end of the connection is causing it and is there a fix ?
Sent from my Mobile TRS-80
Working correctly now, it was a remote node crontab error. Stupid mistake on my part lol
Thanks again
Bryan
Sent from my iPhone
That message can play if an
auto-connect or Permalink is trying to establish (or re-establish)
a connection. The most common occurrence I've witnessed is when
the network connection quality (Internet or otherwise) to/from the
affected site becomes poor. It confuses the system as to whether
or not the node is actually connected and in an attempt to make
sure, it tries or re-tries and then the message is played.
Kevin W3KKC
On 1/4/2018 10:27 AM, Steve Zingman wrote:
Check for a cron task that tries to connect.
Steve
On 1/4/2018 10:20 AM, Bryan Taylor
wrote:
I thought about doing that but I would like to find out why it
started happening. Apparently it’s been doing it for a couple of
days now, but I don’t know what could have caused it to start
doing it.
Bryan
Sent from my iPhone
Just delete the one recording and or
replace it with a low duration low volume beep.