<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">ID requirements in the US provide for a
CW ID. There is no actual requirement to put the transmitters
callsign inside the AX.25 packets.<br>
<br>
And the only way you can determine if a digipeater or IGate is
properly IDing is to go there and monitor the RF to see which ID
they may be providing.<br>
<br>
Of course, that said, it's far easier to just put out a periodic
beacon AND insert your call in the path of every transmitted
packet to be 100% sure that the 10 minute ID requirement is being
fully met.<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile and
Win32<br>
<br>
On 11/5/2014 11:59 AM, David Andrzejewski wrote:<br>
</div>
<blockquote
cite="mid:86C518BC-FDE1-4D24-B347-609338B080C3@davidandrzejewski.com"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<div>I would wonder if it's legal for digis to do neither?
Wouldn't they have to do one or the other to satisfy ID
requirements? (In the US at least)<br>
<br>
<div>
<div>- Dave/KD8TWG</div>
</div>
</div>
<div><br>
On Nov 5, 2014, at 11:24, Lynn W. Deffenbaugh (Mr) <<a
moz-do-not-send="true" href="mailto:ldeffenb@homeside.to">ldeffenb@homeside.to</a>>
wrote:<br>
<br>
</div>
<blockquote type="cite">
<div>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">They definitely should (IMHO)
insert their call if they digipeat something. And without a
posit beacon (even if they choose to do ambiguity), there's
no way to do any path analysis of their participation in the
network.<br>
<br>
But then, I guess it falls under the "to each his own"
category.<br>
<br>
Lynn (D) - KJ4ERJ - Author of APRSISCE for Windows Mobile
and Win32<br>
<br>
On 11/5/2014 11:12 AM, Andrew P. wrote:<br>
</div>
<blockquote
cite="mid:SNT404-EAS290392FAF52BDA80E885846B8870@phx.gbl"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
Is there a reason to have stealth (non-beaconing)
digipeaters? There are some folks in my area who want to
hide their digis from the general public (supposedly to keep
excess traffic off those digis). But, if those digis support
WIDEn-N aliases, they should still digipeat general traffic
in their range, and no one will know who is doing it (unless
those digis add a trace entry of themselves to the path).
<div><br>
</div>
<div>So what would be the point? One digi beacon every 30
minutes wouldn't clog the channel. And, unless those digis
explicitly didn't support standard aliases (WIDEn-N or the
obsolete RELAY and WIDE), they would still digi general
traffic (not just the owner's traffic).</div>
<div><br>
</div>
<div>Just can't figure out why someone would want a stealth
digi.</div>
<div><br>
</div>
<div>Andrew, KA2DDO </div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
aprssig mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.tapr.org/mailman/listinfo/aprssig">http://www.tapr.org/mailman/listinfo/aprssig</a>
</pre>
</blockquote>
<br>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>aprssig mailing list</span><br>
<span><a moz-do-not-send="true" href="mailto:aprssig@tapr.org">aprssig@tapr.org</a></span><br>
<span><a moz-do-not-send="true"
href="http://www.tapr.org/mailman/listinfo/aprssig">http://www.tapr.org/mailman/listinfo/aprssig</a></span><br>
</div>
</blockquote>
<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>