css body, p, .post-body { font-family: 'Google Sans Text', sans-serif !important; } /* Apply Google Sans to Post Titles and Headings */ h1, h2, h3, h4, h5, h6, .post-title, .post h2 { font-family: 'Google Sans', sans-serif; font-weight: 500; }

Thursday, June 25, 2026

Another way to use Digital Radio Modes if you do not have an RF Radio = VoxDMR (Part 3)


What is VoxDMR?   The short explanation is that it is a free app for Android, Windows and Linux that will allow you to get on DMR without a radio.

The longer explanation is:

VoxDMR is a free, hotspot-less Digital Mobile Radio (DMR) software client that allows licensed amateur radio operators to connect directly to DMR networks without a physical transceiver or hardware hotspot. Developed by J. Calado, the application runs on Android, Windows, and Linux platforms, transmitting digital voice directly over the internet. 

Core Mechanics & Features
VoxDMR works similarly to older software clients like DroidStar but offers a refreshed user interface and modern protocol features. 
  • Protocol Integration: It utilizes the Rewind protocol to establish direct communication links with master servers.
  • Network Support: Licensed hams can communicate across multiple major networks including BrandMeister, TGIF, DMR+, and FreeSTAR.
  • Audio Encoding: Uses software-based AMBE+2 vocoder technology to compress, process, and clean real-time digital voice audio.
  • Hardware Compatibility: It supports dedicated Android network radios (such as the Inrico S200 and T320) by mapping physical Push-To-Talk (PTT) side buttons. 

Step-by-Step Configuration Strategy
To activate and use VoxDMR, operators must possess a valid amateur radio license, an active DMR ID, and network access passwords. 
1. Software Installation
  • Android: Download the app via the Google Play Store or obtain the official APK release from the VoxDMR GitHub Repository.
  • Windows: Install using the standard installer package from the Official VoxDMR Webpage or execute the command winget install jcalado.VoxDMR in the Windows Terminal.
  • Linux: Deploy the native Linux package provided on the official software main page. 
2. Vocoder Setup
Upon the first launch on your device, download and initialize the digital vocoder file inside the application menu to activate audio processing. 
3. Server Registration 
  • Open the connections profile menu by tapping the three-line configuration menu icon. 
  • Create a new connection profile and populate the mandatory identity fields:
    • Call Sign (e.g., ZS1I)
    • Radio ID / DMR ID
    • Hotspot / Security Password (configured beforehand in your Self-Care dashboard on BrandMeister or TGIF). 
  • Select your exact target server location (e.g., BrandMeister UK, TGIF United States) from the dropdown menu and hit save. 
4. Initiating Contact
Tap the profile to connect. A green visual indicator confirms a successful connection. Once connected, input your desired Talk Group (TG) number or select a group from your favorites list to start monitoring or transmitting audio.
 
Web-site - VoxDMR = Click HERE 
Setup guide available HERE 
Here you will find everything you need to successfully install VoxDMR and also use the application.  No need for me to explain how to install and operate the software.

Images:  Click on the images for larger view. 














Wednesday, June 24, 2026

The ZS1I 40M WSPR Beacon is back on the air in Mossel Bay, South Africa

My previous post relating to the 40m WSPR Beacon available HERE refers.

The ZS1I 40 Meter Beacon located in Mossel Bay, South Africa is back on the air using the solar power supply.  So far the supply is running smoothly without any hick-ups.

Particulars of the ZS1I Ultimate 3S Beacon:

  • Call: ZS1I
  • Freq.: 7.038 600 Mhz
  • Band:  40 Meters (7 Mhz)
  • Grid:  KF15BT
  • Power:  250 mW
  • Mode: W-2  (WSPR2)
  • Antenna:  EFHW (49:1 Balun)
  • TX Period:  Every 10 Minutes
  •  Beacon on the air from:  7 October 2025 @ 10h00 SAST
  •  First Spotter: 10h20 ZS5SAM (Div 1)   Barrydale. (Distance 134 km)

Time to get the 6m CW Beacon on the air.  I will be working on this beacon in the coming days if "Murphy" stay out of my Shack. 


Image: ZS1I DX Report - Pedro LU7ABF  (Click on image for larger view.)  

No excuse not to tune into or connect to the DMR-ZA Net on a Tuesday evening at 19h30 SAST

The title of this article sounds like click-bait but really I believe there is no "amateur radio" reason why operators cannot tune into the weekly DMR-ZA Net on TalkGroup 655 on a Tuesday evening at 19h30 SAST.  Let me explain!

First some background information about the DMR Net

DMR-ZA is the digital mobile radio amateur network in South Africa, built to link local repeaters and hotspots via the internet. It relies on Talk Group (TG) 655 for general South African traffic, acting as a virtual meeting place for radio amateurs across the country. 
Key Network Details
  • Primary Talk Groups: Talk Group 655 is the open national calling channel. Regional channels (such as province-specific groups) and local repeater talk groups manage localized traffic. 
  • Network Infrastructure: The South African portion of the radio network largely relies on the BrandMeister Wiki server, specifically brandmeister.net.za. 
  • Weekly Net: The official DMR-ZA Net takes place on Tuesday evenings at 19h30, hosted on Talk Group 655. All stations are welcome to check in. 
