Carissa Vixen

This looks identical to the issue I'm experiencing all the time on my install (dupsc21 on openmhz) - I'll check the logs for a definitive overlapping call period and post...

Okay, found a call this afternoon that contains the glitch. Here's the logs of that call. Specifically, Unit ID 1106852 should not be in the TG 2607 file - that's...

Ok, had to switch from a basic Docker install to a local build. I'm now running with the `debug-overlap` changes applied. I don't see `TG Mismatch` in the code changes,...

Ok, `debug-overlap` Take 2 is running - definitely seeing a lot of "TG MISMATCH", even with `"callTimeout": 1` [log_snippet.txt](https://github.com/robotastic/trunk-recorder/files/7361363/log_snippet.txt)

Okay, running again: just a handful of `TG MISMATCH` when I first started up the new copy, haven't seen any again (yet, only running for about 5 minutes). I still...

Not crazy, I'm seeing duplicates as well. I'm kinda wondering if the code change to better detect frequency re-use at the end of a call is unintentionally starting extra recorders.