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

The action you have requested is limited to users in the group: Users.

You can view and copy the source of this page:

Return to Open DMR Terminal Protocol.


Open DMR Terminal Protocol is a new interface of BrandMeister DMR Server. This link provides light access for IP-based terminals. It's designed to cover many specific requirements such as:

This is incomplete version of specification!

The protocol is based on out Rewind Protocol and very close to our [Simple Application Protocol].

Rewind Protocol[edit]

Rewind is our under-layer protocol required for communication with BrandMeister DMR Server. It is based on UDP. Byte-order is LE.

Note: protocol uses two sequence counters. One for routine messages and another one for real-time data (from REWIND_TYPE_DMR_DATA_BASE to REWIND_TYPE_DMR_AUDIO_FRAME). For real-time data you also should set flag REWIND_FLAG_REAL_TIME_1.

Protocol definition header is now available here

Messages for External Application[edit]

Link establishment[edit]


Keep-alive messages should be sent by client every 5 seconds. struct RewindVersionData should follow after Rewind header.

Server respond to this message with the same type but without content (just header).


Simple message to close connection, has no parameters and confirmations.


There is no special login message, new connection should be established by REWIND_TYPE_KEEP_ALIVE. REWIND_TYPE_CHALLENGE will be send by BrandMeister Server when it detects new connection. The parameter of this message is salt value (please check example bellow).


This message is result of processing message REWIND_TYPE_CHALLENGE by client. The parameter is value of calculation SHA256 hash function (please check example bellow). A result of successful authentication procedure will be empty message REWIND_TYPE_KEEP_ALIVE.

Operational support[edit]


Some kind of debugging extension. This message will be send by BrandMeister Server. Parameter of message is UTF-8 encoded text (please check example bellow).

Call control and subscription management[edit]


Use this message to drop incoming call from the server. Message has no content.


To simplify the process of administration and reduce amount of administrative work an application could make subscription to DMR data by itself immediately after authentication procedure. struct RewindSubscriptionData should follow after Rewind header.

On success BrandMeister Server will respond with REWIND_TYPE_SUBSCRIPTION without content.

You can make several subscriptions for connection. Subscription procedure is optional, all routing stuff can be done by LUA on the server side.


This message cancels subscriptions created by REWIND_TYPE_SUBSCRIPTION.

This message has two options:

On success BrandMeister Server will respond with REWIND_TYPE_CANCELLING without content.



Call transmission[edit]


This is a base number for group of messages:

Both messages may be sent several times at once (2-3 times with same sequence number) to be sure on successful delivery.


This message should contain triple AMBE frames of mode 33. Each of 9 bytes, 27 bytes total.


This message contains value of LC (10 bytes), which can be transferred via embedded signalling during voice call. Suitable to transfer Talker Alias and in-call GPS.

Additional Services[edit]




This message should be sent by terminal to server and should indicate current terminal position (please check struct RewindLocationReport).


This message should be sent by server to terminal to initiate one short or periodical reports (please check struct RewindLocationRequest).

Client Library and Example applications[edit]

Our DigestPlay is supplied with client library that implements transport layer and login procedure.

DigestPlay written in C

Call recorder written in Go