New AllStarLink3 - Mumble Bridge (Additions / Extensions) to the ZS1I HUB Network in Mossel Bay (Part 3)

(Click on image for larger view.)

Time to get to the "real juicy bit" on how to install all the "ingredients" to setup the Mumble Bridge / Server / Client.  

Now how do you install and setup an ASL3 / Mumble Bridge / Server / Client?  Million dollar question?   Now there are very few tutorials out there on the Internet that will assist you in installing a ASL3 / Mumble Bridge.  I will however explain in this article how I went about installing and setting up the ZS1I Mumble Bridge on a Raspberry Pi 3 b with the assistance of AI.

For the purpose of this tutorial I am not going to explain how to install AllStarLink Ver 3 on an SD Card for use on a Raspberry Pi. The  ASL3 Landing Page includes the ASL Manual.  Click on the above link and you will be redirected to a comprehensive online manual for AllStarLink Ver 3.  Here you will find all the necessary information to install AllStarLink Ver 3 successfully.

With regards to installing and setting up the Bridge we need to install and setup a public and private node, edit files, test connections to nodes, install and setup Mumble Server, open ports on you Internet Router and a few "odds and ends".  More information on the sequence list available HERE.  Do not run away!  It is fairly simple to get the ASL3 Mumble Bridge up and running.  Having knowledge of Linux and the Raspberry Pi will make it easier to navigate through all the installations and setups. Even if you do not have experience in this regard you will be able to install ASL3 and the Mumble Bridge if you follow all the instructions carefully.

Let's get going!!

Image 1 (Click on image for larger view.) 

I assume you already booted the PI and that you are on the Landing Page as displayed above.  (Image 1) To get to the landing page just enter the Raspberry Pi's IP address in you Internet Browser.  I use Firefox.   Click on Web Admin Portal window.  The AllStarLink System Manager page will open.  Login with your username and password.  (Image 2) 

Image 2 (Click on image for larger view.) 

Image 3  (Click on image for larger view.)

A new window will open , called the cockpit,  displaying many options. (Image 3)  At the top a banner will be displayed  - Web console is running in limited access mode.
Click on "Turn on Administrative Access".   You will now have Administrative Access.  On the left side of the page go to Terminal and click on it.  Terminal will open.  After the $ sign type:

sudo asl-menu [enter]

The asl-menu will open and here we are going to setup a New Private Node.

The AllStarLink Main Menu will open.  Select 1 Node Settings  [enter to select]

In the Node Setup Main Menu select 1 - Allstar Node Setup Menu [enter to select]

A new menu Allstar Node Select Menu will open .  Select A - Add Node  [enter to select]

Enter new node number:  I used 1977 ( Anything between 1800 - 2000.  Do not use private node number already used in other AllStarLink Nodes)

Question will appear asking:  What configuration settings should we use for Node 1977?

Select 0  None of the above (show all settings) [enter to select]

Node 1977 info will appear:

1  Node Number:  1977

2  Node Password:                (Leave blank.)

3  Node Call sign:  ZS1I   (Enter you call sign here)

4  Radio Interface:  Select No Radio interface or Hub Node

5  Duplex Type:  Select 0  Half / Full duplex with no telemetry link -  Use  space bar to select.  Select half duplex.  Next select Back and Back again.  Select 2  Restart Asterisk  <- Needed   [enter to select]

Asterisk will restart

Node Setup Main Menu will appear again.  Select 3  Update Asterisk AMI Password

Enter to select.  If you have not changed it do in now.  I already changed mine earlier.

Select 4 Update Asterisk IAX Port.  Enter Change Port.  I used 4566 -  Ensure that this port forwarding is also opened in you Internet Router.

Exit Main Menu

Select <Back>

The AllStarLink Main Menu will open.

Asterisk must be restarted to make your changes alive.  Are you sure you want to exit now.  (Note:  Asterisk restart can be done selecting 7 Logout/Reboot/Shutdown.  Select 3)

Select Yes and [enter]

Type the following at the prompt in the Terminal

sudo systemctl restart asterisk.service  [enter]

