Links to more information.     The main information page
google code site for echoirlp     The Yahoo group for support     The IRLP Homepage     What you need to know about installing IRLP    The IRLP Yahoo group for support     Randy's site with lots of good info     Tony's site with lots of good info     The source for The Bridge Software     EchoIRLP Wiki page     Gary's site with a whole lot of great IRLP info
Echolink Homepage
Rob Pectol's IRLP Help Site
K6IB'S Site for Vmon and Vcon

These 2 programs are great for remotely accessing your node from a windows pc.

.PDF Help file I wrote in 2007
Echoirlp group FAQ file

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:

1. login as root

2. wget -N

3. chmod +x ./echo-install

4. ./echo-install           (Don't forget the leading period)

5. Answer the prompts.

6. Restart IRLP by running /home/irlp/custom/rc.irlp

Test by connecting to the EchoLink *ECHOTEST* server,
EchoLink node 9999.  

Note: This should be the most up to date version, It will recognize the Cent OS.

Known Issues: Some have reported install failures, where the symptom is an empty
tbd.conf file. So far, we have not been able to debug this. When this occurs, try installing

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  need to configure the router to "forward" UDP ports 5198 and 5199 to the PC on which EchoLink/IRLP is running.

Make sure that your IRLP node is running 110%, because once you add
EchoIRLP, the IRLP support team won't support your node, due to the changes made. 
However, we're here to help if you strike problems at that point...
Just make sure you join the EchoIRLP Yahoo group.


The Install script will make some changes to your node.
One of them is the cuustom_decode file

EchoIRLP uses a prefix to determine wether to make an IRLP call or an Echolink call.
The example below uses * (Star) as the prefix.  To make an Echolink call you would enter
Star plus the Echolink node number.

This is a copy of my Prefix code for the EchoIRLP node

# Echolink Prefix detector
# If you change the EchoIRLP prefix, you must also change "num" below to the number of digits in the prefix.
eval `echo $1 | awk -v num=1 '{
     print "PRE="substr($1,1,num);
     print "NODE="substr($1,(num)+1,length($1))}'`

#Call echolink conferences using star node method
if [ "$PRE" = "S" ] ; then "$ECHO_SCRIPT"/echo_call $NODE ; exit 1 ; fi

This is my disconnect command.  I use the standard 73 for IRLP and I also added the # (Pound) which
is the default on many Echolink nodes.


if [ "$1" = "73" ] ; then "$ECHO_SCRIPT"/echo_end ; exit 1 ; fi #DISCONNECT #COMMAND
if [ "$1" = "P" ] ; then "$ECHO_SCRIPT"/echo_end ; exit 1 ; fi #DISCONNECT #COMMAND

To Enable and Disable the Echolink side of your node
you can add this to custom_decode

Change the DTMF code to suit :)

#Enable and Disable IRLP
if [ "$1" = "nnnnn" ] ; then "$SCRIPT"/disable ; exit 1 ; fi #IRLP DISABLE
if [ "$1" = "nnnnn" ] ; then "$SCRIPT"/enable ; exit 1 ; fi #IRLP ENABLE
#Enable and Disable Echolink
if [ "$1" = "nnnnn" ] ; then "$ECHO_SCRIPT"/echo_disable ; exit 1 ; fi #ECHOLINK DISABLE
if [ "$1" = "nnnnn" ] ; then "$ECHO_SCRIPT"/echo_enable ; exit 1 ; fi #ECHOLINK ENABLE

#Speed Dial an Echolink Conference
if [ "$1" = "nn" ] ; then "$ECHO_SCRIPT"/echo_call 119705 ; exit 1 ; fi #CARE_HUB
#Speed Dial an Echolink Conference with no Timeout
if [ "$1" = "nnn" ] ; then "$ECHO_SCRIPT"/echo_call 119705 notimeout ; exit 1 ; fi #CARE_HUB #No Timeout


EchoIRLP uses a similar method to enable notimeout on a connection as
IRLP uses.  You may find reference to the notimeout option in the IRLP
unofficial manual.  For EchoIRLP, modify the IRLP
$CUSTOM/custom_decode file so a DTMF prefix of your choice runs
echo_call with the "notimeout" argument.  Something like the following
might work.  This code says if the DTMF prefix is "PS", aka "# *", or
if it is "PA" , aka "# A", then run echo_call with the node number and
notimeout as arguments.

if [ "${1:0:2}" = "PS" -o "${1:0:2}" = "PA" ]; then
  "$ECHO_SCRIPT/echo_call" "${1:2}" notimeout &
  exit 1

All of the caveats of using notimeout in IRLP apply to EchoIRLP. 
So use this feature accordingly.   Make sure the owner of the node or
reflector/conference you are connecting to does not object to you
staying connected without transmissions for extended periods.
Changing your default timeout settings may be a better choice.


