Talkgroup ID not honored when there is a connected reflector

[mrickey]

If there is a connected reflector and the user keys up on a talkgroup not in P25hosts.txt, the repeater will retransmit the signal on the selected talkgroup and to the connected reflector.

I feel the behavior should be to retransmit the signal, but not send it to the reflector.

For this scenario, I will use the term "repeater", but it could be a hotspot. I'm also using talkgroup 31077 because this is where our reflector is attached. But, any talkgroup with a reflector should work. I'm using talkgroup 2, because it isn't in P25hosts.txt so it does not connect to a different reflector when I key it up.

Duplication Scenario:

1. Setup radio 1 to monitor talkgroup 31077 on repeater 1
2. Connect repeater 1 to reflector 31077
3. Setup radio 2 to monitor talkgroup 31077 on repeater 2
4. Connect repeater 2 to reflector 31077
5. Verify the two radios can talk to each other
6. Setup radio 3 to monitor repeater 2 but be set for talkgroup 2
7. Key up radio 2

Result:
Radio 1 will hear the traffic and see it on talkgroup 31077
Radio 3 will hear the traffic and see it on talkgroup 2

Expected result:
Radio 3 will hear the traffic and see it on talkgroup 2

I guess you could also test this by simply looking at the reflector dashboard. But, this scenario gives a good example of what we want to do. We would like to hold conversations local to a repeater and not go over the network.

I know we can send a disconnect, but that just adds to the training for our users.

I don't see any obvious setting in the P25Gateway file that looks like what I want to do.

I would be fine the gateway disconnects from the reflector when someone keys up on a talkgroup that isn't associated with a reflector. Or, it could leave the reflector connected and simply not send traffic to the reflector.

THoughts, suggestions?

Thanks in advance,
Michael AF6FB

[g4klx]

Hi Michael

Your example missed a step I think, you still had radio 1 and 2 on TG31077 so it would not be heard by radio 3. As it stands, local RF users will always here local stations using the TG that is set in their radios, regardless of what the gateway is doing. Whether it goes over the network is only an issue in the gateway.

It is an interesting philosophical debate what to do when the TG is not one defined in the gateway. I can see three approaches:

1. It goes over the reflector that is connected with the TG altered over the network, the problem is that the transmitting station may not hear stations returning calls, or even local stations using that reflector.

2. It disconnected the connected reflector.

3. It doesn't go over the connected reflector, but stays local. The reflector stays connected.

Each one of those is supportable as an approach. I think I do approach 1 now, but I could make it an option. The same probably applies to the NXDN system also.

What do you think?

Jonathan G4KLX

[mrickey]

Jonathan,
I agree the system currently operates as described by approach 1.

I think approach 2 is what I would prefer. We have InactivityTimeout set, so the repeater will reconnect to out home reflector after the local traffic has stopped. I am fine if this is enabled with a setting.

To get interest levels up, we are recommending people create a channel called "Monitor" that does not have Selective Call set and is receive only. This allows the radio to hear traffic on any talkgroup. They can then switch to the appropriate channel to have a conversation.

Thanks for listening,
Michael AF6FB