This is actually the most important section, the configuration of SvxLink.
We know from a lot of user feedback that there is sometimes a considerable need for clarification here.
Perhaps the following pages can answer some questions and help you set up your SvxLink node.
Please make sure that there is a separate configuration file for each individual module, these files are located under /etc/svxlink/svxlink.d
This means that normally it is not enough to set up svxlink.conf, but you will have to set it up individually depending on the modules you have configured!
If you don’t find the answers to your questions, please use the forum, here specific problems can often be solved much faster.
…the system start scripts svxlink and remotetrx
…here you can find the binaries (svxlink, qtel, remotetrx, siglevdetcal)
Contains the Async header files (e.g. AsyncAudioSink…AsyncAudioSink…AsyncAudioSink…
Contains the Async header files).h)
…the SvxLink core libraries such as libasyncaudio-0.17.0.99rc1.so
…the SvxLink module libraries such as ModuleMetarInfo.so
…the translation files (translations in 8 languages) for Qtel
…the events.tcl, the „main script“ of the event handling routines
…here are the logic- and module-specific tcl-files, which form the presentation level, i.e. generate speech output, output repeater recognition as Morse characters, etc.
…here are more TCL’s for SvxLink modules
…the soundfiles for the speech output into more country- or language-specific subdirectories like e.g. de_DE/ or en_EN/. If no country setting is detected in the Linux system or if it was not explicitly defined in the logic section, the search is performed in en_US//var/log by default. By default, the SvxLink log file svxlink, which informs about events and errors, is located here. If SvxLink is started in the console, the output is not in this file but in the console itself.
Spool directory for mails, voice mailboxes, voice recordings etc., if the QSO recorder was activated or the PropagationMonitor was configured.