After  restart type the following at the prompt in the Terminal   

cd /etc/allmon3  [enter]

then sudo nano allmon3.ini [enter]

Go to the bottom of the page and enter the  following:

[1977]

host=127.0.0.1

user=admin

pass= xxxxxx  ;your asterisk AMI password we created earlier

 

Let's save the info

Hit Ctrl + X

Yes

[enter]

 

Reboot the node.  At the prompt type:

sudo reboot now [enter]

Go to Web Admin Portal (Click on Window)

Log in again 

AllStarLink System Manager will show up (Cockpit)

Turn on Administrative Access

Let's go to the Allmon3 page

Open and Internet Browser Tab  and type

https://IP Address /allmon3/  [enter]

Browser Page will Refresh.  If not just click refresh button (reload current page)

Node 1977 has been added once the page has reloaded. We now have two nodes displayed.  AllStarLink3 Node (467650) and 1977.  

Image:  Allmon3 Monitoring Dashboard (Click on image for larger view.) 

Login to Allmon3  (left side of page under nodes)

Username:  ZS1I

Password:  XXXXXX

We now need to check if node 1977 can connect to the AllStarLink3 Node you choose.

Choose the block with the two links on the right side of the Allmon3 Monitoring  Dashboard page

Select  command and select connect

Node # = 1977

Permanent = No

Click  Execute

 

The two nodes will be connected.  See Connect State.  It says  ESTABLISHED at both the nodes.

Now Disconnect by clicking on  X left to Node 1977 - Hover over it. The X will turn to a maroon colour.  Screen will come up to disconnect node.  Just click Execute.

The two nodes will now be disconnected.

 

But hey we do not want to connect the two nodes plus the main 49355 node manually.  We want it done automatically.

 

For this to happen we will be using the script provided by KF5FMU on his GitHub page available HERE.  I am not going to go into detail on how to install the script as this has been nicely set out by Freddie KF5FMU on his GitHub pages.  I will however provide an example of my check-connection.conf script file below.

 

check-connection.conf (Script File)

$cd /etc/asterisk/local/ [enter]

sudo nano check-connection.conf [enter]

# AllStarLink 3 Check Connection Configuration

# Created by install-asl3-check-connection.sh

# Your local AllStarLink node number

LOCAL_NODE="467650"

# Space-separated list of target nodes that should stay connected.

TARGET_NODES="1977 49355"

# Connection prefix:

# *3 = transceive connect

# *2 = monitor connect

CONNECT_PREFIX="*3"

# Wait this many seconds after issuing each reconnect command.

RECONNECT_DELAY_SECONDS="2"

# Set to "yes" for extra terminal output when run manually.

# Set to "no" if you want quieter cron logs.

VERBOSE="yes"

# Full path to the Asterisk binary.

ASTERISK_BIN="/usr/sbin/asterisk"

 

If you setup everything correctly and rebooted your Raspberry Pi your selected nodes should now automatically connect to each other. (See image below)

 

(Click on image for larger view.) 

 

Onto the installation of DVSwitch on the Raspberry PI.

 

Go to the Cockpit

Select Terminal (Click on it)

At the prompt enter:

sudo su -  [Enter]

root@asl3:~#

You now have root access. 

 

Let's install DVSwitch:

 

At the prompt type:

wget dvswitch.org/bookworm [enter]

chmod +x bookworm [enter]

. /bookworm [enter]

apt update [enter]

apt install dvswitch-server [enter]

When DVSwitch server is finished installed reboot the Pi

sudo reboot now [enter]

 

We are going to leave DVSwitch as is - no setup - as we will only use the Analog_Bridge folder where we will install a few other firmware files.  Amongst the files will be the mumble_bridge.py (Python) script file.

 

Time now to install Pymumble  

 

To install pymumble on a Raspberry Pi, you need to install its system dependencies first, followed by the Python package itself.

1. Update Your System

Ensure your Raspberry Pi packages are up to date. 

    • Open your terminal.
    • Run: sudo apt update
    • Run: sudo apt upgrade -y

2. Install System Dependencies

