Date   

Re: Beta testing of DummyRepeater for ASL

 

Just  finished my testing  with the Powered USB HUB.

 

Here is my setup   ALL Software running on a single Rpi3…

.

                                                                              MMDVM

                                                                                   |

AST -  Analog_Bridge – HB_Bridge – hb_confbridge – hbparrot

                        |                                                        |

                ThumbDV                                           BMServer 3021.

 

Confbridge has 3 rules

TG9TS2 to AST

TG9991TS2 to Parrot

TG3027TS1 to BM .

 

ONLY ThumbDV  plugged in powered hub .

MMDVM Arduino Due plugged  directly on  RPi3 USB port

Errors in  ThumbDV test ( AMBEtest4.py)  if mmdvm is plugged in powered  USB Hub …

 

All  functionnal  .  Max CPU  use I have seen is   25 %

 

Richard VE2DJE

 

 

 

 

Provenance : Courrier pour Windows 10

 


Re: Beta testing of DummyRepeater for ASL

Steve N4IRS
 

You should be able to listen to TG 3112122 on hoseline.

On 07/09/2017 04:28 PM, David KE6UPI wrote:
Is there a way to listen to D-Star online like BrandMeister's Hoseline?

David



--
Thanks, David

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."
Thomas Jefferson

On Sun, Jul 9, 2017 at 9:55 AM, Steve N4IRS <szingman@...> wrote:
From the just for the heck of it department. To test the Raspberry with 2 Vocoders, I am running the following.

BM (TG 3112122) <--> HB_Bridge <--> Analog_Bridge <--> DummyRepeater <---> DCS006T

Both Analog_Bridge (AB) and DummyRepeater (DR) have Vocoders. AB is using the PiDV and DR is using the ThumbDV plugged into the powered hub.
This is NOT the way to do this long term. This is just a test. I expect I'll put one side or the other to move a lot of traffic between the 2 networks.

73, Steve N4IRS






Re: Beta testing of DummyRepeater for ASL

David KE6UPI
 

Is there a way to listen to D-Star online like BrandMeister's Hoseline?

David



--
Thanks, David

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."
Thomas Jefferson

On Sun, Jul 9, 2017 at 9:55 AM, Steve N4IRS <szingman@...> wrote:
From the just for the heck of it department. To test the Raspberry with 2 Vocoders, I am running the following.

BM (TG 3112122) <--> HB_Bridge <--> Analog_Bridge <--> DummyRepeater <---> DCS006T

Both Analog_Bridge (AB) and DummyRepeater (DR) have Vocoders. AB is using the PiDV and DR is using the ThumbDV plugged into the powered hub.
This is NOT the way to do this long term. This is just a test. I expect I'll put one side or the other to move a lot of traffic between the 2 networks.

73, Steve N4IRS





Re: Beta testing of DummyRepeater for ASL

Steve N4IRS
 

From the just for the heck of it department. To test the Raspberry with 2 Vocoders, I am running the following.

BM (TG 3112122) <--> HB_Bridge <--> Analog_Bridge <--> DummyRepeater <---> DCS006T

Both Analog_Bridge (AB) and DummyRepeater (DR) have Vocoders. AB is using the PiDV and DR is using the ThumbDV plugged into the powered hub.
This is NOT the way to do this long term. This is just a test. I expect I'll put one side or the other to move a lot of traffic between the 2 networks.

73, Steve N4IRS


Re: Beta testing of DummyRepeater for ASL

Steve N4IRS
 

Here is what I have on the hub I'm using. I do not think it is anything special.

lsusb:
Bus 001 Device 012: ID 2001:f103 D-Link Corp. DUB-H7 7-port USB 2.0 hub

Label reads:
P/N: BDUBH7....A2 (Yes, the periods are in the Part Number)
H/W Ver. : A2

Power Supply is 5V 3A

On 07/09/2017 12:05 AM, Richard (Joseph) VE2DJE wrote:

Yess , What are the spécifications of the USB Hub you are using ???
Power  supply capacity ????

 

I will try  MMDVM ,  AST  Analog_Bridge , HBLink,  hb_confbridge and HB_Parrot in the same  Rpi3 ..

 

 

Will try  to use one  USB port for the MMDVM  and another  for the Powered USB hub to THumBDV as a start…

 

Richard

 

Provenance : Courrier pour Windows 10

 



Re: Beta testing of DummyRepeater for ASL

Steve N4IRS
 

Just 1. For what I'm doing I have 2 Vocoders running. One for D-Star (DummyRepeater) and one for DMR.

On 07/09/2017 12:11 AM, Paul Nannery wrote:
How many streams can one thumb dv handle at a time?

On Jul 9, 2017 12:10 AM, "Steve N4IRS" <szingman@...> wrote:
I don't think it's anything special. It's a D-Link DUB-H7 USB 2.0 powered hub I'll get the power supply specs when I move it.
This is a hub I had laying around. when I Google it, I think the newer model shows up. This one is silver and gray.

Steve

On 07/09/2017 12:05 AM, Richard (Joseph) VE2DJE wrote:

