You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • This page has been protected to prevent editing or other actions.

You can view and copy the source of this page.

Return to Homebrew repeater protocol.

At the moment we have two versions of the Homebrew repeater protocol:

Disclaimer[edit]

Connecting to Brandmeister with the protocols Homebrew and MMDVM Hosts is reserved for repeaters and hotspots with an onboard radio (RF) module.

If you are writing software or building an appliance to connect to Brandmeister without a radio transmitter, you must use a more suitable protocol. Please contact the development team (https://t.me/BRANDMEISTERGENERALSUPPORT) and we will assist you in choosing the best protocol for your application.

If you want to interconnect another amateur radio network with Brandmeister, you must use a bridge protocol. Please post a request on the Brandmeister support platform (https://support.brandmeister.network) for assistance .

If you want to interconnect a non-amateur radio network to BrandMeister, don't.

Do not write software or build appliances without radio impersonating the HomeBrew or MMDVM Host protocols. This configuration might not work with newer versions of BrandMeister and we cannot provide any support for it.

G4KLX MMDVMHost version[edit]

This version of the homebrew repeater protocol is implemented at BrandMeister as "MMDVM Host". The protocol is very close to a version of DL5DI but has some principal changes that are not documented in that specification. Over time, changes introduced have alienated these two protocols.

https://github.com/g4klx/MMDVMHost g4klx/MMDVMHost

Publicly-available version as initially specified by DL5DI[edit]

You can find the spec here: File:DMRplus IPSC Protocol for HB repeater.pdf This version of the homebrew repeater protocol is implemented at BrandMeister as "Homebrew Repeater"

Please note, this specification is not necessarily complete.

Corrections and additions[edit]

Site Beacon and RSSI (extensions)[edit]

Incoming call interrupt[edit]

Client could request server to interrupt current incoming call.

Cloud Messaging extension (push notifications)[edit]

One of the targets of the Homebrew Protocol is mobile devices such as mobile phones. This kind of devices have very strong requirements for power saving (Power Management for Mobile Devices). To make access for these devices more comfortable we added support of a native activation mechanism to Homebrew Protocol. Now we can activate devices via Google's Firebase Cloud Messaging which is a native mechanism for Android devices.

Managing connection state[edit]

To do this, the BrandMeister DMR Server supports the following new messages that may be sent by the client:

Downstream message[edit]

In the connection's idle state the server will send any data such as the headers of any voice calls, data calls, and CSBK (but not voice frames) via Cloud Messaging. Client applications should then go back and switch the connection to an active state to get a stream over UDP.

{
  "data" :
   {
     "type" : "Homebrew Repeater",
     "data" : "010203040506070809..."
   },
   "to" : "bk3RNwTe3H0:CI2k_HHwgIpoDKCIZvvDMExUdFQ3P1..."
}

data/data field contains normal DMRD message of Homebrew Protocol in hexadecimal representation.

Application IDs and keys[edit]

We strongly recommended to use your own application token ID. In that case please provide us your application token ID and authorisation key. Both will be hardcoded in the source code. Default application token ID is 393838907279


Examples[edit]

PHP