Order Tray | Contact Us | Home | SIG Lists

[aprsspec] Lower case characters in APRS-IS paths?

AE5PL Lists HamLists at ametx.com
Thu Oct 26 21:29:33 UTC 2006

The APRS-IS data stream is not AX.25 and therefore is not restricted to
AX.25 callsign limitations.  Upper and lower case callsigns have been
the norm on APRS-IS for years.  APRS clients, including the Kenwood
radios support mixed-case callsigns in third-party packets.  APRS-IS
does limit callsigns to 9 or less characters (including SSIDs) to make
uniform the handling of callsigns, object names, etc. within clients.

Xastir needs to allow mixed-case callsigns in all areas where callsigns
are used.  Also, some TNCs (and any TNC in KISS mode) allow mixed-case
callsigns on AX.25.


Pete Loveall AE5PL
mailto:pete at ae5pl.net 

> -----Original Message-----
> From: Tapio Sokura
> Posted At: Thursday, October 26, 2006 4:03 PM
> Subject: [aprsspec] Lower case characters in APRS-IS paths?
> So what does the APRS-IS specification (that doesn't exist in written
> form..?) say about this? Should "Core-2" instead be "CORE-2" 
> or should Xastir's checks be relaxed for APRS-IS packets? If 
> the checks should be relaxed, what exactly should be allowed 
> to be in APRS-IS packet paths?

More information about the aprsspec mailing list