Yess , What are the spécifications of the USB Hub you are using ???
Power  supply capacity ????

 

I will try  MMDVM ,  AST  Analog_Bridge , HBLink,  hb_confbridge and HB_Parrot in the same  Rpi3 ..

 

 

Will try  to use one  USB port for the MMDVM  and another  for the Powered USB hub to THumBDV as a start…

 

Richard

 

Provenance : Courrier pour Windows 10

 




Re: Beta testing of DummyRepeater for ASL

Paul Nannery KC2VRJ
 

How many streams can one thumb dv handle at a time?

On Jul 9, 2017 12:10 AM, "Steve N4IRS" <szingman@...> wrote:
I don't think it's anything special. It's a D-Link DUB-H7 USB 2.0 powered hub I'll get the power supply specs when I move it.
This is a hub I had laying around. when I Google it, I think the newer model shows up. This one is silver and gray.

Steve

On 07/09/2017 12:05 AM, Richard (Joseph) VE2DJE wrote:

Yess , What are the spécifications of the USB Hub you are using ???
Power  supply capacity ????

 

I will try  MMDVM ,  AST  Analog_Bridge , HBLink,  hb_confbridge and HB_Parrot in the same  Rpi3 ..

 

 

Will try  to use one  USB port for the MMDVM  and another  for the Powered USB hub to THumBDV as a start…

 

Richard

 

Provenance : Courrier pour Windows 10

 



Re: Beta testing of DummyRepeater for ASL

Steve N4IRS
 

I don't think it's anything special. It's a D-Link DUB-H7 USB 2.0 powered hub I'll get the power supply specs when I move it.
This is a hub I had laying around. when I Google it, I think the newer model shows up. This one is silver and gray.

Steve

On 07/09/2017 12:05 AM, Richard (Joseph) VE2DJE wrote:

Yess , What are the spécifications of the USB Hub you are using ???
Power  supply capacity ????

 

I will try  MMDVM ,  AST  Analog_Bridge , HBLink,  hb_confbridge and HB_Parrot in the same  Rpi3 ..

 

 

Will try  to use one  USB port for the MMDVM  and another  for the Powered USB hub to THumBDV as a start…

 

Richard

 

Provenance : Courrier pour Windows 10

 



Re: Beta testing of DummyRepeater for ASL

 

Yess , What are the spécifications of the USB Hub you are using ???
Power  supply capacity ????

 

I will try  MMDVM ,  AST  Analog_Bridge , HBLink,  hb_confbridge and HB_Parrot in the same  Rpi3 ..

 

 

Will try  to use one  USB port for the MMDVM  and another  for the Powered USB hub to THumBDV as a start…

 

Richard

 

Provenance : Courrier pour Windows 10

 


Re: Beta testing of DummyRepeater for ASL

Steve N4IRS
 

It looks like it is going to work. I am running bridge from D-Star to DMR as a test. It is receive only. You can listen to the traffic on BM TG 311222 and ASL 2600.
I'll keep everybody informed.

73, Steve N4IRS

On 07/08/2017 11:53 PM, David KE6UPI wrote:
Good news. It sounds like the USB powered hub solves the ThumbDV problem?

David
KE6UPI



--
Thanks, David

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."
Thomas Jefferson

On Sat, Jul 8, 2017 at 5:28 PM, Steve N4IRS <szingman@...> wrote:
I moved the ThumbDV to a powered hub. When I ran the confidence test with 100,000 iterations it passed. So, I have both DMR and D-Star running on a Raspberry Pi2. Both Vocoders are running from AMBEserver (different ports)
The ASL config is 1 public node and 2 private nodes. I switch for one private node to the other depending on the desired mode. I have to say, the Pi is not breaking a sweat. ;)

73, Steve N4IRS



Re: Beta testing of DummyRepeater for ASL

David KE6UPI
 

Good news. It sounds like the USB powered hub solves the ThumbDV problem?

David
KE6UPI



--
Thanks, David

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."
Thomas Jefferson

On Sat, Jul 8, 2017 at 5:28 PM, Steve N4IRS <szingman@...> wrote:
I moved the ThumbDV to a powered hub. When I ran the confidence test with 100,000 iterations it passed. So, I have both DMR and D-Star running on a Raspberry Pi2. Both Vocoders are running from AMBEserver (different ports)
The ASL config is 1 public node and 2 private nodes. I switch for one private node to the other depending on the desired mode. I have to say, the Pi is not breaking a sweat. ;)

73, Steve N4IRS



Re: Beta testing of DummyRepeater for ASL

Steve N4IRS
 

I moved the ThumbDV to a powered hub. When I ran the confidence test with 100,000 iterations it passed. So, I have both DMR and D-Star running on a Raspberry Pi2. Both Vocoders are running from AMBEserver (different ports)
The ASL config is 1 public node and 2 private nodes. I switch for one private node to the other depending on the desired mode. I have to say, the Pi is not breaking a sweat. ;)

73, Steve N4IRS


Re: Beta testing of DummyRepeater for ASL

Steve N4IRS
 