There are two timeout timers to be concerned with. To change them, edit the appropriate file.
A value of zero equals no timeout.

The node-to-node timer is defaulted to 240 seconds (4 minutes), and is located in

The node-to-reflector timeout is defaulted to 1200 seconds (20 minutes) in
Change the line that reads export REFLECT_TIMEOUT_VALUE=1200

Reload rc.irlp after you edit the file(s) so the change(s) will take effect immediately.
As root:

WARNING! Do not connect to any node/reflector using the notimeout option without permission of the node/reflector owner!
You could find yourself locked out

Is there anyway to set the EchoIRLP no activity timeout independantly of IRLP??

EchoIRLP uses the same COS idle activity timers as IRLP.
See the unofficial IRLP manual for details.

Or you can set or add the following line in the /home/EchoIRLP/custom/echo_environment file
to override IRLP idle timeout on EchoIRLP connections.

export ECHO_TIMEOUT_ VALUE=300    # EchoIRLP idle time out in seconds

It is advised to restart IRLP via rc.irlp to pick up any changes to the environment file.
As root:

Denying certain stations from connection to your node

Some node owners do not wish to have PC users connect to there systems.
That's up to you.
Here are some of the options you have.


The "type_deny" file may contain one or more lines containing...


The values must be lower case. These will block their respective
EchoLink node type on incoming calls.  The type_deny  feature does NOT
block any outgoing calls. So, add "user" to block EchoLink PC users.
This is similar to the type blocking feature in EchoLink PC client.

If you set all 4, you wind up with a private system that allows only calls
specified in the node_allow file.  You can mix and match as you please.

To make exceptions to blocked node types, edit the file named
"node_allow" and add the EchoLink  node call signs to be allowed, one
per line, all upper case.  For example:


A similar file named "node_deny" may also be used. 

See the $ECHOIRLP/custom/node_deny file. 

Be sure to use upper case node call signs and follow each
entry with a carriage return, even if you only have one entry.



EchoIRLP will play a TBD audio file to a connecting EchoLink station
if the TBD audio file is located and named
"/home/EchoIRLP/tbd/data/welcomeconnect.tbd". To create this file,
follow these steps.

1. Create a WAV audio file using a method of your choosing. This WAV
file format must be PCM, 16 bit, mono, 8000 Hz sampling rate.

2. Place the file on your IRLP/EchoIRLP node, and run the "tbdcnv"
command to convert it to TBD format.

tbdcnv -i yourfile.wav -o /home/EchoIRLP/tbd/data/welcomeconnect.tbd

Now when stations connect to you via Echolink they will hear your welcome message.

service tbd stop      to stop the bridge
service tbd start      to start the bridge

tbd -d        to enter debug mode     (control-C to exit)

Other handy commands to know

  As root:
Useful for Reloading software after changes.....
Reloads echoIRLP software without rebooting the operating system.

To reboot the node computer    shutdown -r now

There is a new troubleshoot script that does a more thorough job of checking ports to be sure they are open, as required.
Also note that the new script checks for echo-irlp ports.
Make sure node is not connected to another node or a reflector.

As repeater

Always run this first before posting a problem to the Yahoo group.  (The first question is usually, Did you run Troubleshoot-IRLP ?)


Back up your node first...........
As root:

You'll see names of files scrolling by as they are backed up. After it's done, look in /home/irlp/backup for a file called irlp_backup.tgz.
Don't forget to copy it to other media for safe keeping. If you lose your hard drive, it won't do any good to have the backup on the bad drive.

Editing the number of connections
Question ?

Dose anyone know how I get the echolink side of my echoirlp node to
show up as (0/5) so I can have more than 1 connection to it?

You need to edit /usr/local/etc/tbd.conf and change

MaxConferenceClients = 2

to the number of simultaneous connections you want + 1. The reason
for the +1 is that the internal link between IRLP and tbd is counted.

Unlike IRLP, Echolink can have more than 1 station connected to you directly.

Changing Callsign and Node Numbers

Question ?
I have been given a functional EchoIRLP computer which requires new a
callsign, node numbers, etc.  How do I go about making the changes ?

For IRLP, follow the instructions on this web page.

For EchoLink....

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
ConferenceCall =
ConferencePass =

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

Question ?
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

Question ?
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
EchoIRLP Node.

rpm -qi gcc

rpm -qi make

will tell you if the necessary packages are installed.

Question ?
  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

/home/EchoIRLP/ custom/tbd. conf

is still empty, try logging on as root and doing:

cp /usr/local/etc/ tbd.conf.sample /home/EchoIRLP/ custom/tbd.conf
pico -w /home/EchoIRLP/ custom/tbd. conf

