Skip to content

WebCaller v0.15.1 — Public setup and ntfy guide

Pre-release
Pre-release

Choose a tag to compare

@adlererik adlererik released this 18 Oct 02:07
· 44 commits to main since this release

A Signal-like WebRTC phone for Android, iPhone and desktop: adaptive Opus voice, hardware-aware video preferences, encrypted disappearing chat/media, per-call security words and simple invitations. This preview includes the optional self-hosted ntfy incoming-call alert path introduced in v0.15.0.

Easier public setup

  • Updated, checksum-verified download commands and plain-language Debian installation steps.
  • A separate native systemd guide for the optional ntfy server installer, with an explicit distinction from the guided Docker deployment.
  • Exact Android/iPhone subscription instructions, priority-5 sound settings, WebSocket guidance, DNS/login troubleshooting and the usual-phone-icon fallback.
  • Expanded environment reference, first-phone QR/iPhone guidance, update instructions and verification notes.
  • Generic domain/path examples throughout the guides. The README's personal voice, security choices, codec explanations and Signal comparison are preserved.
  • Publishing safeguards now reject embedded ntfy read-capability addresses and publisher tokens. The private setup card uses WebCaller branding.

Install and use

Start with the beginner Docker guide, or choose the native Debian guide for a fresh setup using the optional ntfy server helper. Do not install both over the same data. Download the ZIP or tar.gz below and verify it against SHA256SUMS.txt.

The operator installs the server once. Other people open a single-use invitation, allow the required permissions and follow the phone's call-alert guide. iPhone background browser alerts require the Home Screen icon. See Using WebCaller and Extra ringing.

Updating an existing installation

Follow Operations. Preserve your private .env, database, certificates, runtime configuration and browser site data. From v0.15.0, this patch requires no encryption or database migration. Do not regenerate identities/secrets or rerun the ntfy first-install helper. Restarting the phone service interrupts active calls; schedule it accordingly.

Checks and limits

139 automated tests pass, along with JavaScript/Python/shell checks, the publishing guard and documentation link/shell-example checks. GitHub CI also builds both app and TURN images. A fresh source archive was installed with Node 24.22.0 and checked for startup, health, no-store responses and rejection of unauthenticated WebSockets.

Public source, Git history, previous release notes/downloads and these archives were scanned for known deployment identifiers and credential patterns. The downloads contain reviewed tracked source only: no private server environment, database, certificates, logs, personal screenshots or runtime directories. SHA-256 checksums detect changed downloads; they are not an independent signature or a guarantee that every possible secret format is detectable.

Application encryption, identities, SAS, codecs, call signaling and notification delivery are unchanged. This remains an unaudited preview. Browser-delivered code and device security remain trust requirements. OS settings determine background sound; stock iPhone ntfy still uses an upstream wake-up metadata relay. No guaranteed ringing, post-quantum security or zero-forensic-trace claim is made. See the security model and verification history.