When trying to connect to an EchoLink repeater (K6TUO-R), the connection appears to be made as I get the welcome message with the repeater call sign; however the carrier does not drop and after a few seconds I get these messages:
“An error has occurred,” “The call attempt has timed out,” “The connection has been lost.”

I have recently installed EchoIRLP along with my already existing IRLP node, running on a Raspberry Pi. The IRLP node is up and running fine. The EchoIRLP is a new addition and I have never been able to get it to connect successfully to an EchoLink station/node.

What should I be looking at?


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#267): https://groups.io/g/echoirlp/message/267
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)

On 22/4/22 1:56 am, W5JVJ via groups.io wrote:

When trying to connect to an EchoLink repeater (K6TUO-R), the connection

appears to be made as I get the welcome message with the repeater call sign; however the carrier does not drop and after a few seconds I get these messages:
“An error has occurred,” “The call attempt has timed out,” “The connection has been lost.”

I have recently installed EchoIRLP along with my already existing IRLP node,

running on a Raspberry Pi. The IRLP node is up and running fine. The EchoIRLP is a new addition and I have never been able to get it to connect successfully to an EchoLink station/node.
Are the Echolink ports forwarded to the node, assuming it's behind a NAT router?

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



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#268): https://groups.io/g/echoirlp/message/268
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)

Thanks Tony:

Do you know where I might find the technical information for EchoIRLP on a Raspberry Pi? Or in the alternative, which ports need to be forwarded?

Thanks,

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail: w5jvj@protonmail.com https://larrysues.travel.blog


Sent with ProtonMail secure email.
------- Original Message -------
On Thursday, April 21st, 2022 at 17:06, Tony Langdon <vk3jed@vkradio.com> wrote:

On 22/4/22 1:56 am, W5JVJ via groups.io wrote:

When trying to connect to an EchoLink repeater (K6TUO-R), the connection

appears to be made as I get the welcome message with the repeater call sign; however the carrier does not drop and after a few seconds I get these messages:
“An error has occurred,” “The call attempt has timed out,” “The connection has been lost.”

I have recently installed EchoIRLP along with my already existing IRLP

node, running on a Raspberry Pi. The IRLP node is up and running fine. The EchoIRLP is a new addition and I have never been able to get it to connect successfully to an EchoLink station/node.

Are the Echolink ports forwarded to the node, assuming it's behind a NAT router?

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

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#269): https://groups.io/g/echoirlp/message/269
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)

Larry,

Run the IRLP troubleshooting test:

https://www.irlp.net/ts.htm

Pay attention to test 2 - Port Forwarding.

Ed W6YJ


On 4/22/2022 4:35 AM, W5JVJ -- Larry via groups.io wrote:

Thanks Tony:

Do you know where I might find the technical information for EchoIRLP on a

Raspberry Pi? Or in the alternative, which ports need to be forwarded?

Thanks,

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail: w5jvj@protonmail.com https://larrysues.travel.blog

Sent with ProtonMail secure email.
------- Original Message -------
On Thursday, April 21st, 2022 at 17:06, Tony Langdon <vk3jed@vkradio.com>

wrote:

On 22/4/22 1:56 am, W5JVJ via groups.io wrote:

When trying to connect to an EchoLink repeater (K6TUO-R), the connection appears to be made as I get the welcome message with the repeater call sign; however the carrier does not drop and after a few seconds I get these messages:

“An error has occurred,” “The call attempt has timed out,” “The connection has been lost.”

I have recently installed EchoIRLP along with my already existing IRLP node, running on a Raspberry Pi. The IRLP node is up and running fine. The EchoIRLP is a new addition and I have never been able to get it to connect successfully to an EchoLink station/node.

Are the Echolink ports forwarded to the node, assuming it's behind a NAT
router?

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

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#270): https://groups.io/g/echoirlp/message/270
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)

Thanks Ed & Tony! I did NOT have the ports forwarded correctly. I corrected them and ran the the troubleshoot script again. They are all set correctly and working (according to the troubleshoot script response); however, I'm still getting the same problem (the transmit from my transciever to my HT hangs up after connecting, and then disconnects). I also get an error message when I attempt to connect to the ECHOTEST node (*9999) ("Connecting to ECHOTEST" "The node does not exist").

What do I try next?

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail: w5jvj@protonmail.com https://larrysues.travel.blog


Sent with ProtonMail secure email.
------- Original Message -------
On Friday, April 22nd, 2022 at 13:16, Ed W6YJ <w6yj_lists@67hz.net> wrote:

Larry,

Run the IRLP troubleshooting test:

https://www.irlp.net/ts.htm

Pay attention to test 2 - Port Forwarding.

Ed W6YJ

On 4/22/2022 4:35 AM, W5JVJ -- Larry via groups.io wrote:

Thanks Tony:

Do you know where I might find the technical information for EchoIRLP on a

Raspberry Pi? Or in the alternative, which ports need to be forwarded?

Thanks,

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail: w5jvj@protonmail.com https://larrysues.travel.blog

Sent with ProtonMail secure email.
------- Original Message -------
On Thursday, April 21st, 2022 at 17:06, Tony Langdon vk3jed@vkradio.com

wrote:

On 22/4/22 1:56 am, W5JVJ via groups.io wrote:

When trying to connect to an EchoLink repeater (K6TUO-R), the

connection appears to be made as I get the welcome message with the repeater call sign; however the carrier does not drop and after a few seconds I get these messages: “An error has occurred,” “The call attempt has timed out,” “The connection has been lost.”

I have recently installed EchoIRLP along with my already existing IRLP

node, running on a Raspberry Pi. The IRLP node is up and running fine. The EchoIRLP is a new addition and I have never been able to get it to connect successfully to an EchoLink station/node.

Are the Echolink ports forwarded to the node, assuming it's behind a

NAT

router?

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

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#271): https://groups.io/g/echoirlp/message/271
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)

On Fri, Apr 22, 2022 at 03:44 PM, W5JVJ -- Larry wrote:

What do I try next?

Larry, if the node is W5JVJ-L, the server logs indicate that W5JVJ-L is attempting to log in with the wrong password.
If needed, you can re-set it at echolink.org/validation .


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#272): https://groups.io/g/echoirlp/message/272
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)

Larry,

My guess is something is messed up in tbd.conf orthe tbd environment file.

It has been way too long since I've played with tbd, but try as user root:

killall tbd

tbd -d

That will put tbd in debug mode. Then try another call and note what is
shown on the EchoIRLP repeater's display.

Ed W6YJ


On 4/22/2022 12:37 PM, W5JVJ -- Larry via groups.io wrote:

Thanks Ed & Tony! I did NOT have the ports forwarded correctly. I corrected

them and ran the the troubleshoot script again. They are all set correctly and working (according to the troubleshoot script response); however, I'm still getting the same problem (the transmit from my transciever to my HT hangs up after connecting, and then disconnects). I also get an error message when I attempt to connect to the ECHOTEST node (*9999) ("Connecting to ECHOTEST" "The node does not exist").

What do I try next?

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail: w5jvj@protonmail.com https://larrysues.travel.blog

Sent with ProtonMail secure email.
------- Original Message -------
On Friday, April 22nd, 2022 at 13:16, Ed W6YJ <w6yj_lists@67hz.net> wrote:

Larry,

Run the IRLP troubleshooting test:

https://www.irlp.net/ts.htm

Pay attention to test 2 - Port Forwarding.

Ed W6YJ


On 4/22/2022 4:35 AM, W5JVJ -- Larry via groups.io wrote:

Thanks Tony:

Do you know where I might find the technical information for EchoIRLP on a Raspberry Pi? Or in the alternative, which ports need to be forwarded?

Thanks,

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail: w5jvj@protonmail.com
https://larrysues.travel.blog

Sent with ProtonMail secure email.
------- Original Message -------
On Thursday, April 21st, 2022 at 17:06, Tony Langdon vk3jed@vkradio.com wrote:

On 22/4/22 1:56 am, W5JVJ via groups.io wrote:

When trying to connect to an EchoLink repeater (K6TUO-R), the connection appears to be made as I get the welcome message with the repeater call sign; however the carrier does not drop and after a few seconds I get these messages:

“An error has occurred,” “The call attempt has timed out,” “The connection has been lost.”

