Re: PI-DV3000 error message and ideas about its source
toggle quoted messageShow quoted text
Thank you John, that was helpful to know that it was probably my status within the larger network and not a software glitch in the gateway. The fact that it worked for you was important information.
I did establish the terminals and we will wait until they propagate thru the system. I suspect this was indeed the problem. I had registered at another gateway but that was deleted and I had not reregistered terminals in the new gateway where I registered.
I am waiting to hear how to revise my IrcDDB entry and will make the changes when I get the link.
From: John Hays <john@...>
Sent: Thursday, August 18, 2016 5:43 PM
Subject: Re: [ambe] PI-DV3000 error message and ideas about its source
I have just connected to W7VOI B with Buster and the connection seems to be working, though nobody is transmitting right now. (BTW, you can get a security certificate from AA4RC so you don't get the warning when connecting to your dashboard.)
It is unusual that this would happen with one system. W7VOI does not appear to be at a fixed address? It is currently at 126.96.36.199 -- You might want to check your /dstar/tmp/gateways.txt file and see if it has this address for W7VOI.
You also seem to be reporting into ircDDB with the add-on, but have incomplete data as it doesn't have lat/lon. http://status.ircddb.net/qam.php?call=W7VOI
The main issue may be that W7JZU does not have a registered terminal on the US Trust (also it would be the DPLUS login in DummyRepeater). http://query.ke5bms.com/index.php
On Thu, Aug 18, 2016 at 4:15 PM, Gary Payne via Groups.io <garyw7jzu@...> wrote: