[arm-allstar] help with echolink setup
Roselito de los Reyes
tolitski at hotmail.com
Thu Mar 24 12:18:02 EST 2016
Doug,
I do agree with your statement. A lot of times, our users (filipino kapihan hub) will gauge the audio they hear from an allstar node in Echolink and I think that it is comparing apples and oranges. But for our allstar radio networks to be accessible from the smartphone, the Echolink client is still the easiest tool to connect to our network.
I hope someone will take on an "allstar client" project other than Zoiper that is easy to set up from a "plain user perspective" without much configuration on the server, only then we can be rid of the "Echolink clients" at that time; at least in the perfect world :D
I really appreciate the time and effort this team has put in to make our hobby an enjoyable one.
73,
Lito/KK6OOS
To: w5jr.lists at gmail.com
Date: Thu, 24 Mar 2016 12:56:03 -0400
Subject: Re: [arm-allstar] help with echolink setup
From: arm-allstar at hamvoip.org
CC: doug at crompton.com; arm-allstar at hamvoip.org
Mike,
Here is an example using autopatch mode and dialplan. This is off the top of my head but should work. The only problem is the number of digits in echolink node numbers. Here it is fixed to 6. You could do some things to work around this.
The other thing that everyone has to remember is this is Allstar NOT Echolink. Encouraging Echolink users to become Allstar nodes when possible is recommended. If you end up with more Echolink users than Allstar that defeats the purpose of Allstar and also pollutes our network with bad audio. Also the threat was placed out there about a year ago by Echolink admin that they do not want to be connected to other voip services and reserve the right to ban stations that abuse that. To my knowledge that has not taken place.
In rpt.conf
621=autopatchup,context=echolink_disconnect,noct=1,farenddisconnect=1,dialtime=10000,quiet=1
623=autopatchup,context=echolink_connect,noct=1,farenddisconnect=1,dialtime=10000,quiet=1
in extensions.conf
[echolink_connect]
exten => _xxxxxx,1,System(/etc/asterisk/local/echolink_process 3 ${EXTEN})
exten => _xxxxxx,n,Hangup()
[echolink_disconnect]
exten => _xxxxxx,1,System(/etc/asterisk/local/echolink_process 1 ${EXTEN})
exten => _xxxxxx,n,Hangup()
in /etc/asterisk/local/echolink_process, create and make executable.
#!/bin/bash
#
# /etc/asterisk/local/echolink_process
#
# . /usr/local/etc/allstar.env
sleep 2
# Say the passed digits - optional for testing
/usr/local/sbin/speaktext.sh $1$2
sleep 2
/usr/bin/asterisk -rx "rpt fun xxxxx $1$2
# end of script
Using this method users would enter *623xxxxxx or *621xxxxxx to connect or disconnect from the xxxxxx Echolink node.
73 Doug
WA3DSP
http://www.crompton.com/hamradio
_______________________________________________
arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
Visit the BBB and RPi2 web page - http://hamvoip.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160324/6cce34e5/attachment.html>
More information about the arm-allstar
mailing list