John is right on the money here.
-
Tactical Call Sign SOP:
A tactical call sign is entered in the 4 digit comment field after a station's
legal call sign:
MY: NAØG /EOC
Such tactical calls can be readily pre-programmed in the MYCALL memory of most
radios.
With this procedure, your
At 04:31 AM 5/16/2009, you wrote:
Has anyone actually tried that? I could brush up on my Novell skills
from 1992.
Don't see why it wouldn't work. :)
Never saw a more stable fileserver in my entire IT/telco professional
career as a Novell 3.11 server. :-)
I certainly can't argue with that
At 01:50 PM 5/16/2009, you wrote:
They each have their purpose, we just need better gateway software.
Agreed. If implemented right, linking and callsign routing could
coexist, if the software was written to allow this mix. In addition,
controls to block either would be handy for certain uses.
At 01:16 AM 5/17/2009, you wrote:
John is right on the money here.
-
Tactical Call Sign SOP:
A tactical call sign is entered in the 4 digit comment field after a
station's legal call sign:
This would seem to be the most sensible way.
73 de VK3JED / VK3IRL
http://vkradio.com
I have worked many public service events disaster preparedness
exercises. One would have to be very creative to get meaningful
tactical calls with only 4 characters available. I'm often Lead, so
that's fine, but how about all the numbered Aid Station, Event,
Mobile, Safety, Bicycle,
The 20 character message works very well and would be a good place to do
Tactical if you need more than 4 chars. The issue for the callsign is
that in D-STAR the callsign field is more than identification, it is
part of the addressing scheme. Whereas in APRS you often are just
reporting
