forum.pistar.uk

This for Andy -- Not for General Dissemination

Hi Andy

I think it is time to revise your DMRGateway Overlay as it has been a couple of years and it is no longer viable
ie Network 1
PCRewrite0=2,94000,2,4000,1001
TG 94550 is a talk group on TGIF

Network 2
TGRewrite2=2,80800,2,800,100
Although this range is not currently used on TGIF, these are in a larger range in use on TGIF
ie TG 80795 is used (just outside the range), 80801 to 80899 could get used at any time

Suggestion
Network 1
TGRewrite0=2,1000001,2,1,9999999
PCRewrite0=2,1004000,2,4000,1001
SrcRewrite0=2,1,2,User Callsign,999999
The User Call Sign above directs the PC return directly to the radio regardless of the tg used

or even the following to handle ALL private calls
PCRewrite0=2,1000001,2,1,9999999
SrcRewrite0=2,1,2,User Callsign,999999
I am not a BM user so unaware if this would break anything on BM

Network 2
TGRewrite0=2,1,2,1,9999999
PCRewrite0=2,1000001,2,1,9999999
SrcRewrite0=2,1,2,User Callsign,9999999

The use of the 7 digit network filters 1000000-5000000 are currently in use by a lot of DMRGateway users on TGIF
Some users (myself included) have migrated to 8 digit filters 11000001,12...,13...,14...,15000001 to
access networks 1 to 5

My Network 4 for TGIF Using DMRGateway-4 with Network Filters
[DMR Network 4]
Enabled=1
Name=TGIF_Network
Address=tgif.network
Port=62031
Local=62038
Id=302395444
TGRewrite0=2,14000001,2,1,999999 # on DMRGateway-4 this locks all activity to Net 4
TGRewrite1=2,1,2,1,9999999 # used to access 7 digit talk groups on TGIF after the Net4 lock
PCRewrite0=2,14000001,2,1,9999999
SrcRewrite0=2,1,2,VE3RD,9999999

Private calls to the TGIF parrots on 9990 and 31000 work just fine with this configuration

Just some thoughts
Phil VE3RD
[email protected]

Hi Andy,
I use the overlay for TGIF and found a issue in the way the target TG is displayed in the Pi-star Dashboard. The Target ID is looked up from the 7 digit ID coming from RF, before doing the rewrite rules.

TG programmed in radio: 4040401
TGIF TG: 40401
Prefixed DMR ID 404041 belongs to VU3CTA
Pi-star dashboard displays VU3CTA in the Target field as TG VU3CTA (Both Gateway activity and local RF activity)

I figured out that the dashboard is picking the field from the MMDVM log (below) which is already a callsign. So the dashboard probably cannot do much about the same.
But as a workaround, I can use the prefix 5 for TGIF network. As of now there is no DMR IDs that start with 504, so it would work fine.

This is just a observation and may be considered for the future enhancement.

Thanks,
Bejoy
VU3BOJ

Has anyone made a full update of this since Andy’s original post that they are willing to share?

Keep In Mind when setting rules for the DMRGateway, that the rules are read one at a time starting at Network 1, line by line, and running through to the last Network, last line.

If it finds a match in Network 1 it will ignore all rules that follow in Net 1 and all other networks.

Once a match is found it will process it and no longer read any more rules

This is what I use for a rule set for TGIF Network 4

TGRewrite0=2,14000001,2,1,999999 // All DMR from 14000001 to14999999 = 1 to 999999 and locks in Net 4
TGRewrite1=2,1000001,2,1000001,5599999 // with Net 4 Locked this handles 7 digit talk groups used on TGIF
PCRewrite0=2,14000001,2,1,999999 // This handles all Private calls in the same range
SrcRewrite0=2,1,2,VE3RD,9999999 // This receives ALL private calls on Network 4 and sends them direct to the Radio