[aprssig] Automatic Voice RFelay System (AVRS) and ALLSTAR
John Gorkos jgorkos at gmail.comMon Sep 17 21:03:18 UTC 2012
- Previous message: [aprssig] Automatic Voice RFelay System (AVRS) and ALLSTAR
- Next message: [aprssig] Automatic Voice RFelay System (AVRS) and ALLSTAR STANDARD
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I think that would assume a higher degree of integration than currently exists. Since, by their nature, IRLP, EchoLink, and Allstar nodes have internet connections, it should follow that they should be able to inject their location/status into APRS-IS. The more I think about it, the more do-able that sounds. Unfortunately, I don't know the source-code status of IRLP, and EchoLink is a dog's breakfast unless you're running the Windows version, which I don't think is open-sourced at all. All-star is based on asterisk, so THAT'S doable. I really, REALLY wish people could see a slightly bigger picture than "I don't want people making any money off MY idea" when it comes to releasing source code. APRS would be 10 years farther along if we had the source to WinAPRS, or UIView, enough people with coding experience drift in and out that someone would have picked it up and run with it. I think you're right in the sense that a proper message format should be designed that allows for self-reporting of internet gateways. Once the message format is in place, it's just a matter of getting software developers onboard with the reporting. Having a central repository with all of that info is still important, but the way it GETS that info would be more integrated. John Gorkos On 9/17/12 4:37 PM, "Andrew P." <andrewemt at hotmail.com> 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
- Previous message: [aprssig] Automatic Voice RFelay System (AVRS) and ALLSTAR
- Next message: [aprssig] Automatic Voice RFelay System (AVRS) and ALLSTAR STANDARD
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the aprssig mailing list
