Ruspo Relay 1: Review of the Latest Version

Ruspo Relay internet repeater mode

What is Ruspo Relay?

Ruspo Relay 1 ( ) is an application (program) for desktops and workstations designed for connecting various analog audio devices (for example, two-way radios, intercoms, remote microphones, etc.), and controlling them via a local network or the Internet using VoIP technology (Voice over IP). The program is also used as an Internet repeater to connect geographically remote radio stations or other analog devices to each other.

Ruspo Relay 1 main dashboard
Ruspo Relay 1 main dashboard

This program is popular among both radio professionals and amateurs due to its flexibility and versatility.

In general, thanks to Ruspo Relay, you can position operators or dispatchers where they are more comfortable, and two-way radio equipment – where they will work better.

The first version of the program was released in 2011 and still work around the clock in the possession of many users. This review relates to version 1.30, currently relevant (2019).

Ruspo Relay: Examples of Usage

Controlling of a remote transceiver (radio):

Controlling audio devices such as intercoms, etc .:

Connecting two transceivers in completely different places through the network so that they work as a repeater. Thus, the coordination of two groups of users in different places is carried out:

Controlling and voice communication with a transceiver connected directly to the operator’s computer – for ease of operation or, for example, for playback pre-recorded messages or announcements (auto informer mode):


How does Ruspo Relay work?

When installed on a computer, Ruspo Relay allows you to select a sound subsystem (audio adapter) for operation.

Then, you need to connect the PC to the radio or other analog audio device. This can be done in one of the proposed ways (more details in the instructions and here).

You can also use an inexpensive ready-made solution — an interface (see, for example, here: ; the interface developer also adapts it to various devices and customizes the program.)

PC-to-transceiver interface
PC-to-transceiver interface

Then make settings for sound and connections. Each program instance can be configured both as a server (accepting the connection) and as a client (initiating the connection). The radio or other analog device (intercom, microphone, etc.) can be connected to both the client and the server. In the case of the implementation of the Internet repeater scheme, the devices are connected to both computers tied in a bridge.

For connection may be used a local network or the Internet.

Ruspo Relay Setup Tabs
Ruspo Relay Setup Tabs

Unlike some other solutions, Relay 1 does not require, in general, any third-party services to work. However, until recently, as in the case of any client-server application, a fixed IP address was required for connection to the server side. Now the possibilities of using the program have become even wider. Since October 2017, Ruspo Relay 1 users can interconnect different instances of the program through the Remote Repeater service (read more here: ).

At the final stage, a test connection is made and a test is made. In addition to the basic functions (control of reception / transmission, listening to the air and voice transmission), there is an opportunity of using of some additional ones, such as auto informer, additional channels control and others.

After configuration, the program can work without the participation of the operator. If the network connection is lost, the program try to restore the connection at various intervals.

More information about configuring the program and various settings can be found in the instructions on the official website of the developer:

Similar and competing solutions: Ruspo Relay vs Yaesu Wires-X

The Ruspo Relay program is an original development that uses advanced solutions in the field of digitization, compression and transmission of sound. No direct analogues of the program have yet been found, but there are similar functional solutions from individual manufacturers of radio equipment. In particular, among radio amateurs and professionals, Yaesu Wires-X VoIP solution is well-known ( ). This solution has proven itself well, but its application is relevant only when using Yaesu radio equipment. Moreover, Yaesu Wires-X is designed to connect only Yaesu radios that have the appropriate Mini-DIN interface connector, and you also need to buy an Internet Linking Kit HRI-200 and a special cable. However, among the existing solutions, this is the most worthy object for comparison.

Detailed consideration of both solutions shows the following advantages of Ruspo Relay 1:

+ Ruspo Relay 1 software is vendor-independent: it does not require the purchase of a proprietary interface and cable for connection to the radio, it is not tied to any particular type or model of device; a person who is a little bit familiar with electronics, can connect a two-way radio or other audio device to a PC according to the instructions for the program, using inexpensive and accessible components, moreover, in several different ways;

+ Ruspo Relay 1 does not require, in general, any third-party services for the operation; if the connection is made via a local network, the voice signal does not leave the local network; if the connection is made via the Internet, you can ensure high confidentiality of conversation by working within a virtual private network (VPN);

+ Ruspo Relay 1 is not demanding on computer resources – when testing on a PC with a single-core Celeron 2.4 GHz processor and 512 MB of RAM (OS Windows XP SP2), there were no delays or hang-ups; no additional audio drivers and codecs are required; a similar 10-year-old computer may be found practically for free, and it is not a pity to allocate it to connect to the radio;