pymumble relies on Opus audio codecs and specialized development libraries.

    • Run: sudo apt install python3-dev libopus-dev gcc -y

3. Install pymumble

 
Use pip to install the package. Depending on your OS version, you may need to use a virtual environment.

Option A: Using a Virtual Environment (Recommended for Raspberry Pi OS Bookworm and newer) 

    • Create a environment: python3 -m venv myenv
    • Activate it: source myenv/bin/activate
    • Install the library: pip install pymumble

Option B: System-wide Installation 

 

    • Run: pip3 install pymumble 

4. Verify the Installation

Check that the library imports correctly.

    • Run: python3 -c "import pymumble; print(pymumble.__version__)"
    • If no error appears, the installation was successful. 

Time now to install Pymumble 

Image:  See the ZS1I_467650_Bot  (Click on image for larger view.)

Pymumble is an open-source library that allows you to build custom clients and automated bots for Mumble, a popular privacy-focused, self-hosted voice chat server. Written in Python, it acts as a programmatic interface to connect, speak, listen, and manage server channels.   You will notice on the image above that I opted to use an automated bot for Mumble.  I called it the ZS1I_467650_Bot.  The ZS1I_467650_Bot will automatically connect to the Mumble Server.

Key Features of Pymumble

• Audio Streaming: It allows developers to stream audio directly into Mumble channels (e.g., custom music or soundboard bots) and record incoming audio streams. 

• Event Callbacks: The library triggers events based on server activity, such as when a user connects, disconnects, speaks, or creates a channel. 

• Server Management: It functions as an automated administrative tool to move users, mute/deafen, or send text messages programmatically. 

Common Use Cases

•  Music Bots: Frequently used to create dedicated audio bots (often playing stereo or high-fidelity streams) that provide music in Mumble voice channels. 

• Recording Bots: Used for writing custom scripts to record conversations and save speech data. 

• Amateur Radio Bots: In amateur radio, Pymumble is primarily used to bridge the gap between traditional radio frequencies (RF) and internet-based Voice over IP (VoIP) networks. Radio Amateurs leverage Mumble because its open-source, ultra-low latency Opus audio codec preserves signal clarity—making it a popular tool for building custom gateways, internet links, and remote station controllers.

Getting Started

The library is available and actively maintained across multiple active forks, such as the Azlux Pymumble GitHub Repository and the reworked Sourcehut Pymumble Library.

Note:  I used Option B to install pymumble and it worked first time around.

 

Image:  Mumble_Bridge.py in Thonny Python IDE

Installation of the Mumble_Bridge.py script file 

It is now time to install the Mumble_Bridge.py script file that was created in collaboration with AI.  The script file will be installed in the Analog_Bridge directory located at $ /opt/Analog_Bridge.  Name of the file = mumble_bridge.py (6.6kb Python file dated 8 June 2026 18:38:09) Copy this script file to the Analog Bridge folder using FileZilla or the Terminal. ( $ /opt/Analog_Bridge/Mumble_Bridge.py)

Please take note of the following relating to the Mumble_Bridge.py script:

Open Source Sharing (License File)

 

Copyright (c) 2026 Johan ZS1I and Artificial Intelligence (AI)

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including the rights to use, copy, 
modify, merge, and publish copies of the Software, subject to the following 
conditions:

1. The Software is NOT to be sub-licensed or sold in copies for commercial 
   purposes under any circumstances.
2. Any distributed or modified versions of this Software must retain the 
   above copyright notice, this list of conditions, and this disclaimer.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON INFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN  CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

Mumble_Bridge.py script file can be downloaded by clicking HERE.

Time to install the tcpdump network packet analysis utility program

 

You might not need this firmware but if you run into audio packet issues then this software will assist you in solving the issues.  This firmware  needs to be installed on the Raspberry Pi 4.

 

Always a good thing to reboot your Raspberry Pi after the installation of firmware.  Reboot now.

 

 

Image: Mumble Client

Install the following firmware on the PC that will host your Mumble Client and Server.  

 

I use a Dell Optiplex PC running Linux Mint 22.3 for this purpose. 

 

