Anonymous

Winlink Procedures for Subnet Controllers: Difference between revisions

From WikiNET
m
 
(10 intermediate revisions by the same user not shown)
Line 15: Line 15:


* You will notice that Winlink will automatically fill in the To field of the Winlink message (not the attached ICS 213) with the address in the From field of the original Winlink message, whether it was an FCC call sign or a Winlink tactical address.
* You will notice that Winlink will automatically fill in the To field of the Winlink message (not the attached ICS 213) with the address in the From field of the original Winlink message, whether it was an FCC call sign or a Winlink tactical address.
* Before you post the reply in your Outbox or your Draft Folder, change the From address from your FCC call sign to your regional Winlink tactical address by clicking on the down arrowhead next to your call sign.
* Depending on the precedence of the reply relative to other traffic, post the reply to your Outbox or save it in your Draft folder and move it to your Outbox later.  
* Depending on the precedence of the reply relative to other traffic, post the reply to your Outbox or save it in your Draft folder and move it to your Outbox later.  


When you are ready to transmit the replies in your Outbox to the ECC, see Transmitting and Receiving Traffic Using a Gateway.
When you are ready to transmit the replies in your Outbox to the ECC, see [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]].
 
=== Special Procedure for Handling Multiple Replies to a Winlink Message from the Emergency Coordination Center ===
If you have several teams checked into your subnet and you have read their AROs a Winlink message from the ECC, you should consider whether you will are likely to receive several replies in a row to this message.  If so, it may be more efficient to use one ICS 213 reply than to use several separate replies.  You will find a procedure of accomplishing this below. You should only use this procedure when the following three conditions are true:
 
# The message from ECC did not have a precedence of Emergency.
# It is reasonable to expect that more than one ARO will have a reply ready in a short amount time. (The most likely situation when this would be true is when the AROs are in a position of answering the message themselves rather than routing the message to their Incident Team Leader. For example, a simplex request asking for the weather conditions in the neighborhoods.)
# You are not handling replies to other messages at the same time.
 
