Open DarthXoc opened 1 year ago
I just added rdio-scanner along side my existing trunk-recorder server (Ubuntu Server 20.04) and configured rdio-scanner for DirWatch. Seeing the same behavior described here.
Log file during parsing indicates: 2023/08/12 18:06:06 dirwatch.ingest: no system, /home/n7qob/psern/2023/8/12/2327-1691863556_853525000.1-call_60917.json
Contents of JSON file: cat /home/n7qob/psern/2023/8/12/2327-1691863556_853525000.1-call_60917.json { "freq": 853525000, "start_time": 1691863557, "stop_time": 1691863557, "emergency": 0, "priority": 4, "mode": 0, "duplex": 0, "encrypted": 0, "call_length": 0, "talkgroup": 2327, "talkgroup_tag": "RetPD Pri", "talkgroup_description": "Police Primary", "talkgroup_group_tag": "Law Dispatch", "talkgroup_group": "Renton", "audio_type": "digital tdma", "short_name": "psern", "freqList": [ {"freq": 853525000, "time": 1691863557, "pos": 0.00, "len": 0.44, "error_count": "0", "spike_count": "0"} ], "srcList": [ {"src": 12983, "time": 1691863557, "pos": 0.00, "emergency": 0, "signal_system": "", "tag": ""} ] }
Does it need to parse system from the file name format or from the JSON file. I don't see system in either. This is a P25 trunked setup. I do see a param signal_system under srcList but its null.
Latest release version of both trunk-recorder (4.6.0) and rdio-scanner (6.6.3)
Summary
After setting up a Dirwatch on trunk-recorder's capture directory, Rdio Scanner begins displaying errors saying "dirwatch.ingest: no system".
rdio-scanner config
Version: 6.6.3
Dirwatch
System (Frisco)
System (Denton)
trunk-recorder
Version: 4.4.0
Config
Including trunk-recorder config below. System is operational, but I wanted to include it for reference-
Example
(forgive the file structure, that'll be getting cleaned up when I'm done building my next scanner)