scannerloser
im a loser, baby.
Summary: I re-installed Windows on one of my two main scanning machines, and so I also installed a newer version of SDRTrunk - Version 0.6.1-Beta-3. I found myself hearing traffic for a minute or two, sometimes 5, and then nothing. Silence. Meanwhile, in the other room I could hear traffic on the same network going steady. I look and noticed a bunch of errors:
"MAX TRAFFIC CHANNELS EXCEEDED" (Present on Events tab with no filters turned on)
The machine that was still decoding and scanning traffic on the same P25 network was running SDRTrunk 0.6.1-Beta-1 instead of a later version.
With a server that has multiple dongles, you may not notice any significant drop outs, because the exponential amount of bandwidth you have to absorb the stuck open channels is enough... however anyone running 1 or even 2 dongles will likely have noticed big chunks of missed calls and silence due to this weird issue. So far, I've only noted this condition on P25 networks, and code review appears to point to the P25 sections as likely culprits who's code was changed heavily between beta-1 and beta-2. Search engines (Google/DDG/Etc) are beginning to be filled with reports of this error popping up everywhere, because this is a real issue and a bunch of people are starting to feel the impacts. So far, this appears to be mostly P25 but if you're having this issue on another network I'd love to hear from you.
For anyone having this or other mysterious missing calls, I would strongly recommend that downgrading to v0.6.1-beta-1 be part of your testing process, because so far I've found it works and fixes 100% of the individuals I've helped with issues like this.
Hardware: RTL-SDR (Mine is v5 but this affects all versions and likely other dongles..)
Software Affected: 0.6.1-beta-2, 0.6.1-beta-3. 0.6.1-master AKA 0.6.1 (Final)
Software Not Affected: 0.6.1-beta-1 (https://github.com/DSheirer/sdrtrun...-1/sdr-trunk-windows-x86_64-v0.6.1-beta-1.zip)
Again, TL;DR if you're having issues that seemed to have come out of nowhere over the past few weeks/months or after a software update/Windows re-install, you might want to test downgrading your sdrtrunk to 0.6.1-beta-1 until this is acknowledged as an issue and resolved.
"MAX TRAFFIC CHANNELS EXCEEDED" (Present on Events tab with no filters turned on)
The machine that was still decoding and scanning traffic on the same P25 network was running SDRTrunk 0.6.1-Beta-1 instead of a later version.
With a server that has multiple dongles, you may not notice any significant drop outs, because the exponential amount of bandwidth you have to absorb the stuck open channels is enough... however anyone running 1 or even 2 dongles will likely have noticed big chunks of missed calls and silence due to this weird issue. So far, I've only noted this condition on P25 networks, and code review appears to point to the P25 sections as likely culprits who's code was changed heavily between beta-1 and beta-2. Search engines (Google/DDG/Etc) are beginning to be filled with reports of this error popping up everywhere, because this is a real issue and a bunch of people are starting to feel the impacts. So far, this appears to be mostly P25 but if you're having this issue on another network I'd love to hear from you.
For anyone having this or other mysterious missing calls, I would strongly recommend that downgrading to v0.6.1-beta-1 be part of your testing process, because so far I've found it works and fixes 100% of the individuals I've helped with issues like this.
Hardware: RTL-SDR (Mine is v5 but this affects all versions and likely other dongles..)
Software Affected: 0.6.1-beta-2, 0.6.1-beta-3. 0.6.1-master AKA 0.6.1 (Final)
Software Not Affected: 0.6.1-beta-1 (https://github.com/DSheirer/sdrtrun...-1/sdr-trunk-windows-x86_64-v0.6.1-beta-1.zip)
Again, TL;DR if you're having issues that seemed to have come out of nowhere over the past few weeks/months or after a software update/Windows re-install, you might want to test downgrading your sdrtrunk to 0.6.1-beta-1 until this is acknowledged as an issue and resolved.
