You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug Report: There seems to be a problem with the way SDR Trunk is Logging the OTA aliases for Harris systems in the log file. When an OTA is detected, SDR Trunk will Only log the OTA alias, not the associated RID. Im sure this is something Denny can look at. Ive tried turning on every type of logging, and they all output the same info.
Example: For this call event, "CO-5XLM" is the OTA Alias, but it does not show any RID associated with that entity. The RID of "CO-5XLM" is 5428088.
I see now that the RID is logged after the OTA Alias entry. It would be helpful if the RID and the OTA alias were on the same line, similar to how they are logged in the events tab.
Version: Latest Version V0.6.1 (FInal)
Bug Report: There seems to be a problem with the way SDR Trunk is Logging the OTA aliases for Harris systems in the log file. When an OTA is detected, SDR Trunk will Only log the OTA alias, not the associated RID. Im sure this is something Denny can look at. Ive tried turning on every type of logging, and they all output the same info.
Example: For this call event, "CO-5XLM" is the OTA Alias, but it does not show any RID associated with that entity. The RID of "CO-5XLM" is 5428088.
I see now that the RID is logged after the OTA Alias entry. It would be helpful if the RID and the OTA alias were on the same line, similar to how they are logged in the events tab.
Application Log: https://www.dropbox.com/scl/fi/srgnshsdk3jbwhn0vapoa/20241217_003203.726_0_Hz__call_events.log?rlkey=46hthz9ziflpkailkhmciodfi&dl=0
Desktop
- OS: Windows 10
- CPU Cores: 6 Cores
- RAM: 16GB
The text was updated successfully, but these errors were encountered: