Problem with node on Calls Platform

[georgew0819]

Feed is restricting access to TAC channels and Rescue to ER Calls in archive like it should but appears to be broadcasting them live. How do I fix this without shutting down feed?

 

[buddrousa]

Would blocking those TG's at the receiving equipment be an option?

 

[georgew0819]

I'm using trunk recorder on a linux system fed by several rtl sdr's so doing so removing those talkgroups from the configuration file would prevent me from hearing them. What I may do if this can't be fixed is pull the feed and dedicate another machine or scanner with only the 4 dispatch talkgroups listed. But based on what I had been reading on the calls platform the system was supposed to automatically lockout sensitive tgs so only the feed provider or admin could hear them.

 

[buddrousa]

So your options might be run 2 systems 1 for feeds and 1 for personal use.

 

[GTR8000]

I just checked your node's live calls, and I see a few calls on the NHRCM ER talkgroup, so they are definitely getting through.

There might be a glitch with the filtering, I'm going to reach out to Lindsay about it now.

 

[georgew0819]

I just checked your node's live calls, and I see a few calls on the NHRCM ER talkgroup, so they are definitely getting through.

There might be a glitch with the filtering, I'm going to reach out to Lindsay about it now.

Thanks for helping verify there is an issue hopefully I can get it sorted out so the feed can stay up.

 

[GTR8000]

By the way, this appears to be widespread, not just your feed. I wouldn't worry about it at the moment, nothing you can do on your end to fix it aside from stopping the decoding of those talkgroups. Since you're not responsible for the filtering on the Calls pages, you're not doing anything wrong here.

By the way, does Trunk-Recorder not allow you to specify which talkgroups get sent to BCFY Calls, independent of what you decode/record locally? It's all or nothing in the config file? That's odd, as other software allows you to specify which talkgroups you want to broadcast, without affecting the local playback/recording of those talkgroups. SDRTrunk, for example, has separate flags for Listen, Record, Stream, which makes it very flexible.

 

[georgew0819]

Just started with trunk recorder since it used less resources than unitrunker and trunking recorder in windows. I'll have to look into it some more and see if there is some setting with the api key I can do locally to only send certain tg's short of redoing the configuration file.

 

[GTR8000]

You may also want to check out SDRTrunk.

 

[blantonl]

You've always been able to see them in a node live view... and even listen.

They are currently filtered at an individual level (you can't choose a non-TOS talkgroup or review archives). I get that someone could open a node live view, and hold on one of those talkgroups if it appeared in the live list but it is pretty hard and it's an extremely edge case. I'm aware of it and looking at a solution.

 

[georgew0819]

@GTR8000 , @blantonl I'll check that out, one thing I like about Trunk-Recorder is it assigns a recorder for each channel in the system which means even when one channel is active and your listening to the call the other channels are still recording so no calls are missed unlike when using my BCD325P2 where it may be listening to one talk group and I miss others which may be transmitting at the same time. The idea that the TAC channels and ER Channel can be heard on the Live Node whether a person is the feed provider or not bothers me a little, so if I can't work out something with the config.json I may switch over to a normal Broadcastify feed using the scanner with only the 4 dispatch tgs. Years ago I used to provide a feed for RI which seemed a lot easier. Plug the scanner in to the computer and just lock out the channels you didn't want going to the feed. With these SDR setups although they work better there is more of a learning curve so I probably should have the grandkids look over my work since they know computers better now than I do.

 

[blantonl]

If you create a talkgroups CSV file for trunk-recorder and assign a talkgroup with a priority of 100 it won't be recorded - that's one way to filter talkgroups in trunk-recorder.

HOWEVER, I would strongly recommend that you send EVERYTHING you can up to Broadcastify Calls - mainly for your own sake and use, since you'll always have complete a full access to everything you send up.

 

[edweirdFL]

Any issues with setting full time encrypted groups to 100 priority, to avoid CPU cycles recording and transferring them?

Sure the SRC and usage stats won't accumulate, but for a RPI based calls node, it might run better. Thoughts?