+ Due to the good voice signal compression, Ruspo Relay 1 is not demanding on data transfer network resources; it was tested even with GPRS and dial-up modem connection; it works fine through wireless networks of mobile operators, various routers and hubs; the program uses 1 TCP and 2 UDP ports (for comparison, Wires-X requires 6 UDP ports and a connection of at least 8 MBpS);

+ The Ruspo Relay 1 program goes localized in Russian, English and Spanish languages and is additionally compatible with Localizator (a simple and convenient tool for translating correctly the user interface of the program into any language or even a dialect by the user himself – );

+ Ruspo Relay 1 has unique features:

Auto informer / radio beacon (playback of pre-recorded messages or announcements), moreover, the file of a new message can be transmitted to the target computer remotely;

management of additional channels for re-configuring the radio or device.

Software price and distribution terms

The Ruspo Relay 1 program is paid, but it has a free demo version, which is available for download on the official website . The demo version of the program has certain limitations ( ), but it allows you to familiarize yourself with the program’s capabilities, to experiment with connections and decide whether this program is a right fit for you.

The price of the paid version of the program varies (for different distributors ) about $ 100-125.

The program (technically) allows you to use several copies of the software on one computer, which allows you to achieve additional savings when several radios or audio devices are connected to one computer.


New Options of Ruspo Relay 1


Ruspo Relay 1 Options tab
Ruspo Relay 1 Options tab

Ruspo Relay 1 ( ) is a desktop / workstation application, designed to connect various analog audio devices (e.g. two-way radios, intercoms, remote microphones, etc.) via a local network or the Internet.

This program is popular among both radio professionals and hobbyists thanks to its flexibility and vendor-neutrality. Unlike some other solutions, Relay 1 does not, in general, require any third-party services. However, until recently, as any server-client application, to connect, the server side required a fixed IP address.. It is not a problem at all to assign a fixed IP address within the LAN . And, despite lively forum debates on the imminent exhaustion of white IP4 addresses, it is still not an issue to get an IP4 address from the cable provider or LTE carrier. But, anyway, that imposed certain restrictions on the using of the software, say, in the casual places or in the certain networks.

Now the possibilities of using the program have become even wider. Starting from October 2017, users of the software are able to connect different instances of Ruspo Relay 1 through Remote Repeater service. So, if it is impossible to obtain a real IP address for “server” mode, just contact Ruspo tech support — there is a  Remote Repeater solution for an affordable fee ($9.9/mo, prepaid). For this fee, you get a virtual channel, where may be connected up to 5 instances of the program (probably, located geographically in the very different places and connected to the Internet in different ways).

