Simple Menu
Styled Menu
Next Menu

Trunking Recorder Custom Filename Import

Custom Filename Import lets Trunking Recorder import recorded .mp3 or .wav call files created by any program by splitting each filename and mapping the resulting sections to Trunking Recorder's call fields (Target ID, System ID, Call Date/Time, etc.). This is useful for pulling in recordings from third-party applications, as long as it encodes identifying information in the filename. You can create multiple profiles if you have more than one folder/naming pattern to import.

How matching works

  • Only .mp3 and .wav files in the profile's folder (and subfolders, if enabled) are picked up.
  • Matching files are imported oldest first, based on each file's last-write time.
  • If a file is still locked/being written to, Trunking Recorder waits 3 seconds and checks it again before skipping it for that pass; it will be picked up on a later pass once the recording is done.
  • Any Trunking Recorder field not supplied in the filename can be set to a static value.
  • If Call Date/Time can't be determined from the mapped segments, Trunking Recorder falls back to the file's last-write time.

To set up a Custom Filename Import profile

  1. In Trunking Recorder click the "File" menu item at the top and then select the "Configure" option.
  2. Click the "Call Import" tab, then click the "Custom" tab.
  3. Click the "Add profile" button.
  4. Enter a "Name" for the profile, the "Recordings Folder" where the files will be imported from (it must exist for the profile to save enabled), and check "Import Subfolders" if the files may be nested in subfolders.
  5. Set the "Split character" to the character your filenames use to separate segments. (Default is "_")
  6. Enter a real example filename in the "Sample filename" box. Trunking Recorder splits it live on the "Split character" and lists each resulting piece as a row (with its "Sample value") in the segments list below.
  7. For each row, use the "Maps to" dropdown to choose which field that segment represents: Target ID, Target Label, Source ID, "(Not mapped)", etc.
  8. For any segment mapped to Call Date or Time, fill in the "Date/Time Format" box for that row with the matching .NET date/time format (Example: "yyyyMMdd" for a date segment, "HHmmss" for a time segment).
  9. The "Target ID & Label (ID-Label)" and "Source ID & Label (ID-Label)" mappings are for a single segment that contains both values separated by a "-", they split on the first "-" only, so the label itself may still contain "-" characters.
  10. In the "Fixed values" section, click "Add fixed value" for any field that never appears in the filename, such as System ID. Choose the "Field" and enter the "Value".
  11. Check the "Preview" box at the bottom of the profile, it shows the Target/Source/System/Start values Trunking Recorder will read from the current "Sample filename" so you can confirm the mapping is correct before saving.
  12. Check the "Enable" checkbox for the profile in the "Profiles" list, then click the "Save" button. "Target ID" and "System ID" must each be satisfied by a mapped segment or a fixed value before an enabled profile can be saved.
  13. Click the "Start Recording" button if not already started, Trunking Recorder will begin importing matching files from the folder.
    14. Trunking Recorder Custom Filename Import configuration screen

Example

A filename like 12345_PoliceDispatch_20260813_180020.wav split on "_" produces four segments: "12345", "PoliceDispatch", "20260813", "180020". You could map segment 1 to Target ID, segment 2 to Target Label, segment 3 to Call Date with Format "yyyyMMdd", and segment 4 to Call Time with Format "HHmmss", then add a fixed value mapping System ID to your system's ID.

Optional: alert if no calls are imported

Check the "Alert if no calls imported for" checkbox next to the "Split character" box and enter a number of minutes to have Trunking Recorder send an admin email when the profile hasn't picked up any new calls in that time, useful for catching a folder that stopped receiving new files.

Note: Each Custom Filename Import profile watches one folder and is independent of any other Custom Filename Import (or SDRTrunk/ProScan/DSDPlus) profiles you have configured. If any errors are encountered importing a file, they will be logged in the Trunking Recorder log file.

 

Website templates by JustDreamweaver.com