Native Echolink Support in app_rpt 

App_rpt.c version 0.148 or greater now supports inbound and outbound echolink connections. No other programs  (e.g. rtpDir, or the link box are required. With chan_echolink, Echolink nodes become part of the Allstar link number space.

From an app_rpt/Allstar node, Echolink connections look just like Allstar/App_rpt connections except the Echolink node numbers have been prefixed with a 3 and padded out to 7 digits with leading zeroes. For example, if you want to connect to Echolink node 1234 on your app_rpt system you would dial *3 followed by 3001234. If you have a 6 digit Echolink node number 123456, you would dial *3 followed by 3123456. As you can see we have reserved Allstar node numbers with a leading 3 for the Echolink number space.

For users originating from an Echolink node using Echolink supplied software, nothing changes for them, they just dial the 4 or 6 digit Echolink node number assigned to your app_rpt system and they get connected!

Installation Instructions for ACID

1. Create a new file /etc/asterisk/echolink.conf and put the following text in it:

[el0]
confmode=no
call=W6ABC-R            ; Change this!
pwd=XXXXX               ; Change this!
name=Asterisk-EL-channel-driver ; Change this to your real name!
qth=Asterisk-EL-channel-driver ; Change this to your actual QTH!
email=foo@bar.com ; Change this!
maxstns=20
rtcptimeout=10
node=123456 ; Change this!
recfile=/tmp/recorded.gsm
astnode=2345 ; Change this to your active Allstar node number!
context=radio-secure
server1=server1.echolink.org
server2=server2.echolink.org
server3=server3.echolink.org

 

2. Change the call, pwd, name, qth, email values to something meaningful. (You should know what to do here! pwd is your password for Echolink)

3. Change the node value  to the echolink node number assigned to the app_rpt system (not your client node number!) Use the *-R or *-L Echolink callsign node numbers for this.

4. Change the astnode value to the node number assigned by allstarlink.org of the Allstar node on your app_rpt machine which will allow and make Echolink connections.

5. Verify that you have a radio-secure context in extensions.conf with an entry pointing to the node number defined by astnode.

6. Restart Asterisk 

Testing
 

1. Go into the Asterisk console (asterisk -r) wait 30 seconds or so, then type database show. You should see a bunch of Echolink node numbers get printed on the console.

2. From an Echolink client, try to connect to the node.

3. Try to connect to Echolink client from the Allstar node using the prefixing instructions above.