View source for Homebrew repeater protocol ← Homebrew repeater protocol

At the moment we have two versions of the Homebrew repeater protocol:
* A version that is specified by DL5DI as the result of discussion between DL5DI, G4KLX and DG1HT
* A version that is implemented by G4KLX with his MMDVMHost software

== Disclaimer ==
This protocol should only be used for connecting repeaters/hotspots with RF directly. To connect networks/applications/terminals/analog/bridges, other protocols exist - please contact the [https://t.me/BRANDMEISTERGENERALSUPPORT dev team] so that a good implementation can be made. We can't give support if the protocol is used for other things than connecting repeaters/hotspots with RF directly.

== G4KLX MMDVMHost version ==

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 ==

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 ===

* Default UDP port is 62030.
* All messages except DMRD are in text form.
* Repeater ID should be presented as a hexadecimal string of 8 characters in length (except DMRD, which is binary).
* Salt and SHA-256 hash of the authentication protocol should be also presented as hexadecimal strings.
* Use salt value as a string when calculating hash value (see attached PHP example code).
* Configuration protocol has 306 bytes in length.
* Interval of PING messages should be in the range 5 - 15 seconds (5 is preferred for most firewalls).
* When the TX and RX frequencies have same value we consider this case as a connected hotspot in DMO mode.
* In case of DMO hotspot or IP client all DMR traffic should be transmitted with unset bit of selected slot.

=== Site Beacon and RSSI (extensions) ===

* Synchronous Site Beacon is very important for passive automatic roaming. We added a special message to the protocol. It should be sent by the server to repeaters. No response is required.
** Message format: <pre>RPTSBKN01234567</pre> Where 01234567 is ID of repeater (hexadecimal string of 8 characters).
* BrandMeister supports handling of RSSI reports:
** Message format: <pre>RPTRSSI01234567:1-120.0</pre> Where
*** 01234567 is ID of repeater (hexadecimal string of 8 characters),
*** :1 is slot number (:0 for DMO channel, :1 and :2 for Slot 1 and Slot 2),
*** -120.0 is RSSI value in dBm.
** There is no acknowledge message.

=== Incoming call interrupt ===

Client could request server to interrupt current incoming call.
* Message format: <pre>RPTINTR01234567:1</pre> Where
** 01234567 is ID of repeater (hexadecimal string of 8 characters),
** :1 is slot number (:0 for DMO channel, :1 and :2 for Slot 1 and Slot 2),
* There is no acknowledge message.

=== Cloud Messaging extension (push notifications) ===

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 ([http://www.drdobbs.com/mobile/power-management-for-mobile-devices/184407880 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 [https://firebase.google.com/docs/cloud-messaging/ Firebase Cloud Messaging] which is a native mechanism for Android devices.

==== Managing connection state ====

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

* Switch connection state to idle. In the idle state the server stops sending any messages to the client via UDP (keep-alive messages are not required).
** Message format: <pre>RPTIDLE01234567-393838907279:bk3RNwTe3H0:CI2k_HHwgIpoDKCIZvvDMExUdFQ3P1...</pre> Where 01234567 is the repeater ID (hexadecimal string of 8 characters) then application token ID (393838907279), deimeter (":") and the last part is the device token. We recommend to send this message several times (i.e. 3 times), and the server will respond with MSTACK
* Switch connection state back to active.<br>
** Message format: <pre>RPTWAKE01234567-393838907279:bk3RNwTe3H0:CI2k_HHwgIpoDKCIZvvDMExUdFQ3P1...</pre> Where 01234567 is the repeater ID (hexadecimal string of 8 characters) then application token ID (393838907279), deimeter (":") and the last part is the device token. Upon success the server will respond with MSTACK.

==== Downstream message ====

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.

<pre>
{
  "data" :
   {
     "type" : "Homebrew Repeater",
     "data" : "010203040506070809..."
   },
   "to" : "bk3RNwTe3H0:CI2k_HHwgIpoDKCIZvvDMExUdFQ3P1..."
}
</pre>

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

==== Application IDs and keys ====

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 <font size="+1">393838907279</font>


=== Examples ===
[[Homebrew/example/php|PHP]]

[[Category:Protocol]]
[[Category:Supported protocol]]