Getting Connected
To participate in the net or use the network, you need a licensed amateur radio ID and an internet-linked DMR hotspot or local repeater. 
  • Get an ID: You must register your callsign to receive a specific ID via RadioID.net
  • Network Configuration: If you are setting up your own MMDVM hotspot, the server and network settings are available on the South Africa - BrandMeister Wiki page. 

The above is one way to get connected but I have a few other ways to tune-in / connect to the DMR-ZA net on a Tuesday evening.  I am talking about cross-linking and using equipment that you already have available in the Shack. 

Cross-linking digital radio modes (like DMR, D-STAR, or C4FM) to an analogue radio means translating these proprietary digital voice streams into standard analogue FM so both legacy users and digital operators can talk to each other.  

Mixed-mode operation: This function allows a digital repeater to transmit a digital signal to modern digital radios while simultaneously rebroadcasting the audio in standard analogue FM to users who have not yet upgraded

AllStarLink or Echolink VoIP Gateways:  To connect a local analogue radio to distant digital radio networks (such as DMR or D-STAR talkgroups), operators use VoIP systems like AllStarLink

  • By connecting a simple analogue transceiver (like a Baofeng) to a PC running AllStarLink software, you create a gateway node.

  • The digital network converts the data into internet packets, which are subsequently sent to the analogue node where they are broadcast over the air. 

Cross-linking digital radio modes (like DMR, D-STAR, or C4FM) to an analog radio requires external hardware or bridging software because analog FM radios cannot directly encode or decode digital transmissions. To achieve two-way communication, the digital signal must be decoded into audio and re-transmitted in analog, or routed through an internet-linked VoIP gateway. 

The most effective ways to cross-link between digital and analog radios include:

1. VoIP Gateways (Echolink or AllStarLink)

