Know what
you are installing.

Test builds.
Not a production release claim.

The current development targets are FreePBX module 0.6.0 and Windows application 0.8.0 (file version 0.8.0.0). Their versions are independent. The Module Admin package does not include Windows, and a Windows build does not install the PBX broker.

The current 0.6.0 Module Admin archive has passed local source/package validation. No native Windows build or live PBX acceptance is claimed. The historical 0.5.0 package does not include current session admission, listener migration or policy management. Review the evidence and limitations before installation.

Repository and workflow links below are grounded in local files. Public availability, publication and artefact retention have not been checked. No direct release, package or executable download is assumed.

Updated policy; locally validated package.

The local TELIPHONES-0.6.0.tgz archive and SHA-256 sidecar contain the current module source and pass package validation. The source includes persistent Open/Closed/Frozen state, atomic session leases, source-restricted listener migration, Windows policy requests and post-pair SSH elevation. This is a local experimental package, not a production release or verified public download. Live FreePBX/firewall and native Windows acceptance remain outstanding.

The Module Admin package.

For FreePBX 17 / Debian 12. The reviewed local working tree contains TELIPHONES-0.5.0.tgz and TELIPHONES-0.5.0.tgz.sha256. All four package checks passed, covering metadata, checksum, extraction, source equality and historical archive integrity.

Verify before installing

With the matching trusted sidecar and package in the same directory:

sha256sum -c TELIPHONES-0.5.0.tgz.sha256

A matching checksum establishes byte identity, not independent trust in the publisher. Review source and provenance too. This is a locally validated installation package, not a production-ready release.

Historical 0.4.0 and 0.4.1 archives are preserved. Version 0.4.1 corrected intrusive INPUT placement; it does not contain 0.5.0's managed listener or custom-port support.

After upgrading through Module Admin, repeat the root bootstrap and verify the installed broker is 0.5.0/protocol 6. Do not disable FreePBX Firewall or enable Custom Rules as a workaround.

A successful build artefact.
Not a made-up installer link.

The repository's Windows build workflow is configured to produce the separate TELIPHONES-Windows-x64 artefact after its checks succeed. If an appropriate successful run and retained artefact are available, download it there; GitHub may require sign-in. This is a workflow link, not a verified executable download.

Artefact retention is 14 days. No current run, executable hash or publicly available 0.8.0 build is established here. Check build provenance rather than relying on a version string alone.

• Keep TELIPHONES.exe and TELIPHONES-SSH.exe adjacent.
• Read the included licence and OpenSSL licence.
• Inspect build-info.json for source revision, run identity/attempt and executable hashes.
• Expect unsigned test executables; verify trusted origin rather than disabling Windows protections.
• Install/reuse official WireGuard separately; it is not bundled.

Earlier native test and live login results are operator-reported; native validation of the 0.8.0 MFC interface remains outstanding. GUI-only access needs no OpenSSH; managed SSH does.

The full engineering context.

The source repository includes the module, root broker, Windows C++17 application, tests, contracts and reference gateway. A repository source ZIP is not the Module Admin package and is not a prebuilt Windows application. Uncommitted development changes may not yet be visible in the public repository.

The optional reference gateway is unnecessary for direct My PBXs access. It is a separately operated lab component for Remote Support integration.

A deliberate installation.

Use this local checklist while reviewing. It does not connect to a PBX, validate a file or save data.

• I am using a disposable FreePBX 17 / Debian 12 test system with independent console access.
• I have reviewed the build provenance, trusted source and module checksum.
• I understand that module installation and root broker refresh are separate steps.
• I have read the security limitations and remaining real-PBX validation requirements.
• I will preserve FreePBX Firewall, unrelated policy and an independent management route.