<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body>I keep track of where my software is running by using a 'u' filter on my APRS-IS connection. That sends data from anybody in the world using the specified tocall (APJYC1 is the only tocall for YAAC, so my u-list is very short). This comes in useful when I'm pleading for help in doing translations of YAAC for non-English-language users (as in where are the most of those users? Currently a tossup between French, German, and Japanese, none of which I speak or write well enough to do the translations myself). So far, I only have a Russian translation that's a few years out of date (due to all the features added since the translation was done; I don't speak Russian either, so I can't update it).<div><br></div><div>To make looking for specific types of stations easier, YAAC has a filter capability that allows you to dice-and-slice your current "situational awareness" APRS dataset to look at selected subsets; one selection mechanism is by destination (tocall). Other APRS programs may or may not have equivalent features.<br><div dir="auto"><br></div><div dir="auto">Re: you querying my development server: that instance of YAAC (KA2DDO with no SSID) is stopped right now while I work on another fix for the next build, so it wasn't running to answer your query. When it's up, it usually has a build number higher than currently available, because I'm testing the next build before release. You can tell by using the non-standard directed query ?VER (currently only supported by YAAC and the original implementing software APRSIS32).</div><div dir="auto"><br></div><div dir="auto">Regarding SMSGTE and WHERE, those aren't generic common queries, but the network tactical callsigns of specific servers that handle specialized data queries. CQSRVR is another older network server "station" that depends on the APRS-IS and Tx I-gates to provide service.</div><div dir="auto"><br></div><div dir="auto">Hope this helps explain all of this.</div><div dir="auto"><br></div><div dir="auto">Andrew, KA2DDO</div><div dir="auto">author of YAAC</div></div><br><br>-------- Original message --------<br>From: Bill Vodall <wa7nwp@gmail.com> <br>Date: 3/23/17 12:23 PM (GMT-05:00) <br>To: <br>Cc: aprssig@tapr.org <br>Subject: Re: [aprssig] Auto-response position reports <br><br>> 3. The target station's APRS software or firmware actually implemented<br>> proper handling of the ?APRSP directed query.<br><br>> Andrew, KA2DDO<br>> author of YAAC (which does support ?APRSP)<br><br>This led to another interesting activity. How to find, on the<br>APRS-IS - or better, on the air - what is the callsigns of the<br>stations running YAAC (or any other APRS client)?<br><br>I tried a ?APRSP to ka2ddo but no response...<br><br>><br><br>Another interesting twist - how would a user query their local client?<br> Sending a message to self? Enter the query at the command line?<br>Probably varies on all the clients.<br><br>><br><br>I found a nice list of queries at:<br><br> http://sa7sky.net/documents/APRS-Queries.pdf<br><br>It's missing SMSGTE and WHERE but otherwise has enough to keep me busy<br>for a long time.<br><br>><br><br>73<br>Bill, WA7NWP<br>_______________________________________________<br>aprssig mailing list<br>aprssig@tapr.org<br>http://www.tapr.org/mailman/listinfo/aprssig<br></body></html>