Hi everyone,installed it on the local repeaters PiIRLP node, and it's working perfectly.
I'm very new to EchoIRLP, however a small group including myself have
Except that we had hoped to run it in conference mode, so a number of singleuser nodes could connect for nets, etc.
The following quote is from the user manual:
"Do not change MaxConferenceClients = 2: This tbd.conf setting
controls how many Echolink users are allowed to connect. One client is
your IRLP node which leaves one for an Echolink connection. Do Not
change this or EchoIRLP won’t work properly and may not start at all."
Does this mean that only one user is ever allowed to connect at a time?
Sorry if this is a question covered somewhere else...
Steven VK2STG
Hi everyone,installed it on the local repeaters PiIRLP node, and it's working perfectly.
I'm very new to EchoIRLP, however a small group including myself have
Except that we had hoped to run it in conference mode, so a number of singleuser nodes could connect for nets, etc.
The following quote is from the user manual:
"Do not change MaxConferenceClients = 2: This tbd.conf setting
controls how many Echolink users are allowed to connect. One client is
your IRLP node which leaves one for an Echolink connection. Do Not
change this or EchoIRLP won’t work properly and may not start at all."
Does this mean that only one user is ever allowed to connect at a time?
Sorry if this is a question covered somewhere else...
Steven VK2STG
Hi everyone,
I'm very new to EchoIRLP, however a small group including myself have installed it on the local repeaters PiIRLP node, and it's working perfectly. Except that we had hoped to run it in conference mode, so a number of
single user nodes could connect for nets, etc.
The following quote is from the user manual:
"Do not change MaxConferenceClients = 2: This tbd.conf setting
controls how many Echolink users are allowed to connect. One client is
your IRLP node which leaves one for an Echolink connection. Do Not
change this or EchoIRLP won’t work properly and may not start at all."
Does this mean that only one user is ever allowed to connect at a time?
Sorry if this is a question covered somewhere else...
Steven VK2STG
I don't know where this information is coming from, but it's eitherinaccurate or out of date.
There is no limitation as far as EchoLink is concerned to operating anEchoIRLP node in a mode that allows conferencing. The only stipulation is that
The conference validation procedure applies only to nodes with conferencecallsigns (like *CONF*) which are not RF gateways, and those must be run using the standard tbd distribution rather than EchoIRLP.
Hi Tony.login, when conferencing is enabled?
That sounds like it may be a bug.
Are you saying that EchoIRLP changes its version number identifier during
1. Modified version reporting to use bEchoIrlpMode flag.
Revision 1.16 2004/11/22 00:52:56 wb6ymh
1. Detect EchoIRLP by SF_Port != SF_ReplyPort instead of SF_ReplyPort !=
SF_AUDIO_PORT. Allows conferences to use nonstandard ports without
triggering an EchoIRLP version string.
Revision 1.15 2004/05/29 17:25:22 wb6ymh
...
3. Changed version string sent to EchoLink directory servers from v.vvB to
v.vvI when tbd is used with the EchoIRLP project.
On 30/4/21 12:42 pm, Jonathan Taylor wrote:
Hi Tony.
That sounds like it may be a bug.during login, when conferencing is enabled?
Are you saying that EchoIRLP changes its version number identifier
You would have to ask Skip what he did to work around the policy,
because initially, there was a brief period where EchoIRLP wouldn't work
at all, because tbd was ALWAYS identified as a conference, so I believe
there was a change made so it would report a different version when
running on an EchoIRLP node, but in practice, that change only allowed a
node with a single link to work.
I think that also a specific configuration of the Speak Freely ports
(only used with EchoIRLP) may be needed as well to make it look like an EchoIRLP node, but not 100% sure on that. This particular configuration
is only useful for that purpose. But I do recall it was all a
workaround to enable some level of EchoIRLP functionality at all, while complying with the Echolink policies.
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com
It looks like there is a flag in configvars.c called bEchoIrlpMode, which isset only according to the condition that SF_Port != SF_ReplyPort in the configuration, which is presumably the case (only) in an EchoIRLP installation.
Hi again,do much harm to try it) and so far it seems to work fine... Conferencing works although I've only tried with 2 echolink connections at a time, so far. We'll see if it keeps working!
I've just changed the MaxConferenceClients setting to 6 (thought it wouldn't
Steven VK2STG - - still fiddling with the VK2RFS-R node.
Sysop: | Chris Crash |
---|---|
Location: | Huntington Beach, CA. |
Users: | 578 |
Nodes: | 8 (0 / 8) |
Uptime: | 29:07:43 |
Calls: | 10,736 |
Calls today: | 1 |
Files: | 5 |
Messages: | 443,196 |
Posted today: | 1 |