I have recently installed EchoIRLP along with my already existing IRLP node, running on a Raspberry Pi. The IRLP node is up and running fine. The EchoIRLP is a new addition and I have never been able to get it to connect successfully to an EchoLink station/node.
Are the Echolink ports forwarded to the node, assuming it's behind a NAT >>>>> router?

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

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#273): https://groups.io/g/echoirlp/message/273
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)

Jonathon, I can do that; but, won't I need to reset it to match in a script somewhere at my PiRLP node?

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail: w5jvj@protonmail.com https://larrysues.travel.blog


Sent with ProtonMail secure email.
------- Original Message -------
On Friday, April 22nd, 2022 at 14:50, Jonathan Taylor <K1RFD@K1RFD.com> wrote:

On Fri, Apr 22, 2022 at 03:44 PM, W5JVJ -- Larry wrote:

What do I try next?

Larry, if the node is W5JVJ-L, the server logs indicate that W5JVJ-L is

attempting to log in with the wrong password.

If needed, you can re-set it at echolink.org/validation .

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#274): https://groups.io/g/echoirlp/message/274
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)

On Fri, Apr 22, 2022 at 04:04 PM, W5JVJ -- Larry wrote:

won't I need to reset it to match in a script somewhere at my PiRLP node?

If you remember the correct PW, you can correct it in your config.
Otherwise, you'll need to re-set it to something new, and then also update it in your config.


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#275): https://groups.io/g/echoirlp/message/275
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)

To update/change your EchoLink password on EchoIRLP, edit the file...

/usr/local/etc/tbd.conf

and change this line to match your EchoLink password...

ConferencePass = YOURPASSWORDHERE

I do not have a Raspberry PI IRLP node so it is possible the tbd.conf file
is located elsewhere. It might also be found at
/home/EchoIRLP/custom/tbd.conf

Save the tbd.conf file then restart IRLP or reboot.

David McAnally
WD5M


On Fri, Apr 22, 2022 at 3:04 PM W5JVJ -- Larry via groups.io <W5JVJ= protonmail.com@groups.io> wrote:

Jonathon, I can do that; but, won't I need to reset it to match in a
script somewhere at my PiRLP node?

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail: w5jvj@protonmail.com https://larrysues.travel.blog

Sent with ProtonMail secure email.
------- Original Message -------
On Friday, April 22nd, 2022 at 14:50, Jonathan Taylor <K1RFD@K1RFD.com> wrote:

On Fri, Apr 22, 2022 at 03:44 PM, W5JVJ -- Larry wrote:

What do I try next?

Larry, if the node is W5JVJ-L, the server logs indicate that W5JVJ-L is

attempting to log in with the wrong password.

If needed, you can re-set it at echolink.org/validation .

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#276): https://groups.io/g/echoirlp/message/276
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)

Thanks for this information.

I have corrected the port forwarding and the troubleshoot-irlp script reports everything PASS.

I have corrected the ConferencePass in the tbd.conf file to match the password that works on my iPhone EchoLink app (for some reason it had showed all the letters in caps, none in lowercase).

I am still getting the same error message that I started this thread with: “An error has occurred,” “The call attempt has timed out,” “The connection has been lost.”

Now I am getting the same error message when attempting to connect to the ECHOTEST node.

Any more ideas on why my transceiver remains in transmit after apparently connecting, and until it sends me the audio error message, whereupon it stops transmitting (to my HT).

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail: w5jvj@protonmail.com https://larrysues.travel.blog


Sent with ProtonMail secure email.
------- Original Message -------
On Friday, April 22nd, 2022 at 15:27, WD5M David M. <David.McAnally@gmail.com> wrote:

To update/change your EchoLink password on EchoIRLP, edit the file...

/usr/local/etc/tbd.conf

and change this line to match your EchoLink password...

ConferencePass = YOURPASSWORDHERE

I do not have a Raspberry PI IRLP node so it is possible the tbd.conf file
is located elsewhere. It might also be found at /home/EchoIRLP/custom/tbd.conf

Save the tbd.conf file then restart IRLP or reboot.

David McAnally
WD5M

On Fri, Apr 22, 2022 at 3:04 PM W5JVJ -- Larry via groups.io <W5JVJ= protonmail.com@groups.io> wrote:

Jonathon, I can do that; but, won't I need to reset it to match in a
script somewhere at my PiRLP node?

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail: w5jvj@protonmail.com https://larrysues.travel.blog

Sent with ProtonMail secure email.
------- Original Message -------
On Friday, April 22nd, 2022 at 14:50, Jonathan Taylor K1RFD@K1RFD.com wrote:

On Fri, Apr 22, 2022 at 03:44 PM, W5JVJ -- Larry wrote:

What do I try next?

Larry, if the node is W5JVJ-L, the server logs indicate that W5JVJ-L is attempting to log in with the wrong password.
If needed, you can re-set it at echolink.org/validation .

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#277): https://groups.io/g/echoirlp/message/277
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)

Just a quick note to keep in mind that the passwords for W5JVJ and W5JVJ-L might be different. Still seeing incorrect password.

Additionally, note that those two call signs can’t log in simultaneously from
the same address.


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#278): https://groups.io/g/echoirlp/message/278
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)

On 22/4/22 9:35 pm, W5JVJ -- Larry via groups.io wrote:

Thanks Tony:

Do you know where I might find the technical information for EchoIRLP on a

Raspberry Pi? Or in the alternative, which ports need to be forwarded?

5198-5199/udp


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



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#279): https://groups.io/g/echoirlp/message/279
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)

On 23/4/22 5:37 am, W5JVJ -- Larry via groups.io wrote:

Thanks Ed & Tony! I did NOT have the ports forwarded correctly. I corrected

them and ran the the troubleshoot script again. They are all set correctly and working (according to the troubleshoot script response); however, I'm still getting the same problem (the transmit from my transciever to my HT hangs up after connecting, and then disconnects). I also get an error message when I attempt to connect to the ECHOTEST node (*9999) ("Connecting to ECHOTEST" "The node does not exist").
Check that you're actually logging into the Echolink servers.  the tbd
log file and syslog should have clues there - pay attention to the
number of stations downloaded after "logging in".

0 is bad, a big number is good, a small number means an incremental
update (still good).

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



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#280): https://groups.io/g/echoirlp/message/280
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)

On 23/4/22 9:08 am, Jonathan Taylor wrote:

Just a quick note to keep in mind that the passwords for W5JVJ and W5JVJ-L

might be different. Still seeing incorrect password.

Additionally, note that those two call signs can’t log in simultaneously

from the same address.
In my experience, they will log in, but really weird stuff happens.  Solution:  use a public proxy for the user callsign, port forward the -L.

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



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#281): https://groups.io/g/echoirlp/message/281
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)

On my Raspberry Pi where should I look for those log files (and by what name?)?

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail: w5jvj@protonmail.com https://larrysues.travel.blog


Sent with ProtonMail secure email.
------- Original Message -------
On Friday, April 22nd, 2022 at 20:27, Tony Langdon <vk3jed@vkradio.com> wrote:

On 23/4/22 5:37 am, W5JVJ -- Larry via groups.io wrote:

Thanks Ed & Tony! I did NOT have the ports forwarded correctly. I corrected

them and ran the the troubleshoot script again. They are all set correctly and
working (according to the troubleshoot script response); however, I'm still getting the same problem (the transmit from my transciever to my HT hangs up after connecting, and then disconnects). I also get an error message when I attempt to connect to the ECHOTEST node (*9999) ("Connecting to ECHOTEST" "The node does not exist").

Check that you're actually logging into the Echolink servers. the tbd
log file and syslog should have clues there - pay attention to the
number of stations downloaded after "logging in".

0 is bad, a big number is good, a small number means an incremental
update (still good).

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

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#282): https://groups.io/g/echoirlp/message/282
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)

I found "messages" files at /home/irlp/log/
Sample lines from those files:

Apr 22 2022 14:20:16 -0700 decode: DTME=S952110
EchoIRLP: connected speakfreely W5JVJ-L
EchoIRLP: Connect failure from Echolink 952110 K5OQ-R
EchoIRLP: disconnected bye W5JVJ-L 0
timeout call
EchoIRLP: disconnected rtcp_timeout K5OQ-R 0
decode: DTMF=9999
Node Connected to reflector echo on channel 9
decode: DTMF-73
Node Disconnect from ref9999

