[aprssig] 3rd Party ToCall
Lynn W. Deffenbaugh (Mr)
ldeffenb at homeside.to
Sun Apr 17 06:35:15 EDT 2016
I wasn't as clear as I should have been, but I was asking about the RF
transmitting station's (IGate's) ToCall, not the original ToCall of the
embedded packet. Thanks for the decisive and descriptive answer.
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
On 4/16/2016 11:28 PM, Pete Loveall AE5PL Lists via aprssig wrote:
> 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
>>> 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
>> 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
> aprssig mailing list
> aprssig at tapr.org
More information about the aprssig