
Software for Winlink RMS Sysops
Authorization and Becoming a WL2K Sysop:
Before you inquire to become a WL2K sysop and run an RMS gateway station, we prefer you to be an active user of radio email in the system. If you are not a current user with a valid @winlink.org address, please see this page. All RMS programs require your call sign to be in the WL2K user database, with an administrator-assigned Keycode and password unique to your call sign. You will not be able to complete installation and operate the programs unless this is first set up by a WL2K administrator.
RMS software is authorized to amateurs who will maintain their stations on the network 24/7 or who will use it as a portable emergency asset as part of a recognized organization. VHF/UHF RMS sysops should join the "Winlink_Programs_Group" at yahoogroups.com for alerts and support. HF RMS sysops should join the "WINLINK2K" group at yahoogroups.com.
To request a KEYCODE for RMS Packet or Linux RMS Gateway software, contact Lor Kutchins, W3QA. You must include your call sign and the call sign of the RMS station you are registering. If the RMS station will use a club call sign, include the email address of the club license trustee.
To request a KEYCODE for RMS Pactor or RMS WINMOR software, contact Steve Waterman, K4CJX.
RMS Packet
RMS (Radio Mail Server) Packet is software intended for WL2K sysops. This software supports a VHF/UHF packet radio gateway station to the WL2K system. RMS Packet stations are part of the network of participating stations, and they provide full automated messaging capability to the wireless amateur user using AX.25 packet radio in combination with the WL2K Common Message Servers.
RMS Packet is simple to install and run, and requires a minimum of computer and radio equipment. It runs on virtually any WinXP and later computer with .NET extensions that has a permanent connection to the internet. It supports the most popular TNCs directly, and almost all others through the AGW Packet Engine or Packet Engine Pro software.
RMS Packet is ideal to provide a temporary emergency portal for radio e-mail users, or for fixed installation at unattended remote locations where it can provide wireless e-mail communications to the "last mile".
Computer and Internet Requirements:
All RMS Programs require a full-time Internet connection. The speed of this connection is not critical. RMS Packet is designed to sense loss of connectivity and recover or reconfigure automatically. The computer should be a fairly modern 500 MHz or greater Pentium/Celeron running one of the following OS with .NET 2.0 installed:
- Windows 2000 or 2000 Pro
- Windows XP or XP Pro
- Windows Vista (32 bit or 64 bit versions) any Vista configuration
Specifically, Win 95, Win 98 and Win ME are not supported and will not run the required .NET 2.0.
The computer and TNCs should be powered from a smart uninterruptable power supply (UPS) that has a reserve battery and signals Windows to begin an orderly shutdown via an interface when battery power is low.
A shortcut to the RMS Packet executable should be installed in the "startup" directory and the computer configured to auto-boot on power applied. Check the RMS Packet help for references on how to do this. The objective is to set the computer and RMS program to operate unattended and to start automatically when power is applied.
Click here to download RMS Packet 2 Setup.zip
RMS Relay
RMS Relay is a supplemental program that can provide temporary storage of messages and local routing in the event TCP/IP access to the CMS sites is lost. It will normally only be used with co-located RMS Packet and Paclink programs. (Co-located means in the same computer, LAN, or short distance Ethernet links.) The relay program becomes active when links are lost to CMS sites. Then it provides temporary message storage and routing. RMS Relay would normally only be installed in sites devoted to emergency services. At normal public sites the loss of service to the CMS sites will simply suspend activity until it is restored.
Starting with version 2.1.0.1 the program includes an optional feature that will exchange stored messages with a CMS using links to distant RMS HF gateways over HF. The RMS Relay program will share the same controller and radio used by an RMS HF program running on the same computer. (RMS Relay-- just like RMS HF--could use any of the PTC II models including the II, IIe, IIex, IIpro, and IIusb.) Note that any RMS HF inbound portal is deactivated when RMS Relay is active and no TCP/IP connection to a CMS is available, freeing the controller to serve in HF relay service for the local area VHF ports. In most countries, a control operator is required to initiate manual HF connections.
Click here to download RMS Relay software.
A useful utility for sysop checking connectivity and open ports to CMS systems is RMS Link Test.
Download RMS Link Test.zip
RMS Pactor and RMS WINMOR
RMS (Radio Mail Server) Pactor) and RMS WINMOR, with their suite of administration programs, is software intended for WL2K sysops who operate High-Frequency stations. This software supports HF Pactor and WINMOR radio gateways to the WL2K system. These RMS stations are part of the controlled and frequency-coordinated global network of WL2K participating stations.
RMS Pactor and RMS WINMOR software authorizations are limited in certain world regions. If you have an interest in operating a public, EmComm or MARS WL2K HF station, please contact Steve Waterman, K4CJX.
Linux RMS Gateway
This is a new and updated Telpac Node/LinuX, now called Linux RMS Gateway as it conforms to the new RMS WL2K system.
The Linux RMS Gateway software is independently developed and maintained by Hans-J. Barthen DL5DI and Brian R. Eckert, W3SG, in cooperation with the Winlink 2000 development and administration team. It is distributed mostly as source code under the GNU General Public License (a small component is distributed as a binary only library).
The new software carries the same requirements as its predecessor, as well as a few new requirements, but also has the same flexibility as before for packet-radio in a Linux environment. To build and run the software, you will need:
- an installed and running Linux system (of course)
- the GNU C compiler (GCC) and standard libraries and headers, as well as standard Linux software development utilities (such as GNU Make)
- an existing ax25 installation on your Linux system with an ax25-enabled kernel, ax25-libs, and ax25-tools
- a current MySQL client library
- a current libxml2 library and header (and optionally libxml2-utils for XML document checking)
- a TNC, soundcard, or other packet-radio modem drivers, axip/axudp, or anything else that is supported by Linux to run packet radio
- radio equipment (usually a data-ready FM transceiver for VHF/UHF/SHF)
- a 24/7 Internet connection
- a Keycode and Password for the gateway's callsign to authorize connections to the Winlink2000 CMS hosts
- in some countries a special radio license is necessary to run an automatic amateur radio station
The software and support for testing are available from the authors and the community at http://groups.yahoo.com/group/LinuxRMS. Or, you can download the package here: linux-rmsgw-2.0.1-104.tar.gz