forum.pistar.uk

I have 3 static talkgroups set up on my repeater but there are some users who are managing to use other, random talkgroups and leave them connected. Is there a way to prevent any talkgroups except the ones that I set?

I am using DMR gateway and am connected to Brandmeister and DMR+.

Under the options for DMR+ is where you can prevent users from changing the connected reflector by adding to the end of the line
However this will not alter the use of Brandmeister UA talkgroups. Double check the /etc/mmdvm file to see if there's something that is disabled that looks similar (iirc there isn't)

Sent from my Pixel 4 XL using Tapatalk

M0LMK wrote: ↑Wed Feb 12, 2020 4:33 pm I am using DMR gateway and am connected to Brandmeister and DMR+.

You could edit your talk group rewrite rules, to only include those talk groups that you want. This would prevent any other talk groups from being activated, however this would apply to yourself as well.

VK3HAW wrote: ↑Thu Feb 13, 2020 4:36 am You could edit your talk group rewrite rules, to only include those talk groups that you want. This would prevent any other talk groups from being activated, however this would apply to yourself as well.

Could you give an example entry for me?

Matt - I covered this in my article in my Blog. where I have selected 8000 to be superimposed onto the real talk groups for IPC2.
The point of BrandMeister was that it was an open structure that all talk groups can be available on either slot, but Sysops were the ultimate power in what could be or could not be acceptable. There are WhiteList and BlackList commands for talk groups, but they could be considered against Ham Spirit. If a visitor wanted to call home for example he could on his own home talk group without recourse to your fixed groups, or join with the current 2350 2351 2352 regime, provided he cut the transmission with a burst if TG4000 at the end, dropping all dynamic calls to that slot.
The Uk has elected to use TG 2350 as the national centre of activity on TS2 the same as the chat channels . , where as most other countries elected to use TS1 like France 208, Belgium 206, Netherlands 204. The UK group 235 is available, and is frequently called by foreign and local stations alike and are rarely responded to, as no one except perhaps me are monitoring. The TGWhiteList= and TGBlackList= would need to go in these paragraphs below in the expert/edit/DMR GW page. Without the gateway activated they would go in the mmdvmhost file, that you would have to edit in nano before you could view them in the expert/mmdvmhost screen.
Tecnically UA groups should drop after 10 minutes if unused. BM should see to that.
Regards, Chris

[DMR Network 1]
Enabled=1
Address=87.117.229.173
Port=62031
TypeRewrite0=2,9990,2,9990
SrcRewrite0=2,4000,2,9,1001
PassAllPC0=1
PassAllTG0=1
PassAllPC1=2
PassAllTG1=2
Password="passw0rd"
Debug=1
Id=#######01
Name=BM_United_Kingdom_2341

[DMR Network 2]
Enabled=1
Address=78.129.135.43
Port=55555
TGRewrite0=1,8001,1,1,998
TGRewrite1=2,8801,2,801,98
TGRewrite2=2,82000,2,2000,7998
PCRewrite0=2,84000,2,4000,1001
Password="PASSWORD"
Debug=1
Id=#######01
Name=DMR+_IPSC2-PhoenixF
Options="StartRef=4400;UserLink=1;TS1_1=235;TS1_2=80;TS1_3=81;TS1_4=82;TS1_5=83;TS1_6=84;TS2_1=860;"

To prevent user access to dynamic TG's in BM network, remove the PASSALL rules and add rules for those TG's you want, eg:

TGRewrite0=2,92,2,92,1001

More good info on talk groups rules:
viewtopic.php?f=5&t=2252&p=11542#p11542

https://github.com/g4klx/DMRGateway/wiki/Rewrite-Rules