Documentation / Operations and internals
Start with
the right guide.
Installation and daily use should not require reading the whole architecture. Start with your task; go deeper when you need the exact contract or failure boundary.
A practical place to begin.
Use a disposable FreePBX 17 / Debian 12 PBX with independent root/console access. Initial native/live SSH success does not make the project production-ready.
Filters the guide links below and above. Nothing is sent to a server.
Install, approve and operate.
Complete FreePBX administration guideRequirements, Module Admin installation, the exact root broker bootstrap, upgrades, pairing, CLI, diagnostics, recovery and uninstall.Complete Windows application guideDownloads, WireGuard installation, pairing, supported terminals, health, local logging, appearance and permissions.FreePBX Firewall investigation and diagnosticsRead-only evidence collection, the 0.4.0 reset incident, exact 0.4.1 placement and real-PBX acceptance criteria.Testing programmeRegression coverage, simulated versus real enforcement, source/package checks and disposable-system validation.Read the boundaries
behind the workflow.
ArchitectureComponents, trust boundaries, interfaces, firewall layering, runtime state and reconciliation.Security and verification evidenceIdentity, authentication, lifetime, failure handling and the difference between design, tests and live observations.Workstation pairing contractVersion-1 and version-2 schemas, response binding, managed ports, migration and enforcement integrity.Managed SSH implementation and key inventoryRequest/2 challenge signatures, ephemeral certificate subjects, Windows agent isolation, owned process lifecycle and historical design.Windows developer build and readiness referenceVisual Studio/MFC, static OpenSSL, Actions fixtures, native SSH tests, display matrix and historical investigations.Integrate a support workflow.
Not a second authority.
Remote Support integration guideStaged Connect, Checker and Console integration; prove the local lifecycle before adding external components.Published integration contractsRequest/response relationships, signatures, evidence and authority boundaries for support implementations.Topology definitionsOn-PBX implementation and the On-net/Off-net external contracts.Reference gateway and Checker laboratoryDisposable-host integration tools; no hosted service or production support portal.The source guide stays authoritative.
This website explains the current workflow and points to the repository for complete operational procedures. Privileged bootstrap commands are intentionally not shortened or duplicated here. Read the guide that corresponds to the exact trusted build being installed.
Versions are independent: FreePBX module/broker 0.6.0 with broker protocol 12, Windows application 0.8.0. Repeat root bootstrap after upgrading the module; verify the broker, SSH authority and protected firewall helper. The local 0.6.0 package is rebuilt from the current source, but it is not a published release or live-PBX validated. The 0.8.0 Windows build still requires native validation.
The retained 0.5.0 local test package does not include connection-state policy. Some older architecture, Windows history and security references describe previous development baselines; use the current module guide and connectivity report alongside those historical records.
Repository links are derived from locally inspected paths, not verified public publication. Uncommitted changes may not yet be online. Actions artefacts may expire and are not releases. The download guide explains availability.
Report ordinary reproducible faults with sanitised details through the project repository or support channel. Suspected vulnerabilities and sensitive diagnostics belong in private support, not public issues.