<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>The db connection to echolink servers is not done in real time. So, if a user fires up their desktop or smartdevice application and immediately attempts to connect, they will not be seen as authorized. Wait 10 minutes or so, and it will work direct as the changed database gets polled. </div><div><br></div><div>As you've noticed, if they connect via a proxy, which by definition are more persistent and thus more likely to be in the loaded database at the node end, they will be able to connect almost immediately, since the authentication is done via the proxy, with the credential apparently passed through to the asterisk node.</div><div><br></div><div>The echolink channel software is a compromise to connect to a legacy network that has had little to no development or improvements since its introduction, IMHO. It should not be seen as equivalent in operation to the native Windows-based server.<br><br>--<div>Bryan</div><div>Sent from my iPhone 5.<span style="font-size: 13pt;">..No electrons were harmed in the sending of this message.</span></div><div><br><div><br></div></div></div><div><br>On Jun 8, 2015, at 10:27, Pete M <<a href="mailto:petem001@hotmail.com">petem001@hotmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><span>Is there a command to force a full DB download from echolink?</span><br><span></span><br><span>Seen many time that am echolink user try to connect to my node, it is not known in the DB on my node, this trig a DB download, it receive a partial one then it is rejected cause not in the DB.</span><br><span></span><br><span>the only way I can fix this is by stopping the service then start it back, the echolink driver will make a full DB download and the user can then connect.. So it is not a networking isue, user that use a public echolink proxy conect every time (cause the proxy dont change IP most of the time and are in the DB from the start)</span><br><span></span><br><span>I am not fluent in C so cant read the source to understand how this is working..</span><br><span></span><br><span>Pierre</span><br><span></span><br><span></span><br><span>-----Message d'origine----- From: Tim Sawyer</span><br><span>Sent: Sunday, June 07, 2015 9:00 AM</span><br><span>To: David Osborn</span><br><span>Cc: <a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a></span><br><span>Subject: Re: [App_rpt-users] Echolink Updates</span><br><span></span><br><span>FYI…</span><br><span></span><br><span>asterisk -rx "echolink dbdump" | grep ON0VOS</span><br><span>356825|ON0VOS-L|81.165.69.72</span><br><span></span><br><span>--</span><br><span>Tim</span><br><span>:wq</span><br><span></span><br><blockquote type="cite"><span>On Jun 7, 2015, at 5:32 AM, David Osborn <<a href="mailto:david.osborn@manx.net">david.osborn@manx.net</a>> wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Greetings from the Isle of Man,</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>We seldom use Echolink for outgoing connections but, with an influx of</span><br></blockquote><blockquote type="cite"><span>visitors for the Isle of Man TT races this week, we've seen a couple of</span><br></blockquote></div></blockquote></body></html>