BrandMeisterIMRS
Starting BrandMeister release 20190331-203539 has support of directly-connected IMRS repeaters (Yaesu DR2X).
This allows direct communications between DMR talking groups and SystemFusion radio via IMRS repeater without using any additional hardware (unlike WIRES-X) and with audio quality 1:1. As it is with WIRES-X or YSF bridges, a SystemFusion radio may transmit in DN or VW mode.
Contents
Benefits
- Fully transparent calls between DMR and SystemFusion
- Full call signaling support in both directions
- Sound quality is 1:1 in both directions
- No extra hardware is required(*)
- SystemFusion side doesn’t loose any features
- Subscription to multiple talking groups for each IMRS repeater (thanks SystemFusion II)
Conceptual view
Limitations
- Each connected repeater should have unique public IP (limitation of IMRS)
- Due to technological specific up to 99 DG-IDs can be mapped on per master-basis, that means each BM server can bridge up to 99 DG-IDs
Allocated ports
- UDP 21110
Configuration
// SystemFusionII Repeater with LAN Adapter (IMRS)
FusionRepeater :
{
// UDP Port
port = 21110;
// Call of local "repeater"
call = "CALLSIGN";
// DP-ID of local "repeater"
serial = "xxxxx";
// IMRS TOT Timer (seconds)
interval = 60;
// Subscriptions to groups
subscriptions =
[
// <DG-ID>, <Group ID>
1, 2501,
2, 9504
];
};
Issues with connectivity
DMR radio (and Last Heard) shows talking group number instead ID of operator
- Operator has not registered his call-sign in CCS7 registration system - ask him to register
- CRC check failed during processing of SystemFusion
BrandMeister log entries
When a Fusion Repeater Successfully connects BrandMeister Server
New regular connection of Fusion Repeater (xx.xxx.xxx.xx)
When a session begins from the Fusion Repeater to BrandMeister.
New session a5dcb300-09b6-4fad-8a15-6b0ba61c9f6b of Fusion Repeater system 0 at slot 0 Forwarding System Fusion II call xxxxxxxx (CALLSIGN) to DMR group xxxxx (DG-ID xx)
When a Connection from a fusion repeater connects to BrandMeister and or resets a connection.
Connection of Fusion Repeater system 0 (xx.xxx.xxx.xx) expired Connection of Fusion Repeater system 0 (xx.xxx.xxx.xx) removed New regular connection of Fusion Repeater (xx.xxx.xxx.xx)
When a call is originates from BM to Fusion. At this point this is generic but does show activity going is going to the Fusion Repeater.
Added route to Fusion Repeater system 0 at slot 0 (locked) by Fusion Registry