Broadcastify Calls and Unknown Talkgroups

[Cortexian]

I just expanded my contribution from a single department feed to contributing an entire site's calls to the Calls Platform.

Right now I am only broadcasting the known and documented talkgroups from the Radio Reference database.

Should I also broadcast all of the unknown talkgroups so the community can work on identifying them and we can get the database updated? Or should the Calls Platform be limited to just known talkgroups for a clean experience for listeners?

 

[Deziel0495]

Should I also broadcast all of the unknown talkgroups so the community can work on identifying them and we can get the database updated? Or should the Calls Platform be limited to just known talkgroups for a clean experience for listeners?

The choice is yours. Providing all calls and not just known calls does make it easier to identify unknown talkgroups for anyone who may be listening.

 

[RaleighGuy]

I just expanded my contribution from a single department feed to contributing an entire site's calls to the Calls Platform.

Right now I am only broadcasting the known and documented talkgroups from the Radio Reference database.

Should I also broadcast all of the unknown talkgroups so the community can work on identifying them and we can get the database updated? Or should the Calls Platform be limited to just known talkgroups for a clean experience for listeners?

Broadcastify Calls Platform will filter the talkgroups out that don't belong, send everything to provide the best listener experience.

 

[Cortexian]

Broadcastify Calls Platform will filter the talkgroups out that don't belong, send everything to provide the best listener experience.

Hmm, could you elaborate? Calls shouldn't be removing anything if I send it all. Everything I send "belongs".

 

[RaleighGuy]

Hmm, could you elaborate? Calls shouldn't be removing anything if I send it all.

Calls filter out any TG that isn't allowed from the general listeners (not for the feeder) for example TAC TGs, among others. Calls Platform falls under the same rules as a regular feed, only the prohibited TGs are filtered by Broadcastify/RR rather than by the listener.

 

[Cortexian]

Calls filter out any TG that isn't allowed from the general listeners (not for the feeder) for example TAC TGs, among others. Calls Platform falls under the same rules as a regular feed, only the prohibited TGs are filtered by Broadcastify/RR rather than by the listener.

Ah okay that part makes sense, all prohibited TGs that Broadcastify specifies have been encrypted since the beginning on this system so I've never had to worry. Anything in the clear here is in the clear for Broadcastify hence "everything I send belongs".

Edit: I would assume that if I send unknown TGs through and the somehow include new/unencrypted TGs for prohibited categories, there would be some grace until the TG is identified as such?

 

[mtindor]

Ah okay that part makes sense, all prohibited TGs that Broadcastify specifies have been encrypted since the beginning on this system so I've never had to worry. Anything in the clear here is in the clear for Broadcastify hence "everything I send belongs".

Edit: I would assume that if I send unknown TGs through and the somehow include new/unencrypted TGs for prohibited categories, there would be some grace until the TG is identified as such?

Let me make it easy on you. I've been sending EVERY transmission from our local county simulcast (which includes quite a bit of traffic from neighboring counties) via BCFY CALLS. No issues. Once talkgroups are identified and added to the DB, casual BCFY CALLS listeners will not hear the calls that are prohibited by TOS -- but you will still see/hear them in your personal dashboard feed for your particular node.

Send everything you can, encrypted, not encrypted, tac, talk, whatever. It'll be sorted out on RR's end so that the casual listener does not have access to that which they should not have access to.

Of course, you only want to send calls for the node you specified. You don't want to capture 10 sites in SDRTrunk and send the calls from all of those up to one single node. Each site should have its own node. Of course simulcasts are different since the simulcast IS a single "site" as far as a BCFY Node goes.