On 24/4/22 10:40 pm, Jonathan Taylor wrote:

David, since the format of the callsigns in EchoLink is meant to convey

whether the node is a conference, an RF gateway, or a local (mic/spkrs) node, there are some rules on the server side that are intended to help ensure consistency. We expect that an EchoIRLP node will always be an RF gateway of some sort, which is why it requires a -L or -R suffix. As Tony points out, in the Windows app, this same rule is applied depending on the software's selected
mode (single-user or Sysop).

And because the software used (tbd) was originally designed for
conferences, I added the automatic disabling of the link to RF, if a
conference identifier is configured.  At the time, EchoIRLP was
originally developed, there was a lot of animosity between IRLP and
Echolink owners and user groups.  EchoIRLP was an attempt to bridge (ironically by NOT bridging the networks!) the differences between these
user communities, and I wanted to respect Echolink's rules, as well as
those of IRLP. 

--
73 de Tony VK3JED/VK3IRL
http://vkradio.com



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#293): https://groups.io/g/echoirlp/message/293
Mute This Topic: https://groups.io/mt/90608937/3738798
Mute #file-notice:https://groups.io/g/echoirlp/mutehashtag/file-notice
Group Owner: echoirlp+owner@groups.io
Unsubscribe: https://groups.io/g/echoirlp/leave/11197405/3738798/232177168/xyzzy [vk_echoirlp@freeway.apana.org.au]
-=-=-=-=-=-=-=-=-=-=-=-



--- SBBSecho 3.10-Linux
* Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (432:1/101)