You can bridge analog radios to digital talk groups by connecting an analog "link radio" to a computer or Raspberry Pi running bridging software. 

  • How it works: Software like AllStarLink or Echolink creates a node that connects your local analog transmission to a digital network (via IP).

  • Hardware Needed: A USB soundcard interface (such as a SignalLink or a homebrew sound card fob connected to your radio's data or mic port. 

2. Cross-Mode Hotspots (MMDVM)

If you operate an MMDVM (Multi-Mode Digital Voice Modem) hotspot, you can cross-convert digital modes on the fly. 

  • How it works: While most MMDVM units link digital to digital (e.g., DMR to D-STAR), advanced bridging configurations like MMDVM_Bridge combined with Analog_Bridge allow digital networks to talk to analog VoIP nodes.

  • Transcoding: The system transcodes digital voice packets into analog audio that standard FM radios can receive. 

3. Analog-to-Digital Repeaters (Mixed Mode)

Certain local amateur or commercial repeaters are hardware-equipped for cross-mode operation. 

  • How it works: Systems like Yaesu System Fusion often feature Automatic Mode Select (AMS), which automatically detects an incoming analog FM signal and converts it into a C4FM digital transmission (and vice-versa). 

Now that we know a little bit more about cross-linking / cross-mode operation let's look at how I am doing it here in Mossel Bay. I will explain how I do it but there are always other ways to do it to achieve the same result in the end.

Let's have a look at the flow-chart below in order to give you an overview of all the systems I am running, but also the networks that connects to the ZS1I Hub in Mossel Bay.

Image:  Flowchart (Click on images for larger view.)  

Herewith a list of different equipment / apps and images that cross transmit / receive the DMR-ZA Net on a Tuesday evening. (Click on images for larger view.)

1.  ZS1I 49355 AllStar Hub Network which incorporates Echolink. (ZS1I-R)

2.  DMR / DVSwitch /AllStar Bridge (TG 65522)

3.  ZS1I MMDVM Digital Repeater (TG 65522)

4.  145.550 Mhz Analogue Simplex RF Link

5.  DroidStar / VoxDMR Applications for DMR

6.  ASL3 to Mumble Bridge PC (Mumble Client) as well as Mobile Phone (Plumble Client) 


 

7.  BrandMeister - Hoseline Application (PC or Mobile Phone)

 


8.  DVSwitch Mobile Application (PC or Mobile Phone)

9.  Many Analog-Repeaters and Links are connected to the ZS1I Hub Network on a daily basis. (See column on the right hand side of the flow chart above.)

Some of these analogue repeaters will be connected to the ZS1I Hub Network on a Tuesday evening and they might also be linked to other repeaters country- and world wide.  So why not link up with your local analogue repeater.  You might just be able to connect to the DMR-ZA Net on a Tuesday evening at 19h30 SAST. 

 


Optional Cross-Linking to be added:

1.  SVXLink Reflector / Node

2.  AREDN Mesh Network Node

3.  ZS1I MMDVM Hotspot 

 

Finally:  There are an abundance of means illustrated above to connect to the DMR-ZA Net on a Tuesday evening at 19h30 SAST.  The DMR-ZA Net is an open net and all radio amateurs are welcome to join / connect to the net.  Brian ZS5BR is the net controller and I would like to thank him for professionally conducting the net each Tuesday evening.  Highly appreciated!!

Tuesday, June 23, 2026

Chronological organized list of every terminal command used to diagnose, configure and secure ASL3 to Mumble Bridge (Part 4)


Here is the complete, chronologically organized list of
every terminal command I used throughout this build to diagnose, configure, and secure the ZS1I AllStarLink 3 to Mumble Bridge.

1. Service Control & Restart Sequence

These commands were used to cleanly clear hung socket ports, reload system profiles, and restart the core components of the radio-to-Mumble link.

bash

# Restart the core AllStarLink 3 Asterisk telephony engine
sudo systemctl restart asterisk

# Stop the Asterisk engine to clear stuck configurations
sudo systemctl stop asterisk

# Force kill any hidden or orphaned background Python script processes
sudo killall -9 python3

# Reload systemd when changes are made to background service files
sudo systemctl daemon-reload

# Enable the bridge service to automatically launch on system boot
sudo systemctl enable mumble_bridge.service

# Start the background bridge service link
sudo systemctl start mumble_bridge.service

# Stop the background bridge service link
sudo systemctl stop mumble_bridge.service

# Force-restart the background bridge service link to load code updates
sudo systemctl restart mumble_bridge.service

Use code with caution.

2. Manual Testing & Execution

Used to run the Python script interactively in the terminal window to see real-time error logs and connection confirmations.

bash

# Run the Mumble bridge script manually in foreground console mode
python3 /opt/Analog_Bridge/mumble_bridge.py

Use code with caution.

3. Log Inspection & Troubleshooting

Used to view the live system journals to trace errors like the audio tracking state exceptions.

bash

# View the last 50 lines of the bridge log and follow new messages live
sudo journalctl -u mumble_bridge -n 50 -f

# Follow the live output stream logs of the bridge script
sudo journalctl -u mumble_bridge -f

# View the last 20 lines of the bridge script history logs
sudo journalctl -u mumble_bridge -n 20

Use code with caution.

4. Asterisk CLI Console Management

Used to log directly into the running Asterisk core to watch node registrations and verify channel properties.

bash

# Access the live Asterisk running console interface
sudo asterisk -r

# Enter the Asterisk console with maximum verbosity enabled for packet tracking
sudo asterisk -vvvvr

Use code with caution.

5. Network Diagnostics & Packet Sniffing

Used to discover the true 352-byte packet length structure and track down why your phone's audio was originally dropped [2026-06-07 15:52:20.811].

bash

# Update the system repository list to fetch diagnostic tools
sudo apt update

# Install the tcpdump network packet analysis utility
sudo apt install -y tcpdump

# Snoop loopback traffic on port 33001 to view audio frames coming FROM Asterisk
sudo tcpdump -i lo udp port 33001 -XX

# Snoop loopback traffic on port 35001 to view audio frames going TO Asterisk (limited to 5 packets)
sudo tcpdump -i lo udp port 35001 -XX -c 5

# Snoop loopback traffic on port 35001 continuously to verify phone mic streaming activity
sudo tcpdump -i lo udp port 35001 -XX

Use code with caution.

6. Firewall & Security Configuration

Used to check and explicitly open up network pathways on your host computer for Mumble traffic.

bash

# Explicitly authorize UDP packets through the Linux firewall on port 64738
sudo ufw allow 64738/udp

# Explicitly authorize TCP packets through the Linux firewall on port 64738
sudo ufw allow 64738/tcp

# Reload the firewall configuration table to lock in the open port rules
sudo ufw reload

Use code with caution.

7. File System, Permissions, & Script Automation

Used to create the automatic night backup files and schedule them inside the system clock tracker.

bash

# Open and edit the system service runner definition file
sudo nano /etc/systemd/system/mumble_bridge.service

# Open and edit the main operational Python script file
sudo nano /opt/Analog_Bridge/mumble_bridge.py

# Create the automated evening script backup utility file
sudo nano /opt/Analog_Bridge/backup_bridge.sh

# Make the backup shell script executable so the system can run it
sudo chmod +x /opt/Analog_Bridge/backup_bridge.sh

# Execute the backup script manually right now to create an immediate backup copy
sudo /opt/Analog_Bridge/backup_bridge.sh

# Open the root system task automation scheduler to add the 17:00 execution rule
sudo crontab -e

Use code with caution.

8. Linux Mint Desktop User-Space Audio Control

Used to reset your computer's sound graph context and unlock hidden system volumes when configuring the client app.

bash

# Reset and restart PipeWire, PulseAudio emulation, and WirePlumber audio managers
systemctl --user restart pipewire pipewire-pulse wireplumber

# Launch the PulseAudio Volume Control graphical matrix panel
pavucontrol

# Launch the low-level kernel hardware command-line audio mixer
alsamixer

Use code with caution.


You now have a complete index of every command used in this project that will enable you to successfully install and setup your own ASL3 to Mumble Bridge.

Is Social Media killing amateur radio on-the-air activity?

  In a recent discussion with a fellow radio amateur we discussed the use of WhatsApp, Telegram and even Facebook as a means of forwarding ...