OK here goes....
So I went back over my work, and back over the DMRGateway WiKi and I had totally mis-understood part of the functionality... oops, so if you read my rules and thought I was nuts, you were probably correct.
This ruleset seems to work pretty good (and does not require modification for duplex and simplex hotspots...
Code: Select all
[DMR Network 2]
What to the re-writes do;
We swap TG8 on your hotspot to be TG9 on the network, this is mostly for the Reflectors;
TG 505 should be on TS1 (on the network side) when you are a Repeater or running a Duplex hat (more on this later - stick with me).
Everything from 800-899 should end up on TS2 (on the network side).
3801-3808 should end up on TS2 (on the network side).
Parrot needs to be on TS 2 only on the network side.
Catch-all rule, so anything not matched by the above rules is sent to the network on TS1 (again more on this in a moment).
2nd Catch all rule to match anything we missed above and send it to TS2 (on the network) - the sharp eyed among you will notice that this rule should *NEVER* get a hit, since the one above will be hit first - yes I agree, but again, stick with me
Catch the Private calls used for Reflectors.
OK so thats the explanation, now back to that werird pair of rules that made no sense;
This looks crazy, and it is a little, but in the very best ways
IPSC2+ knows if you connect simplex or duplex, if you connect simplex, it sends the traffic back on TS 2, always - very handy, if you connect duplex it sends it back on either TS1 or TS2 depending on where that TalkGroup should live and where it is being used. The most important thing, and the bit that caught me out because I was not awake, is that these same rules are matched in BOTH directions, so when you write the outbound call from your HT on 80320 (TS2) for example, it is sent to the network as 320 on TS1... Great, now the SAME rule is matched in reverse when the traffic comes back for TG 320 on TS1 form the network - and that all works as expected on duplex boards / repeaters... however...
When you connect a simplex board, the network side helps you out by sending everything back on TS2, and none of the rules were triggered and so it all went into a black hole.... here is where the 2nd rule comes in, that DOES match the traffic now coming back on TS2, and correctly re-writes it back to 80320 TS2 for your radio.
I really made that look hard, but thanks for sticking with it
this is why I need your help testing my moderately nutty ideas
I have already updated all my posts in this thread with the new rule-set - give it a shot pls.