It does work. I was unable to run 2 Vocoders at the same time (Raspberry Pi and ThumbDV issues) Bit I have 2 active instances of chan_usrp running at the same time. So it looks like your idea will work.

Steve


Re: Beta testing of DummyRepeater for ASL

Steve N4IRS
 

Matthew,
It LOOKS like multiple instances of chan_usrp MAY work. At least it does not crash! I did a quick test by adding a second node stanza:

[1999]
rxchannel = USRP/127.0.0.1:36001:37001  ; Use the USRP channel driver. Must be enabled in modules.conf
; 127.0.0.1 = IP of the target application
; 36001 = UDP port the target application is listening on
; 37001 = UDP port ASL is listening on
 
Asterisk did not crash. I have not tried to send or receive audio from 1999, but it MIGHT work.

73, Steve


Re: "Pre-empt" all talkgroups?

Cort N0MJS <n0mjs@...>
 

Yes, it would. That's the closest I can get with confbridge.

Cort Buffington
Office: (785) 856-9802
Mobile: (785) 865-7206

On Jul 5, 2017, at 9:58 PM, David Andrzejewski KD8TWG via Groups.Io <david@...> wrote:

Would this not then essentially turn NA and WW into full-time talkgroups without a timeout? I still want those groups to activate only when someone PTTs them and only for a couple of minutes. 


-- 

David Andrzejewski
E-mail/iMessage/Jabber: david@...
PGP Key ID: 5EBA8A72


On Jul 5, 2017, at 22:40, Cort N0MJS <n0mjs@...> wrote:

'WORLDWIDE': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 15, 'TO_TYPE': ‘OFF', 'ON': [], 'OFF': [60]},
],
'NORTHAMERICA': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 15, 'TO_TYPE': ‘OFF', 'ON': [], 'OFF': [60]},
],

On both conference bridges, the line for repeater is the same:

The way you had 2 minute timeouts and using the same TGID to enable that voice traffic is on is mostly superfluous. To say that I want this group to be on, timeout every 2 minutes, but then turn back on when there’s traffic is the same thing as just leaving it on. So let’s just get rid of that…. and then...

Change the TO_TYPE to OFF and the Timeout to 15 minutes. Now, traffic on TS1, TGID60 will cause REPEATER to be disconnected from both WORLDWIDE and NORTHAMERICA and stay that way for 15 minutes. At the end of 15 minutes, REPEATER will be reconnected to NORTHAMERCIA and WORLDWIDE.

If you want traffic from REPEATER to turn them back on, then enter the TGID you want to use to do that into the ON section….

'WORLDWIDE': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 15, 'TO_TYPE': ‘OFF', 'ON': [1,], 'OFF': [60]},
],
'NORTHAMERICA': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 15, 'TO_TYPE': ‘OFF', 'ON': [3,], 'OFF': [60]},
],

Note – that means that traffic FROM REPEATER, TS1/TGID3 (NORTHAMERICA example) will reconnect REPEATER to NORTHAMERICA. Traffic from K4USD will not.

On Jul 5, 2017, at 9:18 PM, David Andrzejewski KD8TWG via Groups.Io <david@...> wrote:

Yeah I realized that shortly after I sent it. Basically, what I'm trying to accomplish is that when someone keys up on talkgroup 60, I want that to have exclusive access to that time slot and lock everything else out for a set period of time, while still keeping everything else PTT-activated.

- Dave


On 7/5/17 9:54 PM, Cort N0MJS wrote:
I’ll shove some stuff inline here.

On Jul 5, 2017, at 3:21 PM, David Andrzejewski KD8TWG via Groups.Io <david@...> wrote:

No problem, I'm sure I'm the one who sounds like an ass ;)

I'm just trying to wrap my head around how this will work. Okay, so here's my config for time slot 1:

'SIXTY': [
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 60, 'ACTIVE': True, 'TIMEOUT': 15, 'TO_TYPE': 'ON', 'ON': [60,], 'OFF': []},
],

The above does nothing. It defines a “conference bridge” (my name for it) named “SIXTY", but only has one member, so there’s nothing to bridge to or from… it’s like dialing into a phone conference bridge and being the only one there.

'WORLDWIDE': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},

K4USD will always be connected to the "conference bridge" named “WORLDWIDE”. It’s set ACTIVE on startup (initially on), and will time out in 2 minutes, but there’s no timeout action, so the timeout is ignored. There are no TGIDs to activate it or deactivate it, so it’s just going to always be connected.

{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'ON', 'ON': [1,], 'OFF': [60]},
],

REPEATER will be connected to the “conference bridge” named “WORLDWIDE” on startup, and timeout after 2 minutes. Any traffic on TGID 1 will turn it back and/or reset the 2 minute timer on un-key. Traffic on TGID 60 will disconnect REPEATER from WORLDWIDE on un-key.

'NORTHAMERICA': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},

K4USD will always be connected to NORTHAMERICA. It’s et to be active on startup, timeout doesn’t matter since the timeout action is none.

{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'ON', 'ON': [3,], 'OFF': [60]},
],

