Lets start with a look at the accepted method of doing a private call to a parrot
PCRewrite0=2,9990,2,9990,1
SrcRewrite0=2,9990,2,9,1
Now this requires a TG 9990 private call to be created in the code plug with tg9 set in a receiver group associated with tg9990
we can eliminate the TG9 when we use
SrcRewrite0=2,9990,2,9990,1
But what do we do when we want to use multiple private calls to different users digital ids?
A few of us over at TGIF discovered that .............
Most DMR radio's were designed to make and receive private calls. The radio contains the users call sign and digital ID
WE found that the following works just fine, by directing the the return private call directly to the radio.
Assume the radio has my call and Digital ID VE3RD 3023954
PCRewrite0=2,9990,2,9990,1
SrcRewrite0=2,9990,2,VE3RD,1
Alternately SrcRewrite0=2,9990,2,3023954,1 works as well.
Now we need to expand this to work on different networks using the 7 digit tg method
Network 1
PCRewrite0=2,1009990,2,9990,1
SrcRewrite0=2,9990,2,VE3RD,1
Network 4
PCRewrite0=2,4009990,2,9990,1
SrcRewrite0=2,9990,2,VE3RD,1
The above works just fine. The following is supposition
Edited by group Admin. Read below.
Private Calls in DMRGateway
Re: Private Calls in DMRGateway
Go and test it. Then come back and tell us it works.
Many people here wont be literate of your suggestions. If they mess it up they wont be able to put it right. Thats why we only support the base image provided with a pistar download.
Often users suggest changes, but dont stand by them or continue after to support their suggestions to others when things to belly up. Leaving us to try and sort out the mess left behind.
That all said were not looking to stiffle experimentation or futhur advances. So if it works after youve tested these suggestions let us know and ill gladly reinstate the post.
Sent via smoke signals from my SM-G935F M1DNS (Admin)
Many people here wont be literate of your suggestions. If they mess it up they wont be able to put it right. Thats why we only support the base image provided with a pistar download.
Often users suggest changes, but dont stand by them or continue after to support their suggestions to others when things to belly up. Leaving us to try and sort out the mess left behind.
That all said were not looking to stiffle experimentation or futhur advances. So if it works after youve tested these suggestions let us know and ill gladly reinstate the post.
Sent via smoke signals from my SM-G935F M1DNS (Admin)
Andrew M1DNS.
Pi-star Admin Team.
Pi-star Admin Team.
Re: Private Calls in DMRGateway
Quite right. I should have tested it before posting it
I run my DMRGateway with an 8 digit control method as follows
NOTE: This not a stock pi-star gateway as the stock gateway will not handle 7 digit talk groups (either PC or GC) required for use on TGIF
TGRewrite0=2,14000001,2,1,999999 // This line handles all group call talk groups up to 6 digits and locks in Network 4
TGRewrite1=2,1,2,1,9999999 // After use of the above rule to lock in Network 4,This line handles the new 7 digit talk groups used on TGIF
PCRewrite0=2,14000001,2,1,9999999 // This line handles all private call id's up to 6 digit and locks in Network 4
PCRewrite1=2,10000001,2,1,9999999 // After use of the above rule to lock in Network 4, this handles 7 digit private calls
SrcRewrite0=2,1,2,VE3RD,9999999 // This line handles 7 digit private calls.
From the TGIF Last heard, Accessing 7 digit talk group 3020733
Callsign Name DMR ID (Repeater ID) Talkgroup Timestamp RSS
Phil 3023954 (302395444) 31665 TGIF 12:13:11 S9+20dB -63 dBm // A call to 14031665 Accesses Net4 and locks it in
Phil 3023954 (302395444) 3020733 12:13:35 S9+20dB -68 dBm // 7 digit talk groups now work on Net4 Only with the above lock.
The New TGIF parrot responds to both GC and PC on either 9990 or 31000. (Motorola Radios currently have a problem on TGIF with private calls to the parrot - should be fixed shortly)
dialing up 14009990 as a group call triggers the TGIF parrot
dialing up 14009990 as a private call triggers the TGIF parrot
dialing up 14031000 as a group call triggers the TGIF parrot
dialing up 14031000 as a private call triggers the TGIF parrot
The return voice is heard on the radio as all returns on private calls are directed directly to the radio, using the call sign VE3RD which resides in the radio. (Use your own Call Sign here - It MUST be the call sign programmed into your Radio)
I modified my Rewrite rules just for the test as follows and all tests worked as expected, except that 7 digit talk groups can not be handled in this method. This is the standard adopted by the stock pi-star DMRGateway
TGRewrite0=2,4000001,2,1,999999 // This line handles all group call talk groups up to 6 digits
PCRewrite0=2,4000001,2,1,999999 // This line handles all private call IDs up to 6 digit
SrcRewrite0=2,1,2,VE3RD,999999 // This line handles 7 digit IDs.
dialing up 4009990 as a group call triggers the TGIF parrot
dialing up 4009990 as a private call triggers the TGIF parrot
dialing up 4031000 as a group call triggers the TGIF parrot
dialing up 4031000 as a private call triggers the TGIF parrot
The main point I am trying to make here is the use of your callsign in the radio to handle private call return data. Regardless of what tg or id you use, the return to your callsign will handle all returns.
Regarding support, I am the main goto guy on TGIF for issues with the DMRGateway
I can be found most days on 31665 or send me an email at [email protected]
I run my DMRGateway with an 8 digit control method as follows
NOTE: This not a stock pi-star gateway as the stock gateway will not handle 7 digit talk groups (either PC or GC) required for use on TGIF
TGRewrite0=2,14000001,2,1,999999 // This line handles all group call talk groups up to 6 digits and locks in Network 4
TGRewrite1=2,1,2,1,9999999 // After use of the above rule to lock in Network 4,This line handles the new 7 digit talk groups used on TGIF
PCRewrite0=2,14000001,2,1,9999999 // This line handles all private call id's up to 6 digit and locks in Network 4
PCRewrite1=2,10000001,2,1,9999999 // After use of the above rule to lock in Network 4, this handles 7 digit private calls
SrcRewrite0=2,1,2,VE3RD,9999999 // This line handles 7 digit private calls.
From the TGIF Last heard, Accessing 7 digit talk group 3020733
Callsign Name DMR ID (Repeater ID) Talkgroup Timestamp RSS
Phil 3023954 (302395444) 31665 TGIF 12:13:11 S9+20dB -63 dBm // A call to 14031665 Accesses Net4 and locks it in
Phil 3023954 (302395444) 3020733 12:13:35 S9+20dB -68 dBm // 7 digit talk groups now work on Net4 Only with the above lock.
The New TGIF parrot responds to both GC and PC on either 9990 or 31000. (Motorola Radios currently have a problem on TGIF with private calls to the parrot - should be fixed shortly)
dialing up 14009990 as a group call triggers the TGIF parrot
dialing up 14009990 as a private call triggers the TGIF parrot
dialing up 14031000 as a group call triggers the TGIF parrot
dialing up 14031000 as a private call triggers the TGIF parrot
The return voice is heard on the radio as all returns on private calls are directed directly to the radio, using the call sign VE3RD which resides in the radio. (Use your own Call Sign here - It MUST be the call sign programmed into your Radio)
I modified my Rewrite rules just for the test as follows and all tests worked as expected, except that 7 digit talk groups can not be handled in this method. This is the standard adopted by the stock pi-star DMRGateway
TGRewrite0=2,4000001,2,1,999999 // This line handles all group call talk groups up to 6 digits
PCRewrite0=2,4000001,2,1,999999 // This line handles all private call IDs up to 6 digit
SrcRewrite0=2,1,2,VE3RD,999999 // This line handles 7 digit IDs.
dialing up 4009990 as a group call triggers the TGIF parrot
dialing up 4009990 as a private call triggers the TGIF parrot
dialing up 4031000 as a group call triggers the TGIF parrot
dialing up 4031000 as a private call triggers the TGIF parrot
The main point I am trying to make here is the use of your callsign in the radio to handle private call return data. Regardless of what tg or id you use, the return to your callsign will handle all returns.
Regarding support, I am the main goto guy on TGIF for issues with the DMRGateway
I can be found most days on 31665 or send me an email at [email protected]