Development direction / Not a delivery promise
Initial real connections matter. So does everything that happens when a session expires, a process fails or the firewall rebuilds. That is the next standard to meet.
The source implements workstation pairing, controlled WireGuard, broker-enforced session leases, source-restricted listener migration, Windows policy requests, post-pair managed SSH, health monitoring and diagnostics. The current gateway, FreePBX and portable Windows-core suites pass locally.
FreePBX 0.6.0 and Windows 0.8.0 remain independently versioned experimental targets. Native Windows compilation/UI/service validation and the live PBX/firewall/migration acceptance are still outstanding; earlier operator reports do not validate these changes. The 0.6.0 module package has been rebuilt and locally matched to source, but is not a production or public release claim.
Read the baseline and its boundaries →Verify the installed 0.5.0 broker and managed Custom Service, actual WireGuard roaming from unfamiliar public IPs, watchdog intervals and approved firewall rebuilds. Check Fail2Ban ordering and unchanged unrelated rules.
Exercise actual SIP calls, bidirectional RTP and unrelated management traffic throughout connection, rebuild, revocation and uninstall.
Prove revocation and temporary authorisation expiry terminate owned PBX processes and leave empty cgroups, while unrelated SSH survives. Cover certificate refusal, lost reachability and client/server failure separately.
Test Windows/PBX reboots, broker restart, interrupted service operations, failed cleanup, upgrade, rollback and uninstall. Preserve original deadlines and an independent management route.
Verify custom-port import, browser launch and Connection Health on native Windows, with actual Apache/TLS and redirects over WireGuard. Also check supported terminals, Unicode paths, UAC, installation, multiple users, scaling and monitor transitions. Portable build success does not replace these cases.
The unreleased Windows source opens the existing approved managed SSH session in a native dialog. It now includes a libvterm-based screen model, interactive key encoding, UTF-8 handling, ANSI/cursor rendering, scrollback, clipboard actions and a ConPTY-backed OpenSSH path with terminal resize propagation. It reuses TELIPHONES certificate issuance, host pinning, isolated credential handling and owned-process cleanup rather than introducing another remote-access system.
Portable emulator tests cover VT output, keyboard input, UTF-8 chunking, resizing and scrollback. Native MFC/ConPTY process integration, full-screen applications and real SSH behavior are not verified in this environment. Treat the console as experimental until those checks pass.
Build and exercise resize, disconnection, reconnect, UTF-8 and full-screen programs on Windows against a disposable SSH host.
Continue using the approved account, managed short-lived certificate, pinned host identity and owned session. A web-only workstation must request SSH elevation first; root is never implicit.
Improve the separate support workflow through complete end-to-end testing against explicit Connect, Checker and Console implementations. Verify expiry, cleanup and firewall reachability rather than assuming workstation success proves support success.
Deployment maturity includes reviewed packages, consistent source/build provenance, clear upgrade procedures and dependable recovery. It does not imply a hosted service, an engineer portal or universal NAT traversal already exists.
Rendezvous and relay ideas are documented separately as future design. They are not connectivity capabilities in the present product.
Record exact versions, source revisions, build identifiers, test commands and sanitised outcomes. Distinguish operator observation from independently repeatable tests. Keep screenshots genuine and free of keys or customer data.
There are no promised release dates on this page. Goals may change as testing exposes constraints. Use the repository histories and evidence register for the implemented state, not the roadmap.