REPEATER will be connected to the “conference bridge” named “NORTHAMERICA” on startup, and timeout after 2 minutes. Any traffic on TGID 3 will turn it back and/or reset the 2 minute timer on un-key. Traffic on TGID 60 will disconnect REPEATER from NORTHAMERICA on un-key.



So in this case, a user keying up on talk group 60 will cause WW and NA to shut off immediately. Now, I have the timeout set to 15 for talk group 60. Does this mean that talk group 60 will be exclusive for the next 15 minutes after the last user keys up on it, regardless of whether someone keys up on WW or NA during that time? This is what I'm trying to accomplish. I do not want WW or NA to be full-time talk groups, they need to remain PTT-only.

Logic error – you created another conference bridge named SIXTY. Everything going on with SIXTY is exclusive from what’s happening on WORLDWIDE and NORTHAMERICA. Conference bridges are all independent from each other.

If you only created the conference bridge “SIXTY” to try to make that TGID have exclusive access to the timeslot, tell me and I’ll try to write this for you in a way that’ll get what you want. If not, and there’s just something else missing from SIXTY, add it in and I can re-evaluate, but like I said, as of now, SIXTY is essentially meaningless since it’s a conference bridge with one member – kinda like clapping with one hand? (my attempt at humor).

0x49 DE N0MJS


- Dave


July 5, 2017 4:12 PM, "Cort N0MJS" <n0mjs@...> wrote:
David,
Right.. The TGID you want to have exclusive rights is a trigger to turn all others off. Isn’t that what you meant by "configure a talk group in a way that when a user keys up on it, that talk group has the time slot for a certain amount of time, and for that amount of time, no other talk group can be used on that slot, regardless of what other talk groups a user PTTs on”?
I don’t quote you to sound like an ass, but to try and figure out what about this doesn’t solve that requirement – key up on a TGID, then that TGID has exclusive access for a period of time? That says to me, use that TGID to trigger turning all others off for the specified time? No?
On Jul 5, 2017, at 2:55 PM, David Andrzejewski KD8TWG via Groups.Io <david@...> wrote:
Ah, but in that kind of configuration, those talk groups would be on all the time, *except* when any of the "off" talk groups are activated, right?

What about talk groups that use a TO_TYPE of "ON"?
--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206



--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






-- 


David Andrzejewski
E-mail/iMessage/Jabber: david@...
PGP Key ID: 5EBA8A72
https://dandrzejewski.keybase.pub/

--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






Re: "Pre-empt" all talkgroups?

David Andrzejewski KD8TWG
 

Would this not then essentially turn NA and WW into full-time talkgroups without a timeout? I still want those groups to activate only when someone PTTs them and only for a couple of minutes. 


-- 

David Andrzejewski
E-mail/iMessage/Jabber: david@...
PGP Key ID: 5EBA8A72


On Jul 5, 2017, at 22:40, Cort N0MJS <n0mjs@...> wrote:

'WORLDWIDE': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 15, 'TO_TYPE': ‘OFF', 'ON': [], 'OFF': [60]},
],
'NORTHAMERICA': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 15, 'TO_TYPE': ‘OFF', 'ON': [], 'OFF': [60]},
],

On both conference bridges, the line for repeater is the same:

The way you had 2 minute timeouts and using the same TGID to enable that voice traffic is on is mostly superfluous. To say that I want this group to be on, timeout every 2 minutes, but then turn back on when there’s traffic is the same thing as just leaving it on. So let’s just get rid of that…. and then...

Change the TO_TYPE to OFF and the Timeout to 15 minutes. Now, traffic on TS1, TGID60 will cause REPEATER to be disconnected from both WORLDWIDE and NORTHAMERICA and stay that way for 15 minutes. At the end of 15 minutes, REPEATER will be reconnected to NORTHAMERCIA and WORLDWIDE.

If you want traffic from REPEATER to turn them back on, then enter the TGID you want to use to do that into the ON section….

'WORLDWIDE': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 15, 'TO_TYPE': ‘OFF', 'ON': [1,], 'OFF': [60]},
],
'NORTHAMERICA': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 15, 'TO_TYPE': ‘OFF', 'ON': [3,], 'OFF': [60]},
],

Note – that means that traffic FROM REPEATER, TS1/TGID3 (NORTHAMERICA example) will reconnect REPEATER to NORTHAMERICA. Traffic from K4USD will not.

On Jul 5, 2017, at 9:18 PM, David Andrzejewski KD8TWG via Groups.Io <david@...> wrote:

Yeah I realized that shortly after I sent it. Basically, what I'm trying to accomplish is that when someone keys up on talkgroup 60, I want that to have exclusive access to that time slot and lock everything else out for a set period of time, while still keeping everything else PTT-activated.

- Dave


On 7/5/17 9:54 PM, Cort N0MJS wrote:
I’ll shove some stuff inline here.

On Jul 5, 2017, at 3:21 PM, David Andrzejewski KD8TWG via Groups.Io <david@...> wrote:

No problem, I'm sure I'm the one who sounds like an ass ;)

I'm just trying to wrap my head around how this will work. Okay, so here's my config for time slot 1:

