<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Arial">Glen</font></p>
<p><font face="Arial">I wasn't thinking of the digi only responding
to its real callsign, it will do that in any case AFAIK. I was
thinking of the case where (local) users specify the digis real
callsign in their path to keep their traffic "local". <br>
</font></p>
<p><font face="Arial">There's a lot of discussion about rgi and
possible effects of outbound traffic from it but we also need to
consider the benefits of having a well-sited W2-1 (say) Igate to
respond to inbound traffic that might have been stomped on at another
system(s).</font></p>
<p><font face="Arial">Ray vk2tv</font><br>
</p>
<br>
<br>
<div class="moz-cite-prefix">On 06/11/17 20:18, Glen English VK1XX
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:b65963f8-3ced-121f-67d5-8a842a934147@pacificmedia.com.au">
<pre wrap="">yeah, I would guess addr, WIDE1-1, VK1RGI-1 would do it
another thing to change on the client .
again, pity more cannot be gleaned by the digi beacon.
alternatively, the system could have a list of locals...
cheers
On 6/11/2017 6:36 PM, vk2tv wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
Doesn't the aprs specification provide for a station to direct traffic
via a specific digi callsign instead of the generic WIDEx-x to
minimise spread?
Ray vk2tv
On 06/11/17 18:03, Glen English VK1XX wrote:
</pre>
<blockquote type="cite">
<pre wrap="">All
thanks Josh,Ian, Dom, Ray for the inputs, and asking me good questions
for me to think about.
I'll read a bit more into USA centric & written articles.
I think I will filter 1RBM (local cbr) and 1RGI from duplicating
everything. Or at least have a think about it. There really needs to be
a setup for users if they really do want 1RGI is digipeat their 1RBM
UIs. I guess that's what WIDE2-2 is for.
Also got to think of the reverse case... RBM hearing things that I
expect Ginini to hear and not . That of course can happen any time for a
mobile station, long and short delay multipath abundant.
In about 90% of canberra cases, 1RGI will hear whatever 1RBM hears no
problem...
There there is the providing redundancy issue for other paths. Ether
way, IP link and full control will make things flexible.
There's a double edge sword with terminals being dumb /simple and say
unable to update their paths based on whatever they are hearing- there
would be usefulness I would have thought in having the digi beacon spit
out some useful information for UI stations.... or maybe there has been
thought and it didnt catch on.
I'll put UHF on the second sound card/dire wolf TNC channel, that will
be useful.
-glen
_______________________________________________
OZAPRS mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</a>
<a class="moz-txt-link-freetext" href="http://lists.aprs.net.au/mailman/listinfo/ozaprs">http://lists.aprs.net.au/mailman/listinfo/ozaprs</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
OZAPRS mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</a>
<a class="moz-txt-link-freetext" href="http://lists.aprs.net.au/mailman/listinfo/ozaprs">http://lists.aprs.net.au/mailman/listinfo/ozaprs</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
OZAPRS mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OZAPRS@aprs.net.au">OZAPRS@aprs.net.au</a>
<a class="moz-txt-link-freetext" href="http://lists.aprs.net.au/mailman/listinfo/ozaprs">http://lists.aprs.net.au/mailman/listinfo/ozaprs</a>
</pre>
</blockquote>
<br>
</body>
</html>