[aprssig] Automatic Voice RFelay System (AVRS) and ALLSTAR
Andrew P. andrewemt at hotmail.comMon Sep 17 21:07:54 UTC 2012
- Previous message: [aprssig] Automatic Voice RFelay System (AVRS) and ALLSTAR STANDARD
- Next message: [aprssig] Automatic Voice RFelay System (AVRS) and ALLSTAR
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Whoops! Do you have me mixed up with someone else? ;-) What about non-periodic messages at state-change times only? Since both the Echolink/Allstar/IRLP/??? gateways and the AVRS are up 24x7 and connected via reliable wired Internet links, they don't need constant beaconing. Also, I note that there are several IRLP and Echolink gateways in my area that are beaconing anyway (not my doing) and being gated to the APRS-IS. If they put the additional state that AVRS needs in their beacons, it would be done (just more difficult for the AVRS server to filter out of the APRS-IS flood). Up to $.03. ;-) Andrew Pavlin, KA2DDO author of YAAC, not of AVRS ;-) ------Original Message------ From: Lynn W. Deffenbaugh (Mr) To: aprssig at tapr.org Sent: Sep 17, 2012 4:45 PM Subject: Re: [aprssig] Automatic Voice RFelay System (AVRS) and ALLSTAR That would be wonderful, but when I offered to periodically update APRS objects for EchoLink nodes, I was resoundingly shot down because of the increased load on the APRS-IS. I am considering a QRU-like server for these objects that would probably be the best hope. (http://aprsisce.wikidot.com/doc:qru) As a matter of fact, since you've already got all the data in your server, and are already fielding APRS messages, you'd be a shoe-in for implementing such a thing. Drop me a line for details if you're interested. It's really straight-forward. Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32 On 9/17/2012 4:37 PM, Andrew P. wrote: > Perhaps a new APRS message could be defined specifically to beacon such gateways with the relevant parameters (most of which are in the standard position message anyway). Then we wouldn't need a back-door URL to get the data; AVRS could just use a type-filtered feed to get all the gateway beacons (regardless of which net they are on). > > Just my $.02. > > Andrew Pavlin, KA2DDO > ------Original Message------ > From: Bill Vodall > To: aprssig at tapr.org > Sent: Sep 17, 2012 1:49 PM > Subject: Re: [aprssig] Automatic Voice RFelay System (AVRS) and ALLSTAR > > >> I.e. I need callsign, node number, lat/lon of node, RF characteristics >> (freq/offset/tone), and status (connected, listening, down, etc) >> Given that data I can poll it, update a local DB, map the nodes, and make >> AllStar part of the AVRS protocol. > Will this info be generally available on the APRS-IS so we can easily > bring it to the RF domain without doing Internet magic... (Yes - I > know APRS-IS == Internet but there is a subtle difference...) > > 73 > Bill - WA7NWP > > _______________________________________________ > aprssig mailing list > aprssig at tapr.org > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig > > > Sent from my Verizon Wireless BlackBerry > > _______________________________________________ > aprssig mailing list > aprssig at tapr.org > https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig > _______________________________________________ aprssig mailing list aprssig at tapr.org https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig Sent from my Verizon Wireless BlackBerry
- Previous message: [aprssig] Automatic Voice RFelay System (AVRS) and ALLSTAR STANDARD
- Next message: [aprssig] Automatic Voice RFelay System (AVRS) and ALLSTAR
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
