We're announcing some new features are available on the backend of Broadcastify Calls. All of these features are managed and implemented by administrators only.
One of the most important uses for #2 will be the ability for us to create legacy audio feeds from sources that have a lot of backup (potentially lots of calls nodes) as well as less reliance on broadcasters to provide legacy feeds and instead send us everything via SDRs and we can manage the feeds from here.
Thanks!
- We now have the capability to turn a single Broadcastify Legacy feed(s) into a calls node. This means that we can send a feed to a calls group and have it populate individual calls there. This is ONLY appropriate where an audio feed is monitoring a single talkgroup or frequency. We've implemented this for a number of aviation feeds in Dallas County TX, as well as the main Los Angeles County Fire Department channels. You'll see they show up in calls now that can be assigned to playlists etc
- We now have the capability to create a legacy audio feed from a Broadcastify Calls playlist. This allows us to create legacy feeds coverage for areas that have great Broadcastify Calls coverage but no real regular feeds. We've deployed some stuff in the DFW metroplex where we don't have coverage for regular feeds for some of the larger agencies in that area. We also brought up a Boston Fire Department feed from the trunked system patches that are captured via Broadcastify Calls.
One of the most important uses for #2 will be the ability for us to create legacy audio feeds from sources that have a lot of backup (potentially lots of calls nodes) as well as less reliance on broadcasters to provide legacy feeds and instead send us everything via SDRs and we can manage the feeds from here.
Thanks!
Last edited: