[Arm-allstar-irlp] 2 more nodes successfully migrated.

[Doug Crompton]

Phil,

 The hamvoip IRLP code is not a reflector it is a stand-alone node so it
would have all the same restraints as a "real" IRLP node. Unlike Allstar
IRLP can only be connected to a single other node at a time be it a single
node or a reflector. The primary intention of this code is to replace the
many gateway connections from Allstar/Echolink to IRLP that existed on old
buggy PC's. An Allstar/IRLP node would connect to a single reflector which
then would have many IRLP nodes connected. So you can have many on Allstar
but only one on IRLP unless it was connected to a reflector which had many
connected to it. It is important to understand the many differences between
IRLP and Allstar. It makes you appreciate Allstar even more!


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*


On Tue, Apr 10, 2018 at 9:29 PM, Phil Visalli <phil at philv.net> wrote:

> So we successfully migrated two IRLP nodes over to hamvoip with no
> issues.  Both seem stable and work great. Very pleased :) Thank you!
>
> I did notice one oddity, and I'm not sure if its expected/intended or
> something I did wrong.  Both nodes can make calls outgoing and take
> incoming calls just fine.  But i cant connect them to each other.  I
> understand that there is no practical reason to make an IRLP connection
> from one allstar node to another.  I had only tried for testing purposes
> after getting them set up.
>
> So just to satisfy my curiosity.... is this expected behavior ?
>
>
> Phil
> K2ELV
>
> _______________________________________________
> Arm-allstar-irlp mailing list
> Arm-allstar-irlp at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar-irlp
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar-irlp/attachments/20180410/7c0a58ad/attachment.html>