Repository navigation
twocans v0.1.4
If you have a Grandstream phone or adapter, update: in earlier versions a GHP621, HT801 or HT802 fetched its settings from twocans and then ignored them, so it never signed in.
Highlights
- Grandstream provisioning works. The settings file was labelled with the wrong format; it's fixed, and tested on a real GHP621W. The in-app setup steps now say to leave
http://out of the Config Server Path, and to fill in the Firmware Server Path (fm.grandstream.com/gs) when the phone asks. - The installer works on Alpine, whose BusyBox tools stopped its new install log.
- Releases now build themselves, for Intel/AMD and for ARM (a Raspberry Pi), and every push runs the tests and both ARM builds.
- The README leads with the one-line install, with screenshots of the installer and the app.
Upgrading
./twocans updateFrom 0.1.1 or earlier, run the one-line install and point it at your twocans folder. Then reboot any Grandstream phone or adapter, so it fetches its settings again.
Full changelog
Changed
- The README leads with the one-line install, and shows the installer and the
app — screenshots from a demo install with a made-up family.
Added
- Images for ARM (a Raspberry Pi) as well as Intel/AMD: twocans' own web and
speech-to-text images are built natively for both and published under one
name, so Docker pulls the one that fits. A Pi no longer spends 15–30 minutes
building them; the installer checks for an ARM build and only builds locally
when a release lacks one. - Releases build themselves: pushing a version tag runs a GitHub Actions
workflow that builds, publishes and checks the images on both chip types (and
refuses a tag that doesn't matchbackend/VERSION). It can also be run by
hand for an existing tag. - Checks on every push and pull request: the scripts parse, and the whole
test suite runs in the web image against a fresh MariaDB.
Fixed
-
Grandstream phones and adapters fetched their settings and ignored them.
The file was written as numbered settings (<P271>…) but labelled as
Grandstream's other, named format (<config version="2">), so a GHP621 or an
HT801/HT802 never signed in. It's labelled version 1 now, and carries the MAC.
The setup steps also say to leavehttp://out of the Config Server Path (the
phone refuses it) and to fill in the Firmware Server Path when it's asked for. -
The install log used
sed -uandgrep --line-buffered, which BusyBox (as
on Alpine) lacks, and stopped the installer after its first few lines there.
It now usesawk, which behaves the same everywhere.
Compare: v0.1.3...v0.1.4