April 30, 2008

Chester County Winlink Network Gateways and Frequencies
The network's present status, including all local stations call signs, operating frequencies, and locations are frequently updated and issued as a Winlink bulletin. The most current version will be posted on the W3EOC PMBO as a bulletin (see instructions in this SOP for downloading bulletins). The bulletin is also posted on the W3EOC.ORG web page.
In addition, an ARES PMBO bulletin is available that lists all ARES non-public PMBOs dedicated to emergency service and their operating frequencies. This bulletin is produced in Airmail's station bulletin format and may be imported directly into Airmail's station list.
Any VHF or UHF packet gateway may be used to pass traffic into the system. Use the least active channel in your radio horizon to avoid slowing traffic flow. Avoid the use of intermediate packet nodes and digipeaters if you can connect to a gateway station directly. Use moderately aggressive packet parameters to quickly connect and pass your traffic. Relax parameters if the channel is busy and you have no other less-busy alternatives. Always listen before transmitting. Do not start a connection if you hear another station rapidly exchanging packets with a gateway.
The same operating practices apply to Pactor HF PMBO connections, but are more important because simultaneous connections on a single frequency are not possible on HF.
ALWAYS Monitor Administrative Channels (Voice)
During drills and emergency activations all radio email stations must monitor the Chester County ARES-RACES tactical frequencies for status bulletins, specific instructions, logistical information, and message receipt confirmations. MONITOR TACNET AT ALL TIMES.
Tactical frequencies are given in the latest Emergency Operations Guide and Operator Guide.
Recommended AX.25 Packet Parameters
Unlike a traditional packet network, where multiple stations share a common frequency in keyboard-to-keyboard QSOs, the CCAR digital network is optimized for radio email and automatic message forwarding using the B2F protocol. It is more efficient for user stations to use moderately aggressive AX.25 packet parameters in order to connect quickly, transfer traffic, and then disconnect immediately so other stations can use the gateway. Using 'relaxed' parameters will allow more stations to use a frequency, but the overall effect is that all traffic flow is much slower than if individual stations take turns on the frequency. Rather than relaxing parameters, shift to another lesser-used frequency. Our local network has been designed with frequency 'layers' to allow this. Recommended starting parameters are listed below:
Slot time: 200 milliseconds
Persist: 250
Maxframes: 4 to 6
Frack: 5000 milliseconds
Response delay: 2000 milliseconds
Check time: 3 seconds
Packet length: 255 bytes

Be sure to check the format for these parameters used by your TNC or software. Often parameters are entered in numbers that represent milliseconds x 10. Check first.

Handling Messages
CCAR Network Destination Addresses
Destination "TO" Address
***RACES Duty Officer RACES-1@winlink.org
Chester County EOC (IC) chesterEOC@winlink.org
Chester County 911 Supervisor Super-911@winlink.org

***Address all drill traffic bound for Chester County EOC to RACES DUTY OFFICER in Room 026, unless instructed otherwise.
ALWAYS copy RACES-1@winlink.org on ALL messages!
If using Airmail, send all messages VIA 'WL2K.'
Field Station Addresses
Normally, radio email will be delivered to field radio email stations by using a "TO" address in the following format:
callsign@winlink.org
or simply callsign only (if sent from an Airmail radio email station).
Format
Your message should be encapsulated in the email format, that is, it should be written in the message body only. The email "To:", "CC:" and "Subject:" fields are for ROUTING the message to the correct station or email destination.
You must include the person to whom a message is sent in the form of a name and/or job function in the message body. This saves time and confusion. Also, include who originated the message by using a signature (name) at the end of the message.
Date and time, precedence, message numbering, handling instructions and other manual message handling data are not required or to be included in the message body. They are automatically recorded by the system. Manual message logging is also not required for messages once written as email and sent. This does not relieve the requirement to log all voice or hand-written messages from third parties before their translation into radio email.
Example Message From a RACES Operator (1st Party)
To: RACES-1@winlink.org; super-911@winlink.org
CC:
Subject: Tow Truck Request, Auto Accident
_________________________________________________________________________________
TO: 911 SUPERVISOR, RACES DUTY OFFICER

*** THIS IS A DRILL ***
An automobile accident has just been reported on Sauerbach Road North of Route 162 In West Bradford Township. There are no known injuries.

A tow truck is requested.

The incident took place about 10 minutes ago.
The reporting party is
Mr. John Doe
280 Chrome Run Road
Newlin Township

610-555-1234
Signed: Joe Ham, W3ABC
Fire Station 64

Example Message From a Third Party
To: chesterEOC@winlink.org
CC: RACES-1@winlink.org
Subject: HAZMAT Incident --Request team--PRIORITY
_________________________________________________________________________________
TO: EOC DUTY OFFICER

*** THIS IS A DRILL ***
PRIORITY
A tanker truck accident occurred on 202 at Route 30 overpass. HAZMAT team requested.

Tanker type DOT412. Material ID No. 2988 Chlorosilanes. Spill off overpass onto Route 30 and into drainage ditch containing water. Wind southwest 10mph.
Signed: Fred Firechief
Fire Station XX

Requirements For All *Training/Drill* Traffic
1) Route (address) radio email messages inbound to the EOC to the appropriate email addresses. When in doubt, send to RACES-1@winlink.org.
2) ALWAYS include a copy to RACES-1@winlink.org.
3) Compose a concise SUBJECT line that identifies the request and type of message.
4) Date, time, originating station, check, precedence, and handling instructions are NOT USED, as they are handled automatically. Formal NTS traffic, however, is handled with this information in the message body.
5) IN THE MESSAGE BODY, address the name of the person to whom the message is directed or their job function. If unknown, use "DUTY OFFICER".
6) ALL drill/training messages must include the following line:
*** THIS IS A DRILL ***
7) All messages must have a signature in the message body.
8) Attachments up to 50K are permitted by the EOC receiving stations. The smaller, the better. Crop photographs and reduce resolution to the minimum required to convey essential information. Larger attachments can be received with prior notice.
9) Always use plain ASCII text and not HTML email format.
Requirements For All *Real-Time Incident/Disaster* Traffic
Same as above requirements, except all messages shall NOT include the line "THIS IS A DRILL".
How to Send a Position Report
By sending a position report, you allow EOC and ARES/RACES managers to quickly know your precise location, and to make better decisions. Simply send an email to the address below and use the format in the following example.
To: QTH@winlink.org
Subject: POSITION REPORT
_________________________________________________________________________________
TIME: 2005/01/05 14:03
LATITUDE: 39-58.00N
LONGITUDE: 075-38.00W
COMMENT:

The date, time, latitude, and longitude must be in the format shown.
Your position is immediately streamed by the system to the worldwide APRS servers, and may be seen on any number of on-air APRS applications or web sites.
How to Request a Position Report of Other Stations
You may request an email position report of one or more stations by sending a message in the following format:
To: QTH@winlink.org
Subject: POSITION REQUEST
_________________________________________________________________________________
W3XYZ
K1ABC

Type the call signs of the Winlink station(s), one per line, in the message body.
You will receive a report by reply email when you next connect after processing is complete.
How to Adjust Your Attachment Size Limit
Each Winlink user account has a default attachment file size limit of zero bytes. (All attachments are rejected.) To change this, send an email message exactly as follows:
To: SYSTEM@winlink.org
Subject: OPTIONS
_________________________________________________________________________________
Attachments: 50000
"Attachments: 50000" should be on a new line and the only thing in the message body. The attachment size is in bytes and should be dependent on your pathway. 1200 baud Packet should obviously be a smaller file size limit than 9600 baud Packet. No commas are allowed in the number. The maximum size permitted by the system is 100000 bytes. Please never set yours this high unless you are using a high-speed broadband RF or wired telnet link to a PMBO.

Send the message. Soon (2 to 10 minutes), you will have your file size set in the system.

You will receive a confirmation message from the Winlink system similar to that below:
-----Original Message-----
From: CMBO@winlink.org [mailto:CMBO@winlink.org]
Sent: Wednesday, October 06, 2004 21:55
To: W3XYZ@winlink.org
Subject: Automatic System Message

Confirming receipt of user options message at 2004/10/07 02:55 UTC:

Prefix:
Postfix:
BCC: Yes
Attachments: 50000
Alternate:
Key Words: ""

How to Request a Catalog of Help Files and Bulletins
1) Compose a message as follows:
To: INQUIRY@winlink.org
Subject: REQUEST
_________________________________________________________________________________
LIST
In the message body on a new line, type the word, LIST, and nothing else.
2) Send the message by RF or telnet to a Winlink PMBO or Telpac gateway. It will not work to send a request over the Internet using regular email.
3) Wait 1 to 10 minutes and connect to the PMBO or gateway again. You will get a 72K text file with all the catalog items. The first column will be the "category" and the second column will be what you request.
How to Request a File From the Catalog
1) To download a PMBO list, for example, compose a message as follows:
To: INQUIRY@winlink.org
Subject: REQUEST
_________________________________________________________________________________
PMBO
In the message body on a new line, type the word, PMBO. This is the name of the file in the second column of the catalog for the file you are requesting. You can download more than one file. Just put each on a separate line in the message body.
2) Send the message by RF or telnet to a Winlink PMBO or Telpac gateway. It will not work to send a request over the Internet using regular email.
3) Wait 1 to 10 minutes and connect to the PMBO or gateway again. You will receive the text files you requested.