[arm-allstar] Bridging Allstar to an Echolink Proxy-enabled node
Mike Sullivan
kn4imu at gmail.com
Fri May 3 01:19:09 EDT 2019
I swore I sent it before.. but I have been buried in work the past few
weeks so short term memory is non existent for me.
We have a 12/1 cable connection at our tower, not super fast but way more
than we need for effective ASL/EL use. After a couple times, you can
connect to the node, but we never had an issue when using an RF based
Windows setup through a proxy.. I even have problems and I have a home
based proxy server I’ve used client side since we first started Echolink.
Doesn’t change with home wi-fi, cellular, etc.
I’m all for that idea.. but I have a feeling the same issue will exist
using that method as well. It comes with the PITA of Echolink being peer to
peer, I’m sure. I would love to know why Echolink Proxy is not easily
doable.
Mike
On Fri, May 3, 2019 at 01:13 "Doug Crompton via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:
> Mike,
>
> I think I answered this before but maybe you did not see it. Unless you
> have a poor internet connection I would have no idea why your Echolink
> would be operating so poorly. Many other use Echolink without those
> problems.
>
> I think I suggested before that you have another site within your area host
> Echolink and connect that site to the repeater site via Allstar. It doesn't
> matter where they physically connect it is all one network. Can you setup
> Allstar with Echolink somewhere else and use it? Is this just happening at
> the site or anywhere you use Echolink.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
>
> On Fri, May 3, 2019 at 12:44 AM "Mike Sullivan via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > I swear I sent a message about this before, but for the life of me I
> can't
> > find it in my mailbox..
> >
> > We are using the image at our tower, however the Direct Connect
> > functionality of Echolink is very problematic (many of our members get
> > "Un-Authorized" messages when initially connecting, or node offline
> > messages). Before, we used Echolink Proxy on my personal virtual server
> > which solved all of our problems. However, I know app_rpt doesn't support
> > Echolink Proxy (though it does have a proxy feature)
> >
> > I was thinking of a way to fix this. The only way I can think of would be
> > to set up another Allstar node (preferably locally), connect it to
> > something like Svxlink, and connect Svxlink to an Echolink Proxy server.
> > Would it be possible with the Hamvoip image? Or would I need to buy two
> USB
> > interfaces and wire them together, one for Allstar and the other for
> > Svxlink?
> >
> > Any suggestions for this solution would be appreciated. I may be doing
> this
> > for more than just our own club.
> >
> > Mike Sullivan
> > _______________________________________________
> >
> > 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