v0.1.8 — twocans on a Synology

twocans on a Synology: a package to install from Package Center, with a wizard for its questions, or the installer over SSH. Getting it there made call audio's ports movable, and the installer surer-footed on small machines.

Synology

The package — twocans-0.1.8-1.spk, attached below — installs from Package Center → Manual Install on DSM 7.2.1 or later, on a model that runs Container Manager. Its wizard asks the installer's questions, suggesting the Synology's own address and time zone, and ports that are free on it. twocans then appears in DSM's main menu, its ports in the firewall's list of applications, and its recordings, voicemails and backups in a new twocans shared folder (give yourself access in Control Panel → Shared Folder to browse it).

It isn't signed by Synology, so DSM warns before installing; if it refuses, allow it under Package Center → Settings → Trust Level → Any publisher. It has run on one Synology so far (DSM 7.3.2) — reports welcome. See synology/ for how it works.

Over SSH, the one-line installer knows a Synology too: run it with sudo, and it puts twocans on a storage volume, finds Docker in Container Manager, and says which ports to open in DSM's firewall.

Also new

• Call audio's ports can move, as a whole, when something else holds part of 10000–10100 (a UniFi controller's 10001, say). The installer offers a free range, and Asterisk, Docker and the app's router instructions all follow — phones and providers are told the range on every call.
• Ready-made answers: ./install.sh takes TWOCANS_LAN_IP, TWOCANS_TZ and the rest, for installs nobody's at the keyboard for.

Fixed

• Times stamped by the app and checked by the database could be hours out where the two run in different time zones. The database now keeps the app's.
• Speech-to-text no longer stops the install on a kernel that can't cap a container's processor use: it runs uncapped there.
• A slow first start of the database no longer stops the install: it gets up to five minutes.
• The folders for HTTPS certificates are made by the installer, as Docker on some machines won't make them itself.

Updating

./twocans update

Calls, settings and recordings carry over. Containers are recreated, as their settings changed; the call-audio range stays where it is unless something else holds part of it.