<div dir="ltr">You were both spot on. Going through echolink.conf once again ..... i realized I did not have my password in all uppercase. <div><br></div><div>I had also transposed 2 digits in my allstar node number in that config file. Works perfectly now.</div><div><br></div><div>Thanks to both of you.<br></div><div><br></div><div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jul 19, 2015 at 1:00 PM, <span dir="ltr"><<a href="mailto:arm-allstar-request@hamvoip.org" target="_blank">arm-allstar-request@hamvoip.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send arm-allstar mailing list submissions to<br>
<a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" rel="noreferrer" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:arm-allstar-request@hamvoip.org">arm-allstar-request@hamvoip.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:arm-allstar-owner@hamvoip.org">arm-allstar-owner@hamvoip.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of arm-allstar digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Incoming echolink connections failing (Phil Visalli)<br>
2. Re: Incoming echolink connections failing (Doug Crompton)<br>
3. Re: Incoming echolink connections failing (Kenneth Grimard)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sun, 19 Jul 2015 11:16:59 -0400<br>
From: Phil Visalli <<a href="mailto:phil@philv.net">phil@philv.net</a>><br>
To: <a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
Subject: [arm-allstar] Incoming echolink connections failing<br>
Message-ID:<br>
<<a href="mailto:CAAMk9h-nqTGBqKSwenUMvqVAf3xCPvjgMYcLmWXtc6F8_cdehQ@mail.gmail.com">CAAMk9h-nqTGBqKSwenUMvqVAf3xCPvjgMYcLmWXtc6F8_cdehQ@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
I've been troubleshooting this issue for a few days now and cant seem to<br>
figure it out, and was wondering if others are having this same issue using<br>
version 1.0 on the Pi2.<br>
<br>
I've renamed echlink.xxxx to echolink.conf and edited it to suit my needs.<br>
The permit and deny lines are commented out. Im able to connect out to<br>
echolink servers (and pass traffic) from my allstar node, but incoming<br>
connections fail.<br>
<br>
I have udp ports 5298 and 5199 forwarded to the Pi2 and have confirmed my<br>
port forwards are indeed working. When there is a connection attempt i see<br>
the following line in /var/log/asterisk/messages:<br>
<br>
ERROR[367] chan_echolink.c: Cannot find DB entry for IP addr 192.168.1.1<br>
<br>
The client gets the following message:<br>
<br>
Cannot connect to KD2IAN-L - UN-AUTHORIZED<br>
<br>
I am able to poll the echolink db from cli:<br>
<br>
asterisk -rx "echolink dbdump" | grep KD2IAN<br>
336512|KD2IAN|32.138.245.81<br>
356468|KD2IAN-L|74.67.157.29<br>
<br>
Can anyone give me a bump in the right direction? I cant explain why that<br>
error message in messages refers to "192.168.1.1", but im sure that has<br>
something to do with the problem. Just as a sidenote, I had an original pi<br>
running an echolink node using svxlink running prior to moving over to the<br>
Pi2 and allstar. i have not run that and my new allstar node at the same<br>
time, but if I turn off my allstar node, fire up the PI, and change my port<br>
forwards to point to that machine I am able to make a successful incoming<br>
connection to it..... so i am 99% sure the network (port forwards, isp<br>
blocking, ect) is not the issue.<br>
<br>
Phil V<br>
KD2IAN<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150719/823b9afb/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150719/823b9afb/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Sun, 19 Jul 2015 12:21:24 -0400<br>
From: Doug Crompton <<a href="mailto:doug@crompton.com">doug@crompton.com</a>><br>
To: ARM Allstar <<a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a>><br>
Subject: Re: [arm-allstar] Incoming echolink connections failing<br>
Message-ID: <BLU171-W45B393DFE423A705969372BA860@phx.gbl><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
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>
If you can't find the problem perhaps sending your config file minus the password might help. 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.<br>
<br>
73 Doug<br>
WA3DSP<br>
<a href="http://www.crompton.com/hamradio" rel="noreferrer" target="_blank">http://www.crompton.com/hamradio</a><br>
<br>
<br>
Date: Sun, 19 Jul 2015 11:16:59 -0400<br>
From: <a href="mailto:phil@philv.net">phil@philv.net</a><br>
To: <a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
Subject: [arm-allstar] Incoming echolink connections failing<br>
<br>
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.<br>
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.<br>
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:<br>
ERROR[367] chan_echolink.c: Cannot find DB entry for IP addr 192.168.1.1<br>
<br>
The client gets the following message:<br>
Cannot connect to KD2IAN-L - UN-AUTHORIZED<br>
I am able to poll the echolink db from cli:<br>
asterisk -rx "echolink dbdump" | grep KD2IAN336512|KD2IAN|32.138.245.81356468|KD2IAN-L|74.67.157.29<br>
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.<br>
Phil VKD2IAN<br>
<br>
_______________________________________________<br>
<br>
arm-allstar mailing list<br>
<a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" rel="noreferrer" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a><br>
<br>
Visit the BBB and RPi2 web page - <a href="http://hamvoip.org" rel="noreferrer" target="_blank">http://hamvoip.org</a><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150719/f10bffa1/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150719/f10bffa1/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Sun, 19 Jul 2015 16:44:24 +0000<br>
From: Kenneth Grimard <<a href="mailto:n1dot1@gmail.com">n1dot1@gmail.com</a>><br>
To: <a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
Subject: Re: [arm-allstar] Incoming echolink connections failing<br>
Message-ID: <<a href="mailto:55ABD3E8.8000404@gmail.com">55ABD3E8.8000404@gmail.com</a>><br>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"<br>
<br>
also m,ake sure the password and callsign are upper case also<br>
<br>
ken n1dot<br>
<br>
<br>
<br>
On 7/19/2015 4:21 PM, Doug Crompton wrote:<br>
> Phil,<br>
><br>
> There is nothing different in the Echolink code on the Pi or BBB any<br>
> version. From the error it seems you might have a problem with the<br>
> password. Echolink has three possible passwords - call, call-L, and<br>
> call-R Each can have it own password or they could all be the same.<br>
> Make absolutely sure your call and suffix match the password on file<br>
> with echolink.<br>
><br>
> Echolink also has the ability to restrict -L and/or -R connections so<br>
> if you use those suffixes some station may not be able to connect<br>
> depending on their settings.<br>
><br>
> If you can't find the problem perhaps sending your config file minus<br>
> the password might help.The only things you have to do to make<br>
> echolink work is have the config file and port forwarding setup. Note<br>
> however you can NOT have more than one echolink connection per public<br>
> IP address. So the RPi2 has to be the only Echolink at you location in<br>
> that case unless the other system is using a proxy.<br>
><br>
> *73 Doug<br>
> WA3DSP<br>
> <a href="http://www.crompton.com/hamradio*" rel="noreferrer" target="_blank">http://www.crompton.com/hamradio*</a><br>
><br>
><br>
> ------------------------------------------------------------------------<br>
> Date: Sun, 19 Jul 2015 11:16:59 -0400<br>
> From: <a href="mailto:phil@philv.net">phil@philv.net</a><br>
> To: <a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
> Subject: [arm-allstar] Incoming echolink connections failing<br>
><br>
> I've been troubleshooting this issue for a few days now and cant seem<br>
> to figure it out, and was wondering if others are having this same<br>
> issue using version 1.0 on the Pi2.<br>
><br>
> I've renamed echlink.xxxx to echolink.conf and edited it to suit my<br>
> needs. The permit and deny lines are commented out. Im able to<br>
> connect out to echolink servers (and pass traffic) from my allstar<br>
> node, but incoming connections fail.<br>
><br>
> I have udp ports 5298 and 5199 forwarded to the Pi2 and have confirmed<br>
> my port forwards are indeed working. When there is a connection<br>
> attempt i see the following line in /var/log/asterisk/messages:<br>
><br>
> ERROR[367] chan_echolink.c: Cannot find DB entry for IP addr 192.168.1.1<br>
><br>
> The client gets the following message:<br>
><br>
> Cannot connect to KD2IAN-L - UN-AUTHORIZED<br>
><br>
> I am able to poll the echolink db from cli:<br>
><br>
> asterisk -rx "echolink dbdump" | grep KD2IAN<br>
> 336512|KD2IAN|32.138.245.81<br>
> 356468|KD2IAN-L|74.67.157.29<br>
><br>
> Can anyone give me a bump in the right direction? I cant explain why<br>
> that error message in messages refers to "192.168.1.1", but im sure<br>
> that has something to do with the problem. Just as a sidenote, I had<br>
> an original pi running an echolink node using svxlink running prior to<br>
> moving over to the Pi2 and allstar. i have not run that and my new<br>
> allstar node at the same time, but if I turn off my allstar node, fire<br>
> up the PI, and change my port forwards to point to that machine I am<br>
> able to make a successful incoming connection to it..... so i am 99%<br>
> sure the network (port forwards, isp blocking, ect) is not the issue.<br>
><br>
> Phil V<br>
> KD2IAN<br>
><br>
> _______________________________________________ arm-allstar mailing<br>
> list <a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
> <a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" rel="noreferrer" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a> Visit<br>
> the BBB and RPi2 web page - <a href="http://hamvoip.org" rel="noreferrer" target="_blank">http://hamvoip.org</a><br>
><br>
><br>
> _______________________________________________<br>
><br>
> arm-allstar mailing list<br>
> <a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
> <a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" rel="noreferrer" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a><br>
><br>
> Visit the BBB and RPi2 web page - <a href="http://hamvoip.org" rel="noreferrer" target="_blank">http://hamvoip.org</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150719/6b37ef55/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20150719/6b37ef55/attachment-0001.html</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
arm-allstar mailing list<br>
<a href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" rel="noreferrer" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a><br>
<br>
<br>
End of arm-allstar Digest, Vol 14, Issue 27<br>
*******************************************<br>
</blockquote></div><br></div></div></div>