You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to support 3 protocols, and 2 of them will allow supporting DMRGateway
Homebrew protocol (G4KLX 2015, adopted in Brandmeister) - not supported yet
MMDVM protocol 2020 (G4KLX in MMDVMHost Type=Direct and DMRGateway before 8/2020) - supported fully
DMR Gateway protocol (G4KLX in MMDVMHost Type=Gateway and DMRGateway after 8/2020) - not supported yet
So currently, if you want to use Hytera_Homebrew_Bridge with DMRGateway you need to use DMRGateway version before this commit: g4klx/DMRGateway@b344248
The text was updated successfully, but these errors were encountered:
To connect to DMRGateway configure settings.ini section [homebrew] like this
[homebrew]# from which IP:port the connection to MMDVM is made# useful for example for DMRGateway configuration (must match DMRGateway.ini configs RptAddress/RptPort)local_ip = <RptAddress from DMRGateway.ini>
local_port = <RptPort from DMRGateway.ini>
# master ip, port and passwordmaster_ip = 192.168.1.3
master_port = 62031
password = B3S3CURE
I have a Hytera RD-985 repeater and it is working fine with Brandmeister but I also need a bridge to talk to a private server and Brandmeister at the same time. I have only just heard of this system and need all the help I can get is there any documentation on this please.
de Peter GJ8PVL, Jersey. Email: [email protected]
To be more drop-in replacement for gw_hytera_mmdvm we need to support DMRGateway
per discussion at g4klx/DMRGateway#99
We need to support 3 protocols, and 2 of them will allow supporting DMRGateway
Type=Direct
and DMRGateway before 8/2020) - supported fullyType=Gateway
and DMRGateway after 8/2020) - not supported yetSo currently, if you want to use Hytera_Homebrew_Bridge with DMRGateway you need to use DMRGateway version before this commit: g4klx/DMRGateway@b344248
The text was updated successfully, but these errors were encountered: