[arm-allstar] Echolink Conferences

[dan at ozment.net]

Thanks, Dave!

No VPNs involved.  Currently WB4QOJ-R is not the Allstar and it is 
running a current version of the real Echolink software.  W4DTO-L is 
Allstar running on a Pi.

On 2017-06-13 12:49, David McGough wrote:
> Hi Dan,
> 
> Do you have any VPNs connecting the different sites?
> 
> Is the WB4QOJ-R system running AllStar, the "real" echolink PC software 
> or
> other (e.g.: theBridge)?
> 
> 73, David KB4FXC
> 
> 
> On Tue, 13 Jun 2017, "Dan Ozment via arm-allstar" wrote:
> 
>> No, they are at different locations.  The Allstar node and Echolink
>> W4DTO-L is at our repeater location.  W4DTO-L is being managed by
>> Allstar.  The other Echolink node, WB4QOJ-R, is offsite and is a stand
>> alone Echolink node.  Plan # 1 was for users to connect to WB4QOJ-R
>> remotely, and we use Allstar to link -L to -R.  That's the case where 
>> we
>> aren't getting audio back from the RF side to -R.
>> 
>> The other thing we discussed was just shutting down W4DTO-L and 
>> defining
>> the -R node on Allstar.  Users would connect directly to it.  But, I 
>> can
>> see that we might over power the Pi if we go that route.
>> 
>> I'm stumped as to why the first method isn't working.  If I connect
>> directliy to W4DTO-L with an Echolink client on the outside of that
>> network I get two way audio.  So, I thing port forwrding is good 
>> there.
>> Same thing is true of the -R node.  If we connect to it from a client 
>> al
>> is good.  But, when I connect the two together I don't see to get 
>> audio
>> routed all the way through.
>> 
>> 
>> 
>> On 2017-06-13 10:30, "Doug Crompton via arm-allstar" wrote:
>> > Dan,
>> >
>> >  I don't have a good enough picture of what you are doing? When you say
>> > -L
>> > and -R Echolink nodes are you saying they are both on the same public
>> > IP
>> > address? That would not work. Give me a map of what Echolink is on what
>> > network?
>> >
>> > I have an Echolink -L node connected to a separate node on my hub
>> > server.
>> > That node is in turn connected to the hub on the same server. Echolink
>> > port
>> > forwarding is to that server. I can connect and disconnet the Echolink
>> > at
>> > will but just connecting/disconnecting the two Allstar nodes. I could
>> > not
>> > have any other Echolink on my public IP even if it was on another
>> > Allstar
>> > server unless I used a proxy.
>> >
>> >
>> > *73 Doug*
>> >
>> > *WA3DSP*
>> >
>> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>> >
>> >
>> > On Tue, Jun 13, 2017 at 8:50 AM, "Dan Ozment via arm-allstar" <
>> > arm-allstar at hamvoip.org> wrote:
>> >
>> >> Still working with Echolink on my repeater connected node, and I
>> >> wondered if someone could give me some advice on a direction.
>> >>
>> >> I set up Echolink on the node as a "-L" node with the default Echolink
>> >> configuration (no conference mode).  I was able to connect to Echolink
>> >> from my phone, and it works well with two way audio between Echolink
>> >> and
>> >> the RF side.
>> >>
>> >> My plan was to connect our public "-R" node to that one from an
>> >> external
>> >> source and let our users come in on the "-R" node.  It connects up
>> >> great.  Audio from Echolink is sent out over the repeater, but we
>> >> don't
>> >> get audio from the repeater back to the Echolink "-R" node.  Any
>> >> thoughts as to why that would happen?
>> >>
>> >> Another idea was to run the "-R" node from the Pi that is hosting
>> >> Allstar.  I would need to allow conference mode and up to 20 users
>> >> (although 5 to 10 is more realistic).  I'm using one of the later
>> >> versions of the Pi 2.   Could it handle both?
>> >>
>> >> When we tried putting the "-R" node on the Allstar Pi we had mixed
>> >> results keeping three users connected.  I wonder if I was just
>> >> overpowering the Pi.
>> >>
>> >> I realize I'm not providing much configuration info here so that folks
>> >> can help me diagnose what's going on.  At this point I'm trying to
>> >> decide on the best approach to get our main Echolink node (WB4QOJ-R)
>> >> successfully operational through our main Allstar node.
>> >>
>> >> Thanks for any input.
>> >>
>> >> 73,
>> >>
>> >> Dan
>> >>
>> >> W4DTO
>> >> _______________________________________________
>> >>
>> >> 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
>> _______________________________________________
>> 
>> 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
>>