Broadcastify Calls Platform - TG limits/filtering by site?

n0nhj · Jan 7, 2023

Good Day:
I put up a few of TrunkRecorder sites this past fall. Those are monitoring DTRS sites at high locations, that routinely cover traffic from several counties.
Just this morning, I was monitoring the actual log for the unit monitoring the Colorado DTRS site in SE Utah on Abajo Peak, I'm seeing & hearing traffic from both Dolores County SO (3670) and San Miguel County SO (8561) dispatch TG's but when ever TrunkRecorder tries to upload those files it's getting a 502 bad gateway error & broadcastify_uploader failed messages.

In looking through the Calls Platform, I don't see that the Dolores SO TG has ever been captured on the Calls Platform, yet the Abajo site is their primary coverage, and over the past 3 months that I've been running TrunkRecorder for that that site, I'm sure there have been many hundred if not thousands of transmissions on that TG.
Looking through the list of the captured talk groups for my TR site, it's only showing State Patrol and CDOT traffic, and no local TG's at all. Both of these TGs I've mentioned are listed as Law Dispatch in the RR Database so it shouldn't be a limitation on the tactical channels.

So is the Calls Platform doing some filtering of what Talkgroups it accepts based on the site that was signed up?

Thanks
Chuck

Below is an example of one entry from TR

[2023-01-07 10:18:25.312473] (info) [CDTRS] 6C TG: 3670 Freq: 8.529750e+08 Starting P25 Recorder Num [0] TDMA: false Slot: 0 QPSK: true
[2023-01-07 10:18:27.495781] (info) [CDTRS] 6C TG: 3670 Freq: 8.529750e+08 Unit ID set via Control Channel, ext: 276334 current: -1 samples: 0
[2023-01-07 10:18:37.930907] (info) [CDTRS] 6C TG: 3670 Freq: 8.529750e+08 Unit ID set via Control Channel, ext: 276306 current: -1 samples: 0
[2023-01-07 10:18:44.017938] (info) [CDTRS] 6C TG: 3670 Freq: 8.529750e+08 Concluding Recorded Call_impl - Last Update: 4s Call_impl Elapsed: 19
[2023-01-07 10:18:44.018096] (info) [CDTRS] 6C - Stopping P25 Recorder Num [0] TG: 3670 Freq: 8.529750e+08 TDMA: false Slot: 0 Hz Error: -19 51
[2023-01-07 10:18:44.018283] (info) [CDTRS] 6C TG: 3670 Freq: 8.529750e+08 - Transmission src: 276306 pos: 0 length: 1.08
[2023-01-07 10:18:44.018388] (info) [CDTRS] 6C TG: 3670 Freq: 8.529750e+08 - Transmission src: 276334 pos: 1.08 length: 8.46
[2023-01-07 10:18:44.018548] (info) [CDTRS] 6C TG: 3670 Freq: 8.529750e+08 - Transmission src: 276306 pos: 9.54 length: 2.16
[2023-01-07 10:18:44.484820] (error) [CDTRS] TG: 3670 Freq: 8.529750e+08 Broadcastify Metadata Upload Error: <html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
</body>
</html>
[2023-01-07 10:18:44.485167] (error) Plugin Manager: call_end - broadcastify_uploader failed

n0nhj · Jan 7, 2023

And just captured this - 8025 which is a stat DOT TG was uploaded successfully, followed 13 seconds later by the Dolores SO Dispatch TG that appears to have been rejected.

