FYI.. --- Message 1 --- RMS Express can be configured to connect to several different servers, and I think there is some confusion about what each type of connection is appropriate. Paclink/Winmor/Robust packet/packet WL2K connections -- These make radio connections to an RMS which pipes the connection to a CMS. Paclink/Winmor/Robust packet/packet P2P connections -- These make direct connections to another station running RMS Express. They do not connect to an RMS or a CMS. Telnet P2P connections -- This makes a direction through a LAN, MESH network or the Internet to another user running RMS Express who's listening for incoming Telnet P2P connections. This is a network connection, not a radio connection. Pactor/Winmor Radio-only connections -- These make radio connections to an RMS that's operating as a node in the Winlink Hybrid Network. Any messages transmitted with this connection are relayed via radio to the destination Message Pickup Stations (MPS) using radio-forwarding from RMS-to-RMS. Messages do not get sent to a CMS. This also is the mode you use to pick up radio-only messages from one of your MPS stations. Telnet Radio-only -- This makes a Telnet connection to RMS Relay that's running as a node on the Winlink Hybrid Network. Typically it's used by sysops of these RMS to pick up messages from their running copies of RMS Relay and to post radio-only messages to be sent by their servers. Any messages transmitted with this connection are relayed via radio to the destination Message Pickup Stations (MPS) using radio-forwarding from RMS-to-RMS. Messages do not get sent to a CMS. Telnet Post-office -- This is a network (not radio) connection through a LAN, MESH network or the Internet to a copy of RMS Relay configured to runs as a Network Post Office Server. This type of session allows you to create one or more entries describing post office servers. You can turn on background message processing to poll multiple post office servers. If you are using RMS Express on a MESH or LAN network to connect to a RMS Relay running as a post office server, this is the type of connection you should use. Phil W4PHS ---------- Forwarded message 2 ---------- From: mikeaburton@outlook.com [wl2kemcomm] <wl2kemcomm@yahoogroups.com> Date: Fri, Sep 25, 2015 at 2:32 PM Subject: [wl2kemcomm] Re: Comments about different types of RMS Express connections To: wl2kemcomm@yahoogroups.com Phil's explanation of the various connectivity methodologies with RMS Express is timely. During a recent exercise for cross -border communications and SET in San Diego, many of the methods were used. The San Diego environs plus parts of Baja are interconnected by a 5 GHZ Ubiquiti EMCOMM LAN, with average speed of 100 MPS. There are two packet gateways that use this network over many hops, to connect to an HF gateway for auto forwarding and Pactor 4. Thus users in the USA that are part of this network, can connect using RMS Express Telnet and if Internet fails, to ensure out of the area delivery. For the event not only was normal gateway activity processed, so was the use of a Tenet Post Office connection. Using the new features of background forwarding, a non-ham was able to obtain messages via the LAN. This Telnet PO connection with a lap top and portable 5 GHZ dish relieved having an operator and equipment at that one location.The use of tactical calls, multiple stations on RF and LAN telnet moved over 250 messages in a 4 hour period, all via Winlink. The various combinations and features that are within RMS Express are only limited by ones imagination. Our group thanks Phil for the banner effort and appreciated being able to test some of the features before normal release. __._,_.___ ________________________________ . __,_._,___