'SIXTY': [
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 60, 'ACTIVE': True, 'TIMEOUT': 15, 'TO_TYPE': 'ON', 'ON': [60,], 'OFF': []},
],

The above does nothing. It defines a “conference bridge” (my name for it) named “SIXTY", but only has one member, so there’s nothing to bridge to or from… it’s like dialing into a phone conference bridge and being the only one there.

'WORLDWIDE': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},

K4USD will always be connected to the "conference bridge" named “WORLDWIDE”. It’s set ACTIVE on startup (initially on), and will time out in 2 minutes, but there’s no timeout action, so the timeout is ignored. There are no TGIDs to activate it or deactivate it, so it’s just going to always be connected.

{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'ON', 'ON': [1,], 'OFF': [60]},
],

REPEATER will be connected to the “conference bridge” named “WORLDWIDE” on startup, and timeout after 2 minutes. Any traffic on TGID 1 will turn it back and/or reset the 2 minute timer on un-key. Traffic on TGID 60 will disconnect REPEATER from WORLDWIDE on un-key.

'NORTHAMERICA': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},

K4USD will always be connected to NORTHAMERICA. It’s et to be active on startup, timeout doesn’t matter since the timeout action is none.

{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'ON', 'ON': [3,], 'OFF': [60]},
],

REPEATER will be connected to the “conference bridge” named “NORTHAMERICA” on startup, and timeout after 2 minutes. Any traffic on TGID 3 will turn it back and/or reset the 2 minute timer on un-key. Traffic on TGID 60 will disconnect REPEATER from NORTHAMERICA on un-key.



So in this case, a user keying up on talk group 60 will cause WW and NA to shut off immediately. Now, I have the timeout set to 15 for talk group 60. Does this mean that talk group 60 will be exclusive for the next 15 minutes after the last user keys up on it, regardless of whether someone keys up on WW or NA during that time? This is what I'm trying to accomplish. I do not want WW or NA to be full-time talk groups, they need to remain PTT-only.

Logic error – you created another conference bridge named SIXTY. Everything going on with SIXTY is exclusive from what’s happening on WORLDWIDE and NORTHAMERICA. Conference bridges are all independent from each other.

If you only created the conference bridge “SIXTY” to try to make that TGID have exclusive access to the timeslot, tell me and I’ll try to write this for you in a way that’ll get what you want. If not, and there’s just something else missing from SIXTY, add it in and I can re-evaluate, but like I said, as of now, SIXTY is essentially meaningless since it’s a conference bridge with one member – kinda like clapping with one hand? (my attempt at humor).

0x49 DE N0MJS


- Dave


July 5, 2017 4:12 PM, "Cort N0MJS" <n0mjs@...> wrote:
David,
Right.. The TGID you want to have exclusive rights is a trigger to turn all others off. Isn’t that what you meant by "configure a talk group in a way that when a user keys up on it, that talk group has the time slot for a certain amount of time, and for that amount of time, no other talk group can be used on that slot, regardless of what other talk groups a user PTTs on”?
I don’t quote you to sound like an ass, but to try and figure out what about this doesn’t solve that requirement – key up on a TGID, then that TGID has exclusive access for a period of time? That says to me, use that TGID to trigger turning all others off for the specified time? No?
On Jul 5, 2017, at 2:55 PM, David Andrzejewski KD8TWG via Groups.Io <david@...> wrote:
Ah, but in that kind of configuration, those talk groups would be on all the time, *except* when any of the "off" talk groups are activated, right?

What about talk groups that use a TO_TYPE of "ON"?
--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206



--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






-- 


David Andrzejewski
E-mail/iMessage/Jabber: david@...
PGP Key ID: 5EBA8A72
https://dandrzejewski.keybase.pub/

--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






Re: "Pre-empt" all talkgroups?

Cort N0MJS <n0mjs@...>
 

'WORLDWIDE': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 15, 'TO_TYPE': ‘OFF', 'ON': [], 'OFF': [60]},
],
'NORTHAMERICA': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 15, 'TO_TYPE': ‘OFF', 'ON': [], 'OFF': [60]},
],

On both conference bridges, the line for repeater is the same:

The way you had 2 minute timeouts and using the same TGID to enable that voice traffic is on is mostly superfluous. To say that I want this group to be on, timeout every 2 minutes, but then turn back on when there’s traffic is the same thing as just leaving it on. So let’s just get rid of that…. and then...

Change the TO_TYPE to OFF and the Timeout to 15 minutes. Now, traffic on TS1, TGID60 will cause REPEATER to be disconnected from both WORLDWIDE and NORTHAMERICA and stay that way for 15 minutes. At the end of 15 minutes, REPEATER will be reconnected to NORTHAMERCIA and WORLDWIDE.

If you want traffic from REPEATER to turn them back on, then enter the TGID you want to use to do that into the ON section….

'WORLDWIDE': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 15, 'TO_TYPE': ‘OFF', 'ON': [1,], 'OFF': [60]},
],
'NORTHAMERICA': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 15, 'TO_TYPE': ‘OFF', 'ON': [3,], 'OFF': [60]},
],

