<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="" face="Tahoma,sans-serif" color="#000000">Matt,<br><br> It would be interesting if it turned out to be the server settings but I have played with many server settings over the years and never had a crash. The echolink code has been stable for a long time. If you can narrow this down so we could test it here it would be helpful. <br><br>Have you looked at echolink dbdump and dbget in the client. Does the database populate before you have the crash? <br><br>dbdump in the client is kind of useless in that it just scrolls all the nodes out. You can do<br><br>asterisk -rx "echolink dbdump" | more or send it to a file.<br><br>My current servers:<br><br>server1=server1.echolink.org<br>;server2=server5.echolink.org<br>server3=server3.echolink.org<br>server2=naeast.echolink.org<br><br>The code requires three servers. Half the time there are not three that actually work and if you look at address resolution on the servers you will see that many are really the same IP address. At the moment server 2,3,NAEAST and NAWEST all have the same IP. <br><br>Name: server1.echolink.org<br>Address: 174.129.36.165<br><br>server2.echolink.org canonical name = server3.echolink.org.<br>Name: server3.echolink.org<br>Address: 174.129.209.125<br><br>Name: server3.echolink.org<br>Address: 174.129.209.125<br><br>Name: server4.echolink.org<br>Address: 50.18.55.39<br><br>Name: server5.echolink.org<br>Address: 68.178.144.151<br><br>naeast.echolink.org canonical name = server3.echolink.org.<br>Name: server3.echolink.org<br>Address: 174.129.209.125<br><br>nawest.echolink.org canonical name = server3.echolink.org.<br>Name: server3.echolink.org<br>Address: 174.129.209.125<br><br>None of the echolink servers including ones not listed here seem to return pings which is strange. I thought they use to.<br></font><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">http://www.crompton.com/hamradio</font></b><font style="font-size:16pt;" size="4"><br></font><br><br><div><hr id="stopSpelling">Date: Sun, 29 May 2016 19:57:02 +0100<br>To: arm-allstar@hamvoip.org<br>Subject: Re: [arm-allstar] Asterisk crashing when Echolink connected<br>From: arm-allstar@hamvoip.org<br>CC: matt@m0lmk.co.uk<br><br>
Hi David,<br>
<br>
I'll keep it on the list if you don't mind as it may help others if this
problem comes up again. I have a working theory but I need to do a bit
more testing to confirm.<br>
<br>
Here are these servers listed in my echolink.conf...<br>
<br>
server1=servers.echolink.org<br>
server2=naeast.echolink.org<br>
server3=backup.echolink.org<br>
<br>
I noticed that the crash happened just after this line in the asterisk
console..<br>
<br>
-- Received OK from Echolink server servers.echolink.org<br>
-- Received OK from Echolink server backup.echolink.org<br>
allstar*CLI> <br>
Disconnected from Asterisk server<br>
Executing last minute cleanups<br>
<br>
So, I've changed the servers to the following...<br>
<br>
server1=europe.echolink.org<br>
server2=servers.echolink.org<br>
server3=backup.echolink.org<br>
<br>
And now it only connects to a single server in the asterisk console...<br>
<br>
-- Call changed from OUTBOUND to *ECHOTEST*<br>
-- Name changed from OUTBOUND to (Conference [9]) CONF<br>
-- Received OK from Echolink server europe.echolink.org<br>
-- Directory pgm done downloading(partial,compressed), 377 records<br>
<br>
And have been up for 20 minutes without a crash. Maybe the problem was a
bad server in the echolink pool?<br>
<br>
In answer to your questions.<br>
<br>
Is IPv6 networking in this mixture anywhere? - We have an ipv6 tunnel
set up on our main router but all internal networking is ipv4<br>
What are your Echolink and AllStar node numbers? 43412 (AllStar), 214700
(Echolink)<br>
Does the crash occur when connecting to all Echolink nodes (like the
Echolink *ECHOTEST* conference server, node #9999)? Happens on all nodes
I have tried<br>
Does AllStar connectivity work properly? Yes. I have not seen any
asterisk crashes when not connected or when connected to an allstar node<br>
<br>
My current echolink.conf<br>
<br>
[el0]<br>
confmode=no<br>
call=MB7IBK-L ; Change this!<br>
pwd=pypassword ; Change this!<br>
name=MB7IBK ; Change this to your real name!<br>
qth=Broadstairs, UK ; Change this to your actual QTH!<br>
<a class="ecxmoz-txt-link-abbreviated" href="mailto:email=matt@m0lmk.co.uk">email=matt@m0lmk.co.uk</a> ; Change this!<br>
maxstns=20<br>
rtcptimeout=10<br>
node=214700 ; Echolink node number - Change this!<br>
recfile=/tmp/recorded.gsm<br>
astnode=43412 ; Change this to your active Allstar node
number!<br>
context=radio-secure<br>
server1=europe.echolink.org<br>
server2=servers.echolink.org<br>
server3=backup.echolink.org<br>
;server1=servers.echolink.org<br>
;server2=naeast.echolink.org<br>
;server3=backup.echolink.org<br>
; Change following setting to your parameters<br>
freq=145.2125<br>
tone=103.5<br>
lat=51.36242 <br>
lon=1.44442<br>
power=1<br>
height=1<br>
gain=0<br>
dir=0<br>
;deny=<br>
;permit=<br>
<br>
<br>
<br>
Hope that helps.<br>
<br>
Matt<br>
M0LMK<span><br>
</span>
<blockquote style="border:0px none;" cite="mid:Pine.LNX.4.44.1605291435580.725-100000@goliath.inttek.net">
<div style="" class="ecx__pbConvHr"><div style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px;"> <div style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a href="mailto:arm-allstar@hamvoip.org" style="color:#737F92 !important;padding-right:6px;font-weight:bold;text-decoration:none !important;">David McGough via arm-allstar</a></div> <div style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:right;"> <font color="#9FA2A5"><span style="padding-left:6px;">29
May 2016 at 19:46</span></font></div> </div></div>
<div style="color:#888888;" class="ecx__pbConvBody"><div>Hi Matt,<br><br>As others
have mentioned, I've not seen this issue previously. I've got a<br>few
questions to try and help debug this, feel free to send my a private<br>e-mail
with answers, if you would prefer.<br><br>Is IPv6 networking in this
mixture anywhere?<br><br>What are your Echolink and AllStar node
numbers?<br><br>Does the crash occur when connecting to all Echolink
nodes (like the <br>Echolink *ECHOTEST* conference server, node #9999)?<br><br>If
only specific node numbers cause the crash, what nodes are they?<br><br>Does
AllStar connectivity work properly?<br><br><br>Thanks,<br><br>73, David
KB4FXC<br><br><br></div><div><br>_______________________________________________<br><br>arm-allstar
mailing list<br><a class="ecxmoz-txt-link-abbreviated" href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br><a class="ecxmoz-txt-link-freetext" 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 and RPi2 web page - <a class="ecxmoz-txt-link-freetext" href="http://hamvoip.org" target="_blank">http://hamvoip.org</a><br></div></div>
<div style="" class="ecx__pbConvHr"><div style="width:100%;border-top:1px solid #EDEEF0;padding-top:5px;"> <div style="display:inline-block;white-space:nowrap;vertical-align:middle;width:49%;">
<a href="mailto:arm-allstar@hamvoip.org" style="color:#737F92 !important;padding-right:6px;font-weight:bold;text-decoration:none !important;">Matt via arm-allstar</a></div> <div style="display:inline-block;white-space:nowrap;vertical-align:middle;width:48%;text-align:right;"> <font color="#9FA2A5"><span style="padding-left:6px;">29
May 2016 at 19:31</span></font></div> </div></div>
<div style="color:#888888;" class="ecx__pbConvBody">
Results so far...<br>
<br>
RPi 3 still shows the same behavior although not as often. I've now
changed the power supply and am still seeing the same issue. The last
thing on my list is the interface but I don't have a spare so that's
going to be tough to test.<br>
<br>
It seems to only crash asterisk when initially connecting to a remote
node and as soon as asterisk restarts, the connection works fine.<br>
<br>
<span>How very odd.<br>
<br>
Matt<br>
M0LMK<br>
</span>
<br>
<div>_______________________________________________<br><br>arm-allstar
mailing list<br><a class="ecxmoz-txt-link-abbreviated" href="mailto:arm-allstar@hamvoip.org">arm-allstar@hamvoip.org</a><br><a class="ecxmoz-txt-link-freetext" 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 and RPi2 web page - <a class="ecxmoz-txt-link-freetext" href="http://hamvoip.org" target="_blank">http://hamvoip.org</a></div></div>
</blockquote>
<br>
<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>