The issue I have with this is duplicate tactical calls in different RF areas.<br><br>On more than one occasion, I have run into events outside my RF area using the same tactical calls on ARPS as my event, typically along the lines of SAG-3 and MED-2, for example. As it is now, there is some advantage to all MED-* units receiving the same message, however, when the med units outside your event also receive it, it can cause issues. Ideally, you would run your local event on a dedicated channel and/or use NOGATE in your paths, but sometimes due to geographic needs, you use the existing APRS infrastructure, including APRS-IS and two-way Igates. <br>
<br>I understand the idea that any station for CALL should receive all messages send to it, and that only the specific CALL-SSID should ack, but what do you do in the case of a club call that is used at 7 different hospitals? <br>
<br>If one call would always equal one ham, this scheme makes since, but in the cases of tactical events, where several base calls are using different SSID's for actually different stations, then this method tends to add confusion instead of adding functionality.<br>
<br>Yes, training of operators would go a long way in elevating this concern, but in the heat of battle, little nuances like this get overlooked and confusion/misinformation can set in.<br><br>Just an observation.<br><br>
73,<br>Randy<br>WF5X<br><br><br><div class="gmail_quote">On Sat, Aug 7, 2010 at 10:36 PM, Stephen H. Smith <span dir="ltr"><<a href="mailto:wa8lmf2@aol.com">wa8lmf2@aol.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im"> On 8/7/2010 5:54 PM, Bob Bruninga wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Yes, "recently-heard" still applies... Today, for example, I am in Utah at a conference with my WB4APR-7 HT. I drove to the airport in my WB4APR-9 and my home station or work station are also on the air. I expect a message sent to ANY of my WB4APR stations (if seen by an Igate near me) to send it out to RF including my HT in UTAH. I use "expect" in the future sense, because as we are learning, this is not presently the case).<br>
<br>
I DO agree with the need for an option (defaults to ON) so that someone can turn off the delivery of messages to some SSID's.. though that adds even more complexity..<br>
</blockquote>
<br>
<br></div>
I would propose that this be implemented in a manner similar to call forwarding on phone numbers, or auto-forwarding between email accounts. "OFF" unless explicitly set, perhaps by a message to the APRS server, similar to what is sent to select port 14580 filters or the CQSVR. Perhaps an auto-expire of 24 or 48 hours or so, so that forwarding set for a short out-of-area trip will cancel itself if forgotten.<br>
<br>
On the other hand, is all this complexity worth it??? How often have you had an urgent message sent to an APRS address that would actually matter, if you missed it due to being away from a particular SSID?<br>
<br>
<br>
<br>
-------------------------------------------------------------------------------<br>
<br>
--<br>
<br>
Stephen H. Smith wa8lmf (at) <a href="http://aol.com" target="_blank">aol.com</a><br>
EchoLink Node: WA8LMF or 14400 [Think bottom of the 2M band]<br>
Skype: WA8LMF<br>
Home Page: <a href="http://wa8lmf.net" target="_blank">http://wa8lmf.net</a><br>
<br>
NEW! *** HF APRS over PSK63 ***<br>
<a href="http://wa8lmf.net/APRS_PSK63/index.htm" target="_blank">http://wa8lmf.net/APRS_PSK63/index.htm</a><br>
<br>
Universal HF/VHF/UHF Antenna Mounting System<br>
<a href="http://wa8lmf.net/mobile/UniversalAntMountSystem.htm" target="_blank">http://wa8lmf.net/mobile/UniversalAntMountSystem.htm</a><br>
<br>
"APRS 101" Explanation of APRS Path Selection & Digipeating<br>
<a href="http://wa8lmf.net/DigiPaths" target="_blank">http://wa8lmf.net/DigiPaths</a><div><div></div><div class="h5"><br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@tapr.org" target="_blank">aprssig@tapr.org</a><br>
<a href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig" target="_blank">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br>
</div></div></blockquote></div><br><div style="visibility: hidden; display: inline;" id="avg_ls_inline_popup"></div><style type="text/css">#avg_ls_inline_popup { position:absolute; z-index:9999; padding: 0px 0px; margin-left: 0px; margin-top: 0px; width: 240px; overflow: hidden; word-wrap: break-word; color: black; font-size: 10px; text-align: left; line-height: 13px;}</style>