1.  Install the Mumble Client (PC) version.  This is your main control program where you will see all the clients, channels, servers and bots.  Mumble uses a client-server architecture which allows users to talk to each other via the same server.

 

In the Terminal window run the following commands:

 

sudo apt update && sudo apt install mumble -y 

 

Image:  Mumble Server 

 

2.  Install the Mumble Server.  Also called Murmur.  Murmur is the VoIP server component for Mumble.  Murmur is installed in a system-wide fashion, but can also be run by individual users.  Each Murmur process supports multiple virtual servers, each with their own user base and channel list. 

 

In the Terminal window run the following commands:

 

sudo apt update && sudo apt install mumble-server -y 

 

After installation reboot the PC:  sudo reboot now 

We are nearly finish installing all the firmware needed.  The final firmware installation will be done on your mobile phone.  I use an Oppo phone which runs Android.  Here is how I installed the Mumble Client.

Image:  Plumble Phone Client 

Plumble Free Ver 3.2.0 nowadays called Mumla - Mumble VoIP can be downloaded from the Google PlayStore

Note:  I would advise that the Mumble PC Client and the Murmur (Mumble) Server be installed completely separate from ASL3 / DVSwitch/Mumble_Bridge on the Raspberry Pi 4.  I found that the performance is just better and faster and there is no clashing/fighting between the firmware.

Enough for now.  In Part 4 we will be looking at the setup and configuration of all the firmware to ensure clean, crisp, good audio between all the network connections.  

Important Notification: New Annual Verification process by RadioID.net

The ID numbers used for DMR and other amateur radio digital networks are a finite resource. Due to the growing popularity of these modes, along with some users requiring multiple IDs, certain regions are expected to face ID shortages in the near future.

To help ensure that available IDs are being used efficiently, the organization in charge of maintaining the ID database will periodically verify that currently assigned IDs are still needed and that the information associated with them remains accurate.

Beginning July 1, 2026, RadioID.net will implement an annual verification process. On the anniversary of each account’s creation, it will send an email to the account holder requesting confirmation that the assigned ID(s) are still needed and that the the account information remains accurate and up to date.

If no confirmation is received, the associated ID(s) will be temporarily deactivated. If RadioID.net is unable to obtain a response after a reasonable period, the ID(s) will be removed from the database and made available for reassignment.

This process is intended to preserve the long-term availability of ID numbers and maintain an accurate database for the amateur radio community.

If you have any questions or concerns regarding this process, please contact RadioID through their support page. 

Mossel Bay DMR Repeater back on the air after structural upgrading and modifications!!

Image:  Mossel Bay DMR Repeater (Click on image for larger view.)

The Mossel Bay DMR Repeater is back on the air after comprehensive structural upgrades and modifications.  The cooling issue was solved by adding a second fan to the transmitter of the repeater.  This fan runs continuously and will keep the transmitter cool.  The second fan also for the transmitter will start when the temperature reach more than 50 Degrees Celsius and will increase in speed as the temperature rises.  I am sure this will keep the transmitter cool even on the hottest of days.

Higher rubber feet (4) was added to the bottom of the repeater to allow for better airflow in the repeater cabinet.  I also added two aluminum carry handles.  But why carry handles?  In the shack the handles come in handy if you want to work on the repeater of move it to another area of the shack.  The repeater was constructed to be installed in a 19 inch rack but in its current location there is no space for a 19 inch rack.  

I have a few other minor alterations that I would like to make in the future.  More on this in a future article.

(Click on image for larger view.) 

Herewith more information regarding the repeater:

Digital Mobile Radio (DMR) Repeater

DMR Repeater Talkgroup 65522:   This repeater is NOT located on a remote site which requires a separate license.  This allows ZS1I to monitor and control the repeater while it is on the air.  

Mossel Bay DMR Repeater Information:

Mode: DMR
Band:  70cm
TX Frequency:  438.262500 Mhz
RX Frequency:  430.662500 Mhz
Radio Mode:  Duplex
Talk Group (TG): 65522
Colour Code:  1 or 2
Time Slot:  1  

