W2YMM Echoirlp Howto

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.

===================================================================

THIS WAS FOR OLDER NODES A FEW YEARS AGO

JUST INFORMATIONAL AT THIS POINT W2ymm

I have uploaded a temporary fix to allow auto updating of the EchoIRLP code

to work correctly. Note that this applies to ALL nodes, regardless of how

they were installed.. Further fixes may be released later, but this fix

will enable them to be fetched automatically.

Dave, if you've altered the echo_update script, you need to port my changes

(simply uncommenting the find_best_server hook) to any newer version than

the standard script.

To update your node.

1. Download update-fix.tar.gz from the files area of this group.

2. Use scp to copy update-fix.tar.gz to /home/EchoIRLP/scripts

3. As repeater, run tar -zxvf update-fix.tar.gz

4. If you have echo_update in /home/EchoIRLP/noupdate/scripts, copy

echo_update there as well.

5. Run $ECHO_SCRIPT/echo_update files

Your node should now be fixed and receiving any new updates.

=================================================================

All you need to do is install EchoIRLP.

Strongly recommended to backup your node first, just in case something goes

pear shaped during the installation. Not common, but in rare cases the

install script has not quite worked right... Use the standard

"backup_for_reinstall" script to do this as per the IRLP docs.

Download the script at http://redhat.irlp.net/echo-install

Run the script (as root)

Supply the information as needed (Echolink callsign - has to be a -L or -R,

PC user or *CONFERENCE* won't work), password and other information as

asked for by the script.

When all is done, restart the IRLP node and enjoy. :-)

I'm assuming that the 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...

73 de VK3JED

http://vkradio.com

=================================================================

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

DISCONNECT COMMAND

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

====================================================================

-----------------------------------------------------------------------------------------------------------

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.

Regards,

David McAnally (KF7FLY)

---------------------------------------------------------------

======================================================================

if [ "$1" = "12345" ]; then $ECHO_SCRIPT/echo_enable ; exit 1 ; fi

if [ "$1" = "54321" ]; then $ECHO_SCRIPT/echo_disable ; exit 1 ; fi

Change the DTMF code to suit :)

---------------------------------------------------------------------------

=====================================================================

user (PC users)

link (-L stations)

repeater (-R stations)

conference (*conferences*)

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.

----------------------------------------------------------------------

=======================================================================

> I have recently installed a simplex IRLP node to complement my other

> UHF repeater node. This new node is more experimental, as such I

> would like to install EchoIRLP. I have a Ghost image backup of the

> working node; it runs the latest image, Fedora 3 with automated

> updates enabled.

> Are there any conflicts with this configuration, for example:

> 1. Will the IRLP automated updates `break' the EchoLink

> functionality?

> 2. Does the services run at the same time, on a first come,

> fist serve basis or is preferred to script access times to IRLP &

> EchoLink?

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.

> 3. Is there a technical guide for EchoIRLP?

No, other than this message group archive, files area and source code.

Want to write one?

> Any comments addressed to a new installer would be appreciated.

Be sure your IRLP node is fully functional before starting EchoIRLP

install. Don't request support from the IRLP support team for

anything after you install EchoIRLP.

You must have a registered a repeater or link EchoLink node using the

standard EchoLink PC application and methods before you install

EchoIRLP. Only repeater or link EchoLink nodes are allowed on

EchoIRLP.

The install server (redhat.irlp.net) has been down lately. I posted

an alternate install method in the messages recently, but try to use

the standard method or wait for redhat.irlp.net to be restored. Basic

install instructions and notes can be found in the group files area.

Regards,

David McAnally (KF7FLY)

================================================================

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

> script?

> Many folk using the Windows client have turned on this mute function to

> appease their irate listeners.

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

though.

export ECHO_SAY_NODE=CALLSIGN

If you are referring to the so called "silent" EchoLink callers who

like to connect, listen a few seconds, then disconnect... some

repeater and link nodes have resorted to blocking EchoLink PC users,

and enabling only an approved list PC nodes in an exception list. The

files to do this are also located in the /home/EchoIRLP/custom/

directory as described below.

type_deny

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

user

link

repeater

conference

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.

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:

K1RFD

W1CDM

VK2JTP

WB2REM

I1HJP

A similar file named "node_deny" may also be used. I have an updated

version of the EchoIRLP code that allows us to optionally use regular

expressions in the node_allow and node_deny files.

Regards,

David McAnally (KF7FLY)

====================================================================

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

*ECHOTEST*

XX3XXX-R

Also see related files named type_deny and node_allow. The type_deny

file may contain one ore more lines of the following, also case

sensitive and follow each with a carriage return. The type_deny file

only affects inbound connections. The node_allow file allows

exceptions to type_deny blocks.

user

conference

link

repeater

Regards,

David McAnally (KF7FLY)

--------------------------------------------------------------------

===================================================================

You could use this (this is a rough example):

0 0 * * * (/home/irlp/scripts/decode 9253 > /dev/null 2>&1)

0 2 * * * (/home/irlp/scripts/decode 73 > /dev/null 2>&1)

That will make the connection to 9253 at midnight and then disconnect

at 2am. Of course, replace the 9253 and 73 with your dtmf prefixes

(if applicable)

Jim

Jim Nessen KD6HWC

======================================================================

==========================================================

Ø ---------------------------------------------------------------

Ø IRLP Remote admin install script

Ø The remote admin install script is located on the irlp.net ftp site. To obtain the

file and run the script, type the following commands as user root:

wget ftp://ftp.irlp.net/pub/remote/install-ra

chmod +x install-ra

./install-ra

---------------------------------------------------------------

The remote admin console allows you to operate your node from a

remote location, using a standard web browser. It allows you to

enable/disable the node, disconnect the current connection, launch a

remote desktop call to a laptop or desktop computer (ADPCM or GSM),

send any DTMF sequence to the decode script, regenerate DTMF tones,

and view the messages file... all online.

The scripts and pages are mobile browser friendly (BlackBerry and

Palm devices have been checked).

To install the console, you require the following:

- Redhat 7.3, 9, or Fedora Core 3 base operating system

- A working IRLP node installed

- At least 300 megs of hard drive space free (only used during

install)

- Some patience : can take an hour to install on slower systems

As part of the install, the YUM updater software is installed on your

node. It is like apt-get in that it can update the linux system

without intervention, and pulls its files from a worldwide system of

mirrors. It is a direct replacement for apt-get, and has about 100

files that are only available through the Fedora Legacy Project

mirrors, which are the current and up to date standards for all

retired Redhat and Fedora operating systems. This part of the

install needs a lot of hard drive space and time to setup.

Once setup, the YUM tool can be used to install any software that

comes in RPM format.

To install the console, please confirm you have the drive space

available by using the command

If you have fewer than 300000 (blocks) free, you will need to make

space to install the files.

The install script is located on the irlp.net ftp site. To obtain the

file and run the script, type the following commands as user root:

wget ftp://ftp.irlp.net/pub/remote/install-ra

chmod +x install-ra

./install-ra

Follow the directions in the script.

The script takes about 30 minutes to complete.

Once complete, you will have a web server running on port 15426. To

access the control page of your node from outside, you will need to

make sure that TCP port 15426 is forwarded through your router. This

was an old port used by IRLP in the past, so maybe your node already

has it forwarded.

I have set up a quick "redirection" website which will allow you to

access your node remotely. The site is

http://www.irlp.net/redirect/

Type in your node number and the port number (defaults to 15426) and

you will be automatically redirected to your node's control page.

Type in your username and password you set in the script, and you

will have remote access to your node.

There will be more details on the features soon.

=========================================================

Specific ports, you need to forward:

TCP 15425 (IRLP control)

UDP 2074 - 2093 (IRLP audio)

UDP 5198 - 5199 (Echolink)

=================================================================

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

What version of Linux do you have on your node?

If you're running FC3, 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.

==================================================================

Timing Values

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

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

/home/irlp/custom/timeoutvalue

The node-to-reflector timeout is defaulted to 1200 seconds (20 minutes) in

/home/irlp/custom/environment

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:

/home/irlp/custom/rc.irlp

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

-=====================================================

Examples of my Custom Decode File for EchoIRLP

#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

#Speed dial an IRLP Reflector

if [ "$1" = "nn" ] ; then "$SCRIPT"/connect_to_reflector ref9453 ; exit 1 ; fi # WIN SYSTEM

#My aux outputs from the irlp board and wav play notify

# Key and un-key the AUX2 output of the interface board.

if [ "$1" = "nn" ] ; then "$BIN"/aux2on ; $SCRIPT/wavplay aux2on ; exit 1 ; fi

if [ "$1" = "nnn" ] ; then "$BIN"/aux2off ; $SCRIPT/wavplay aux2off ; exit 1 ; fi

#Example of triggering a wav file by dtmf

if [ "$1" = "nnnn" ] ; then "$SCRIPT"/wavplay myid ; exit 1 ; fi

========================================================================

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

====================================================================

NOTE: IRLP is now using the CENT OS. (See method near the top of the page)

Install method for Fedora 5 (Installs latest version of the Bridge)

Steps to install EchoIRLP software on your IRLP system:

1. login as root

2. wget ftp://redhat.irlp.net/echoirlp/install/echo-install-new

3. chmod +x ./echo-install-new

4. ./echo-install-new

5. Answer the prompts.

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

Test by connecting to the EchoLink *ECHOTEST* service,

EchoLink node 9999.

Rough Draft

Work in progress........

From the EchoIRLP Yahoo group-

Echoirlp FAQ