Does this provide any clues?

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail: w5jvj@protonmail.com https://larrysues.travel.blog


Sent with ProtonMail secure email.
------- Original Message -------
On Friday, April 22nd, 2022 at 20:30, Tony Langdon <vk3jed@vkradio.com> wrote:

On 23/4/22 9:08 am, Jonathan Taylor wrote:

Just a quick note to keep in mind that the passwords for W5JVJ and W5JVJ-L

might be different. Still seeing incorrect password.

Additionally, note that those two call signs can’t log in simultaneously

from the same address.

In my experience, they will log in, but really weird stuff happens.
Solution: use a public proxy for the user callsign, port forward the -L.

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

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#283): https://groups.io/g/echoirlp/message/283
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)

Larry,

Take a look at:

/var/log/tbd.log

Ed W6YJ

On 4/23/2022 10:45 AM, W5JVJ -- Larry via groups.io wrote:

I found "messages" files at /home/irlp/log/
Sample lines from those files:

Apr 22 2022 14:20:16 -0700 decode: DTME=S952110
EchoIRLP: connected speakfreely W5JVJ-L
EchoIRLP: Connect failure from Echolink 952110

K5OQ-R

EchoIRLP: disconnected bye W5JVJ-L 0
timeout call
EchoIRLP: disconnected rtcp_timeout K5OQ-R 0
decode: DTMF=9999
Node Connected to reflector echo on channel 9
decode: DTMF-73
Node Disconnect from ref9999

Does this provide any clues?

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail:w5jvj@protonmail.com https://larrysues.travel.blog

Sent with ProtonMail secure email.
------- Original Message -------
On Friday, April 22nd, 2022 at 20:30, Tony Langdon<vk3jed@vkradio.com>

wrote:

On 23/4/22 9:08 am, Jonathan Taylor wrote:

Just a quick note to keep in mind that the passwords for W5JVJ and W5JVJ-L might be different. Still seeing incorrect password.

Additionally, note that those two call signs can’t log in simultaneously from the same address.

In my experience, they will log in, but really weird stuff happens.
Solution: use a public proxy for the user callsign, port forward the -L.

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

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#284): https://groups.io/g/echoirlp/message/284
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)

The tbd log file lives in your WorkingDirectory (as defined in
tlb.conf).  The name of the file you're looking for depends on the way
logging is configured.  Syslog is usually in /var/log

On 24/4/22 3:37 am, W5JVJ -- Larry via groups.io wrote:

On my Raspberry Pi where should I look for those log files (and by what

name?)?

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail: w5jvj@protonmail.com https://larrysues.travel.blog

Sent with ProtonMail secure email.
------- Original Message -------
On Friday, April 22nd, 2022 at 20:27, Tony Langdon <vk3jed@vkradio.com>

wrote:

On 23/4/22 5:37 am, W5JVJ -- Larry via groups.io wrote:

Thanks Ed & Tony! I did NOT have the ports forwarded correctly. I corrected

them and ran the the troubleshoot script again. They are all set correctly and
working (according to the troubleshoot script response); however, I'm still getting the same problem (the transmit from my transciever to my HT hangs up after connecting, and then disconnects). I also get an error message when I attempt to connect to the ECHOTEST node (*9999) ("Connecting to ECHOTEST" "The node does not exist").

Check that you're actually logging into the Echolink servers. the tbd
log file and syslog should have clues there - pay attention to the
number of stations downloaded after "logging in".

0 is bad, a big number is good, a small number means an incremental
update (still good).

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

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



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#285): https://groups.io/g/echoirlp/message/285
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)

Oops, I meant tbd not tlb, so wherever you see tlb in my response below, substitute tbd.

On 24/4/22 7:53 am, Tony Langdon via groups.io wrote:

The tbd log file lives in your WorkingDirectory (as defined in
tlb.conf).  The name of the file you're looking for depends on the way logging is configured.  Syslog is usually in /var/log

On 24/4/22 3:37 am, W5JVJ -- Larry via groups.io wrote:

On my Raspberry Pi where should I look for those log files (and by what name?)?

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail: w5jvj@protonmail.com
https://larrysues.travel.blog


Sent with ProtonMail secure email.
------- Original Message -------
On Friday, April 22nd, 2022 at 20:27, Tony Langdon <vk3jed@vkradio.com> wrote:

On 23/4/22 5:37 am, W5JVJ -- Larry via groups.io wrote:

Thanks Ed & Tony! I did NOT have the ports forwarded correctly. I corrected them and ran the the troubleshoot script again. They are all set correctly and working (according to the troubleshoot script response); however,

I'm still getting the same problem (the transmit from my transciever to my HT hangs up after connecting, and then disconnects). I also get an error message when I attempt to connect to the ECHOTEST node (*9999) ("Connecting to ECHOTEST" "The node does not exist").

Check that you're actually logging into the Echolink servers. the tbd
log file and syslog should have clues there - pay attention to the
number of stations downloaded after "logging in".

0 is bad, a big number is good, a small number means an incremental
update (still good).

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

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



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#286): https://groups.io/g/echoirlp/message/286
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)

Success!

Thank you all for your patience! I have worked through the advice given and successfully connected to EchoLink W5OQ-R!

Two quick questions:
1) What is the correct number for the EchoTest node?
2) Does it matter if I connect as W5JVJ or W5JVJ-L? Can I change that?

Many thanks again for the wonderful assistance!

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail: w5jvj@protonmail.com https://larrysues.travel.blog


Sent with ProtonMail secure email.
------- Original Message -------
On Saturday, April 23rd, 2022 at 16:55, Tony Langdon <vk3jed@vkradio.com> wrote:

Oops, I meant tbd not tlb, so wherever you see tlb in my response below, substitute tbd.

On 24/4/22 7:53 am, Tony Langdon via groups.io wrote:

The tbd log file lives in your WorkingDirectory (as defined in
tlb.conf). The name of the file you're looking for depends on the way logging is configured. Syslog is usually in /var/log

On 24/4/22 3:37 am, W5JVJ -- Larry via groups.io wrote:

On my Raspberry Pi where should I look for those log files (and by what

name?)?

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail: w5jvj@protonmail.com https://larrysues.travel.blog

Sent with ProtonMail secure email.
------- Original Message -------
On Friday, April 22nd, 2022 at 20:27, Tony Langdon vk3jed@vkradio.com

wrote:

On 23/4/22 5:37 am, W5JVJ -- Larry via groups.io wrote:

Thanks Ed & Tony! I did NOT have the ports forwarded correctly. I

corrected them and ran the the troubleshoot script again. They are all set correctly and working (according to the troubleshoot script response); however,
I'm still getting the same problem (the transmit from my transciever to my HT hangs up after connecting, and then disconnects). I also get an error message when I attempt to connect to the ECHOTEST node (*9999) ("Connecting to ECHOTEST" "The node does not exist").

Check that you're actually logging into the Echolink servers. the tbd log file and syslog should have clues there - pay attention to the number of stations downloaded after "logging in".

0 is bad, a big number is good, a small number means an incremental update (still good).

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

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

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#287): https://groups.io/g/echoirlp/message/287
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)

Larry,

Congratulations on both getting it working and the perseverance to see
it through....

The EchoLink test node is 9999.

Convention is callsign node - no radio attached, callsign-L is with a
simplex radio attached, and callsign-R is for use with repeaters. These
aren't hard and fast though.

Ed W6YJ


On 4/23/2022 3:17 PM, W5JVJ -- Larry via groups.io wrote:

Success!

Thank you all for your patience! I have worked through the advice given and

successfully connected to EchoLink W5OQ-R!

Two quick questions:
1) What is the correct number for the EchoTest node?
2) Does it matter if I connect as W5JVJ or W5JVJ-L? Can I change that?

Many thanks again for the wonderful assistance!

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail: w5jvj@protonmail.com https://larrysues.travel.blog

Sent with ProtonMail secure email.
------- Original Message -------
On Saturday, April 23rd, 2022 at 16:55, Tony Langdon <vk3jed@vkradio.com>

wrote:

Oops, I meant tbd not tlb, so wherever you see tlb in my response below,
substitute tbd.

On 24/4/22 7:53 am, Tony Langdon via groups.io wrote:

The tbd log file lives in your WorkingDirectory (as defined in
tlb.conf). The name of the file you're looking for depends on the way
logging is configured. Syslog is usually in /var/log

