[aprssig] How to Send to the APRS IS

[Andrew Rich]

Thanks Lynn 

Sent from my iPhone

> On 10 May 2017, at 7:07 pm, Lynn W. Deffenbaugh (Mr) <ldeffenb at homeside.to> wrote:
> 
> This is correct behavior.  From http://www.aprs-is.net/q.aspx
> 
>> qAS - Packet was received from another server or generated by this server. The latter case would be for a beacon generated by the server. Due to the virtual nature of APRS-IS, use of beacon packets by servers is strongly discouraged. The callSSID following the qAS is the login or IP address of the first identifiable server (see algorithm).
> 
> Because the packet didn't come from RF (the TCPIP* in the path), the APRS-IS server believes that VK4TEC (the authenticated callsign of the APRS-IS connection login) is a server servicing other stations.  Hence the qAS added to the packet.
> 
> At least, that's my non-authoritative analysis of this behavior.
> 
> Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and Win32
> 
> 
>> On 5/10/2017 4:11 AM, Andrew Rich wrote:
>> Here is what I send
>> 
>> VK4TEC-9>APZ001,TCPIP*:!2720.25S/15302.59E>
>> 
>> Here is what I see
>> 
>> VK4TEC-9>APZ001,TCPIP*,qAS,VK4TEC:!2720.26S/15302.57E>
>> 
>> I logged on as "user VK4TEC pass <passcode>"
>> 
>> Andrew
>> 
>> 
>> 
>> _______________________________________________
>> aprssig mailing list
>> aprssig at tapr.org
>> http://www.tapr.org/mailman/listinfo/aprssig
> 
> _______________________________________________
> aprssig mailing list
> aprssig at tapr.org
> http://www.tapr.org/mailman/listinfo/aprssig
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/aprssig_lists.tapr.org/attachments/20170510/0121274d/attachment.html>