[2023-01-07 10:50:14.008522] (info) [CDTRS] 13C TG: 8025 Freq: 8.529750e+08 - Transmission src: 247501 pos: 0 length: 2.7
[2023-01-07 10:50:14.008670] (info) [CDTRS] 13C TG: 8025 Freq: 8.529750e+08 - Transmission src: 241752 pos: 2.7 length: 1.26
[2023-01-07 10:50:14.008772] (info) [CDTRS] 13C TG: 8025 Freq: 8.529750e+08 - Transmission src: 247501 pos: 3.96 length: 2.7
[2023-01-07 10:50:14.008871] (info) [CDTRS] 13C TG: 8025 Freq: 8.529750e+08 - Transmission src: 241752 pos: 6.66 length: 10.62
[2023-01-07 10:50:14.008969] (info) [CDTRS] 13C TG: 8025 Freq: 8.529750e+08 - Transmission src: 247501 pos: 17.28 length: 19.98
[2023-01-07 10:50:14.009070] (info) [CDTRS] 13C TG: 8025 Freq: 8.529750e+08 - Transmission src: 241752 pos: 37.26 length: 14.4
[2023-01-07 10:50:14.009175] (info) [CDTRS] 13C TG: 8025 Freq: 8.529750e+08 - Transmission src: 247501 pos: 51.66 length: 9.9
[2023-01-07 10:50:14.009278] (info) [CDTRS] 13C TG: 8025 Freq: 8.529750e+08 - Transmission src: 241752 pos: 61.56 length: 5.76
[2023-01-07 10:50:14.009378] (info) [CDTRS] 13C TG: 8025 Freq: 8.529750e+08 - Transmission src: 247501 pos: 67.32 length: 0.72
[2023-01-07 10:50:15.518839] (info) [CDTRS] TG: 8025 Freq: 8.529750e+08 Broadcastify Upload Success - file size: 414895
[2023-01-07 10:50:28.303260] (info) [CDTRS] 14C TG: 3670 Freq: 8.529750e+08 Starting P25 Recorder Num [0] TDMA: false Slot: 0 QPSK: true
[2023-01-07 10:50:32.459260] (info) [CDTRS] 14C TG: 3670 Freq: 8.529750e+08 Unit ID set via Control Channel, ext: 276306 current: -1 samples: 0
[2023-01-07 10:50:34.529248] (info) [CDTRS] 14C TG: 3670 Freq: 8.529750e+08 Unit ID set via Control Channel, ext: 276363 current: -1 samples: 0
[2023-01-07 10:50:38.573001] (info) [CDTRS] 14C TG: 3670 Freq: 8.529750e+08 Unit ID set via Control Channel, ext: 276306 current: -1 samples: 0
[2023-01-07 10:50:44.002600] (info) [CDTRS] 14C TG: 3670 Freq: 8.529750e+08 Concluding Recorded Call_impl - Last Update: 4s Call_impl Elapsed: 16
[2023-01-07 10:50:44.003010] (info) [CDTRS] 14C - Stopping P25 Recorder Num [0] TG: 3670 Freq: 8.529750e+08 TDMA: false Slot: 0 Hz Error: -1929
[2023-01-07 10:50:44.003531] (info) [CDTRS] 14C TG: 3670 Freq: 8.529750e+08 - Transmission src: 276363 pos: 0 length: 2.16
[2023-01-07 10:50:44.003845] (info) [CDTRS] 14C TG: 3670 Freq: 8.529750e+08 - Transmission src: 276306 pos: 2.16 length: 1.26
[2023-01-07 10:50:44.004123] (info) [CDTRS] 14C TG: 3670 Freq: 8.529750e+08 - Transmission src: 276363 pos: 3.42 length: 2.16
[2023-01-07 10:50:44.004403] (info) [CDTRS] 14C TG: 3670 Freq: 8.529750e+08 - Transmission src: 276306 pos: 5.58 length: 1.62
[2023-01-07 10:50:44.442522] (error) [CDTRS] TG: 3670 Freq: 8.529750e+08 Broadcastify Metadata Upload Error: <html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
</body>
</html>
[2023-01-07 10:50:44.442702] (error) Plugin Manager: call_end - broadcastify_uploader failed

n0nhj · Jan 22, 2023

Found the problem - detailing here in case someone else finds this post with a similar problem.

My Talkgroups file was not formatted correctly. Once I deleted the talkgroups csv file, then all of the new talkgroups that had not been seen before started uploading correctly.

A correctly formated talkgroups csv file worked, and allowed even TGs that were not in the csv file, to upload correctly.

dpetrucc · Apr 11, 2023

n0nhj said:
Found the problem - detailing here in case someone else finds this post with a similar problem.

My Talkgroups file was not formatted correctly. Once I deleted the talkgroups csv file, then all of the new talkgroups that had not been seen before started uploading correctly.

A correctly formated talkgroups csv file worked, and allowed even TGs that were not in the csv file, to upload correctly.

I am experiencing the same issue currently and i have looked through my whole csv file and I can't seem to find anything that would be considered incorrect formatting. Could you elaborate on your findings?

n0nhj · Apr 11, 2023

I gave up, deleted my csv file (after copying it to another folder). It ran fine without any TG file, and then built a new one as it heard traffic.
Since these are remote sites running on a raspberry Pi, I don't need a file. I could never find what the problem with the file was.

dpetrucc · Apr 11, 2023

n0nhj said:
I gave up, deleted my csv file (after copying it to another folder). It ran fine without any TG file, and then built a new one as it heard traffic.
Since these are remote sites running on a raspberry Pi, I don't need a file. I could never find what the problem with the file was.

Thanks for the reply, i got mine fixed today. Did a full new install of the latest repo and used the radio reference formatted .csv and my issues were gone. Mine was just like your with only a few talkgroups having the issue just an fyi

Broadcastify Calls Platform - TG limits/filtering by site?

n0nhj

In way too deep...

n0nhj

In way too deep...

n0nhj

In way too deep...

dpetrucc

Newbie

n0nhj

In way too deep...

dpetrucc

Newbie

Similar threads