Error(?) Message Question

[kevino]

Sometimes I can access recordings of trunked system talkgroups that haven't yet been added to the RR database (info not yet confirmed, etc.) by selecting the link for an active TG on the system and then substituting the TG number at the end of the URL with the number of the 'new' TG. Sometimes, I'll get a message that says the talkgroup is not in the database. Other times, I get a message that says "This Group ID can only be accessed by system broadcaster or an admin".

This seems to indicate that some recordings can only be accessed by the system broadcaster or an admin. Is that the case? And if so, why would certain recordings be restricted?

Thanks!

 

[n0esc]

Traffic that is fed into the system via the Calls system can/should be all possible talkgroups on a system vs being restricted to not broadcasting tactical channels and such on the traditional feeds. Depending on the service tag for a talkgroup in the database the calls are filtered on the server side, and restricted to people providing Calls uploads, so as a node provider you can listen to tactical and restricted traffic while a normal subscriber will not be able to do so.

 

[kevino]

Traffic that is fed into the system via the Calls system can/should be all possible talkgroups on a system vs being restricted to not broadcasting tactical channels and such on the traditional feeds. Depending on the service tag for a talkgroup in the database the calls are filtered on the server side, and restricted to people providing Calls uploads, so as a node provider you can listen to tactical and restricted traffic while a normal subscriber will not be able to do so.

If traffic is unencrypted, why would it be held back from Broadcastify listeners?

 

[n0esc]

For the same reason that traditional feeds cannot broadcast any of the following:

Feed Providers are not allowed to broadcast:
"SWAT type" operations if on channels or talkgroups dedicated to those operations
Narcotics / CID / Investigations or other tactical operations on channels or talkgroups dedicated to those operations
Dedicated channels or talkgroups for Ambulance to Hospital Communications
Dedicated Federal Government or Military Communications (exceptions include any fire fighting operations, NASA space communications, park ranger operations)
Any commercial service broadcast (FM/AM/TV etc)
Music or talk show of any kind (commercial or non-commercial)
DJ or other type of similar activity (commercial or non-commercial)
Open Microphones

As you can see here in the Calls ToS, that does not apply to providers.

Broadcastify-Calls - The RadioReference Wiki

wiki.radioreference.com

It's a perk of sorts, limiting Broadcatifys liability from streaming sensitive information while allowing the providers to listen to the content they could hear anyways as they are the one supplying it.

 

[kevino]

For the same reason that traditional feeds cannot broadcast any of the following:

Feed Providers are not allowed to broadcast:
"SWAT type" operations if on channels or talkgroups dedicated to those operations
Narcotics / CID / Investigations or other tactical operations on channels or talkgroups dedicated to those operations
Dedicated channels or talkgroups for Ambulance to Hospital Communications
Dedicated Federal Government or Military Communications (exceptions include any fire fighting operations, NASA space communications, park ranger operations)
Any commercial service broadcast (FM/AM/TV etc)
Music or talk show of any kind (commercial or non-commercial)
DJ or other type of similar activity (commercial or non-commercial)
Open Microphones

As you can see here in the Calls ToS, that does not apply to providers.

Broadcastify-Calls - The RadioReference Wiki

wiki.radioreference.com

It's a perk of sorts, limiting Broadcatifys liability from streaming sensitive information while allowing the providers to listen to the content they could hear anyways as they are the one supplying it.

Thanks for the explanation.