<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'><font style="" color="#000000" face="Tahoma,sans-serif">Phil,<br><br> There is nothing different in the Echolink code on the Pi or BBB any version. From the error it seems you might have a problem with the password. Echolink has three possible passwords - call, call-L, and call-R Each can have it own password or they could all be the same. Make absolutely sure your call and suffix match the password on file with echolink.<br><br>Echolink also has the ability to restrict -L and/or -R connections so if you use those suffixes some station may not be able to connect depending on their settings.<br id="FontBreak"></font><br><font style="" face="Tahoma,sans-serif">If you can't find the problem perhaps sending your config file minus the password might help.</font><font style="" face="Tahoma,sans-serif"> The only things you have to do to make echolink work is have the config file and port forwarding setup. Note however you can NOT have more than one echolink connection per public IP address. So the RPi2 has to be the only Echolink at you location in that case unless the other system is using a proxy.</font><font style="" face="Tahoma,sans-serif"><br></font><font style="" face="Tahoma,sans-serif"><br></font><b><font style="font-size:16pt;" size="4">73 Doug</font><font style="font-size:16pt;" size="4"><br></font><font style="font-size:16pt;" size="4">WA3DSP</font><font style="font-size:16pt;" size="4"><br></font><font style="font-size:16pt;" size="4">http://www.crompton.com/hamradio</font></b><font style="font-size:16pt;" size="4"><br></font><br><br><div><hr id="stopSpelling">Date: Sun, 19 Jul 2015 11:16:59 -0400<br>From: phil@philv.net<br>To: arm-allstar@hamvoip.org<br>Subject: [arm-allstar] Incoming echolink connections failing<br><br><div dir="ltr">I've been troubleshooting this issue for a few days now and cant seem to figure it out, and was wondering if others are having this same issue using version 1.0 on the Pi2.<div><br></div><div>I've renamed echlink.xxxx to echolink.conf and edited it to suit my needs. The permit and deny lines are commented out. Im able to connect out to echolink servers (and pass traffic) from my allstar node, but incoming connections fail. </div><div><br></div><div>I have udp ports 5298 and 5199 forwarded to the Pi2 and have confirmed my port forwards are indeed working. When there is a connection attempt i see the following line in /var/log/asterisk/messages:</div><div><br></div><div>ERROR[367] chan_echolink.c: Cannot find DB entry for IP addr 192.168.1.1<br></div><div><br></div><div>The client gets the following message:</div><div><br></div><div>Cannot connect to KD2IAN-L - UN-AUTHORIZED</div><div><br></div><div>I am able to poll the echolink db from cli:</div><div><br></div><div><div>asterisk -rx "echolink dbdump" | grep KD2IAN</div><div>336512|KD2IAN|32.138.245.81</div><div>356468|KD2IAN-L|74.67.157.29</div></div><div><br></div><div>Can anyone give me a bump in the right direction? I cant explain why that error message in messages refers to "192.168.1.1", but im sure that has something to do with the problem. Just as a sidenote, I had an original pi running an echolink node using svxlink running prior to moving over to the Pi2 and allstar. i have not run that and my new allstar node at the same time, but if I turn off my allstar node, fire up the PI, and change my port forwards to point to that machine I am able to make a successful incoming connection to it..... so i am 99% sure the network (port forwards, isp blocking, ect) is not the issue.</div><div><br></div><div>Phil V</div><div>KD2IAN</div></div>
<br>_______________________________________________
arm-allstar mailing list
arm-allstar@hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
Visit the BBB and RPi2 web page - http://hamvoip.org</div> </div></body>
</html>