Thanks for taking the time to answer the question, that answer is good but it is not exactly what is happening..
 
The echolink driver trigger a DB download and do receive a partial DB (the update that need to be done) at that moment.. So the new user should be in that new DB. So why is it rejected?
 
one thing I did noticed. even after 10 minute it still wont work.. in fact, when i receive a call from one of my user asking why there echolink connection to the repeater wont work, usely they been trying for some time, and by the time and go and do some test, they’ve been online for a lot more then 10 minute..
 
I do understand that Scott don’t work on the project anymore.. But there must be a way to do something in the software like:
 
receive echolink connection -
check the IP and calsign against the DB
IP and call in DB  yes, make a connection
No ask for a partial DB download
check against the new DB
user in DB? yes connect
No ask for a full DB download.
Check if ip and call in the DB
yes connect.
No reject the connection..
 
 
do this make sens?
 
I am reading the source right now..
 
If only I could understand C..
 
 
 
Sent: Monday, June 08, 2015 11:27 AM
To: APP RPT
Subject: Re: [App_rpt-users] Echolink Updates
 
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. 
 
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.
 
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.

--
Bryan
Sent from my iPhone 5...No electrons were harmed in the sending of this message.
 
 

On Jun 8, 2015, at 10:27, Pete M <petem001@hotmail.com> wrote:

Is there a command to force a full DB download from echolink?

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.

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)

I am not fluent in C so cant read the source to understand how this is working..

Pierre


-----Message d'origine----- From: Tim Sawyer
Sent: Sunday, June 07, 2015 9:00 AM
To: David Osborn
Cc: app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] Echolink Updates

FYI…

asterisk -rx "echolink dbdump" | grep ON0VOS
356825|ON0VOS-L|81.165.69.72

--
Tim
:wq

On Jun 7, 2015, at 5:32 AM, David Osborn <david.osborn@manx.net> wrote:

Greetings from the Isle of Man,

We seldom use Echolink for outgoing connections but, with an influx of
visitors for the Isle of Man TT races this week, we've seen a couple of

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.