Note – that means that traffic FROM REPEATER, TS1/TGID3 (NORTHAMERICA example) will reconnect REPEATER to NORTHAMERICA. Traffic from K4USD will not.

On Jul 5, 2017, at 9:18 PM, David Andrzejewski KD8TWG via Groups.Io <david@...> wrote:

Yeah I realized that shortly after I sent it. Basically, what I'm trying to accomplish is that when someone keys up on talkgroup 60, I want that to have exclusive access to that time slot and lock everything else out for a set period of time, while still keeping everything else PTT-activated.

- Dave


On 7/5/17 9:54 PM, Cort N0MJS wrote:
I’ll shove some stuff inline here.

On Jul 5, 2017, at 3:21 PM, David Andrzejewski KD8TWG via Groups.Io <david@...> wrote:

No problem, I'm sure I'm the one who sounds like an ass ;)

I'm just trying to wrap my head around how this will work. Okay, so here's my config for time slot 1:

'SIXTY': [
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 60, 'ACTIVE': True, 'TIMEOUT': 15, 'TO_TYPE': 'ON', 'ON': [60,], 'OFF': []},
],

The above does nothing. It defines a “conference bridge” (my name for it) named “SIXTY", but only has one member, so there’s nothing to bridge to or from… it’s like dialing into a phone conference bridge and being the only one there.

'WORLDWIDE': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},

K4USD will always be connected to the "conference bridge" named “WORLDWIDE”. It’s set ACTIVE on startup (initially on), and will time out in 2 minutes, but there’s no timeout action, so the timeout is ignored. There are no TGIDs to activate it or deactivate it, so it’s just going to always be connected.

{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'ON', 'ON': [1,], 'OFF': [60]},
],

REPEATER will be connected to the “conference bridge” named “WORLDWIDE” on startup, and timeout after 2 minutes. Any traffic on TGID 1 will turn it back and/or reset the 2 minute timer on un-key. Traffic on TGID 60 will disconnect REPEATER from WORLDWIDE on un-key.

'NORTHAMERICA': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},

K4USD will always be connected to NORTHAMERICA. It’s et to be active on startup, timeout doesn’t matter since the timeout action is none.

{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'ON', 'ON': [3,], 'OFF': [60]},
],

REPEATER will be connected to the “conference bridge” named “NORTHAMERICA” on startup, and timeout after 2 minutes. Any traffic on TGID 3 will turn it back and/or reset the 2 minute timer on un-key. Traffic on TGID 60 will disconnect REPEATER from NORTHAMERICA on un-key.



So in this case, a user keying up on talk group 60 will cause WW and NA to shut off immediately. Now, I have the timeout set to 15 for talk group 60. Does this mean that talk group 60 will be exclusive for the next 15 minutes after the last user keys up on it, regardless of whether someone keys up on WW or NA during that time? This is what I'm trying to accomplish. I do not want WW or NA to be full-time talk groups, they need to remain PTT-only.

Logic error – you created another conference bridge named SIXTY. Everything going on with SIXTY is exclusive from what’s happening on WORLDWIDE and NORTHAMERICA. Conference bridges are all independent from each other.

If you only created the conference bridge “SIXTY” to try to make that TGID have exclusive access to the timeslot, tell me and I’ll try to write this for you in a way that’ll get what you want. If not, and there’s just something else missing from SIXTY, add it in and I can re-evaluate, but like I said, as of now, SIXTY is essentially meaningless since it’s a conference bridge with one member – kinda like clapping with one hand? (my attempt at humor).

0x49 DE N0MJS


- Dave


July 5, 2017 4:12 PM, "Cort N0MJS" <n0mjs@...> wrote:
David,
Right.. The TGID you want to have exclusive rights is a trigger to turn all others off. Isn’t that what you meant by "configure a talk group in a way that when a user keys up on it, that talk group has the time slot for a certain amount of time, and for that amount of time, no other talk group can be used on that slot, regardless of what other talk groups a user PTTs on”?
I don’t quote you to sound like an ass, but to try and figure out what about this doesn’t solve that requirement – key up on a TGID, then that TGID has exclusive access for a period of time? That says to me, use that TGID to trigger turning all others off for the specified time? No?
On Jul 5, 2017, at 2:55 PM, David Andrzejewski KD8TWG via Groups.Io <david@...> wrote:
Ah, but in that kind of configuration, those talk groups would be on all the time, *except* when any of the "off" talk groups are activated, right?

What about talk groups that use a TO_TYPE of "ON"?
--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206



--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






-- 


David Andrzejewski
E-mail/iMessage/Jabber: david@...
PGP Key ID: 5EBA8A72
https://dandrzejewski.keybase.pub/

--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






Re: "Pre-empt" all talkgroups?

David Andrzejewski KD8TWG
 

Yeah I realized that shortly after I sent it. Basically, what I'm trying to accomplish is that when someone keys up on talkgroup 60, I want that to have exclusive access to that time slot and lock everything else out for a set period of time, while still keeping everything else PTT-activated.

- Dave


On 7/5/17 9:54 PM, Cort N0MJS wrote:
I’ll shove some stuff inline here.

