Of course. This system is highly complex with a lot of moving parts. We gotta dial it in....
Broadcastify Calls Duplicate Calls Handing Updates
- Thread starter blantonl
- Start date
Not sure if any changes have been made yet on your end but in the past 45 minutes there were 3 EMS dispatches. Only one of them contained the voice part that comes after the beep.
Also a new issue I’m coming across now that we’re relying on someone else’s ingest: Either he has a weak signal or just poor decoding because some of the transmissions have syllables that are completely garbled or missing. I compared those particular transmissions back to my files I upload to rdio scanner and mine aren’t garbled. I know the process for selecting whose ingest to use is based on measurable things like latency, uptime, etc but it would be nice if users can report when those feeds don’t provide decent audio. Maybe if enough reports consistently come through it can get flagged for manual review of those particular transmissions.
Thank you!
Also a new issue I’m coming across now that we’re relying on someone else’s ingest: Either he has a weak signal or just poor decoding because some of the transmissions have syllables that are completely garbled or missing. I compared those particular transmissions back to my files I upload to rdio scanner and mine aren’t garbled. I know the process for selecting whose ingest to use is based on measurable things like latency, uptime, etc but it would be nice if users can report when those feeds don’t provide decent audio. Maybe if enough reports consistently come through it can get flagged for manual review of those particular transmissions.
Thank you!
I had done some tweaks but let me tweak it a little further. I just rolled another "turn of the dial" to see if that helps. Let me know.
You can report a problem node to the owner. Bring up the node's page and click "report a problem" and send them a problem report.
You can report a problem node to the owner. Bring up the node's page and click "report a problem" and send them a problem report.
Any updates on the status of the API? I know it's a work in progress and coming soon. Looking forward to it!
It's been released, but right now it's only available to our existing partners right now.
I haven't decided how we might take it to market otherwise.
I haven't decided how we might take it to market otherwise.
Any idea when you might open up API access to new apps? Speaking as an iOS dev, a lot of the existing apps look like they haven’t been updated since iOS 7.
Our top partner's apps are updated all the time.
I have issues with the feeds that I'm providing duplicating calls in my county because dispatch sometimes patches EMS and Rescue talkgroups together and its causing the same message to be uploaded twice but on different talkgroups
Ok, which system, what talkgroups are being duplicated? Need some clear concrete examples and more info here.
also, which talk groups are “primary” vs secondary when patched?
also, which talk groups are “primary” vs secondary when patched?
Ok- interesting issue here with patched/duplicates- MPSCS takgroup paging.
Pagegroups are forced to always transmit at certain sites at a system level. Often there are no radios affiliated with the pagegroup. It exists only for Unication pagers to receive. This pagegroup is multiselected (patched) to the dispatch talkgroup. So, several sites will see that one transmission on both the pagegroup and dispatch talkgroup. Subsequent dispatch talkgroup traffic only goes where a radio is affiliated with the dispatch talkgroup. If the calls platform assigns the dispatch talkgroup to a node covering a site that a radio is not affiliated to, no further transmission will be captured.
Pagegroups are forced to always transmit at certain sites at a system level. Often there are no radios affiliated with the pagegroup. It exists only for Unication pagers to receive. This pagegroup is multiselected (patched) to the dispatch talkgroup. So, several sites will see that one transmission on both the pagegroup and dispatch talkgroup. Subsequent dispatch talkgroup traffic only goes where a radio is affiliated with the dispatch talkgroup. If the calls platform assigns the dispatch talkgroup to a node covering a site that a radio is not affiliated to, no further transmission will be captured.
As long as the dispatch TG is on the scanlist, the traffic should be picked up via another node. (If I understand the structure of the calls platform correctly.)
If I understand it, yes, it will. But it can take a while for the platform to recognize and re-assign the talkgroup to another node. I think I read somewhere it could take 15 minutes, but don't quote me on that. unfortunately, a lot can be missed in the first 15 min of an incident.
Similar threads
