[App_rpt-users] Echolink Updates

[Tim Sawyer]

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 at 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
> stations trying to connect "back home" via Echolink - and failing.
> 
> The issue seems to be that AllStar is unaware of the nodes that the users
> are trying to connect to. An example is ON0VOS-L (node 356825).
> 
> If I issue the command "asterisk -rx "database show" | grep ON0" I get a
> list of entries similar to ON0VOS, but not the one that I'm interested in. 
> Also, comparing with the current logins page on the Echolink site. There
> are a lot of other nodes missing from the Allstar database.
> 
> Does anyone know why this might be and what I can do about it? I want our
> visitors to be able to leave with a favourable view of AllStar and even if I
> have to fudge a nasty hack to make the desired nodes accessible, I'll do it!
> 
> Here's a clipping of sections of the response to the database show command
> mentioned above.
> 
> /echolink/a/call/ON0OST-R                         : 82010:91.181.37.10
> /echolink/a/call/ON0RCL-R                         : 377156:83.101.44.168
> /echolink/a/call/ON0TLO-R                         : 488668:193.22.239.31
> /echolink/a/call/ON0WL-R                          : 409331:81.83.131.158
> /echolink/a/call/ON0WV-R                          : 357361:91.181.123.174
> 
> /echolink/b/call/ON0OST-R                         : 82010:91.181.102.165
> /echolink/b/call/ON0RCL-R                         : 377156:83.101.44.168
> /echolink/b/call/ON0TLO-R                         : 488668:193.22.239.31
> /echolink/b/call/ON0WL-R                          : 409331:81.83.131.158
> /echolink/b/call/ON0WV-R                          : 357361:91.181.69.224
> 
> /echolink/b/nodenum-call/160278	: ON0LIR-R
> /echolink/b/nodenum-call/171471	: ON0GRC-R
> /echolink/b/nodenum-call/187696	: ON0LG-R
> /echolink/b/nodenum-call/282623	: ON0KTK-R
> /echolink/b/nodenum-call/352778	: ON0DVS-R
> /echolink/b/nodenum-call/357361	: ON0WV-R
> /echolink/b/nodenum-call/368568          : ON0KB-R
> /echolink/b/nodenum-call/377156          : ON0RCL-R
> /echolink/b/nodenum-call/394137          : ON0LN-R
> /echolink/b/nodenum-call/409331          : ON0WL-R
> /echolink/b/nodenum-call/429437          : ON0BA-R
> /echolink/b/nodenum-call/45573            : ON0AN-R
> /echolink/b/nodenum-call/47009            :ON0LFE-L
> /echolink/b/nodenum-call/488668          : ON0TLO-R
> /echolink/b/nodenum-call/522270          : ON0LIL-L
> /echolink/b/nodenum-call/81560            : ON0GB-R
> /echolink/b/nodenum-call/82010            : ON0OST-R
> /echolink/b/nodenum-call/93644            : ON0LIM-R
> 
> Whilst copying this lot, I saw the following on the Asterisk CLI:
> 
>    -- Received OK from Echolink server server1.echolink.org
>    -- Directory pgm done downloading(partial,compressed), 739 records
>    -- new CALL=ON0VOS-L,ip=81.165.69.72,name=        145.337,5 FM
> 
> Aha!, I thought - an update. So I re-ran the database show command and it
> came up empty again. No sign of ON0VOS in the database
> 
> So, the download is being received but it's not updating the database. Can
> the entry be added manually?
> 
> What am I missing here?
> 
> Thanks
> 
> David Osborn
> GD4HOZ
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at 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.