[arm-allstar] multiple echo link connections and "under water" audio

[Douglas Goree]

I have found using echolink on android AT&T using vpn makes it work a
lot better, really good. I don't know if vpn can be put on Allstar though.

On Fri, Feb 14, 2020 at 9:56 PM "Joe KD2NFC via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> I don’t know if this is the same underwater sound I hear at times but if
> you sit on the WINS system long enough you hear folks with bad audio from
> their allstar nodes. Garbled, underwater sounding audio. Others on that
> system describe it as it packet loss.
>
> Joe
> KD2NFC
>
>
> Sent from my iPhone
>
> > On Feb 14, 2020, at 7:53 PM, David McGough via ARM-allstar <
> arm-allstar at hamvoip.org> wrote:
> >
> > 
> >
> > I'll try to reproduce this audio issue over the next several days.
> >
> > If anyone has some active nets where this issue is happening, I'll try
> to
> > link in via echolink and have a listen.
> >
> > Also, if any user can link a HamVoIP system into one of these nets,
> using
> > chan_echolink, and capture some audio that might be useful. Please
> record
> > the audio file using PCM (uLAW). That is accomplished by setting the
> > rpt.conf node parameter: archivetype=pcm
> >
> > 73, David KB4FXC
> >
> >
> >
> >> On Fri, 14 Feb 2020, "Patrick Perdue via ARM-allstar" wrote:
> >>
> >> I am experiencing it on a rPI 4 1GB, also tested with the same results
> > on a rPi 2, and same with a stock ASL server on x64 VPS.
> >
> > On 2/14/2020 3:00 PM, "Kevin Custer via ARM-allstar" wrote:
> >> I have had the "underwater" sounding audio issue with certain X86
> >> servers using DIAL.  It usually occurs after the node has sit idle for
> >> some time, and usually presents this issue for a few transmissions
> >> then clears up.  The fix was to move to different hardware.  I've
> >> never experienced it on a RPi no matter the distribution.
> >>
> >> Kevin W3KKC
> >>
> >>> On 2/14/2020 10:41 AM, "David McGough via ARM-allstar" wrote:
> >>> This isn't typical of what I've heard when listening to nets with many
> >>> echolink users, so I'm curious as to what the cause is??
> >>>
> >>> Do remember that the HamVoIP distro is radically different from ASL,
> >>> from
> >>> a software perspective. ASL or any AllStar running on a cloud-hosted
> VPS
> >>> is the WORST CASE scenario for bad audio issues. So, don't make a
> >>> generalization assuming that if there is a problem with VPS hosted ASL,
> >>> there will also be the same problems with HamVoIP running on a
> dedicated
> >>> RPi3 or RPi4 board.
> >>>
> >>> Do you know of a repeatable scenario where bad quality echolink audio
> >>> can
> >>> be produced?
> >>>
> >>> 73, David KB4FXC
> >>
> >> _______________________________________________
> >>
> >> 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/4 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/4 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/4 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/4 web page - http://hamvoip.org