(Multiple Instances)
(Multiple Instances)
Line 24: Line 24:
 
=== Multiple Instances ===
 
=== Multiple Instances ===
  
Technically BrandMeister Core loads configuration files from /opt/BrandMeister/Instances/. Each .conf file (in libconfig format) or folder (containing set of .json files) corresponds to each BrandMeister Core instance.
+
Technically BrandMeister Core loads configuration files from /opt/BrandMeister/Instances/. Each .conf file (in libconfig format) or folder (containing set of .json files) corresponds to each BrandMeister Core instance. You can read more information about that at [BrandMeister Server Clustering].
  
 
If you need to create a second instance (or whatever else) of BrandMeister Core you have to create corresponding configuration and register it by call <i>/opt/BrandMeister/setup.sh install</i>.
 
If you need to create a second instance (or whatever else) of BrandMeister Core you have to create corresponding configuration and register it by call <i>/opt/BrandMeister/setup.sh install</i>.

Revision as of 22:28, 15 April 2021

General information

BrandMeister Core supports multiple configuration formats:

JSON (default)

  • Sample Configuration File: /opt/BrandMeister/BrandMeister.sample.json
  • Configuration File: /opt/BrandMeister/BrandMeister.json

LibConfig (old)

  • Sample Configuration File: /opt/BrandMeister/BrandMeister.sample.conf
  • Configuration File: /opt/BrandMeister/BrandMeister.conf

Consul KV

  1. // contents of /opt/BrandMeister/BrandMeister.json
  2. {
  3. "configuration" : "http://127.0.0.1:8500/v1/kv/bm/2842",
  4. "token" : "86bc3216-8751-7bca-57bc-e949981d9130" // optional token if ACLs enabled
  5. }

Multiple Instances

Technically BrandMeister Core loads configuration files from /opt/BrandMeister/Instances/. Each .conf file (in libconfig format) or folder (containing set of .json files) corresponds to each BrandMeister Core instance. You can read more information about that at [BrandMeister Server Clustering].

If you need to create a second instance (or whatever else) of BrandMeister Core you have to create corresponding configuration and register it by call /opt/BrandMeister/setup.sh install.

Script automatically creates symlinks to default configuration files /opt/BrandMeister/BrandMeister.json or /opt/BrandMeister/BrandMeister.conf

Local Configuration

Configuration file location : /opt/BrandMeister/Data

bridge.json

Allows you to establish links with other networks

  1. {
  2. // Syntax:
  3. // <Group ID> : [ { "network" : <Network ID>, "slot" : <Slot Number> }, ... ]
  4.  
  5. // Please see details and examples at our wiki:
  6. // https://bm.pd0zry.nl/index.php/Network_Bridging
  7.  
  8. // Bridged groups for CBridge2228
  9. // 3182  : [ { "network" : 2228, "slot" : 0 } ], // DCI-FU-3182
  10. // 8952  : [ { "network" : 2228, "slot" : 0 } ], // DCI-iCall
  11. // 3100  : [ { "network" : 2228, "slot" : 0 } ], // DMRX-3100
  12. // 3777215 : [ { "network" : 2228, "slot" : 0 } ], // DMRX-Comm1-3777215
  13. // 3777216 : [ { "network" : 2228, "slot" : 0 } ], // DMRX-Comm1-3777216
  14. // 8951  : [ { "network" : 2228, "slot" : 0 } ], // DMRX-TAC1-8951
  15. // 9310  : [ { "network" : 2228, "slot" : 0 } ], // DMRX-TAC310
  16. // 9311  : [ { "network" : 2228, "slot" : 0 } ], // DMRX-TAC311
  17. // 9312  : [ { "network" : 2228, "slot" : 0 } ], // DMRX-TAC312
  18. // 1776  : [ { "network" : 2228, "slot" : 0 } ] // MIT-1776
  19. }

generic.json

Sets the general configuration for Generic.lua

  1. {
  2. // General configuration for Generic.lua
  3. "AutomaticRouting" :
  4. {
  5. "Mode" : "None", // possible values: "National", "NationalOnly", "Regional", "None"
  6. "Slot" : 1
  7. },
  8. "CallEnrichment" :
  9. {
  10. "TalkerAlias" : true,
  11. "ConfirmedCall" : true
  12. },
  13. "Timers" :
  14. {
  15. "HandOff" : 15,
  16. "OnDemand" : 600
  17. }
  18. }
  19.  
  20. // Automatic Routing Modes
  21. // NationalOnly: route the talkgroup that matches the first 3 digits of the repeater ID
  22. // National: Do NationalOnly + talkgroup matching first 4 digits of the repeater ID
  23. // Regional: Do only talkgroup with first 4 digits of the repeater ID
  24. // None: Do nothing automatic

round.json

Settings for the weekly CQWW Round every saturday evening on TG91

  1. {
  2. "WWCQ" :
  3. {
  4. "Mode" : "By-Default", // possible values: "Disabled", "By-Default" and "On-Demand"
  5. "Slot" : 1 // Slot for mode "By-Default"
  6. }
  7. }

General information[edit]

BrandMeister Core supports multiple configuration formats:

JSON (default)

LibConfig (old)

Consul KV

  1. // contents of /opt/BrandMeister/BrandMeister.json
  2. {
  3. "configuration" : "http://127.0.0.1:8500/v1/kv/bm/2842",
  4. "token" : "86bc3216-8751-7bca-57bc-e949981d9130" // optional token if ACLs enabled
  5. }

Multiple Instances[edit]

Technically BrandMeister Core loads configuration files from /opt/BrandMeister/Instances/. Each .conf file (in libconfig format) or folder (containing set of .json files) corresponds to each BrandMeister Core instance. You can read more information about that at [BrandMeister Server Clustering].

If you need to create a second instance (or whatever else) of BrandMeister Core you have to create corresponding configuration and register it by call /opt/BrandMeister/setup.sh install.

Script automatically creates symlinks to default configuration files /opt/BrandMeister/BrandMeister.json or /opt/BrandMeister/BrandMeister.conf

Local Configuration[edit]

Configuration file location : /opt/BrandMeister/Data

bridge.json[edit]

Allows you to establish links with other networks

  1. {
  2. // Syntax:
  3. // <Group ID> : [ { "network" : <Network ID>, "slot" : <Slot Number> }, ... ]
  4.  
  5. // Please see details and examples at our wiki:
  6. // https://bm.pd0zry.nl/index.php/Network_Bridging
  7.  
  8. // Bridged groups for CBridge2228
  9. // 3182  : [ { "network" : 2228, "slot" : 0 } ], // DCI-FU-3182
  10. // 8952  : [ { "network" : 2228, "slot" : 0 } ], // DCI-iCall
  11. // 3100  : [ { "network" : 2228, "slot" : 0 } ], // DMRX-3100
  12. // 3777215 : [ { "network" : 2228, "slot" : 0 } ], // DMRX-Comm1-3777215
  13. // 3777216 : [ { "network" : 2228, "slot" : 0 } ], // DMRX-Comm1-3777216
  14. // 8951  : [ { "network" : 2228, "slot" : 0 } ], // DMRX-TAC1-8951
  15. // 9310  : [ { "network" : 2228, "slot" : 0 } ], // DMRX-TAC310
  16. // 9311  : [ { "network" : 2228, "slot" : 0 } ], // DMRX-TAC311
  17. // 9312  : [ { "network" : 2228, "slot" : 0 } ], // DMRX-TAC312
  18. // 1776  : [ { "network" : 2228, "slot" : 0 } ] // MIT-1776
  19. }

generic.json[edit]

Sets the general configuration for Generic.lua

  1. {
  2. // General configuration for Generic.lua
  3. "AutomaticRouting" :
  4. {
  5. "Mode" : "None", // possible values: "National", "NationalOnly", "Regional", "None"
  6. "Slot" : 1
  7. },
  8. "CallEnrichment" :
  9. {
  10. "TalkerAlias" : true,
  11. "ConfirmedCall" : true
  12. },
  13. "Timers" :
  14. {
  15. "HandOff" : 15,
  16. "OnDemand" : 600
  17. }
  18. }
  19.  
  20. // Automatic Routing Modes
  21. // NationalOnly: route the talkgroup that matches the first 3 digits of the repeater ID
  22. // National: Do NationalOnly + talkgroup matching first 4 digits of the repeater ID
  23. // Regional: Do only talkgroup with first 4 digits of the repeater ID
  24. // None: Do nothing automatic

round.json[edit]

Settings for the weekly CQWW Round every saturday evening on TG91

  1. {
  2. "WWCQ" :
  3. {
  4. "Mode" : "By-Default", // possible values: "Disabled", "By-Default" and "On-Demand"
  5. "Slot" : 1 // Slot for mode "By-Default"
  6. }
  7. }