<HTML><HEAD>
<META content="text/html; charset=UTF-8" http-equiv=content-type></HEAD>
<BODY dir=ltr>
<DIV dir=ltr>
<DIV style="FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>Any formal solution needs to cater for VK0F.. through VK9F, not just
dropping the 3 in VK3F. Abbreviating by omitting the digit risks producing
clashes locally.</DIV>
<DIV> </DIV>
<DIV>Graeme VK2HFG</DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'>
<DIV style="FONT: 10pt tahoma">
<DIV><FONT size=3 face=Calibri></FONT> </DIV>
<DIV style="BACKGROUND: #f5f5f5">
<DIV style="font-color: black"><B>From:</B> <A
title=vk2tv@exemail.com.au>vk2tv</A> </DIV>
<DIV><B>Sent:</B> Saturday, December 21, 2019 4:25 PM</DIV>
<DIV><B>To:</B> <A title=ozaprs@aprs.net.au>oz >> Australian APRS
Users</A> </DIV>
<DIV><B>Subject:</B> [OZAPRS] Fwd: Re: Fwd: Re: Foundation and RF APRS new
thread</DIV></DIV></DIV>
<DIV> </DIV></DIV>
<DIV
style='FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: "Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; DISPLAY: inline'><FONT
face=Arial>I'm a slow learner, ticked the wrong box again. Ho hum!</FONT><BR>
<DIV class=moz-forward-container><BR><BR>-------- Forwarded Message --------
<TABLE class=moz-email-headers-table style="COLOR: #000000" cellSpacing=0
cellPadding=0 border=0>
<TBODY>
<TR>
<TH vAlign=baseline noWrap align=right>Subject: </TH>
<TD>Re: [OZAPRS] Fwd: Re: Foundation and RF APRS new thread</TD></TR>
<TR>
<TH vAlign=baseline noWrap align=right>Date: </TH>
<TD>Sat, 21 Dec 2019 16:24:49 +1100</TD></TR>
<TR>
<TH vAlign=baseline noWrap align=right>From: </TH>
<TD>vk2tv <A
class=moz-txt-link-rfc2396E>mailto:vk2tv@exemail.com.au</A></TD></TR>
<TR>
<TH vAlign=baseline noWrap align=right>To: </TH>
<TD>Carlos PECO BERROCAL <A
class=moz-txt-link-rfc2396E>mailto:carlos.peco@gmail.com</A></TD></TR></TBODY></TABLE><BR><BR><FONT
face=Arial>Hi Carlos,<BR><BR>I got my information from here </FONT><BR><FONT
face=Arial><A
href="https://rsgb.org/main/operating/licensing-novs-visitors/international-prefixes/"
moz-do-not-send="true">https://rsgb.org/main/operating/licensing-novs-visitors/international-prefixes/</A><BR><BR>and
here <BR></FONT><FONT face=Arial><A href="https://www.qrz.com/atlas"
moz-do-not-send="true">https://www.qrz.com/atlas </A>(enter Panama in the
search box)<BR><BR>I did search for a full example of a 3F callsign but didn't
find one.<BR><BR>You could be right but I think that a permanent and sensible
solution to the Foundation callsign debacle is the preferred route to
take. <BR><BR>I suggested VI and you suggest AX but in retrospect I see a
problem with both of them in that if any amateur can use VI or AX for special
occasions, logically the entire VI or AX blocks are already be "allocated".
<BR><BR>I've been messing about looking for a temporary solution for Jack and
using an ALIAS instead of a callsign seems to tick all the boxes.<BR><BR>1. In
an instance of xastir I used the ALIAS VKFTVZ as the station "callsign" . In the
"Comment" box I put "vk2tv APRS test" (beacon text in other systems)<BR>2. I
created a passcode for the ALIAS, VKFTVZ and entered that in the interface
control box of xastir<BR>3. I was able to send my normal xastir instance on
another machine a message and from that machine I sent a reply. All good.<BR>4.
aprs.fi shows the ALIAS and the beacon that was sent ... </FONT><FONT
face=Arial><FONT size=+3><SPAN
style="FONT-SIZE: 12px; FONT-FAMILY: verdana, arial, helvetica, sans-serif; WHITE-SPACE: nowrap; WORD-SPACING: 0px; TEXT-TRANSFORM: none; FLOAT: none; FONT-WEIGHT: 400; COLOR: rgb(0,0,0); FONT-STYLE: normal; ORPHANS: 2; WIDOWS: 2; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(255,255,255); TEXT-INDENT: 0px; font-variant-ligatures: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial">2019-12-21
16:03:42 AEDT:<SPAN> </SPAN></SPAN><B
style="BOX-SIZING: border-box; FONT-SIZE: 12px; FONT-FAMILY: verdana, arial, helvetica, sans-serif; WHITE-SPACE: nowrap; WORD-SPACING: 0px; TEXT-TRANSFORM: none; FONT-WEIGHT: 700; COLOR: rgb(0,0,0); FONT-STYLE: normal; ORPHANS: 2; WIDOWS: 2; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(255,255,255); TEXT-INDENT: 0px; font-variant-ligatures: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial"><A
style="BOX-SIZING: border-box; CURSOR: pointer; TEXT-DECORATION: none; COLOR: rgb(0,0,255); OUTLINE-STYLE: none; BACKGROUND-COLOR: transparent"
href="https://aprs.fi/?c=raw&limit=&call=VKFTVZ"
moz-do-not-send="true">VKFTVZ</A></B></FONT><SPAN
style="FONT-SIZE: 12px; FONT-FAMILY: verdana, arial,
helvetica, sans-serif; WHITE-SPACE: nowrap; WORD-SPACING: 0px; TEXT-TRANSFORM: none; FLOAT: none; FONT-WEIGHT: 400; COLOR: rgb(0,0,0); FONT-STYLE: normal; ORPHANS: 2; WIDOWS: 2; DISPLAY: inline !important; LETTER-SPACING: normal; BACKGROUND-COLOR: rgb(255,255,255); TEXT-INDENT: 0px; font-variant-ligatures: normal; font-variant-caps: normal; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial"><FONT
size=+1>>APX215,TCPIP*,qAC,T2TAS:=3102.12S/15252.72E`vk2tv APRS test<BR>5.
The use of an ALIAS (maximum of 6 characters to met the AZ25 spec) should pass
unimpeded through Igates. And FWIW, an ALIAS can have an SSID, just like a
callsign can.<BR></FONT><BR><FONT size=+1>On the surface this method seems to
solve Jack's problem of using a callsign (ALIAS, actually) that resembles his
real callsign</FONT>, <FONT size=+1>sends his real callsign in the beacon,
satisfies aprs.fi,<BR>lets him appear on aprs.fi, and meet his licencing
obligations. <BR><BR>What more could he want except for the ACMA to sort of the
callsign debacle they created?<BR><BR>HTH<BR>Ray
vk2tv<BR><BR><BR></FONT></SPAN></FONT>
<DIV class=moz-cite-prefix>On 21/12/19 2:56 pm, Carlos PECO BERROCAL
wrote:<BR></DIV>
<BLOCKQUOTE
cite=mid:CAJqR=erSATvm3UFdhihg77mDVBW1X=jy+2so5g21-pZP+vPKTA@mail.gmail.com
type="cite">hi Ray,
<DIV> </DIV>
<DIV>So I looked into the Panama callsigns... they all have a number after the
prefix.</DIV>
<DIV> </DIV>
<DIV>So an alphanumeric combination like 3FABC does not match any amateur
callsign anywhere in the world. Happy to be proven wrong.</DIV>
<DIV> </DIV>
<DIV>Foundation calls would be better using a different prefix, like AX. They
would attract more attention from hams overseas.</DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>cheers</DIV>
<DIV>Carlos VK1EA</DIV>
<DIV><BR><BR>On Saturday, December 21, 2019, vk2tv <<A
moz-do-not-send="true">vk2tv@exemail.com.au</A>> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex">
<DIV><FONT face=Arial>Ticked the wrong box and sent this only to
Norm.</FONT><BR>
<DIV><BR><BR>-------- Forwarded Message --------
<TABLE style="COLOR: #000000" cellSpacing=0 cellPadding=0 border=0>
<TBODY>
<TR>
<TH vAlign=baseline noWrap align=right>Subject: </TH>
<TD>Re: [OZAPRS] Foundation and RF APRS new thread</TD></TR>
<TR>
<TH vAlign=baseline noWrap align=right>Date: </TH>
<TD>Sat, 21 Dec 2019 13:49:08 +1100</TD></TR>
<TR>
<TH vAlign=baseline noWrap align=right>From: </TH>
<TD>vk2tv <A target=_blank
moz-do-not-send="true">mailto:vk2tv@exemail.com.au</A></TD></TR>
<TR>
<TH vAlign=baseline noWrap align=right>To: </TH>
<TD>Norm McMillan <A target=_blank
moz-do-not-send="true">mailto:vk3xci@gmail.com</A></TD></TR></TBODY></TABLE><BR><BR><FONT
face=Arial>Given the international use of APRS, aprs-is and sites like <A
href="http://aprs.fi" target=_blank moz-do-not-send="true">aprs.fi</A>, a 3F
callsign has the potential to cause a problem. Would you like YOUR callsign
appearing on <A href="http://aprs.fi" target=_blank
moz-do-not-send="true">aprs.fi</A> if you didn't initiate it? We shouldn't
be trying to fix one problem by creating other problems.<BR><BR>I don't see
having the callsign as an object as problematic, per se, but the aprs-is
authorisation to allow a station to send an object is based on the callsign
(without SSID) that's set in the config file (certainly for xastir and
Direwolf). Whilst that config file "might" accept a callsign longer than 6
characters, and so might <A href="http://aprs.is" target=_blank
moz-do-not-send="true">aprs.is</A> we eventually hit the AX25 specification
conflict that will probably drop an improperly formatted source station
address - a letter appearing in the numerical -only SSID field -, or maybe
corrupt the callsign therein. <BR><BR></FONT>Australian amateurs can use vk,
vi or ax, under prescribed circumstances so maybe something along the lines
of an extension of the (say) VI prefix to allow Foundation licencees to use
it would be a simple solution - Jack could become VI3JTS, as an example.
Perhaps the use of a data friendly callsign could be optional for stations
who need it. I'm just tossing ideas into the air, we need to start somewhere
to resolve the mess.<BR><BR>Can anyone confirm/deny that the WIA is actually
working with the ACMA on a solution, or is everyone waiting for somebody
else to start the ball rolling? Just curious. If the ball isn't already
rolling, maybe we from this group should start its journey. Maybe Jack
should contact his local federal member of parliament, asking him to find
out why the ACMA permitted the use of data by Foundation licencees but kept
a callsign structure that prevents that happening in practice. Take it up
with the Anti-Discrimination Commissioner, there must be a disabled
Foundation licencee who wants to use Packet/APRS but can't because the
callsign structure discriminates against him/her. Play it for all it's
worth. We have both the power and the right to make a noise about this and
we shouldn't have to wait years for a result. <BR><BR>Soapbox safely stowed
away ... for now<SPAN><SPAN>:-)</SPAN></SPAN><BR><BR>Ray vk2tv<BR><BR>
<DIV>On 21/12/19 12:59 pm, Norm McMillan wrote:<BR></DIV>
<BLOCKQUOTE type="cite">
<DIV dir=ltr>
<DIV>Hmmmm,</DIV>
<DIV>looks like all the nF... prefixes are internationally allocated, is
that going to cause a problem?</DIV>
<DIV>The proper answer of course, is to get rid of the 4 letter suffix,
the numerical area id suffix, and have a "callsign for life"</DIV>
<DIV>Like that's going to happen!</DIV>
<DIV> </DIV>
<DIV>For now, I'll tell users to use nFxxx and put a callsign in the
comment line. It's all we've got 'till someone tell me different.</DIV>
<DIV> </DIV>
<DIV>norm vk3xci<BR></DIV>
<DIV> </DIV>
<DIV>norm vk3xci!<BR></DIV></DIV>
<DIV> </DIV>
<DIV class=gmail_quote>
<DIV class=gmail_attr dir=ltr>On Sat, Dec 21, 2019 at 11:34 AM Josh <<A
target=_blank moz-do-not-send="true">vk2hff@vk2hff.ampr.org</A>>
wrote:<BR></DIV>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0px 0px 0px 0.8ex">Hi
Norm,<BR><BR>On 21/12/2019 10:30 am, Norm McMillan wrote:<BR>>
Someone with more knowledge than I might like to comment on the<BR>>
legality of both cases? I'm not an APRSdroid user so I don't know
if<BR>> it's possible to put a comment with a callsign in
APRSdroid.<BR>Yes, APRSdroid allows a custom comment but defaults to the
aprsdroid URL<BR>if no comment is provided.<BR>Regarding legality, there
is no requirement to identify yourself on<BR>every transmission.<BR>And
your ID doesn't have to be sent via AX.25 - sending your
full<BR>callsign via CW (or voice etc) once every 10 minutes would
fulfill the<BR>requirement, providing it was sent on the same frequency
as your APRS<BR>transmissions - not that I'd recommend this
option.<BR><BR>Including your callsign in your APRS beacon comment field
would<BR>obviously also meet the requirement. From ACMA's
perspective your APRS<BR>object name does not have to match your
callsign - that's just our<BR>convention for position
beacons.<BR>><BR>> Another question... would a 3F*** call be gated
IS to RF? Guess it<BR>> depends on the software etc.<BR>><BR>That
comes down to each individual igate's configuration.<BR>As an example,
mine won't gate any objects from IS to RF except for<BR>messages for
nearby stations recently heard directly via RF, or WXSVR-AU<BR>alerts
within my igate's area. The callsign makes no difference.<BR><BR>IMO the
best approach for F calls is to set their callsign field to<BR>nFxxx,
and include their full callsign in the comment field.<BR><BR>- Josh
VK2HFF<BR><BR>______________________________<WBR>_________________<BR>OZAPRS
mailing list<BR><A target=_blank
moz-do-not-send="true">OZAPRS@aprs.net.au</A><BR><A
href="http://lists.aprs.net.au/mailman/listinfo/ozaprs" rel=noreferrer
target=_blank
moz-do-not-send="true">http://lists.aprs.net.au/<WBR>mailman/listinfo/ozaprs</A><BR></BLOCKQUOTE></DIV><BR>
<FIELDSET></FIELDSET> <PRE>______________________________<WBR>_________________
OZAPRS mailing list
<A target=_blank moz-do-not-send="true">OZAPRS@aprs.net.au</A>
<A href="http://lists.aprs.net.au/mailman/listinfo/ozaprs" target=_blank moz-do-not-send="true">http://lists.aprs.net.au/<WBR>mailman/listinfo/ozaprs</A>
</PRE></BLOCKQUOTE><BR></DIV></DIV></BLOCKQUOTE></DIV><BR>
<FIELDSET class=mimeAttachmentHeader></FIELDSET> <PRE class=moz-quote-pre wrap="">_______________________________________________
OZAPRS mailing list
<A class=moz-txt-link-abbreviated moz-do-not-send="true">OZAPRS@aprs.net.au</A>
<A class=moz-txt-link-freetext href="http://lists.aprs.net.au/mailman/listinfo/ozaprs" moz-do-not-send="true">http://lists.aprs.net.au/mailman/listinfo/ozaprs</A>
</PRE></BLOCKQUOTE><BR></DIV>
<P>
<HR>
_______________________________________________<BR>OZAPRS mailing
list<BR>OZAPRS@aprs.net.au<BR>http://lists.aprs.net.au/mailman/listinfo/ozaprs<BR></DIV></DIV></DIV></BODY></HTML>