Broadcastify Calls

KD0FEO

Wright County, MN
Feed Provider
Joined
Dec 21, 2008
Messages
49
Location
Cokato, MN
New calls uploader here. I’ve noticed that my software is picking up traffic from several counties, many of which already have multiple nodes uploading the same calls. Am I safe to disable those and focus primarily on my own sites area? Or should I just keep pumping everything, even if it feels like I’m adding unnecessary load to the system? I am noticing a lot of duplicate calls on my node, is this a concern? How do I remedy it? Any help for a new calls uploader is welcome.

1753655105509.png

On most of those overlapping calls, my node is marked as "Current [A]" which I don't understand, is that good or bad? I'm located a bit farther out and have less site traffic, so it appears my skew may be lower than the busier metro-area systems in the Twin Cities. Node in question: 4916 - Site in question: Sherburne - Wright Co. Simulcast (Wright County)
 

Enforcer52

Broadcastify, Calls Platform, Public Playlist
Feed Provider
Joined
Sep 4, 2023
Messages
801
Location
Lake Livingston, TX
I would not upload calls that are already being duplicated by others, just causes more overhead on the servers, and on your own system. 3,446 duplicate calls is a bit much. Personally I only upload calls that are not being uploaded by others. Just causing a lot of redundancy on the system, and benefits no one.
 

GTR8000

NY/NJ Database Guy
Database Admin
Joined
Oct 4, 2007
Messages
16,422
Location
BEE00
I would not upload calls that are already being duplicated by others, just causes more overhead on the servers, and on your own system. 3,446 duplicate calls is a bit much. Personally I only upload calls that are not being uploaded by others. Just causing a lot of redundancy on the system, and benefits no one.
Actually in this case redundancy is a good thing. If one nodes fails or goes offline, another node can pick up the slack. Lindsay designed BCFY Calls to specifically handle duplication of uploaded talkgroups for this very reason, so there is no need to concern yourself with the capacity of the servers.

Send it all and let BCFY sort it out. If one of the other nodes goes down and you stopped decoding some of those talkgroups, you may regret losing those archives.
 

Enforcer52

Broadcastify, Calls Platform, Public Playlist
Feed Provider
Joined
Sep 4, 2023
Messages
801
Location
Lake Livingston, TX
If there are several others already sending the same channels to Calls as the OP stated, then there really isn't a reason to send them again and get thousands of duplicate rejects.
 

KD0FEO

Wright County, MN
Feed Provider
Joined
Dec 21, 2008
Messages
49
Location
Cokato, MN
Actually in this case redundancy is a good thing. If one nodes fails or goes offline, another node can pick up the slack. Lindsay designed BCFY Calls to specifically handle duplication of uploaded talkgroups for this very reason, so there is no need to concern yourself with the capacity of the servers.

Send it all and let BCFY sort it out. If one of the other nodes goes down and you stopped decoding some of those talkgroups, you may regret losing those archives.
This is what I was looking for, I wasn't sure if I was doing something wrong by having duplicates. I'll keep pumping them in as long as I don't get in trouble! Also can you elaborate what the "Current [A]" means next to my node on the calls I upload?
 

GTR8000

NY/NJ Database Guy
Database Admin
Joined
Oct 4, 2007
Messages
16,422
Location
BEE00
Current [A] means Current, Assigned. In other words, that is the primary active node for any talkgroups it's sending to Calls.


Spend some time reading through that thread. A lot of discussion early on in the process, but will likely answer your questions. Pay attention mostly to Lindsay's posts, naturally.
 
Top