Excessive teardowns
376 views
Skip to first unread message
Kazzaw
Jun 20, 2021, 7:16:12 PM6/20/21
to sdrtrunk
Hi all,
20210617 091558.686 [sdrtrunk pool-1-thread-4] INFO i.g.d.s.t.FrequencyErrorCorrectionManager - Auto-Correcting Tuner PPM to [0.4] [1GB/1GB 79%]
I have been having issues with Teardown appearing in my SDRTrunk instance.
I 'could' potentially be demanding too much from SDRTrunk, however I have had this running previously for 48hrs with no teardowns appearing (about 2 weeks ago). I then took my system away with me for a week, and didn't fire up SDRTrunk for another week. This week I have been having issues consistently.
What I'm trying to do:
I have 4x RTL SDR dongles.
Dongle 1 is monitoring a TIII CC, 160MHz
Dongle 2 is monitoring 2 TIII CCs, 418MHz range
Dongle 3 is monitoring 2 TIII CCs, 463MHz range
Dongle 4 is monitoring a TIII CC, 506MHz range.
It is worth noting that Dongle 2 and 3 are monitoring the same system, just different sites. Duplicate calls are disabled (as there will be quite a few across these sites).
Dongle 1 and 4 have a general 'unknown' talkgroup recoding preference, and 2 and 3 have some TG's programmed in with a general blanket (TG Range 1-max) as unknown as well.
My issue according to the LSN/LCN appears to be coming from Dongle 3, as all the teardown channels have the matching LSN/LCN for that system.
I'm stuck at working out what could be causing these teardown issues (and even if teardown is an issue or can be ignored).
My logs contain lots of entries, however they are all one of these 4 lines
I 'could' potentially be demanding too much from SDRTrunk, however I have had this running previously for 48hrs with no teardowns appearing (about 2 weeks ago). I then took my system away with me for a week, and didn't fire up SDRTrunk for another week. This week I have been having issues consistently.
What I'm trying to do:
I have 4x RTL SDR dongles.
Dongle 1 is monitoring a TIII CC, 160MHz
Dongle 2 is monitoring 2 TIII CCs, 418MHz range
Dongle 3 is monitoring 2 TIII CCs, 463MHz range
Dongle 4 is monitoring a TIII CC, 506MHz range.
It is worth noting that Dongle 2 and 3 are monitoring the same system, just different sites. Duplicate calls are disabled (as there will be quite a few across these sites).
Dongle 1 and 4 have a general 'unknown' talkgroup recoding preference, and 2 and 3 have some TG's programmed in with a general blanket (TG Range 1-max) as unknown as well.
My issue according to the LSN/LCN appears to be coming from Dongle 3, as all the teardown channels have the matching LSN/LCN for that system.
I'm stuck at working out what could be causing these teardown issues (and even if teardown is an issue or can be ignored).
My logs contain lots of entries, however they are all one of these 4 lines
20210617 104024.376 [sdrtrunk pool-1-thread-2] DEBUG i.g.d.r.AudioRecordingManager - Audio Segment detected with NO TO identifiers [1GB/1GB 66%]
20210617 104027.042 [sdrtrunk pool-1-thread-1] INFO i.g.d.m.d.d.m.d.p.PacketSequenceMessageFactory - Unknown Packet SAP: UDP/IP HEADER COMPRESSION - returning unknown packet [955MB/1GB 50%]
20210617 104146.884 [sdrtrunk pool-1-thread-6] INFO i.g.d.m.d.d.m.d.p.PacketSequenceMessageFactory - Unknown Short Data Packet Header Type - creating unknown packet. [825MB/1GB 43%]
20210617 103021.515 [sdrtrunk pool-1-thread-1] INFO i.g.d.m.d.d.m.d.p.PacketSequenceMessageFactory - Unrecognized IP Packet Version: 7 - returning unknown packet [673MB/1GB 35%]
20210617 104027.042 [sdrtrunk pool-1-thread-1] INFO i.g.d.m.d.d.m.d.p.PacketSequenceMessageFactory - Unknown Packet SAP: UDP/IP HEADER COMPRESSION - returning unknown packet [955MB/1GB 50%]
20210617 104146.884 [sdrtrunk pool-1-thread-6] INFO i.g.d.m.d.d.m.d.p.PacketSequenceMessageFactory - Unknown Short Data Packet Header Type - creating unknown packet. [825MB/1GB 43%]
20210617 103021.515 [sdrtrunk pool-1-thread-1] INFO i.g.d.m.d.d.m.d.p.PacketSequenceMessageFactory - Unrecognized IP Packet Version: 7 - returning unknown packet [673MB/1GB 35%]
One entry of
20210617 091558.686 [sdrtrunk pool-1-thread-4] INFO i.g.d.s.t.FrequencyErrorCorrectionManager - Auto-Correcting Tuner PPM to [0.4] [1GB/1GB 79%]
Startup log also attached as text document
Jeff Chapman
Jun 22, 2021, 8:00:32 AM6/22/21
to sdrtrunk
Sorry, I have to ask; What is a teardown? Wile I'm at it; What is a "TIII" Control Channel? Thank You
rlm...@gmail.com
Jun 22, 2021, 10:30:21 AM6/22/21
to sdrtrunk
A search of this forum reveals..........
"Teardown is the channel state between when the call is ended and either a)the channel gets reset for the next call, or b) the channel gets removed."
Kazzaw
Jun 23, 2021, 1:39:11 AM6/23/21
to sdrtrunk
A TIII Control channel i am referring to as a DMR Tier 3 Control Channel
Austin Hruskach
Aug 22, 2021, 7:15:50 PM8/22/21
to sdrtrunk
I only get excessive teardowns when my CPU reaches max utilization. Its a bug that I noticed.
On Sunday, June 20, 2021 at 7:16:12 PM UTC-4 Kazzaw wrote:
jim...@gmail.com
Sep 14, 2021, 6:32:30 PM9/14/21
to sdrtrunk
I dont have a super computer and it runs great %99.9 percent of the time. I don't get them unless I try to open the Alias list when the system has 5-10 active channels going on at the same time.
OS Name Microsoft Windows 10 Pro
Version 10.0.19042 Build 19042
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP
System Manufacturer Acer
System Model Aspire Z24-890
System Type x64-based PC
Processor Intel(R) Core(TM) i5-9400T CPU @ 1.80GHz, 1800 Mhz, 6 Core(s), 6 Logical Processor(s)
Installed Physical Memory (RAM) 12.0 GB
Austin Hruskach
Sep 18, 2021, 10:59:47 AM9/18/21
to sdrtrunk
Same happens to me when I open Alias editor. I think it has to do with it fetching the Radio Reference database from online.
Reply all
Reply to author
Forward
0 new messages