<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><meta name="Generator" content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang="EN-US" link="blue" vlink="purple"><div class="WordSection1"><p class="MsoNormal">There is an unintended ambiguity in the APRS SPEC regarding the addressee in the APRS MESSAGE format.</p><p class="MsoNormal"> </p><p class="MsoNormal">It was intended that the TOCALL of any transmitted message could be sent to ANY 9 character callsign field and this included mixed-case. Although TNC’s have historically forced callsigns to UPEPRCASE only, this is only a limitation of TNC’s and was not intended to be a limitation of APRS.</p><p class="MsoNormal"> </p><p class="MsoNormal">STATION names, OBJECT names, ITEM names were intended to be a general 9 character mixed case field in APRS padded to 9 with spaces.</p><p class="MsoNormal"> </p><p class="MsoNormal">We just noticed that some radios do not allow sending an APRS message to a mixed case address.</p><p class="MsoNormal"> </p><p class="MsoNormal">Unfortunately, the QIKCOM-2 satellite which does DTMF-to-Voice and APRS-to-voice has a special message address of “QIKCOMsay” for all messages it is expected to speak. So some people will not be able to exercise this text-to-voice messaging capability.</p><p class="MsoNormal"> </p><p class="MsoNormal">I wont make this mistake in any future satellite, but we are stuck with it. </p><p class="MsoNormal"> </p><p class="MsoNormal">SO, we might ought-to-identify all APRS radios and APRS clients that have this uppercase-only restriction on MESSAGE Callsigns.</p><p class="MsoNormal"> </p><p class="MsoNormal">I can say the Kenwoods have it. Others?</p><p class="MsoNormal"> </p><p class="MsoNormal">See <a href="http://aprs.org/aprs11.html">http://aprs.org/aprs11.html</a> and specifically, see:</p><p class="MsoNormal">See <a href="http://aprs.org/aprs11/aprs-names-and-spaces.txt">http://aprs.org/aprs11/aprs-names-and-spaces.txt</a></p><p class="MsoNormal"> </p><p class="MsoNormal">Bob, WB4APR</p></div></body></html>