[arm-allstar] disconnect from one way audio

[Brian Marshall]

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