This repeater is linked to the ZS1I AllStar Hub Network (Node 49355) (Analog Repeaters / Simplex Link Radio / Echolink / SVXLink / AllStar / South Cape Reflector) via the ZS1I DMR Bridge and Repeater.

DMR Bridge:

DMR Talkgroup 65522: Through digital bridging software (such as DVSwitch), the hub connects directly to DMR Repeater Talkgroup 65522. This allows digital radio operators on the BrandMeister or South African DMR networks to converse natively with analog FM operators.  

Finally:  Thank you to those who support and use the ZS1I HUB Network, Mossel Bay regularly. 

Please use the ZS1I HUB Network.  Transmit - let radio amateurs know you are there.  Start or answer a "QSO" and make new friends.

NEVER FEAR THAT YOU ARE "TYING UP THE NETWORK SYSTEM" - IT IS THERE TO BE USED.   

Let's try to kill the silent Amateur Radio Killer out there!! (Part 2)

(Click on image for larger view.)

In Part 1 we looked at the first "killer" in this series named the Internet Outage Killer.   Article available HERE.

Many of you would say use real amateur radio radio's and you will not have to deal with silent amateur radio killers.  With all do respect it is not about real radios.  I use what I have available and that will serve the purpose that I have intended for it.  In other words I use the communications medium for a specific reason and purpose.  It is definitely not a hard and fast rule.  I use old valve tech to the newest surface technology, VoIP, Digital Voice modes etc. whenever I feel like using at the time. 

Now in this article I will be looking at the next silent Amateur Radio Killer out there.  In short, the dreaded Server Killer - A "server killer" most commonly refers to a cyberattack or malicious script designed to crash, overload, or disable a network server (such as a DDoS attack). Depending on the context, it can also refer to malware targeting system security.

I am referring to the concept of "Internet Dependence" or "Server Centralization," which many operators call the silent amateur radio killer.

While modes like DMR, D-STAR, and Yaesu System Fusion (C4FM) offer crystal-clear digital voice, they heavily rely on internet-connected master servers and network bridges (like BrandMeister, EvoHam servers, or Reflectors) to route audio globally. When these external servers go down, the internet infrastructure drops, or an emergency grid failure occurs, the radios immediately fall dead and silent—defeating the off-grid, self-reliant purpose of amateur radio. 

---

Why Centralized Servers are Considered a "Silent Killer"

• The "Brick" Effect: If a master server or local gateway goes offline, your expensive digital radio cannot connect to talk-groups, leaving you completely cut off from the network. 
• No Warning Signs: Unlike analog radio, where static creeps in to warn you of a weak signal or a failing repeater, digital voice gives no warning. It works perfectly until it instantly drops into absolute silence. 
• Single Points of Failure: Centralized network servers handle routing IDs and call-signs. If hackers target these servers or the host data centers experience outages, entire networks go down globally. 
• Loss of the "Radio Art": Critics argue that routing 99% of a voice conversation over the commercial internet via "hot-spots" turns a radio into nothing more than an expensive, glorified VoIP microphone. 

Direct Comparison of Vulnerability

Digital Voice Mode	Primary Server/Network Infrastructure	Vulnerability to Internet/Server Outage
DMR (Digital Mobile Radio)	BrandMeister, TGIF, IPSC2 Master Servers	High; local hot-spots and linked repeaters fail if servers drop.
D-STAR	Gateway Servers, REF/XRF/DCS Reflectors	High; call-sign routing and global linking cease without the internet.
System Fusion (C4FM)	Yaesu Wires-X Servers	High; rooms and internet node linking go offline completely.
FreeDV (Open Source HF)	None (Pure Over-The-Air HF)	Zero; completely independent of servers for voice traffic.

The True Off-Grid Alternatives

To combat this vulnerability, many hams are moving away from server-dependent commercial protocols and returning to true decentralized RF infrastructure:

• FreeDV: An open-source digital voice protocol designed for HF (shortwave) bands. It does not use any central internet routing; voice is encoded, sent over the air via standard SSB radios, and decoded directly on the receiving side. If the internet dies, FreeDV keeps working. 
• M17 Project: A completely open-source, non-proprietary VHF/UHF digital voice protocol developed specifically to break away from commercial, server-reliant restrictions. 
• Digital Simplex / Local Repeater Modes: Using DMR or Fusion in "simplex" (radio-to-radio) mode removes the internet entirely, relying strictly on direct line-of-sight RF range. 

Is moving away from server-dependence the true Off Grid Alternative or would running your own server from home not be the better alternative?

Running your own server at home creates a personal private network, but it does not create a true off-grid alternative. If your home internet or power goes down, your network still collapses. 

Moving away from servers completely (pure over-the-air RF) and running a private home server serve two completely different goals.

Why a Home Server is Not True "Off-Grid"

• Dependency on Internet ISPs: If you run a DMR or AllStar Asterisk server at home, you still rely on your internet service provider to route traffic to your fellow radio amateurs  houses.
• Power Grid Vulnerability: A home server requires constant power. If a storm knocks out the local grid, you need substantial backup batteries or generators to keep it running. 
• Public IP Changes: Home internet connections usually have dynamic IP addresses, which can change and break connection links unless you manage complex Dynamic DNS settings. 

The Benefits of Running Your Own Server

While it is not off-grid, hosting your own server (like a Private BrandMeister Master, a XLX D-STAR Reflector, or an AllStar Link Node) offers massive advantages: 

• Complete Privacy: You control who connects to your talk-groups or rooms, away from public network moderators.
• Immunity to Global Outages: If the main worldwide servers get hacked or experience a data center outage, your private network remains completely untouched.
• Custom Configuration: You can build unique talk-group structures and automated scripts tailored exactly to your local radio club. 

The Ultimate Hybrid: Mesh Networking

