<div dir="ltr">Yes, every one from the command line on the BBB.<br><br>[root@bbb-allstar1 asterisk]# ping <a href="http://server1.echolink.org">server1.echolink.org</a><br>PING <a href="http://server1.echolink.org">server1.echolink.org</a> (174.129.36.165) 56(84) bytes of data.<br>
64 bytes from <a href="http://ec2-174-129-36-165.compute-1.amazonaws.com">ec2-174-129-36-165.compute-1.amazonaws.com</a> (174.129.36.165): icmp_seq=1 ttl=44 time=47.7 ms<br>64 bytes from <a href="http://ec2-174-129-36-165.compute-1.amazonaws.com">ec2-174-129-36-165.compute-1.amazonaws.com</a> (174.129.36.165): icmp_seq=2 ttl=44 time=45.9 ms<br>
<br>[root@bbb-allstar1 asterisk]# ping <a href="http://server3.echolink.org">server3.echolink.org</a><br>PING <a href="http://server3.echolink.org">server3.echolink.org</a> (174.129.209.125) 56(84) bytes of data.<br>64 bytes from <a href="http://ec2-174-129-209-125.compute-1.amazonaws.com">ec2-174-129-209-125.compute-1.amazonaws.com</a> (174.129.209.125): icmp_seq=1 ttl=39 time=44.7 ms<br>
64 bytes from <a href="http://ec2-174-129-209-125.compute-1.amazonaws.com">ec2-174-129-209-125.compute-1.amazonaws.com</a> (174.129.209.125): icmp_seq=2 ttl=39 time=46.5 ms<br><br>[root@bbb-allstar1 asterisk]# ping <a href="http://nawest.echolink.org">nawest.echolink.org</a><br>
PING <a href="http://server3.echolink.org">server3.echolink.org</a> (174.129.209.125) 56(84) bytes of data.<br>64 bytes from <a href="http://ec2-174-129-209-125.compute-1.amazonaws.com">ec2-174-129-209-125.compute-1.amazonaws.com</a> (174.129.209.125): icmp_seq=1 ttl=39 time=48.8 ms<br>
64 bytes from <a href="http://ec2-174-129-209-125.compute-1.amazonaws.com">ec2-174-129-209-125.compute-1.amazonaws.com</a> (174.129.209.125): icmp_seq=2 ttl=39 time=45.7 ms<br><br>[root@bbb-allstar1 asterisk]# ping <a href="http://naeast.echolink.org">naeast.echolink.org</a><br>
PING <a href="http://server3.echolink.org">server3.echolink.org</a> (174.129.209.125) 56(84) bytes of data.<br>64 bytes from <a href="http://ec2-174-129-209-125.compute-1.amazonaws.com">ec2-174-129-209-125.compute-1.amazonaws.com</a> (174.129.209.125): icmp_seq=1 ttl=39 time=46.0 ms<br>
64 bytes from <a href="http://ec2-174-129-209-125.compute-1.amazonaws.com">ec2-174-129-209-125.compute-1.amazonaws.com</a> (174.129.209.125): icmp_seq=2 ttl=39 time=51.6 ms<br><br><br><div></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Aug 27, 2014 at 12:29 PM, Doug Crompton <span dir="ltr"><<a href="mailto:doug@crompton.com" target="_blank">doug@crompton.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr"><font face="Tahoma">Joel,<br><br> Can you ping the servers?<br><br>[root@WA3DSP_Allstar ~]# ping <a href="http://server1.echolink.org" target="_blank">server1.echolink.org</a><br>PING <a href="http://server1.echolink.org" target="_blank">server1.echolink.org</a> (174.129.36.165) 56(84) bytes of data.<br>
64 bytes from <a href="http://ec2-174-129-36-165.compute-1.amazonaws.com" target="_blank">ec2-174-129-36-165.compute-1.amazonaws.com</a> (174.129.36.165): icmp_seq=1 ttl=47 time=19.3 ms<br>64 bytes from <a href="http://ec2-174-129-36-165.compute-1.amazonaws.com" target="_blank">ec2-174-129-36-165.compute-1.amazonaws.com</a> (174.129.36.165): icmp_seq=2 ttl=47 time=19.9 ms<br>
<br>Also make sure your node call name and PW are correct in the config file. I think case matters in the call and it certainly does in the PW. Also the node number is the one for that call.<br></font><div class=""><br><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"><a href="http://www.crompton.com/hamradio" target="_blank">http://www.crompton.com/hamradio</a></font></b><font style="font-size:16pt" size="4"><br>
</font><br><br></div><div><hr>Date: Wed, 27 Aug 2014 11:44:05 -0500<br>From: <a href="mailto:w0kgw3@gmail.com" target="_blank">w0kgw3@gmail.com</a><br>To: <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>
Subject: Re: [arm-allstar] Question on Echolink configuration<div><div class="h5"><br><br><div dir="ltr">Still no luck, none of the servers seem to respond. <br><br>I guess it's time to get out the sniffer and see what's going on.<br>
<div><div></div></div></div><div><br><br><div>
On Tue, Aug 26, 2014 at 7:22 PM, Doug Crompton <span dir="ltr"><<a href="mailto:doug@crompton.com" target="_blank">doug@crompton.com</a>></span> wrote:<br><blockquote style="border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr"><font face="Tahoma">Joel,<br><br> I never had any luck with those servers. Here are the ones I use that work -<br><br>server1=<a href="http://server1.echolink.org" target="_blank">server1.echolink.org</a><br>
server2=<a href="http://server5.echolink.org" target="_blank">server5.echolink.org</a><br>server3=<a href="http://server3.echolink.org" target="_blank">server3.echolink.org</a><br><br>Also go into the client and you can do - 'echolink dbdump' and it should display the entire list.<br>
<br>You can also display specifically by node number or callsign -<br><br>WA3DSP_Allstar*CLI> echolink dbget c WA3DSP-L<br>147090|WA3DSP-L|50.191.8.33<br><br>WA3DSP_Allstar*CLI> echolink dbget n 147090<br>147090|WA3DSP-L|50.191.8.33<br>
<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"><a href="http://www.crompton.com/hamradio" target="_blank">http://www.crompton.com/hamradio</a></font></b><font style="font-size:16pt" size="4"><br>
</font><br><br><div><hr>Date: Tue, 26 Aug 2014 18:59:57 -0500<br>From: <a href="mailto:w0kgw3@gmail.com" target="_blank">w0kgw3@gmail.com</a><br>To: <a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>
Subject: [arm-allstar] Question on Echolink configuration<div><div><br><br><div dir="ltr"><div><div><div>I'm receiving a pile of errors connecting to echolink.<br><br>[Aug 26 18:46:50] ERROR[405] chan_echolink.c: Error in parsing header on <a href="http://naeast.echolink.org" target="_blank">naeast.echolink.org</a><br>
[Aug 26 18:47:10] ERROR[405] chan_echolink.c: Error in parsing header on <a href="http://nasouth.echolink.org" target="_blank">nasouth.echolink.org</a><br>[Aug 26 18:47:30] ERROR[405] chan_echolink.c: Error in parsing header on <a href="http://servers.echolink.org" target="_blank">servers.echolink.org</a><br>
<br></div>(repeat each one every 20 seconds)<br><br></div>I tried with the default server1 setup, then with nawest which is what I'm supposed to be using, then naeast, but the errors constantly crop up and it does not show up on the echolink node lists. Currently a fresh BBB 1.1 image is loaded, with node configuration changes as listed in the setup documents<br>
<br>I've forwarded the correct ports to the BBB from the internet through my firewall (and tested them).<br><br>asterisk]# cat echolink.conf<br>[el0]<br>confmode=no<br>call=W0KGW-R<br>pwd=Yes I changed this<br>name=W0REA/R Isle, MN Repeater<br>
qth=Isle, MN<br>email=<a href="mailto:w0kgw3@gmail.com" target="_blank">w0kgw3@gmail.com</a><br>maxstns=5<br>rtcptimeout=10<br>node=234724<br>recfile=/tmp/recorded.gsm<br><br>astnode=41187<br>context=radio-secure<br>server1=<a href="http://naeast.echolink.org" target="_blank">naeast.echolink.org</a><br>
server2=<a href="http://nasouth.echolink.org" target="_blank">nasouth.echolink.org</a><br>server3=<a href="http://servers.echolink.org" target="_blank">servers.echolink.org</a><br>server4=<a href="http://backup.echolink.org" target="_blank">backup.echolink.org</a><br>
<br>
</div>Cheers,<br>Joel<br>W0KGW<br><div><div><div><div></div></div></div></div></div>
<br></div></div>_______________________________________________
arm-allstar mailing list
<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a>
Visit the BBB web page - <a href="http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/" target="_blank">http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/</a></div> </div></div>
<br>_______________________________________________<br>
<br>
arm-allstar mailing list<br>
<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a><br>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a><br>
<br>
Visit the BBB web page - <a href="http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/" target="_blank">http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/</a><br></blockquote></div><br></div>
<br>_______________________________________________
arm-allstar mailing list
<a href="mailto:arm-allstar@hamvoip.org" target="_blank">arm-allstar@hamvoip.org</a>
<a href="http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a>
Visit the BBB web page - <a href="http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/" target="_blank">http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/</a></div></div></div> </div></div>
<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" target="_blank">http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar</a><br>
<br>
Visit the BBB web page - <a href="http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/" target="_blank">http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/</a><br></blockquote></div><br></div>