[arm-allstar] Echolink Conferences

[Doug Crompton]

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
>
>