INSTALLING AN ECHOIRLP NODE

Document Sample
INSTALLING AN ECHOIRLP NODE Powered By Docstoc
					                       INSTALLING AN ECHOIRLP NODE
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.
Also, Note that the IRLP support team won't support your node, due to the changes made.
However, the EchoIRLP Yahoo group is here to help if you have a problem.
This information was based on EchoIRLP Version 1.6
And The Bridge Version 0.77
On a Linux RedHat Version 9
But should be ok for Fedora Core 3 and Cent OS
INDEX:
GETTING STARTED
Prerequisites… … … … … … … … … … … … … … … … … … … ..2
Steps to install EchoIRLP software… … … … … … … … … … … … … 2
Firewall info… … … … … … … … … … … … … … … .… … … … … 3
CUSTOMIZATION
Timing Values… … … … … … … … … … … … … … … … … … … … … … … … .3
Blocking/Allowing Nodes… … … … … … … … … … … … … … … … … … … … … 4
Announce Connection… … … … … … … … … … … … … … … .… … … … … … ..5
Welcome Audio Files… … … … … … … … … … … … … … … … … … … … … … 5
Custom_Decode Examples… … … … … … … … … … … … … … … … … … … … .5
TECHNICIAL
IRLP Remote Admin Script… … … … … … … … … … … … … … … … … … … … … … … … .7
TBD.CONF Template File
Info about GCC… … … … … … … … … … … … … … … … … … … … … … … … … … … … … .7
Removing EchoIRLP… … … … … … … … … … … … … … … … … … … … … … … … … … … 8
Faq … … … … … … … … … … … … … … … … … … … … … … … … … … … 9
Upgrading the BRIDGE… … … … … … … … … … … … … … … … … … … … … … … … … … 9
LINKS … … … … … … … … … … … … … … … … … … … … … … … … … … 10




For more information, be sure to see the real FAQ in the EchoIRLP yahoo group

http://groups.yahoo.com/group/EchoIRLP/files/




Updated 3/16/2008 W2YMM




                                                                                          1
Prerequisites:
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.
(See page 07 for GCC info)
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.
4. Make a backup copy of IRLP using the script
/home/irlp/scripts/backup_for_reinstall, or just make copies of these IRLP files.
/home/irlp/custom/rc.irlp
/home/irlp/custom/custom_decode
/home/irlp/custom/custom_on
/home/irlp/custom/custom_off
/home/irlp/custom/environment


Steps to install EchoIRLP software on your IRLP system:
1. Login as root
2. wget ftp://redhat.irlp.net/echoirlp/install/echo-install
3. chmod +x ./echo-install
4. ./echo-install
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.

Alternate way to install using the script from the Google site:

1. login as root

2. wget -N http://echoirlp.googlecode.com/svn/trunk/install/echo-install

3. chmod +x ./echo-install

4. ./echo-install

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.

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




                                                                                               2
Firewall Info
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.
Specific ports, you need to forward:
TCP 15425 (IRLP control)
UDP 2074 - 2093 (IRLP audio)
UDP 5198 - 5199 (Echolink)




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

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.




                                                                                                  3
BLOCKING / ALLOWING NODE TYPES
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
WB2REM
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.
-------------------------------------------------------------------------------------------
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.
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




                                                                                              4
CHANGE HOW THE ANNOUNCE MESSAGE IS PLAYED
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



WELCOME AUDIO FILE
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

CUSTOM _ DECODE EXAMPLES
These are located in /home/irlp/custom/custom_decode

These are examples of my custom_decode file.
#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
This is a copy of my Prefix code for the EchoIRLP node (W2YMM)
# 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



                                                                                                       5
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
Change the DTMF code to suit :) nn is where you put in your desired digits.

I use two options for disconnecting, IRLP users are used to using 73, where as
The Echolink users were used to using Pound. Now we have both.


tbd.conf template file
I just took a peek in the file section and could not find a sample
tbd.conf file. I re-ran the install script and ended up with another 0 byte
tbd.conf file. Is TBD 0.77 the version I should be installing?
Yeah, 0.77 is still the one at this stage. As for the conf file, David, do
you know where the sample one hides?
73 de VK3JED
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>
9
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 = server1.echolink.org



                                                                                       6
DirServerHost1 = server2.echolink.org
DirServerHost2 = server3.echolink.org
DirServerHost3 = server4.echolink.org
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
     t
Don’ 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.
--
Regards,
David McAnally (KF7FLY)
10

IRLP Remote admin install script
( I highly recommend installing this 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

Info about GCC
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


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




REMOVING 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
disconnect)
* /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
* 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




                                                                         8
FAQ
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?
No

2. Does the services run at the same time, on a first come,
First 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.



Upgrading the BRIDGE

First, if you are not experiencing problems known to be resolved by
upgrading tbd, don't fix something that is not broken by upgrading.

These are the steps I used to manually update tbd on EchoIRLP nodes.

1. Login as root and download thebridge-0.96.tgz to the node using wget or
other means. The latest released version of tbd can be found at
http://cqinet.sf.net.
2. tar zxvf thebridge-0.96.tgz
3. cd thebridge-0.96



                                                                             9
4. ./configure
5. make
6. /sbin/service tbd stop
7. mv /home/EchoIRLP/tbd/tbd /home/EchoIRLP/tbd/tbd.old
8. mv /home/EchoIRLP/tbd/tbdcmd /home/EchoIRLP/tbd/tbdcmd.old
9. mv src/tbd /home/EchoIRLP/tbd/tbd
10 mv tbdcmd/tbdcmd /home/EchoIRLP/tbd/tbdcmd
11. chown repeater.repeater /home/EchoIRLP/tbd/tbd*
12 /sbin/service tbd start
13. Look for error messages in /var/log/messages and test.




Links
http://www.echoirlp.net
http://groups.yahoo.com/group/EchoIRLP/
http://www.irlp.net
http://www.irlp.net/new-install
http://www.echolink.org/
http://groups.yahoo.com/group/irlp/
http://redhat.irlp.net
http://redhat.irlp.net/echo-install
http://cqinet.sourceforge.net/
http://vkradio.com
http://irlp.kc6hur.net



WINSCP
http://winscp.net/eng/index.php
PUTTY
http://www.chiark.greenend.org.uk/~sgtatham/putty/




Notes, All of this information was taken from emails on the Yahoo EchoIRLP group.
If you have more info to add, please add it or let me know.
W2YMM@ARRL.net
Thanks to David WD5M (ex KF7FLY), Tony VK3JED, Skip WB6YMH, and all the others for this
EchoIRLP project.




                                                                                     10

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:3
posted:8/1/2012
language:
pages:10