Search results

Thank you. I've added it.

I've noticed on TAFL some frequency changes for a lot of sites on the MPSRN. I find it strange they're making changes after the system in PEI has been online for 9 years. Two PEI sites completely changed their frequency line up (Stanhope and Borden). The other 14 were untouched. Noticed a lot...

I know nothing about it, but I'm assuming they're following suit with NS and PEI with a DMR Tier 3 Capacity Max trunking system. Just a guess, but I'd start there.

Ours didn't need any programming. Best to try it and see if it works.

On the main Broadcastify website, this is true. Except anyone has the ability to generate "Listener Alerts" for any feed using the ScannerRadio mobile app. I believe these are based on the number of listeners and may require reports from multiple listeners to show up. AFAIK these "alerts" are...

It's actually pretty straight forward for the XTL 1500 and CM200 Models. XTL to CM200 Pin 13 ACT to pin 3 PTT Pin 21 RX to pin 2 MIC Pin 14 GRD to pin 7 GRD CM200 to XTL 1500 Pin 11 RX to pin 23 MIC Pin 8 COS to pin 16 PTT

Feel free to submit these to the database and I can get them added. RadioReference Login

Note the above link is to setup a traditional feed and not for the calls system. Calls requires a Software Defined Radio (SDR) and software to operate it such as SDRTrunk, but there is other software available. Broadcastify-Calls - The RadioReference Wiki

You could try contacting the provider through the "Report a Problem" button. For problem type, just choose "Other".

I use SDRTrunk as well but the system I monitor is not simulcast, so the traffic on my local site is minimal. Sometimes it can be hours between transmissions, especially on evenings and weekends.

I send everything I'm capable of receiving, because even if someone else sends duplicate talkgroups, the calls system will filter it and choose the best provider. Then if a node goes down, there is a backup.

Feel free to submit these to the database. I can get them added.

If streaming from SDRTrunk, you don't need virtual audio cables. You create your playlist, and select what you'd like from the playlist to go to your stream(s). SDRTrunk does the rest. You can send playlist items to different streams if you'd like. Back when I had a regular feed, I sent...

Only active nodes are listed on the nodes page, which is why you don't see it. But to find out which node a talkgroup was captured on, select the magnifying glass and it will show you more details, including the ID of the node that captured it. Video: Watch 2024-03-07 17-54-08 | Streamable

You can. The node providing calls to SEGARRN can be found here and there is a button to report a problem. Node 1986: Southeast Georgia Regional Radio Network (SEGARRN) (Site: Bulloch County Simulcast) - Live

Broadcastify Calls (Broadcastify Calls) and live audio feeds (Broadcastify - Listen Live to Police, Fire, EMS, Aviation, and Rail Audio Feeds) are two separate systems and are not connected in any way. Navigating to the county you pictured on the calls platform, last activity on most talkgroups...

Similar to regular feeds, calls nodes are provided by volunteers. Many reasons why it could be no longer available. I'm not seeing any nodes in the list sending to SEGARRN, so it could be offline for technical reasons or the provider stopped sending calls for whatever reason.

These would mostly be input frequencies for the tower sites, vehicle repeaters and could also be for simplex if the radio(s) are programmed for it. Someone with a more in-depth background can likely provide a better explanation.

If you're referring to the changes to the NB Fire category... A user submitted some changes and after adding them to the database and upon further discussion, the person realized they made a mistake with 1 entry (confused it for another that was already in the database). Normally a talkgroup or...

Had activity back in early December on 48308-312. No voice just registrations. Likely someone spinning the channel knob. Will assume these are EMO Ops 1 thru 5 but will have to monitor for confirmation. I'm assuming EMO OPS 48300 will likely be used for interoperability with EMO and 48308-12...