search

juribeparada / MMDVM_CM

Cross-mode conversion tools for MMDVM software
43 stars 53 forks source link

Block specific YSF ID #26

Open w2jdm opened 5 years ago

w2jdm commented 5 years ago

Any chance there is a way to block a user if the YSF ID is "openSPOT"? These things key up each time someone else talks, so what is happening is the bridge hits the Brandmeister timer and gets blocked due to too many transmissions in a short period of time. Just blocking this one YSF ID would solve 99% of the problem.

juribeparada commented 5 years ago

Please update to the latest version of YSF2DMR. Last PR https://github.com/juribeparada/MMDVM_CM/pull/25 should implement that, using DropUnknown=1 in [DMR Id Lookup].

w2jdm commented 5 years ago

I am running this latest version with the modification and have tried it. To give some perspective on why that will be difficult to utilize is at any given moment, between YSF, FCS, and native Wires X, there are probably close to 400 users connected. When I implement this as a test, it blocks up to 1/3rd of the users. The end result will be conversations occurring on YSF, FCS, and Wires X, that don't bridge across and vice versa, leaving users confused. It will not only block users who legitimately don't have a registered ID, but also users who put their handle in their radios. For example, "W2JDM-Jason" would also get blocked, even though I have a DMR ID. This might also cause significant buffering as the reflector tries to catch up. The sheer number of users makes this option not viable. Which is why I was looking to be more granular in the blocks.

Our pain point is really the OpenSpot when in default configuration. This occurs at least once a day, if not more. Mostly originating from the FCS network. I believe the manufacturer puts this large room I'm bridging as a default connection when they ship it, and for some reason, it will transmit right after someone drops for .7 seconds. When this accumulates after a long-running QSO, BM responds by enabling Parrot back, or a nasty block message as a protective measure. By blocking "openSPOT" YSF ID alone, that will solve 90% of the problems we would ever experience while allowing conversations to bridge properly. Any thoughts or ideas would be appreciated.