Calls - Security/Event Ops on City Simulcast broadcasting allowed?

[SpectralContent]

The Broadcastify terms of service clearly dictate that broadcasting private businesses (including private security) is not allowed. No question there. However, could city (or county) funded security/patrol/event access services that use talkgroups on the city/county simulcast system be acceptable to publicly broadcast?

For example, I recently found a talkgroup for Baltimore City, 9281 - City Asset Patrol, that does routine patrols of city-owned properties. They are not law enforcement officers, but are not a private business either. They are using the city's simulcast system and are apart of the city's services as far as I have gathered (one being the Housing Authority of Baltimore City). However, since it was classified as a Security TG on the RRDB, it is not allowed to be publicly viewable on the calls platform.

I am assuming this Security classification on the DB assumes this TG to be a private security entity? Or is any security/festival event ops considered against the TOS, even if it is on a city/county system?

I'm not sure how many people would really be interested in listening to these sorts of TGs, but just curious for clarification. Thanks!

 

[blantonl]

It's based on the service tag of the talkgroup. That's it.

Here how it breaks down in Broadcastify Calls

| Multi-Dispatch |           1 |
| Law Dispatch   |           1 |
| Fire Dispatch  |           1 |
| EMS Dispatch   |           1 |
| Multi-Tac      |           1 |
| Law Tac        |           0 |
| Fire-Tac       |           1 |
| EMS-Tac        |           1 |
| Interop        |           1 |
| Hospital       |           0 |
| Ham            |           1 |
| Public Works   |           1 |
| Aircraft       |           1 |
| Federal        |           0 |
| Business       |           0 |
| Railroad       |           1 |
| Other          |           0 |
| Multi-Talk     |           1 |
| Law Talk       |           0 |
| Fire-Talk      |           1 |
| EMS-Talk       |           1 |
| Transportation |           1 |
| Emergency Ops  |           1 |
| Military       |           0 |
| Media          |           0 |
| Schools        |           0 |
| Security       |           0 |
| Utilities      |           1 |
| Data           |           0 |
| Deprecated     |           0 |
| Corrections    |           0 |
+----------------+-------------+

 

[SpectralContent]

It's based on the service tag of the talkgroup. That's it.

Here how it breaks down in Broadcastify Calls

| Multi-Dispatch |           1 |
| Law Dispatch   |           1 |
| Fire Dispatch  |           1 |
| EMS Dispatch   |           1 |
| Multi-Tac      |           1 |
| Law Tac        |           0 |
| Fire-Tac       |           1 |
| EMS-Tac        |           1 |
| Interop        |           1 |
| Hospital       |           0 |
| Ham            |           1 |
| Public Works   |           1 |
| Aircraft       |           1 |
| Federal        |           0 |
| Business       |           0 |
| Railroad       |           1 |
| Other          |           0 |
| Multi-Talk     |           1 |
| Law Talk       |           0 |
| Fire-Talk      |           1 |
| EMS-Talk       |           1 |
| Transportation |           1 |
| Emergency Ops  |           1 |
| Military       |           0 |
| Media          |           0 |
| Schools        |           0 |
| Security       |           0 |
| Utilities      |           1 |
| Data           |           0 |
| Deprecated     |           0 |
| Corrections    |           0 |
+----------------+-------------+

Got it. Thanks!

 

[Reconrider]

It's based on the service tag of the talkgroup. That's it.

Here how it breaks down in Broadcastify Calls

Spoiler

| Multi-Dispatch |           1 |
| Law Dispatch   |           1 |
| Fire Dispatch  |           1 |
| EMS Dispatch   |           1 |
| Multi-Tac      |           1 |
| Law Tac        |           0 |
| Fire-Tac       |           1 |
| EMS-Tac        |           1 |
| Interop        |           1 |
| Hospital       |           0 |
| Ham            |           1 |
| Public Works   |           1 |
| Aircraft       |           1 |
| Federal        |           0 |
| Business       |           0 |
| Railroad       |           1 |
| Other          |           0 |
| Multi-Talk     |           1 |
| Law Talk       |           0 |
| Fire-Talk      |           1 |
| EMS-Talk       |           1 |
| Transportation |           1 |
| Emergency Ops  |           1 |
| Military       |           0 |
| Media          |           0 |
| Schools        |           0 |
| Security       |           0 |
| Utilities      |           1 |
| Data           |           0 |
| Deprecated     |           0 |
| Corrections    |           0 |
+----------------+-------------+

Just wondering how does this work when the talkgroup isn't entered into the DB yet?

Is that talkgroup only allowed to be heard from the uploader, or admins?

 

[SpectralContent]

Just wondering how does this work when the talkgroup isn't entered into the DB yet?

Is that talkgroup only allowed to be heard from the uploader, or admins?

Yes, you are correct. You can send any talkgroup to your own calls node. All unentered, or even DB entered TGs that are not able to be publicly broadcast can still be accessed on your own. I personally like sending TGs I'm trying to identify to the calls node as it is much easier to view activity on there than via recordings from SDRTrunk.

 

[GTR8000]

Unknown talkgroups (i.e. those not in the RRDB) are publicly accessible. This is done for the express purpose of allowing them to be identified by way of listening to the audio. Of course once identified and added to the RRDB, they may disappear based on the service tag.

 

[Reconrider]

Yes, you are correct. You can send any talkgroup to your own calls node. All unentered, or even DB entered TGs that are not able to be publicly broadcast can still be accessed on your own. I personally like sending TGs I'm trying to identify to the calls node as it is much easier to view activity on there than via recordings from SDRTrunk.

Unknown talkgroups (i.e. those not in the RRDB) are publicly accessible. This is done for the express purpose of allowing them to be identified by way of listening to the audio. Of course once identified and added to the RRDB, they may disappear based on the service tag.

Perfect. I had a feeling this was the case GTR but I wasn't to sure. Thanks for explaining.