On Jul 5, 2017, at 3:21 PM, David Andrzejewski KD8TWG via Groups.Io <david@...> wrote:

No problem, I'm sure I'm the one who sounds like an ass ;)

I'm just trying to wrap my head around how this will work. Okay, so here's my config for time slot 1:

'SIXTY': [
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 60, 'ACTIVE': True, 'TIMEOUT': 15, 'TO_TYPE': 'ON', 'ON': [60,], 'OFF': []},
],

The above does nothing. It defines a “conference bridge” (my name for it) named “SIXTY", but only has one member, so there’s nothing to bridge to or from… it’s like dialing into a phone conference bridge and being the only one there.

'WORLDWIDE': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},

K4USD will always be connected to the "conference bridge" named “WORLDWIDE”. It’s set ACTIVE on startup (initially on), and will time out in 2 minutes, but there’s no timeout action, so the timeout is ignored. There are no TGIDs to activate it or deactivate it, so it’s just going to always be connected.

{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'ON', 'ON': [1,], 'OFF': [60]},
],

REPEATER will be connected to the “conference bridge” named “WORLDWIDE” on startup, and timeout after 2 minutes. Any traffic on TGID 1 will turn it back and/or reset the 2 minute timer on un-key. Traffic on TGID 60 will disconnect REPEATER from WORLDWIDE on un-key.

'NORTHAMERICA': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},

K4USD will always be connected to NORTHAMERICA. It’s et to be active on startup, timeout doesn’t matter since the timeout action is none.

{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'ON', 'ON': [3,], 'OFF': [60]},
],

REPEATER will be connected to the “conference bridge” named “NORTHAMERICA” on startup, and timeout after 2 minutes. Any traffic on TGID 3 will turn it back and/or reset the 2 minute timer on un-key. Traffic on TGID 60 will disconnect REPEATER from NORTHAMERICA on un-key.



So in this case, a user keying up on talk group 60 will cause WW and NA to shut off immediately. Now, I have the timeout set to 15 for talk group 60. Does this mean that talk group 60 will be exclusive for the next 15 minutes after the last user keys up on it, regardless of whether someone keys up on WW or NA during that time? This is what I'm trying to accomplish. I do not want WW or NA to be full-time talk groups, they need to remain PTT-only.

Logic error – you created another conference bridge named SIXTY. Everything going on with SIXTY is exclusive from what’s happening on WORLDWIDE and NORTHAMERICA. Conference bridges are all independent from each other.

If you only created the conference bridge “SIXTY” to try to make that TGID have exclusive access to the timeslot, tell me and I’ll try to write this for you in a way that’ll get what you want. If not, and there’s just something else missing from SIXTY, add it in and I can re-evaluate, but like I said, as of now, SIXTY is essentially meaningless since it’s a conference bridge with one member – kinda like clapping with one hand? (my attempt at humor).

0x49 DE N0MJS


- Dave


July 5, 2017 4:12 PM, "Cort N0MJS" <n0mjs@...> wrote:
David,
Right.. The TGID you want to have exclusive rights is a trigger to turn all others off. Isn’t that what you meant by "configure a talk group in a way that when a user keys up on it, that talk group has the time slot for a certain amount of time, and for that amount of time, no other talk group can be used on that slot, regardless of what other talk groups a user PTTs on”?
I don’t quote you to sound like an ass, but to try and figure out what about this doesn’t solve that requirement – key up on a TGID, then that TGID has exclusive access for a period of time? That says to me, use that TGID to trigger turning all others off for the specified time? No?
On Jul 5, 2017, at 2:55 PM, David Andrzejewski KD8TWG via Groups.Io <david@...> wrote:
Ah, but in that kind of configuration, those talk groups would be on all the time, *except* when any of the "off" talk groups are activated, right?

What about talk groups that use a TO_TYPE of "ON"?
--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206



--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






-- 


David Andrzejewski
E-mail/iMessage/Jabber: david@...
PGP Key ID: 5EBA8A72
https://dandrzejewski.keybase.pub/


Re: "Pre-empt" all talkgroups?

Cort N0MJS <n0mjs@...>
 

I’ll shove some stuff inline here.

On Jul 5, 2017, at 3:21 PM, David Andrzejewski KD8TWG via Groups.Io <david@...> wrote:

No problem, I'm sure I'm the one who sounds like an ass ;)

I'm just trying to wrap my head around how this will work. Okay, so here's my config for time slot 1:

'SIXTY': [
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 60, 'ACTIVE': True, 'TIMEOUT': 15, 'TO_TYPE': 'ON', 'ON': [60,], 'OFF': []},
],

The above does nothing. It defines a “conference bridge” (my name for it) named “SIXTY", but only has one member, so there’s nothing to bridge to or from… it’s like dialing into a phone conference bridge and being the only one there.

'WORLDWIDE': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},

K4USD will always be connected to the "conference bridge" named “WORLDWIDE”. It’s set ACTIVE on startup (initially on), and will time out in 2 minutes, but there’s no timeout action, so the timeout is ignored. There are no TGIDs to activate it or deactivate it, so it’s just going to always be connected.

