Outpost Packet Message Manager Version 1.3

Transcription

1 Page 1 Outpost Packet Message Manager Version 1.3 Author: Jim Oberhofer KN6PE Title: Tour and Training, v1.3 Document Rev: 1.0 Release Date: 26 December 2004 File: OutpostTnT130.pdf

2 2 v1.3 Page 2

3 Overview What is Outpost? A Windows-based packet messaging client Supports ARES, RACES, and other amateur radio emergency response teams and their need to pass digital traffic Helps automate the packet message handling environment Manages all message handling between you and your TNC and BBS Lets you read, delete, create, reply to, or forward messages back to the BBS 3 v1.3 Page 3

4 Overview Why use Outpost? Leverages the existing packet hardware, network, and BBS infrastructure Compatible with many existing BBSs and TNC PBBSs Uses your existing TNC and packet radio equipment Only a packet client (end-users) change is required Hides the complexity of the packet operating environment Similar look and feel to contemporary programs Shorter learning curve for packet operations Allows users to focus on the message, not the medium Implements most local emergency management policies for digital communications Still under active development based on user requests and on-going alignment with the Outpost mission. 4 v1.3 Page 4

5 Overview General Outpost Features Message Management Multiple message folders Supports the three primary message types: Private, NTS, and Bulletins Text Formatting in a free-form message window NTS Message Maker for creating NTS packet messages On-line report builder using report templates Send/Receive Session Management Automatically controls the sequence for initializing the TNC, connecting to, and sending messages to and retrieving messages from the BBS Configurations and Setups BBS, TNC, and Comm Port manages a list of BBSs & TNCs Message Retrieval choose the message types and timing for retrieving messages Send/Receive automation 3 ways for automatically initiating BBS sessions 5 v1.3 Page 5

6 Overview What s new in v1.3? Collaborative messaging Incoming messages Enhanced look and feel Other enhancements First release that allows Outpost to be aware of and act on requests from other Outpost instances. Includes: Urgent Message identification Processing delivery and read receipt requests Implementing slot time automation for multiple Outpost channel access coordination Adds configurable message receipt annunciation (plays a.wav file) for all incoming messages. Changes to the main Outpost message list display to highlight Unread and Urgent messages. Several other enhancements based on user requests 6 v1.3 Page 6

7 Overview Outpost History Commenced Development November 2002 v0.95; First Beta Release May 2003 v1.0; First Release October 2003 v1.1; enhanced look and feel March 2004 v1.2; on-line reports, MSYS support May 2004 v1.3; collaborative messaging December v1.3 Page 7

8 8 v1.3 Page 8

9 Topics Features Setups Tools and Controls Creating Messages A Typical Session Limitations and Constraints Questions 9 v1.3 Page 9

10 Features Message management Familiar -app look and feel Separate folders for message storage Clearer message identification (unread=bold, urgent=red) Follows a formal message workflow Manage BBS and TNC setups Additional settings to control how Outpost behaves 10 v1.3 Page 10

11 Features Message viewing Supports viewing, printing, or saving a message to a local file Reply and Forward message formatting 11 v1.3 Page 11

12 Features Message creation Supports Private, Bulletin, and NTS message types Message formatting before sending Set messages to Urgent Request delivery or read receipts Different ways for originating messages NTS Message Maker 12 v1.3 Page 12

13 Setups Application setups TNCs: create, update, or delete Configure Serial Comm Ports that are associated with each TNC BBSs: create, update, or delete Change the Station Identifier (the call sign assigned to the TNC) 13 v1.3 Page 13

14 Setups Application setups TNCs Comm Ports BBSs Station ID (call signs) Tactical Calls (if required) BBS Types Notes... Create, update, or delete TNCs Defaults are the most common TNC commands 14 v1.3 Page 14

15 Setups Application setups TNCs Comm Ports BBSs Station ID (call signs) Tactical Calls (if required) BBS Types Notes... A Comm Port setting are linked to a TNC Supports Hardware Flow Control Confirmed operational with USB-to-Serial port adapters 15 v1.3 Page 15

16 Setups Application setups TNCs Comm Ports BBSs Station ID (call signs) Tactical Calls (if required) BBS Types Notes... Defaults are the most common BBS commands Need to be careful with BBS prompt uniqueness 16 v1.3 Page 16

