<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Yaesu APRS radios will not ack a
message if it comes from an -SSID that is not -0 (suppressed)
through -15 even though the APRS protocol for messages is always
in the payload portion for 3rd party packets gated from the
APRS-IS to RF with the ack coming back.<br>
<br>
APRSISCE/32 upcases APRS message targets. At least I think it
does but I didn't check the source code just now.<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and
Win32<br>
<br>
On 4/25/2016 5:07 PM, Robert Bruninga via aprssig wrote:<br>
</div>
<blockquote
cite="mid:67fd9eec9502dcc31c672c6d16508d64@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<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>
<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 moz-do-not-send="true"
href="http://aprs.org/aprs11.html">http://aprs.org/aprs11.html</a>
and specifically, see:</p>
<p class="MsoNormal">See <a moz-do-not-send="true"
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>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
aprssig mailing list
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>
<a class="moz-txt-link-freetext" href="http://www.tapr.org/mailman/listinfo/aprssig">http://www.tapr.org/mailman/listinfo/aprssig</a>
</pre>
</blockquote>
<br>
</body>
</html>