{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'ON', 'ON': [1,], 'OFF': [60]},
],

REPEATER will be connected to the “conference bridge” named “WORLDWIDE” on startup, and timeout after 2 minutes. Any traffic on TGID 1 will turn it back and/or reset the 2 minute timer on un-key. Traffic on TGID 60 will disconnect REPEATER from WORLDWIDE on un-key.

'NORTHAMERICA': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},

K4USD will always be connected to NORTHAMERICA. It’s et to be active on startup, timeout doesn’t matter since the timeout action is none.

{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'ON', 'ON': [3,], 'OFF': [60]},
],

REPEATER will be connected to the “conference bridge” named “NORTHAMERICA” on startup, and timeout after 2 minutes. Any traffic on TGID 3 will turn it back and/or reset the 2 minute timer on un-key. Traffic on TGID 60 will disconnect REPEATER from NORTHAMERICA on un-key.



So in this case, a user keying up on talk group 60 will cause WW and NA to shut off immediately. Now, I have the timeout set to 15 for talk group 60. Does this mean that talk group 60 will be exclusive for the next 15 minutes after the last user keys up on it, regardless of whether someone keys up on WW or NA during that time? This is what I'm trying to accomplish. I do not want WW or NA to be full-time talk groups, they need to remain PTT-only.

Logic error – you created another conference bridge named SIXTY. Everything going on with SIXTY is exclusive from what’s happening on WORLDWIDE and NORTHAMERICA. Conference bridges are all independent from each other.

If you only created the conference bridge “SIXTY” to try to make that TGID have exclusive access to the timeslot, tell me and I’ll try to write this for you in a way that’ll get what you want. If not, and there’s just something else missing from SIXTY, add it in and I can re-evaluate, but like I said, as of now, SIXTY is essentially meaningless since it’s a conference bridge with one member – kinda like clapping with one hand? (my attempt at humor).

0x49 DE N0MJS


- Dave


July 5, 2017 4:12 PM, "Cort N0MJS" <n0mjs@...> wrote:
David,
Right.. The TGID you want to have exclusive rights is a trigger to turn all others off. Isn’t that what you meant by "configure a talk group in a way that when a user keys up on it, that talk group has the time slot for a certain amount of time, and for that amount of time, no other talk group can be used on that slot, regardless of what other talk groups a user PTTs on”?
I don’t quote you to sound like an ass, but to try and figure out what about this doesn’t solve that requirement – key up on a TGID, then that TGID has exclusive access for a period of time? That says to me, use that TGID to trigger turning all others off for the specified time? No?
On Jul 5, 2017, at 2:55 PM, David Andrzejewski KD8TWG via Groups.Io <david@...> wrote:
Ah, but in that kind of configuration, those talk groups would be on all the time, *except* when any of the "off" talk groups are activated, right?

What about talk groups that use a TO_TYPE of "ON"?
--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206



--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206






Re: "Pre-empt" all talkgroups?

David Andrzejewski KD8TWG
 

No problem, I'm sure I'm the one who sounds like an ass ;)

I'm just trying to wrap my head around how this will work. Okay, so here's my config for time slot 1:

'SIXTY': [
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 60, 'ACTIVE': True, 'TIMEOUT': 15, 'TO_TYPE': 'ON', 'ON': [60,], 'OFF': []},
],
'WORLDWIDE': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 1, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'ON', 'ON': [1,], 'OFF': [60]},
],
'NORTHAMERICA': [
{'SYSTEM': 'K4USD', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [], 'OFF': []},
{'SYSTEM': 'REPEATER', 'TS': 1, 'TGID': 3, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'ON', 'ON': [3,], 'OFF': [60]},
],



So in this case, a user keying up on talk group 60 will cause WW and NA to shut off immediately. Now, I have the timeout set to 15 for talk group 60. Does this mean that talk group 60 will be exclusive for the next 15 minutes after the last user keys up on it, regardless of whether someone keys up on WW or NA during that time? This is what I'm trying to accomplish. I do not want WW or NA to be full-time talk groups, they need to remain PTT-only.

- Dave


July 5, 2017 4:12 PM, "Cort N0MJS" <n0mjs@...> wrote:

David,
Right.. The TGID you want to have exclusive rights is a trigger to turn all others off. Isn’t that what you meant by "configure a talk group in a way that when a user keys up on it, that talk group has the time slot for a certain amount of time, and for that amount of time, no other talk group can be used on that slot, regardless of what other talk groups a user PTTs on”?
I don’t quote you to sound like an ass, but to try and figure out what about this doesn’t solve that requirement – key up on a TGID, then that TGID has exclusive access for a period of time? That says to me, use that TGID to trigger turning all others off for the specified time? No?
On Jul 5, 2017, at 2:55 PM, David Andrzejewski KD8TWG via Groups.Io <david@...> wrote:
Ah, but in that kind of configuration, those talk groups would be on all the time, *except* when any of the "off" talk groups are activated, right?

What about talk groups that use a TO_TYPE of "ON"?
--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206


9601 - 9620 of 9882