Outpost Packet Message Manager
Tactical Call and KA-Node/NETROM Support
Outpost v2.1 Release Highlights
Outpost v2.1 is now available and delivers 2 key pieces of functionality... Tactical Call and KA-Node/NetRom support.
Outpost's implementation of tactical calls is based on substituting a tactical call designator in place of the standard Call Sign for message creation (From:), TNC initialization (my <call>), and BBS activities (List Mine). While apparently all BBSs do not inherently support tactical calls, experimentation has shown that a tactical call can be structured to satisfy the log-on and call-sign checking of a BBS, and can achieve the intent of what Tactical Calls can offer. While the Outpost implementation is not fool-proof and does have limitations, the v2.1 implementation gives packet users the look and feel of tactical calls while operating within the FCC rules.
Is it legal?
There are three points to reiterate:
See the application note describing an example on how this configuration is set up (pending).
As described in the TAPR Publication #95-1 “Packet Radio: What? Why? How? / Articles and Information on General Packet Radio Topics,” by Greg Jones, WD5IVD (http://www.tapr.org/pr_intro.html#NetSchemes), NET/ROM was one of the first networking schemes to try to address the problems with digipeaters. A user connects to a NET/ROM station as if connecting to any other packet station. From there, he can issue commands to instruct the station to connect to another user locally or connect to another NET/ROM station. This connect, then connect again, means that to a user's TNC, you are connected to a local station only and its transmissions do not have to be digipeated over the entire network and risk losing packets.
Outpost implements KA-Node/Netrom access by managing the connect sequence for each KA-Node/Netrom node between Outpost and the BBS. to do this, 4 pieces of information are required:
Outpost extends the BBS Setup form by adding a Path Tab to select one of the 3 navigation approaches (direct, digipeater, KA-Node/Netrom). See the application note describing an example on how this configuration is set up (pending).
Please send any feedback to
updated: January 15, 2016