If you want the power of a server but the independence of true off-grid radio, the best alternative is Amateur Radio Emergency Data Network (AREDN). I have propagated the use of AREDN all along (since the early 2000's) as this will serve you well when the commercial server killer (commercial server outage) strikes as long as you have back-up power to run the equipment on.

• Off-Grid Internet: Radio amateurs use modified commercial Wi-Fi routers to create an independent, high-speed microwave data network.
• Local Servers: You can run a server at your house, and other hams can connect to it over the air without using the commercial internet at all. 

---

During a recent Severe Weather event in the Southern Cape we experienced power and internet outages which resulted in the following servers being off-line during this event:

• BrandMeister Master South Africa
• Echolink Servers (All over the world)
• AllStarLink Servers (All over the world)

These outages did not only effected the Southern Cape but also other parts of South Africa.  On a local level the outage did not kill the local DMR Digital Repeater as well as the ZS1I AllStarLink HUB Network in the Mossel Bay area as AREDN provided the server and backup for these systems to operate locally.  Echolink was completely off the air for the duration of the event as it needs the Internet to function.   In Part 1 I mentioned the use of Starlink if it was available but as mentioned supra we all know by now that Starlink in South Africa will not be implemented under the current dispensation unless a miracle happen.  Be as it may we as radio amateurs cannot sit and wait for that day to arrive .  We need to look at alternatives and in Part 1 I also discussed the alternatives.

I would like to encourage my fellow radio amateurs to look at AREDN but also to look into hosting your own server locally in the Shack. (like a Private BrandMeister Master, a XLX D-STAR Reflector, or an AllStar Link Node)  Some might be of the opinion that power- and internet outages do not last for weeks or months and to wait for a while will not hurt anybody or I will use my local analog repeater or HF Radio etc. if there is a need to communicate.  

I respect your opinion but would it not be great to have alternatives available and I am not even talking about the opportunities here to learn and experiment to find alternative that work great.  My whole life I tried not to be dependent on others.  I try to be self sufficient as far as possible but also in the amateur radio hobby.  So far I achieved what I wanted to do but there is ample work to be done in killing this amateur radio killer aka "Server Killer".

In a future posting I will be looking at other methods to "replace dead servers" which will allow me and hopefully others to communicate locally when servers go down.  At least the equipment that depend on the Internet will not be useless in times of need.  In the Afrikaans language we have a saying " 'n Boer maak 'n plan!".  We need different plans / alternatives and the more the merrier.  I made a few plans!  Lookout for Part 3 coming soon.

Finally:  Do you have a back-up plan for your digital voice radios should servers or the internet fails.  If you have a solution or ideas then tell us about it.  Send your comments to the following Email.

New AllStarLink3 - Mumble Bridge (Additions / Extensions) to the ZS1I HUB Network in Mossel Bay (Part 2)

When working or setting up any amateur radio addition or extension, I believe to do it in a structured manner.  I have therefor compiled a list of the sequence on how I installed all the firmware needed for the AllStarLink3 (ASL3) / Mumble Bridge.  I have said it before that articles on this Blog is not to brag or boast and therefor it is also used as a "library" or reference / storage facility should I want to revert back to a project I undertook.

I need to inform readers that this listed method worked for me and the equipment I used.  I can therefor not guarantee that it will work for your setup. 

Herewith the sequence list:

Install the following firmware on the Raspberry Pi 4 

1.  Use a new clean SD Card to write the firmware on.  I only use SanDisk Ultra Class 10 cards in all of my projects.  Never had a card fail on me.

2.  Write AllStarLink3 (ASL3) Bookworm firmware to the SD Card using Raspberry Pi Imager.

3.  Install and run ASL3 Raspberry Pi.  I use a Raspberry Pi 4 Model B Rev 1.5 4 Gig Ram.  I am sure one can run the firmware of a Raspberry Pi Zero 2 W.  I opted to install the Mumble Server  and Mumble Client on one of my Dell Optiplex PC's.

4.  Setup a Public Node using the asl-menu command.  In my instance the public node number is 467650.

5.  Setup a Private Node using the asl-menu command.  In my instance the private node number is 1977. 

For assistance on how to setup the above two nodes and DVSwitch, do a search on Youtube for videos by Ham Radio Crusader.  Link:  https://www.youtube.com/@HamRadioCrusader  

6.  Connect the following 3 x Nodes permanently together:  467650, 1977 and 49355 (ZS1I Hub Node)  I used a script to connect all three nodes together permanently.  

7.  Install the ASL3 Check Connection Script to connect the above three nodes permanently together.

8.  Install DVSwitch on the Raspberry Pi.  No setup needed. I used the Analog_Bridge folder to store the bridge files and firmware.  When you install DVSwitch the Analog_Bridge directory will be amongst other directories that were installed in "/ " under the opt directory.  $ /opt/Analog_Bridge  This is the directory I used to work out and run the mumble_bridge.py script.

9.  Install pymumble on the Raspberry Pi.  I used the system wide installation.  Run:  $ pip3 install pymumble from the cursor in the /home/pi main root directory.

10.  It is now time to install the AI created Mumble_Bridge.py script file in the Analog_Bridge directory.  Name of file = mumble_bridge.py (6.6 kb python file 8 June 2026 18:38:09)  Copy this file to the Analog_Bridge folder using FileZilla.

11.  Install the tcpdump network packet analysis utility program.  This program will assist you if you have any audio packet issues.

Install the following firmware on the Dell Optiplex PC running Linux Mint 22.3

1.  Install the Mumble Client (PC) version.  This is your main control program where you will see all the clients, channels, servers etc.  Mumble uses a client–server architecture which allows users to talk to each other via the same server.

2.  Install the Mumble Server. Also called Murmur.  Murmur is the VoIP server component for Mumble. Murmur is installed in a system-wide fashion, but can also be run by individual users. Each murmur process supports multiple virtual servers, each with their own user base and channel list.

Installed the following application on my Oppo Phone

Plumble Free Ver 3.2.0 nowadays called Mumla - Mumble VoIP and available via PlayStore. 

Note:  I would advise that the Mumble PC Client and the Murmur (Mumble) Server be installed completely separate from ASL3 / DVSwitch/Mumble_Bridge on the Raspberry Pi.  I found that the performance is just better and faster and here is no clashing/fighting between the firmware.