Remote Repeater service have 99.1% average uptime and may be used for constant connection (for example, if Ruspo Relay 1  works as an Internet bridge (repeater) for two-way radios in different locations.

For connection, you have to chose a Client connection mode and input service address and port numbers (provided by the support) in the IP and Port fields. In the common case, you also have to remove a tick from the Stay server ON check-box. Other options are the similar with the conventional case of use. They are comprehensively described in manual.

Free demo version of the program works via Remote Repeater as well, but under usual limitations ( ).

Installing the LetsEncrypt SSL Certificate, and Arranging an Automatic Renewal

Chrome warning
Chrome warning…


There are a lot of reasons to use TLS encryption on a website. Some of them are obvious (e.g. the protection of visitor’s safety), some are related to the subtleties like SEO and user experience. Many analysts recommend switching to HTTPS because search engine of Google consider HTTPS as one of the ranking signals. Beside that, new versions of browsers, (e.g. Chrome) frighten visitors of non-encrypted websites, marking them as “unsafe”.

Until recently, many webmasters, bloggers and SOHO business owners used to encrypt their resources with free StartSSL and WoSign certificates. Since StartSSL and WoSign certificates were going to be distrusted by Mozilla ( and Google, and there were no other free options to get SSL for a long term, we have chosen an LetsEncrypt ( option. Since LetsEncrypt certificate is valid for 90 days only, automation is really needed. Recommended automation tool is EFF’s Certbot ( This utility semi-automatically enables HTTPS on your website, deploying Let’s Encrypt certificates.

Hereinafter we share our own experience on initial installation and automation, briefly.


Above mentioned resources give full description for different situations. Here we just demonstrate a logic of using the software for one particular case (only one domain/subdomain on VPS, which had previously another certificate; Nginx as a webserver, and CentOS7 as an OS; root SSH access; also presumed that we can stop webserver temporarily without negative consequences).

Step by step:

1. Install certbot:
yum install certbot

(several EPEL dependencies will be downloaded along; that’s Ok)

2. To obtain a certificate using a built-in “standalone” plugin, you may need to temporarily stop your existing webserver:
systemctl stop nginx

3. Start process:
certbot certonly --standalone -d

and make sure that things go smoothly:


- Congratulations! Your certificate and chain have been saved at /etc/letsencrypt/live/ Your cert will expire on 2017-04-28. To obtain a new or tweaked version of this certificate in the future, simply run certbot again. To non-interactively renew *all* of your certificates, run "certbot renew"

Certificates actually will be placed at

Symlinks to certificates will be placed at
You may use Webroot plugin of the Certbot (it allows to get a certificate without stopping/starting Nginx) instead of Standalone plugin, but you will probably need to restart/reload Nginx later anyway in order to activate changes made in config file(s). It made no difference in our case.

4. Find the Nginx config file(s). In our case there are:
/etc/nginx/nginx.conf and the linked one /etc/nginx/conf.d/ext.conf

Make sure to remove or comment off the old Certificate parameters and add the new ones:
# disabled 2017-01-28
# ssl_certificate /etc/nginx/conf.d/yourold.crt;
# ssl_certificate_key /etc/nginx/conf.d/;
# added 2017-01-28
ssl_certificate /etc/letsencrypt/live/;

ssl_certificate_key /etc/letsencrypt/live/;
ssl_trusted_certificate /etc/letsencrypt/live/;

Also it is useful to add directories used by Webroot plugin of the Certbot to the Webroot path (it allows to renew the certificate in the future without stopping/starting Nginx). So add:
location /.well-known {
alias /home/site/.well-known;
into the both parts of the config file:
server {
listen 80;


server {
listen 443 ssl;

(There may be a vague point here, but we found by experience that though Standalone plugin uses port 443, Webroot plugin uses port 80 for verification).

It may be useful to put a test file (a.txt, for instance), into specified directory /.well-known/acme-challenge (to test access later).

Also, if there was not SSL before, several usual options must be added, but we leave old ones.

5. Then don’t forget starting webserver:

systemctl start nginx

Make sure it works and test file is accessible from the Internet via both http and https.

6. Now let’s turn to the future renewals automation.
Find .conf file in /etc/letsencrypt/renewal/

Edit options used in the renewal process like this:


# authenticator = standalone
authenticator = webroot
webroot-path = /home/site

un-comment line:
renew_before_expiry = 5 days

7. Launch Certbot renew using test (dry-run) mode:
certbot renew --dry-run -w /home/site

Make sure all things are OK, especially verification:

Congratulations, all renewals succeeded. The following certs have been renewed: ...

9. It makes sence to archive folder /etc/letsencrypt and configuration files (/etc/nginx/conf.d), and store them in a cool, dry place 🙂

8. Add command

certbot renew -w /home/site -q

into the Crontab for daily fulfillment. It will not reload a certificate every day if you set renew_before_expiry properly (see p.6).

9. Make sure your Nginx reloads configuration after certificate renewal. Obvious way for that may be adding command like
nginx -t -q && nginx -s reload
into the Crontab for the certain date. A little bit smarter way would be to tie reloading with the exact moment of certificate renewal. In this case we can modify renewal command (p.8) with hook like this:
certbot renew --no-self-upgrade -w /home/site -q --renew-hook "nginx -t -q && nginx -s reload"

or (with full paths):

certbot renew --no-self-upgrade -w /home/site -q --renew-hook "/usr/sbin/nginx -t -q && /usr/sbin/nginx -s reload"

10. If you have configured some of the other servers (e.g. Webmin) to use the same certificates, don’t forget to reload/restart their configuration as well, e.g.:
systemctl stop webmin
systemctl start webmin

After all that, you may create an appropriate rolling event in your calendar to check if certificate is up-to-date on the website after each 90 days.

This method was approved and works well on both our websites: and


Our experience shows that the Letsencrypt and the Certbot itself run like clockwork. Some issues may appear from the Cron side and usually they caused by incorrect permissions, wrong script name or environment. If you have got problems of that sort, you may have a look at the logs, and to study a couple of useful articles:
6 Reasons Your Cron Job is Not Running ( ).

Paths and files, related to Certbot: