[arm-allstar] Cut off transmissions

[Nathaniel Biser]

Doug,

My apologies for cutting you off this morning, but the audio gaps in your
transmissions were so horrible that I couldn't continue the QSO. Thanks for
helping me fix the supermon login to asterisk manager issue I was having.
It seems though, by fixing the login to asterisk manager issue, we
exacerbated my transmission/audio cutoff issue.

I was running my pi via wifi, I switched it over and configured it to run
wired to my router to see if it was my wifi connection that was causing the
transmission cutoff issue. (When the pi was wireless, it was literally
sitting on top of my wifi router anyway, but maybe switching to wired would
fix my issue?) it had no effect.

I still have the same problem but I think I found the cause. Here's my step
sequence:

1. On the lsnodes page, I clicked "Seatch/Command another node"

2. Typed in the remote node (27225, or whatever), selected the CONNECT
command from the drop down menu, then I clicked submit.

3. I switch over to the Supermon page and at the bottom (where the node
information is that indicates what node your connected to, link state,
etc). The link state says CONNECTING, then 4 seconds later it says
ESTABLISHED. 4 seconds later it flips back to CONNECTING, then 4 seconds
later ESTABLISHED, then 4 seconds later, CONNECTING, etc. it does this over
and over without end at exactly 4 second intervals .

4. I disconnected the node via the lsnodes->search/command another node
menus; the same pages I used to connect the node in the first place.

5. On the supermon page, I enter the node number in the box at the top/left
of the screen, and click the connect button.

6. I CONNECT AND STAY CONNECTED! Audio isn't cutting in and out haphazardly
while monitoring or in QSO.

I am not sure what the difference is between the two methods of connecting
to a node, but obviously I'm going to use the supermon page to
connect/disconnect for now as this seems to relieve my transmission/receive
cutoff issue.

It has been consistently connected without issue now and it appears my
issue is resolved. I'll monitor it and report if I have the issue again.

Any ideas as to why? The steps I outlined above are repeatable with the
same results each time.

-Nate
KC3HOZ



On Wed, May 10, 2017 at 10:14 PM "Doug Crompton via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Nate,
>
>    If only you are experiencing it and it appears that way then it could be
> a number of things. You have I think ruled out the Internet. The other
> thing to look for is your node radio transmitting when it drops out. That
> is does it continue to transmit. Both the USB FOB and the radio probably
> have LED's to show transmitting. If they are on and you hear the dropout
> then perhaps there is a problem in the audio to the radio from the FOB or
> maybe it is a PL issue. You could try turning off PL on receive on the
> radio you are using to talk to your node. Another possible problem is TX
> timeout. Is it possible you have the txtimeout set too short on the node
> radio? It should be at least 3 minutes.
>
> It will require some troubleshooting to determine the problem. What node
> radio are you using? Does the TX light on the FOB and/or radio go off when
> you hear the interruption?
>
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
> On Wed, May 10, 2017 at 9:29 PM, "Nathaniel Biser via arm-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > I've been monitoring the 27225 philly hub node for a while and every so
> > often I hear transmissions get unexpectedly cut off.  I'll be listening
> to
> > two people conversing and sometimes both of their transmissions are cut
> off
> > prematurely when they are conversing back and forth.  The two parties
> don't
> > seem to notice it, but for me it is highly annoying. it doesn't happen
> all
> > the time and it is very intermittent
> >
> > Does this happen to anyone else monitoring?  Is there a setting that I
> can
> > change to mitigate this?
> > I do have high speed intetnet, and there wasn't any heavy traffic on it
> > during the times I experienced this.
> >
> > Thanks,
> >
> > -Nate
> > KC3HOZ
> > _______________________________________________
> >
> > 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
>