iw0hks/svxlink repository overview

⁠What is Svxlink?

SvxLink is a project that develops software targeting the ham radio community. It started out as an EchoLink application for Linux back in 2003 but have now evolved to be something much more advanced.

The SvxLink Server is a general purpose voice services system, which when connected to a transceiver, can act as both an advanced repeater system and can also operate on a simplex channel. One could call it a radio operating system since it sits between the hardware (transceiver) and the applications (modules) and handle basic system services as well as input and output.

SvxLink is very extensible and modular. Voice services are implemented as modules which are isolated from each other. Modules can be implemented in either C++ or TCL. Examples of modules are:

• Help – A help system
• Parrot – Play back everything that is received
• EchoLink – Connect to other EchoLink stations
• DtmfRepeater – Repeater received DTMF digits
• TclVoiceMail – Send voice mail to other local users
• PropagationMonitor – Announce propagation warnings from dxmaps.com
• SelCall – Send selective calling sequences by entering DTMF codes

⁠Help

is possible to discuss about this image directly on the dedicated form HERE⁠

⁠Version

SVXLINK: 19.09.1

DEBIAN: 10 and 10-slim

⁠Usage

This image need a bind volume and the sound card. To accomplish this is possible to lunch the image in this way:

docker run --name svxlink -d -v /volume/bind:/conf -p 5198/udp -p 5199/udp -p 5200/tcp -p 5300/tcp iw0hks/svxlink

Is possible also to use docker-compose:

version: '2.4'
services:
  svxlink:
    container_name: svxlink
    image: iw0hks/svxlink
    ports:
      - 5199:5199/udp
      - 5198:5198/udp
      - 5200:5200/tcp
      - 5300:5300/tcp
    volumes:
      - /volume/bind:/conf
    devices:
      - /dev/snd:/dev/snd

This is an example so please take as is.

At the moment there are no enviroment variables so the configuration need to be done manually editing the files in /volume/bind/svxlink/. In this directory is possible to find all the svxlink configurations.

⁠To Do

I hope soon to implement also the aux part of svxlink to have one image to perform the various aspect of svxlink like remote tx/rx or traslator. At the moment the other services nee to be lunched manually if needed running

docker exec svxlink commandTOlunch