[aprssig] 3rd Party ToCall
Pete Loveall AE5PL Lists
hamlists at ametx.com
Sat Apr 16 22:28:32 CDT 2016
The TOCALL you reference is the RF TOCALL which is unique to the IGate (should be same as the software uses for messages, for instance). Your subject refers to the 3rd Party ToCall which is what the originator of the original packet (FROMCALL in this example) originally transmitted (makes sense since the packet could be sending data in the TOCALL such as a Mic-E packet). What goes before the 3rd party portion of the packet is up to the IGate except that the IGATECALL must match in both the RF header as well as the 3rd party header.
Pete Loveall AE5PL
pete at ae5pl dot net
> -----Original Message-----
> From: Lynn W. Deffenbaugh (Mr) via aprssig
> Sent: Saturday, April 16, 2016 9:14 PM
> Subject: [aprssig] 3rd Party ToCall
> On http://www.aprs-is.net/IGateDetails.aspx it states:
> > IGates must use the 3rd-party format on RF of
> > IGATECALL>APRS,GATEPATH}FROMCALL>TOCALL,TCPIP,IGATECALL*:original
> > packet data
> > where GATEPATH is the path that the gated packet is to follow on RF.
> > This format will allow IGates to prevent gating the packet back to
> > APRS-IS.
> Does that literally mean >APRS as the ToCall on the RF-transmitted packet, or is
> it acceptable for the gating software to supply it's own application identifier
> ToCall since it is actually the transmitting station's software that created the
> 3rd party wrapper?
> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
More information about the aprssig