Then look for the following and edit them:
ConferenceCall = W1AW
ConferencePass = CW
EmailAdr = [email protected]

Put your info in and save the file (control-X, y, return).

Try starting tbd.
service tbd start

Question ?
I've had a frequency change on my repeater. Where
do I edit this information so as to be correct on the status page?


Three places. Something we need to change to one in the future.

/home/EchoIRLP/ custom/tbd. conf

/home/EchoIRLP/ custom/echo_ environment

/home/EchoIRLP/ custom/userdata. txt

Then restart the services, as root, with the command
/home/irlp/custom/ rc.irlp

Disable and Enable with custom_cron

Question ?

Can I have cron do a shut down and restart echolink over night ?

Adding the following two lines to custom.crons should do it:

0 23 * * * (/home/EchoIRLP/ scripts/echo_ disable >/dev/null 2>&1)
0 06 * * * (/home/EchoIRLP/ scripts/echo_ enable >/dev/null 2>&1)

The 23 above will disable it at 11 pm and the 06 will re-enable it at 6 am.

Question ?
I have been using K6IB time and call announcements that need a DTMF
tone to activate can anyone let me know how I can set my node to
make this automatic so on the hour the time is broadcast to locals
plus my call.

Sure, just add an entry into custom.crons that calls the appropriate
command at the top of every hour..

0 * * * * (/home/irlp/ custom/irlpvaux 4 > /dev/null 2>&1)

Once saved, run update files.
                    Uninstalling EchoIRLP                    

How do I un-install EchoIRLP?

As indicated in the installation steps, the following IRLP files are
modified by EchoIRLP. So restoring these files to their state prior
to installing EchoIRLP will disable EchoIRLP. Or, you may edit these
files and remove the EchoIRLP lines of code.

* /home/irlp/custom/ rc.irlp (this file was modified to start or
restart tbd and enable EchoIRLP when IRLP starts)

* /home/irlp/custom/ custom_decode (this file was modified to
enable a DTMF prefix for EchoIRLP connections, and to call EchoIRLP to

* /home/irlp/custom/ custom_on (this file was modified to update
EchoIRLP status upon connecting)

* /home/irlp/custom/ custom_off (this file was modified to update
EchoIRLP status upon disconnecting)

* /home/irlp/custom/ environment (this file was modified to load
the EchoIRLP "echo_environment" settings)

Reboot or restart the node.

Uninstall the tbd (thebridge) service by executing the following
commands as root login.

* service tbd stop
* cd /usr/src
* tar xvf thebridge-0. 77.tgz  (Or whatever version is currently installed)
* cd /usr/src/thebridge- 0.77/RedHat
* ./uninstall

EchoIRLP installs the following directories and files, which can be
removed after restoring the modified IRLP files and uninstalling tbd.

* rm -rf /home/EchoIRLP

Do you dislike the Echolink Hit and Run type connections ?
This may be useful to you.

If the PC user doesn't have his machine in conference mode (non-conference
mode is enable by default) he cannot connect to an EchoIRLP node.

The nature of EchoIRLP is a conference connection.
I believe a large percentage of the unsuccessful connect/disconnects is due
to this.
The other large percentage I believe is the usual port forward problem.

I have gotten over the problem by replacing the three .wav files that
EchoIRLP uses during connect/disconnects to provide a "ding" only on
connects and disconnects and turning off the callsign announce facility in
the echo_environment file.

The values may be NO, YES or CALLSIGN.

Re-record the following:

Connecting to Echolink... echolinkon.wav
Disconnected. .. echo_off.wav
Connected... echo_on.wav

The files must be 8000 8bit mono


I recently reinstalled Echolink on my IRLP node. I could not connect
to other Echolink nodes and I still can't. My node is not listed on
the Echolink list now. Please give me some direction to fix this issue.


A few quick things to try to narrow down the possibilities:
1. If your IRLP node is behind a router, be sure you added port
forwarding for UDP 5198 & 5199 to the box's IP.

2. As user repeater enter "ps ax | grep tbd" without the quotes. You
should see two lines below with tbd in them.

3. Also try "ls -al /home/EchoIRLP/ tbd/data" without the quotes and take
note of the size of the hosts file.

4. Look in /home/EchoIRLP/ custom/tbd.conf and see if the correct
information is there. If you are using pico, be sure to use the -w
option (pico -w /home/EchoIRLP/ custom/tbd. conf)

5. Try making a connection from your keyboard by using the decode
command and see what if any error messages appear.

If you try these and report back, it will make diagnosing the problem a
little easier.

AND Double check your password.  Very common mistake

Multiple Connections