17 Setups Application setups TNCs Comm Ports BBSs Station ID (call signs) Tactical Calls (if required) BBS Types Notes... Supports BBSs that require a Secondary Tactical Call Logon (such as the modified AA4RE BBS) 17 v1.3 Page 17

18 Setups Application setups TNCs Comm Ports BBSs Station ID (call signs) Tactical Calls (if required) BBS Types - MSYS Notes... MSYS BBS requires additional BBS prompt handling 18 v1.3 Page 18

19 Tools and Controls Types of controls Controls the flow of each Send/Receive Session Sets how messages are created and handled Set various data fields to automatically populate on-line reports, other areas Set up default Directory Names Various Log Settings Controls to re-size message listing column widths An Interactive Packet Window where the user can directly interact with the TNC or BBS 19 v1.3 Page 19

20 Tools and Controls Send/Receive Settings Selects different ways to automatically schedule message send and retrieve sessions Select which message types are retrieved Once a message is received, select what to do about it 20 v1.3 Page 20

21 Tools and Controls Message Settings Define default settings for new messages, includes Default destinations Auto message numbering Handling replies and forwards Set up defaults for requesting message receipts Setting for permanently deleting messages 21 v1.3 Page 21

22 Tools and Controls Report Settings Message number automatically increments and populates the Subject Line NTS Messages On-line reports Standard report variables automatically replace <tags> in On-line Reports (described later) Three flexible fields are userdefined and automatically replace <tags> in On-line Reports 22 v1.3 Page 22

23 Tools and Controls Directory Settings Used for optional organization of application files Archive directory used for message archive export and import files (*.oaf) Reports directory checked for any On-line Reports (*.txt) Log directory is home for all Outpost logs (*.txt) Defaults to the Outpost application directory User defined to any existing or new directory on the PC 23 v1.3 Page 23

24 Tools and Controls Other Controls TNC Session counter displays in session logs; increments with each Send/Receive Session Bulk delete of the Deleted Msgs Folder Display controls Resets column widths to their default settings Packs column widths for optimal viewing Manual control to resize or hide any column 24 v1.3 Page 24

25 Tools and Controls Interactive Packet Window Window to manually interact with the TNC and BBS Printing and logging controls Cut-and-paste clipboard support into and out of the IPW window cntl-c (upper case C ) to get the TNC s attention cntl-c (lower case c ) to cut text to the Windows clipboard Can directly create a message from highlighted IPW text 25 v1.3 Page 25

26 Creating Messages Direct entry Allows cursor placement within the text field Supports TAB characters (cntl-tab) thereby reducing character count Allows text files to be directly imported into the message form 26 v1.3 Page 26

27 Creating Messages NTS Message Maker Step 1: Forms-based with field validity checking 27 v1.3 Page 27

28 Creating Messages NTS Message Maker Step 1: Forms-based with field validity checking Step 2: Press Check; reformats the message per the agreed NTS Packet message standard 28 v1.3 Page 28

29 Creating Messages NTS Message Maker Step 1: Forms-based with field validity checking Step 2: Press Check; reformats the message per the agreed NTS Packet message standard Step 3: Saves the message to a message window; message type is NTS. Press Send when ready. 29 v1.3 Page 29

30 Creating Messages On-line Report Builder Step 1: Set up the Report Settings (described previously) Step 2: Understand the list of Report <tags> NOTE: there are some report variables that have to methods for representing them Tag <D>, <date1> <date2> <T>, <time> <M>, <msg#> <C>, <call> <name> <bbs> <subj>text <org> <city> <county> <state> <province> <tacloc> <tacid> <text1, 2, 3> = / comment Description mm/dd/yy (5/21/04). dd-mmm-yyyy (21-May-2004) hh:mm (22:45) Message Number; from Report Settings Call, as entered at the Station ID form Name, as entered at the Station ID form BBS name; current BBS Places text on subject line Organization; from Report Settings City name; from Report Settings County name; from Report Settings State name, 2 char; from Report Settings Province name, 2 char; instead of state Tactical Location; from Report Settings Tactical ID, 3 char; from Report Settings User defined text; from Report Settings Prompt Place a comment in the report 30 v1.3 Page 30

31 Creating Messages On-line Report Builder Step 1: Set up the Report Settings (Tools > Report Settings) Step 2: Collect the list of Report tags, most in the format <tag> Step 3: Develop the report template, save as a.txt file. NOTE: see the use of comments (/), <tags>, and prompts (=) 31 v1.3 Page 31

32 Creating Messages On-line Report Builder Step 1: Set up the Report Settings (Tools > Report Settings) Step 2: Collect the list of Report tags, most in the format <tag> Step 3: Develop the report template, save as a.txt file. Step 4: From a new message form, File > Open a Report and choose a report template. NOTE: Subject line is updated, <tags> are replaced, and cursor is positioned at the first prompt. Press cntl-tab to progress to the next prompt. Press Send when done. 32 v1.3 Page 32

33 Creating Messages Cut-and-Paste from other apps From Excel, highlight the fields to be copied, then paste into an Outpost message. At the receiving station, highlight and copy the message, then paste back into Excel. Tabs are preserved so the message can be pasted back into another spreadsheet. 33 v1.3 Page 33

34 A Typical Session Open Comm Port Initialize the TNC Connect to the BBS Send all messages from Out Tray If Private is set Retrieve List, Read, and Delete each message If NTS is set, Retrieve List, Read, and Delete each message If Bulletins is set, Retrieve List, if don t have it, read each message Send any message receipt replies Exit the BBS, Close the Comm Port 34 v1.3 Page 34

35 A Typical Session Influenced by Send/Receive Settings Send Messages Only sent from the Out Tray to this BBS Messages must be Sent not Saved Moved to Sent Folder when sent Retrieve Messages Depends on the Retrieve settings; if none are selected, none are retrieved Depends on the Keep on BBS setting Bulletins are never deleted New messages are stored in the In Tray Send Receipts Any pending Delivery and Read Receipts are sent back to the requester Open Comm Port Initialize the TNC Connect to the BBS Send all messages from Out Tray If Private is set Retrieve List, Read, and Delete each message If NTS is set, Retrieve List, Read, and Delete each message If Bulletins is set, Retrieve List, if don t have it, read each message Send any message receipt replies Exit the BBS, Close the Comm Port 35 v1.3 Page 35

36 Considerations, Limitations and Constraints What Outpost does not do No support for any bulletin board forwarding protocol No direct internet access No support for common mail protocols (POP3, SMTP, etc.) Things to avoid Sending bulletins to a named person (instead of a group Identifier such as ALLEOC, etc.) will cause repeated retrievals by that person Embedding the BBS prompt string in a message (fails to ensure the uniqueness of the BBS prompt) will cause erroneous results 36 v1.3 Page 36

37 For more information Visit the Outpost website Send inquiries to Jim Oberhofer, 37 v1.3 Page 37

38 Other Information 38 v1.3 Page 38

39 Tools > Send/Receive Settings Area Automation Automation Retrieving Retrieving Retrieving Retrieving Retrieving Receiving Receiving Receiving Other Setting Description Choose one 1. No Automation 2. Schedule a Send/Receive Every [ ] minutes 3. Schedule a Send/Receive at [ ] [ ] [ ] [ ] minutes past the hour Send a message immediately when it is complete Retrieve Private Messages Retrieve NTS Messages Retrieve New Bulletins Skip (do not retrieve) Bulletins I sent to the BBS Retrieve Selected Bulletins Play this sound on arrival Print Message to the (default) printer Keep messages on the BBS; do not delete after retrieving Show TNC Session Window during Send/Receive Setting 1. Default Unchecked Checked Unchecked Unchecked Unchecked Unchecked Unchecked Unchecked Unchecked Unchecked 39 v1.3 Page 39

40 Tools > Message Settings Area Setting up a new message Setting up Setting up Replies and Forwards Replies and Tracking Messages Tracking Deleting Messages Setting Description Choose one 1. Set default to Private 2. Set default to Bulletin Default destination [ ] Add message number to subject line Check one 1. Set default to Private for replies and forwards 2. Set default to original message type (excludes NTS) for replies and forwards Close original message on reply or forward Always request a delivery receipt Always request a read receipt Prompt before permanently deleting a message Setting 1. Default Unchecked Unchecked 1. Default Checked Unchecked Unchecked Checked 40 v1.3 Page 40

41 Tools > Report Settings Setting Description Next Message Number Organization City County State/Prov Tactical Location Tactical ID Text Variable #1 Text Variable #2 Text Variable #3 Setting 100 Blank Blank Blank Blank Blank Blank Blank Blank Blank 41 v1.3 Page 41