1. IRLP must already be installed and fully configured and working. EchoIRLP uses IRLP code.
2. Your node must have the compiler (GCC) and development software installed.
This may not have been installed from the latest IRLP Linux software CDROM unless you chose to install everything.
If you didn't, dont worry, you can still install it. Keep reading
3. You must have used the Windows EchoLink client to register your EchoLink node.
Your EchoLink node must be a -R (repeater) or -L (link) radio node.
Once you have your EchoLink node working on the Windows client, you will use that configuration information in EchoIRLP install.
Jot down / remember your EchoLink Password (You'll need it later)
4. Make a backup copy of IRLP using the script
/home/irlp/scripts/backup_for_reinstall, or just make copies of these IRLP files.
5. EchoLink requires that your router or firewall allow inbound and outbound UDP to destination ports 5198 and 5199, and outbound
TCP to port 5200. Source ports are dynamically assigned. If you are using a home-network router, you will also need to configure the router to "forward" UDP ports 5198 and 5199 to the PC on which EchoLink is running.
(Note, most problems i've seen are due to incorrect port forwarding)
Steps to install EchoIRLP software on your IRLP system:
Validate the new EchoLink call sign / node number on EchoLink, verifying it
using the EchoLink PC client software. Remember, EchoIRLP only allows link
(-L) or repeater (-R) nodes.
Then edit these files and settings on the EchoIRLP node listed below.
/home/EchoIRLP/ custom/tbd. conf
/home/EchoIRLP/ custom/echo_ environment
/home/EchoIRLP/ custom/userdata. txt
Restart IRLP from root login with script /home/irlp/custom/ rc.irlp, or
reboot the node.
How EchoIRLP functions
EchoIRLP is enabled from rc.irlp, at the bottom of the script,
assuming you use the install script to install EchoIRLP.
theBridge starts from Linux services, although it is also restarted
from rc.irlp. theBridge is the only background service applicaiton
added by EchoIRLP. EchoIRLP is an add-on to IRLP.
It runs with IRLP and requires IRLP to function.
Only one or the other type of connection may be active at any given time.
You cannot use EchoIRLP to cross link the two VOIP networks.
Is there a way in EchoIRLP to mute incoming connect/disconnect messages
from Echolink stations via tbd.conf or echo_environment or via a custom
You may wish to experiment with this setting in echo_environment:
There is a comment above this setting describing it. The values may
be NO, YES or CALLSIGN. I don't think it will make connections silent
Getting the required development tools before installing EchoIRLP
I would like to ask for assistance in installing ECHOIRLP into my
IRLP node. I understand I need aptget first, Where do I get it
and how do I get it into my node scrips??
What you really need is gcc and the development tools.
If you're running FC3 or later, you can get your system ready for EchoIRLP by running
yum install gcc make
If you chose to install the "development tools" when you installed
Linux, these are already installed, and you are ready to go.
How do I go about finding out if I did install gcc etc when I loaded
FC3. I am also looking at converting the IRLP Node I have to an
rpm -qi gcc
rpm -qi make
will tell you if the necessary packages are installed.
Why when trying to install EchoIRLP on my node, When I enter ./echo-install in the root
directory I receive a message "permission denied".
Be sure to set the file permission to eXecutable as follows:
chmod +x ./echo-install
tbd.conf file is empty...
I'm having the same problem on a fresh upgrade of a node (RH7.? to CentOS 4.4) I haven't edited either file, and I used the echoirlp install script to set this up (I didn't back up echoIRLP from the old node)
I've restarted the node a few times and TBD always fails on this problem
Oct 07 2009 22:35:39 +1000 Node Enabled
Oct 07 2009 22:35:43 +1000 EchoIRLP: shutdown
Oct 07 2009 22:35:44 +1000 EchoIRLP: starting
Oct 07 2009 22:35:44 +1000 EchoIRLP: ECHO_MYCALL does not match callsign in tbd.conf! Shutting down ...
Everything on the IRLP side is working as far as I can tell.
I have tried the install 3 times.
If you have tried installing EchoIRLP more than once and
I and probably a few others have traced the echo-install script and I
Donít see where it would leave the file empty. One possible cause is
Having more than one version of thebridge in the /usr/src/ directory.
The echo-install script may use the wrong version. I'm also guessing
This empty file issue may have something to do with the newer bash
Shell in Fedora, and we have some script syntax that is being rejected
That worked in previous versions. I've seen some similar reports
From others running my updated EchoIRLP scripts on Fedora. I don't
Yet have a Fedora system to debug on yet.
Disclaimer ....I am by no way an expert when it comes to this stuff, but I wanted to pass along some information that I have come across in my pursuit of creating and maintaining my own EchoIRLP node. YMMV Good Luck W2YMM
Audio levels inconsistent ...
Audio level variation is typical of EchoLink systems, especially PC users.
And may be seen from IRLP or EchoIRLP systems from time to time too. There
is no automatic audio leveling feature in IRLP or EchoLink or EchoIRLP.
Education of the system owners to properly set audio levels using
documented methods is the only solution at this time. Testing and setting
audio levels through subjective human ears on connected EchoLink/IRLP
systems is NOT the proper method. The following are good audio setting
I understand what IRLP is. I understand what Echolink is. I "think" I have a pretty good handle on what EchoIRLP is, however, I will tell you what I know and please correct my misunderstandings if there are any.
EchoIRLP is, for all intents and purposes a Linux "bolt on" to IRLP which allows an IRLP node, to also be an Echolink node. You cannot, however, just run EchoIRLP. EchoIRLP requires IRLP to already be in place. Yes? YES.
Next question, what then is Echolinux?
Lastly, What is function of thebridge and tbd with respect to IRLP / EchoIRLP ?
Thebridge i.e. tbd is basically used as a protocol converter
between IRLP and Echolink by the EchoIRLP scripts. IRLP
uses SpeakFreely as it's basis which uses it's own frame
format. Echolink uses a slightly modified version of RTP
as it's frame format. Both can use GSM codecs so ... TheBridge
just converts the frame format as it forward the packets
between the two systems.
You can use Thebridge w/o IRLP but then you have a conference or
reflector, not a node.
Thelinkbox (tlb) is another project
that was derived from thebridge which you can use standalone,
but it does not support IRLP.
echolinux was an early Linux client.
Finally javEcho is a Echolink client for Linux written in Java,
it has nothing to do with IRLP or thebridge.
I hope this helps.
73's Skip WB6YMH
The Raspberry Pi computer is now being tested
to work with IRLP. See the EchoIRLPi page for more info.