Deploying multiple MMDVM server Portals


UPDATE: MMDVM Servers, all but Peter have had their credentials changed.  The log-in setting will no longer be published in our WiKi due to non-members being provided access to our MMDVM servers.  Our servers are a finite resource and loading by non-members is a disservice to our membership. This change is a pain for use by and for our members.  The default password (passw0rd) will no longer be used as a convince.  The new passwords will be complex and different on each server, adding an element of inconvenience to our membership but also to help counter sharing, thanks to one or more of our membership who provided these credentials to non-members. 

To Request Credentials, Email:  Include your name and call and if you are a member of PNW DMR, our page.  Only members of PNW DMR will be provided access to our servers. 

If you receive the new credentials, please to not share them.  Refer anyone, even a person who you know is a member, to our MMDVM server page: (this page).


Bridget was our first MMDVM server portal deployed to access the PNW DMR network directly.  We have since expanded our portals to include other talkgroup decks as well as in-state hosting of our servers by way of a single VM hosting multiple instances of the MMDVM servers.  Our effort now is to perfect and publish this multiplexing approach much the same was we did for W6SS's single instance method.  We are also using to discuss and update or efforts.

The PNW DMR MMDVM project is a package of programs made up by many smart people who have developed the necessary moving parts.  Vance, W6SS created "ipscbuild", which enabled most anyone to be able to deploy the Python programs without major experience with Linux and Python.  The goal has since been to stack up multiple "Bridgets" (MMDVM-IPSC services) onto a single low cost virtual machine provided by a major data center VPS hosting company.  And doing so in a way that the common man can duplicate it with little experience in Linux and Python.

Our multiple use or stacking of instances was created by Dylan KI7SBI with his implementation of Docker for the multiplexing.  Dylan's first Dockerfile is what we call Suzy, which is our MMDVM server tailored for the east side users (of Washington).  We will ultimately publish the scripting and documentation much the same that W6SS has done with his ipscbuild script.

We hope to soon have a MMDVM server on our Full Time Talker manager, which provides 59 talkgroups full time from a palette of either our native PNW talkgroups or 59 talkgroups available via the PNW c-Bridge.

We now have an MMDVM dashboard, authored by Casey KI7TRR.  It is a significant project which has been released but still very much a project in motion.  We intend to add more support and potentially add features similar to DMRX's Dash and the c-Bridge's NetWatch.

All of our work is based on the long time projects on GitHub by Cort, N0MJS and his crew of supporters.  Without their efforts and support of our independent interest in their larger projects, our small contribution would never have gotten lift-off.

This is PNW DMR's current DMR repeater expansion area and many members are using Bridget for lack of repeater coverage while we continue our efforts to bring more repeaters into central and eastern Washington.

We also have a public portal (Peter) available for non-Members. Anyone is free to try it out or just use it to test out their MMDVM Client set-ups.  See our MMDVM Matrix to determine which talkgroups are available via Peter.  We have 2 servers for Peter, one in Bremerton and the other in Spokane.


Server Settings for Peter (PNW's Public MMDVM Server)

SEE: Peter for server details Connector:  HotSpot/MMDVM

Protocol: MMDVM

When setting up your openSPOT, be sure to have the "advanced mode" checkbox checked so that you can enter the server IP and UDP port into the fields and then click Add Server. Do NOT enable "Use DMRplus options". (See: Image 1, Image 2).

If running Pi-Star, you MAY need to open a UDP port in the Pi-Star firewall to run a non-standard port such as is likely here with Bridget. Check out the solution at IO by Stacey KB7YS or read down the page.

Be sure that the "DMRplus options for DMRplus" setting does NOT have the "Use DMRplus options" checkbox checked.


PNW DMR's MMDVM servers are now private for our members use only.  PNW has deployed a public server called Peter for limited use by non-members.

Do NOT release any MMDVM server credentials OTA or otherwise.  Refer members to our Wiki for that information.  Non-members should only have access to Peter which is openly shared on the Web for it's ability to demonstrate our project to interested groups as well as to provide some contact to PNW from the outside on talkgroups that are not otherwise available via Brandmeister.

All portals have DNS addresses available.  Please use them rather than the older IP addresses.  We will be moving the servers around the state and any moves made will be transparent to our users if users use the DNS addresses.

Be sure to put TG 9 in your Rx group for all channels in your Bridget zone for the MMDVM server annunciation.

Be sure not to put your hotSpot on any repeater output or input/output frequency as it likely will result in looping and render the server useless and busy out a timeslot on the c-Bridge.

Typical client devices used on PNW DMR are the "spots"; open, ZUM and Nano or just Google: this for wider MMDVM  information.



We have created a new MMDVM group at DMR  It is for direct support in creating more MMDVM to IPSC "Bridget" servers within a single VM but doesn't include specific details on our PNW DMR member use of our portals.  That support is still provided in our Wiki or other areas within our dmr IO group.

This particular project has been in the works for months but is based on the great work of multiple folks going back 4 years or so.  All software is open-sourced and available on GitHub by Cort, N0MJS and his crew of supporters.  Also kudos to and for the fine assistance of Corey N3FE, one of the USA Brandmeister admins who initially shepherded our efforts at PNW DMR.  Also to Vance, W6SS for being the one who coded the installation script (still used by our Dockerfile) and explained how it worked, which is instrumental to enabling Linux neophytes to be able to install and manage their own MMDVM projects. And finally to Dylan KI7SBI, who put this project inside Dockerfiles to enable multiple MMDVM servers to reside on a single VM.

The partner programs used are:  dmr_utils, dmrlink, hblink and Docker (set-up by KI7SBI)
Running on Debian 8.9/64 at DO SFO as well as well as CoLo'ed machines located in Washington.


Revised: 10/02/2018 07:41