Question ?
Is there a way to support multiple connections on the echolink side of
EchoIRLP (like the Windows PC version?). When I made a connection to
one station from EchoIRLP then tried a second, it just told me I was
already connected to the first station.

This requires extensive redesign of the calling logic, which hasn't
been attempted to this date. Just needs someone with the time and
patience to work on it. :-)
     but,  You can initiate a second Echolink
connection from the console or a SSH session by simply running

tbdcmd connect CALLSIGN

But there's currently no way to do it from DTMF. Of course, multiple
incoming connections are no problem at all.
Just make sure MaxConferenceClients is set to more than 2

Question ?    Not EchoIRLP related, but something I'd like to try

I would like to use AUX Output 2 to chance channels on a Moto Maxtrac.
The problem is I cannot get it to just pull AUX1 ti ground for a
moment to just change one channel.

Any ideas ?


From my custom_decode files:

if [ "$1" = "S500" ] ; then "$BIN"/aux2on ; usleep 750000 ; "$BIN"/aux1off ; exit 1 ; fi

This is a command I use to remotely reset one fo my Windows machines from work. Set usleep to 100000 for a 1/10 of a second pulse. Use your choice of touch tones for the command.

tbd.conf template file

NOTE: you'll need to see what version of thebridge you have

The echo-install script uses the tbd.conf file from the tbd
Installation tar as a template. During the echo-install process, a
Copy is made in /home/EchoIRLP/custom/. However, once the script
Thinks it has edited the script it removes any temporary copy, leaving
Only the tbd.conf file it thought it had edited. The echo-install
Script also removes the tbd source files, leaving just the tar file.
To get a copy of the tbd.conf template file, copy the template file
From the tbd source as follows..

cd /usr/src/
tar zxvf thebridge-0.77.tgz
cp /usr/src/thebridge-0.77/tbd.conf /home/EchoIRLP/custom/tbd.conf.template
chown repeater.repeater /home/EchoIRLP/custom/tbd.conf.template
chmod 750 /home/EchoIRLP/custom/tbd.conf.template
cd /usr/src
rm -rf thebridge-0.77
Edit the /home/EchoIRLP/custom/tbd.conf.template file to set the
Following parameters. If any of these lines are commented with a
Leading ";", remove the ";" to uncomment them. I have used <> below to
Indicate something you must provide. Any settings I have not listed
Here you can leave asis from the template.
cd /home/EchoIRLP/custom/
Edit tbd.conf.template with favorite editor
ConferenceCall = <Your EchoLink Call with -L or -R suffix in upper case>
ConferencePass = <Your EchoLink password usually uppercase>
ConferenceQth = <Your location>
WorkingDir = /home/EchoIRLP/tbd/data
EmailAdr = <Your email for EchoLink support to contact you>
EnableDiskCommands = 1
AdminPass = <Your TBD admini password>
SysopPass = <Your TBD Sysop Password>
RunAsUser = repeater
ConferenceID = <Same as ConferenceCall above in lower case>
Banner = Welcome to <You call> EchoIRLP.
Banner = <Your node description>
Banner = <Your node location>
; You may wish to substitute the EchoLink server names from your Windows client
DirServerHost =
DirServerHost1 =
DirServerHost2 =
DirServerHost3 =
MaxConferenceClients = 2
SB_Enable = 1
UserCountEnable = 0
MaxCountEnable = 0
UserCountInLocation = 0
MaxPlayBackPause = 5
MinPlayBackPause = 3
MaxPlayWithoutPause = 300
ShowStationInfo = 1
SF_Enable = 1
RTP_Pass = <Same as $ECHO_TBD_PASSWD in echo_environment file>
SF_Port = 2174
SF_ReplyPort = 2074
DefaultAutoLurk = 0
BlabOffTimer = 0
CmdPort = 5198
EventScript = /home/EchoIRLP/scripts/echoirlp-status
WriteHostFile = 1

Then copy the file and restart tbd or the node.

cp -p tbd.conf.template tbd.conf
service tbd restart

Check your log files for errors.
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

Status Page AVRS
Update Nov 30, 2012 - If you are using the new Debian version of IRLP, please use this new echo-install-new shell script
Update 12/10/2012
A BETA version of The Bridge is being
released (1.09) I believe.
Stay tuned for details.....Still being tested..
Question ??

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.
      Installing and Echolink onto and IRLP node       

How to and troubleshooting

Tips and FAQ            EchoPirlp



EchoIRLP Wiki
long island ny
This was written when I used an old Desktop computer.
For EchoIRLP on the Raspberry Pi check my other page
Some of this information may be out of date...  Check the ECHOIRLP Yahoo group for current info......
As of June 2016 there is a new repository for the EchoIRLP code
is is at
As of June 2016 there is a new repository for the EchoIRLP code
is is at