If any of the the above conditions is not true, use separate ICS 213 replies for each reply as described in [[Winlink Procedures for Subnet Controllers#Handling Replies to Winlink Formal Traffic|Handling Replies to Winlink Formal Traffic]] above. 
 
If all three conditions above are true, you may want to use the following steps to combine multiple replies into one ICS 213 reply.
 
*Find the original message in your Winlink Inbox or your Read Items folder.
* Follow steps 2 through 5 of [[#Instructions for sending a REPLY to an ICS213|Instructions for Sending a Reply to an ICS213.]] As part of step 5, type the name of the team replying to message followed by a colon. Then type the reply directly into the Winlink template while you have the ARO read it to you. When the ARO reads field 10 (the name and position of the person replying), add that information after the reply rather than in field 10 of your reply template.
* Ask for any fills you need.
* Repeat step 5 for reach team's reply.
* Once you have all the replies or you expect some time will elapse before you get any more replies, fill in Field 10 with your name and position and click on Submit.
* Before you post the reply in your Outbox or your Draft Folder, change the From address from your FCC call sign to your regional Winlink tactical address by clicking on the down arrowhead next to your call sign
* Depending on the precedence of the reply relative to other traffic, post the reply to your Outbox or save it in your Draft folder and move it to your Outbox later.
When you are ready to transmit the replies in your Outbox to the ECC, see [[Winlink Procedures for Subnet Controllers#Transmitting and Receiving Traffic Using a Gateway|Transmitting and Receiving Traffic Using a Gateway]].


=== Handling Replies to ECC Traffic Originally Received by Voice ===
=== Handling Replies to ECC Traffic Originally Received by Voice ===
Line 70: Line 91:
After you have filled out the template, clicked on Submit and closed the browser window, you will see the content of the 213 in the body of a Winlink message.  Please
After you have filled out the template, clicked on Submit and closed the browser window, you will see the content of the 213 in the body of a Winlink message.  Please


* Update the To field of the Winlink with one of the ECC tactical addresses.  When in doubt use PDXECCMSGC-1.  
* Update the From field by clicking on the the "V" shape next to your FCC call sign and selecting your region's tactical address. If no tactical address is shown, see the section above regarding enabling a tactical address.
* Update the subject field of the Winlink message by inserting one of the following at the beginning of the subject line based on the precedence of the message.  
* Update the To field of the Winlink with one of the ECC tactical addresses.  When in doubt use PDXECCMSGC-1.
 
* For Emergency messages use //WL2K Z/
* For Priority messages use //WL2K P/
* For Health & Welfare or Routine use //WL2K R/


If you have Emergency messages you should post them to your Winlink Outbox and then contact Tactical Net on MC-8 informing it of these messages before taking Priority messages. Tactical Net may
If you have Emergency messages you should post them to your Winlink Outbox and then contact Tactical Net on MC-8 informing it of these messages before taking Priority messages. Tactical Net may
Line 92: Line 109:


=== Transmitting and Receiving Traffic Using a Gateway ===
=== Transmitting and Receiving Traffic Using a Gateway ===
 
After listening to the gateway frequency until it appears to no longer be busy, open and start a Packet Winlink or VARA FM Winlink session. If the exercise instructions indicate that a pair of experimental gateways have been set up at Portland Emergency Coordination Center, use one of the following gateways. Otherwise choose any gateway after asking Winlink Express to update its table of gateways.  See “Steps for Updating a Table of Available Gateways” in Checklists for Winlink Tasks.
==== Request Access to the Gateway ====
Before accessing one of the ECC gateways, you should contact Tactical Net on MC-8 informing it of these messages.  Report the messages you have ready to transmit by Winlink by precedence level. Tactical Net may
 
* give you immediate access to the Winlink gateway to transmit your Priority traffic; or
* tell you that Command Net will call you back on your frequency to give you time on the Winlink gateway to transmit them by Winlink.
 
Note: When you receive permission to use the gateway you may be told to transmit only your messages with the highest of precedence if you have messages of more than one precedence. If possible, place only the messages of that precedence in your Outbox before opening a Packet or VARA session.
 
==== Transmit Traffic to and Receive Traffic from a Gateway ====
Once you have received permission to use the gateway, open and start a Packet Winlink or VARA FM Winlink session. If the exercise instructions indicate that a pair of experimental gateways have been set up at Portland Emergency Coordination Center, use one of the following gateways. Otherwise choose any gateway after asking Winlink Express to update its table of gateways.  See “Steps for Updating a Table of Available Gateways” in Checklists for Winlink Tasks.
{| class="wikitable"
{| class="wikitable"
|Function
|Function
Line 110: Line 117:
|Experimental Packet Gateway
|Experimental Packet Gateway
|KI7QIB-12
|KI7QIB-12
|145.010 (use VFO mode)
|145.010 (use VFO mode or channel 488 in the MCARES 2023 Standard Template)
|-
|-
|Experimental VARA Gateway
|Experimental VARA Gateway
|KI7QIB-13
|KI7QIB-12
|145.010 (use VFO mode)
|145.010 (use VFO mode or channel 488 in the MCARES 2023 Standard Template)
|}
|}
When you access a gateway you may receive a warning message "The server you are connected to does not currently have an Internet connection.  Do you want to connect to this server?" This will occur if there is an Internet outage or we are simulating one.  Please confirm that you want to proceed.
When you access a gateway you may receive a warning message "The server you are connected to does not currently have an Internet connection.  Do you want to connect to this server?" This will occur if there is an Internet outage or we are simulating one.  Please confirm that you want to proceed.
Line 125: Line 132:
# Use another gateway if you are relatively certain that the gateways can access the Internet to exchange mail with the Common Message Servers.  
# Use another gateway if you are relatively certain that the gateways can access the Internet to exchange mail with the Common Message Servers.  
# If you have Internet access, use Telnet Winlink.
# If you have Internet access, use Telnet Winlink.
# Transmit by regular email.  For instance, PDXECCMSGC-1@winlink.org.  Put one of the following at the beginning of the subject line to indicate the precedence of the message and to facilitate obtaining “white list” status for your message:
# Transmit by regular email.  For instance, PDXECCMSGC-1@winlink.org.  Put the following at the begining of the subject to facilitate obtaining “white list” status for your message: //WL2K
## For Emergency messages use //WL2K Z/
## For Priority messages use //WL2K P/
## For Health & Welfare or Routine use //WL2K R/
# Hand deliver if that’s possible.
# Hand deliver if that’s possible.


Line 149: Line 153:


5. Now type in the response and when done click SUBMIT.
5. Now type in the response and when done click SUBMIT.
=== Instructions for Generating an ICS 309 ===
After an exercise or at the end of a deployment shift you should generate an ICS 309 using Winlink Express. This report will list all traffic you have sent and received using Winlink Express. See [[Checklists for_Winlink Tasks#Steps for Generating an ICS-309|Steps for Generating an ICS 309]]. Any Winlink traffic listed on the resulting ICS 309 does not need to be listed on a NET Form 8. You should still use NET Form 8 or a regular ICS 309 to list traffic you sent or received by voice, however.