Winlink Procedures for Subnet Controllers: Difference between revisions
From Portland NET Wiki
BruceSchafer (talk | contribs) Moved subsection on reporting roster by Winlink here |
BruceSchafer (talk | contribs) →From Field: Corrected typos in form numbers |
||
| Line 79: | Line 79: | ||
==== From Field ==== | ==== From Field ==== | ||
In this case, we're talking about the From field of the Winlink message, which will typically be different than the From field of of an ICS Form 213 being sent by Winlink. The From field of the Winlink message should indicate which station is sending the message by Winlink while the From field in an ICS Form | In this case, we're talking about the From field of the Winlink message, which will typically be different than the From field of of an ICS Form 213 being sent by Winlink. The From field of the Winlink message should indicate which station is sending the message by Winlink while the From field in an ICS Form 213 indicates the person who originated the Form 213 (or equivalent NET Form 8). | ||
For NET exercises we recommend that you use tactical addresses for the From field instead instead of your FCC call sign Using a tactical addresses instead of your FCC has several advantages. In particular, they can be associated with the name of regional subnets. Using a regional tactical address as your From address will help assure that replies are directed to the subnet controller for the region on duty when replies to that message after a shift change. | For NET exercises we recommend that you use tactical addresses for the From field instead instead of your FCC call sign Using a tactical addresses instead of your FCC has several advantages. In particular, they can be associated with the name of regional subnets. Using a regional tactical address as your From address will help assure that replies are directed to the subnet controller for the region on duty when replies to that message after a shift change. | ||
