[arm-allstar] disconnect from one way audio

Thu May 31 12:52:57 EST 2018

Brian,

 I am sure Dave will get back to you on this but as far as I know to date
this is the only micronode that has had this problem. We have tested with
other micronodes and with Mark and have not found any issues. I am not sure
what specifically would be wrong with that particular node. If you have any
version information on it let us know. Is it doing it with both permanent
and non-permanent connects?

As far as I am concerned here the one-way audio problem is fixed. I have
had zero issues since that fix went into place. The only place you are
going to have an issue is with connections to non-hamvoip nodes as far as
one way is concerned. In that case the one way could occur in one direction
but not the other. The detection and correction would be lacking on the
other end. This could also happen with hamvoip versions prior to V1.5 or
V1.5 versions that have not been updated in quite awhile. The one way audio
senses a loss of connection and disconnects and reconnects the node. This
happen so fast you may not even notice it.

*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Thu, May 31, 2018 at 12:58 PM, "Brian Marshall via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Hi All,
>
> David, sorry I missed your last email in my inbox. We did not resolve this,
> however we have been working around it. We have a member with a Hamvoip
> node that is about a year out of date (imaged in late 2017) which does not
> have this issue. So we connect the micro nodes to the really old hamvoip
> node and then connect that to our club node which is on the latest version
> as of this last monday.
>
> If we connect a micro node directly to the club node on the latest hamvoip
> software the node will be disconnected after 45 seconds with a one way
> audio error. During those 45 seconds we can confirm 2-way audio works fine,
> but the hamvoip node for some reason detects one way audio. Nobody we have
> discussed this with has been able to point us to a resolution.
>
> Let me know if I can help in any way. Happy to participate in
> troubleshooting.
>
> On Thu, May 31, 2018 at 10:51 AM, Scott Weis <kb2ear at kb2ear.net> wrote:
>
> > Did you ever figure this out, I'm getting the same thing with a node on
> the
> > same network segment. Not a micronode.
> >
> > Thanks & 73
> > de Scott KB2EAR
> >
> > -----Original Message-----
> > From: arm-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
> > "Brian Marshall via arm-allstar"
> > Sent: Tuesday, May 8, 2018 12:54 PM
> > To: David McGough <kb4fxc at inttek.net>
> > Cc: Brian Marshall <bmarshallbri at gmail.com>; Brian Marshall via
> > arm-allstar
> > <arm-allstar at hamvoip.org>
> > Subject: Re: [arm-allstar] disconnect from one way audio
> >
> > Sure thing. Can you send me your public key and I'll create an account
> for
> > you with sudo access?
> >
> > On Tue, May 8, 2018 at 10:53 AM, David McGough <kb4fxc at inttek.net>
> wrote:
> >
> > >
> > > Hi Brian,
> > >
> > > If you've got external ssh access enabled, I'd like to take a look at
> > > your node, at some point when a micro-node user is available for
> testing?
> > >
> > > 73, David KB4FXC
> > >
> > >
> > > On Tue, 8 May 2018, Brian Marshall wrote:
> > >
> > > > Hi David,
> > > >
> > > > Thanks for the reply. We have been working directly with Mark
> > > > Guibord,
> > > the
> > > > creator of micro-node and he is stumped. He has tested with multiple
> > > nodes
> > > > and consistently has the same result. Micro-node users have no issue
> > > > connecting to other hamvoip nodes, so this is something that is
> > > > specific with my node. I'm thinking it's a config issue, but I am
> > > > not enough of an asterisk guy to run that down. I am a linux
> > > > engineer but VOIP is not my wheel house so I'm scratching my head.
> > > >
> > > > Any advice would be greatly appreciated. If there's any further
> > > information
> > > > gathering or testing I can do to help please let me know.
> > > >
> > > > Thanks
> > > >
> > > > On Tue, May 8, 2018 at 10:22 AM, David McGough <kb4fxc at inttek.net>
> > > wrote:
> > > >
> > > > >
> > > > > Hi Brian,
> > > > >
> > > > > I've done testing here with micro-nodes and don't see any problems.
> > > Also,
> > > > > I've got a few micro-node users who connect to one of my hubs and
> > > > > have
> > > had
> > > > > no problems.
> > > > >
> > > > > So, I'm not sure what is happening.  The code which I'm using to
> > > > > test
> > > for
> > > > > one-way audio has been in the AllStar app_rpt module for a long
> > > > > time---I'm guessing at least 10 years.
> > > > >
> > > > > How many micro-node users are having this problem?  ...Also, have
> > > > > the problematic micro-node users connect to another hamvoip
> > > > > node/hub and
> > > check
> > > > > for disconnects.
> > > > >
> > > > >
> > > > > 73, David KB4FXC
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > On Tue, 8 May 2018, "Brian Marshall via arm-allstar" wrote:
> > > > >
> > > > > > Has anyone run in to this? I have some guys with a micro-node
> > > > > > nano
> > > that
> > > > > is
> > > > > > able to connect to our node but they get kicked after 45 seconds
> > > with the
> > > > > > following error.
> > > > > >
> > > > > > [May 7 18:34:00] ERROR[445]: app_rpt.c:18581 rpt: No link
> > > > > > messages from [2454] in 46 seconds -- One way audio??? Forcing
> > reconnect.
> > > > > >
> > > > > > However during that 45 seconds we can demonstrate there is in
> > > > > > fact 2
> > > way
> > > > > > audio as we can talk to each other over the link. Can anyone
> > > > > > point me towards what might be causing this? We are running the
> > > > > > latest hamvoip version but this has been going on for a few
> > > > > > months now. It seems to
> > > have
> > > > > > popped up at some point after a software update and has never
> > > > > > gone
> > > away
> > > > > > since.
> > > > > >
> > > > > > We have had several other folks with micro-nodes test and the
> > > behavior is
> > > > > > pretty consistent. I'm not sure if this is specific to
> > > > > > micro-nodes
> > > or if
> > > > > > there is some other condition causing it. We have on rare
> > > > > > occasion
> > > seen
> > > > > it
> > > > > > with other node types.
> > > > > >
> > > > > > We have no issues with people connecting via allstar or echolink
> > > directly
> > > > > > though.
> > > > > >
> > > > > > Any help, advice or direction would be greatly appreciated.
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> > --
> > Brian Marshall
> > +1-720-295-7324
> > KE0LTD
> > @pgp.mit.edu
> > <https://pgp.mit.edu/pks/lookup?op=get&search=0x100AB721E04E2412>
> > https://www.linkedin.com/in/bmarshallbri
> > _______________________________________________
> >
> > 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
> >
> >
>
>
> --
> Brian Marshall
> +1-720-295-7324
> KE0LTD
> @pgp.mit.edu
> <https://pgp.mit.edu/pks/lookup?op=get&search=0x100AB721E04E2412>
> https://www.linkedin.com/in/bmarshallbri
> _______________________________________________
>
> 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
>