[arm-allstar] ECHO and Cache
David
david at kg5rdf.com
Fri Nov 24 15:39:59 EST 2017
I guess, I was not clear. This has nothing to do with private nodes. The one issue was a "," and was corrected, After 30 minutes not 30 seconds the node stop hearing. Thanks for answering the question about the cache.
The second issue occurred after upgrading the node, so I was asking if repeater tail setting could cause Simple-usb Echo mod to get confused.
Thanks David
Sent from my T-Mobile 4G LTE Device
-------- Original message --------From: Doug Crompton via arm-allstar <arm-allstar at hamvoip.org> Date: 11/24/17 12:48 PM (GMT-06:00) To: ARM Allstar <arm-allstar at hamvoip.org> Cc: Doug Crompton <wa3dsp at gmail.com> Subject: Re: [arm-allstar] ECHO and Cache
Dave,
When you change things in any of the config files it could case other
issues so you have to be aware of what you are changing. There is no cache
that should take 30 seconds to complete a command unless it was held off by
something like COS. If you have something that works and then you change
something and it does not work then try going back to the way it was
before. It is very hard to troubleshoot a problem not knowing exactly what
you did to cause the problem.
You need to have an understanding of how things route and how to add
additional and private nodes to Allstar. Even I have been guilty of doing
things in a hurry and not getting it right the first time. Routing of
private nodes requires planning the path and then setting up everything
properly in the various config files. There is a howto on that at the
hamvoip.org web page.
The Asterisk client is the best place to go to see what is going on. Open a
client window at BOTH the connecting and connecting to ends and see what is
happening when you attempt the connect. For instance if you see no response
in the log at the end you are trying to connect to then your connect is
never reaching there. This gives you a clue as to what is happening. It
could be a port forwarding issue or an improper routing statement at the
source end. In another case if your connect attempt shows up but is
rejected it would show an error that would give a clue as to what is
happening. When you ask for help here we need to know this information to
better help in the troubleshooting process. Otherwise we are just guessing.
*73 Doug*
*WA3DSP*
*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
On Fri, Nov 24, 2017 at 11:32 AM, "David via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
> I am going to create some new images for two of my nodes, but wanted to
> understand if I created my two issues:
> - One of my nodes using usb-simple tune, Echo, locks into a kerchunk loop
> and no echo audio heard. I did change the value for repeater tail, in the
> code, several revisions back.
> - I have had issues connecting one node to another. Node x can connect to
> node y, but y not to x. When I was connecting my AREDN private nodes to my
> public nodes yesterday, I found a "," instead of a "." in my multi server
> code. Fixed it and y can connect to x now, but disconnect input keyup after
> 30 minutes, but output keyup functions. When I go back to x connecting to
> y, everything functions fine. Does all-star servers have a cache?
> Thanks David
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
_______________________________________________
arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
Visit the BBB and RPi2/3 web page - http://hamvoip.org
More information about the arm-allstar
mailing list