On 24/4/22 3:37 am, W5JVJ -- Larry via groups.io wrote:

On my Raspberry Pi where should I look for those log files (and by what name?)?

W5JVJ -- Larry
(916) 271-1991
Switch to Signal for encrypted messaging
Switch to Proton Mail for end-2-end encryption options.
I am migrating to Proton Mail: w5jvj@protonmail.com
https://larrysues.travel.blog

Sent with ProtonMail secure email.
------- Original Message -------
On Friday, April 22nd, 2022 at 20:27, Tony Langdon vk3jed@vkradio.com wrote:

On 23/4/22 5:37 am, W5JVJ -- Larry via groups.io wrote:

Thanks Ed & Tony! I did NOT have the ports forwarded correctly. I corrected them and ran the the troubleshoot script again. They are all set correctly and working (according to the troubleshoot script response); however,

I'm still getting the same problem (the transmit from my transciever to my HT hangs up after connecting, and then disconnects). I also get an error message when I attempt to connect to the ECHOTEST node (*9999) ("Connecting to ECHOTEST" "The node does not exist").

Check that you're actually logging into the Echolink servers. the tbd >>>>>> log file and syslog should have clues there - pay attention to the >>>>>> number of stations downloaded after "logging in".

0 is bad, a big number is good, a small number means an incremental
update (still good).

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

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

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#288): https://groups.io/g/echoirlp/message/288
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)

On 24/4/22 9:05 am, Ed W6YJ wrote:

Larry,

Congratulations on both getting it working and the perseverance to see
it through....

The EchoLink test node is 9999.

Convention is callsign node - no radio attached, callsign-L is with a
simplex radio attached, and callsign-R is for use with repeaters.
These aren't hard and fast though.

However, an EchoIRLP node MUST have a -L or -R callsign.  A user
callsign won't work (enforced by the Echolink servers), and a conference callsign/ID will cause EchoIRLP to disable the link between tbd and the
radio interface and run tbd as a pure conference (it will still work for
IRLP in this mode).

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



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#289): https://groups.io/g/echoirlp/message/289
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)

On Sun, Apr 24, 2022 at 1:01 AM Tony Langdon <vk3jed@vkradio.com> wrote:

However, an EchoIRLP node MUST have a -L or -R callsign. A user
callsign won't work (enforced by the Echolink servers), and a conference callsign/ID will cause EchoIRLP to disable the link between tbd and the
radio interface and run tbd as a pure conference (it will still work for
IRLP in this mode).

I would be interested in the reason for this limitation on user EchoLink
nodes in tbd/tlb. I think I recently mentioned on theLinkbox group that
this behaviour seemed contrary to how the EchoLink windows client functions with user nodes. The limitation is built-in to the tbd/tlb programs. I plan
to experiment with a modified tlb to see if this limitation can be removed,
or at least be made to work like the Windows client.

David M.
WD5M


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#290): https://groups.io/g/echoirlp/message/290
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)

On 24/4/22 4:22 pm, WD5M David M. wrote:

I would be interested in the reason for this limitation on user EchoLink nodes in tbd/tlb. I think I recently mentioned on theLinkbox group that
this behaviour seemed contrary to how the EchoLink windows client functions with user nodes. The limitation is built-in to the tbd/tlb programs. I plan to experiment with a modified tlb to see if this limitation can be removed, or at least be made to work like the Windows client.

My understanding is it's the servers, which authorise clients based on
both login/password, as well as software version.  The Windows client
has two distinct modes of operation - sysop (for RF links) and user
(with all of the RF linking features disabled).  Similarly, tbd won't authenticate with a -L or -R callsign, unless put into a configuration
that's specific to EchoIRLP (specifically, having SF_Port and
SF_ReplyPort set to different values) that causes it to send a different version number.  At one stage it also had to be limited to no more than
2 connections - i.e. one connected Echolink station, but that limitation appears to have been removed in recent times.  tlb, being designed for
RF links doesn't have the limits on -L/-R operation that tbd has.

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



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#291): https://groups.io/g/echoirlp/message/291
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)

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


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#292): https://groups.io/g/echoirlp/message/292
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)

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)