TELIPHONES
Get the software
Explore

Windows workstation. FreePBX authority.

Your PBX.
A private route.

Bring the connection, the approval and the tools together. Reach FreePBX over WireGuard, open its web interface and start an explicitly authorised SSH session.

Try the interactive demos Start with a test PBX

Native Windows 10/11 x64 · FreePBX 17 / Debian 12
Open-source software. Experimental, not production-ready.

01 / My PBXsArchitecture illustration
Your Windows workstationOne saved connection.

Local keys · preferred browser · OpenSSH-backed terminal

↓ Direct WireGuard · PBX host route only
Your FreePBX serverExplicitly approved access.

Workstation identity + permissions + original expiry

FreePBX GUINormal sign-inManaged SSHOnly if authorised
A connection diagram, not a software screenshot or live connection. No route to the wider PBX network is granted.
Development status

FreePBX 0.6.0 adds Open/Closed/Frozen connection states. The Windows 0.8.0 target clarifies web-only versus SSH pairing. New targets require local validation; real-PBX acceptance testing remains outstanding.

Read the evidence →
Try it / Synthetic workflows

Operate the demo.
No PBX required.

Send a sample pairing request, approve it in the module view, then test connection admission and the safe simulated console. Both views share browser-local state.

Interactive demo • no PBX connection — no network connections, shell commands, credentials or passwords are used.

Open the FreePBX and Windows demos →
01 / Less coordination

Remote administration,
with the pieces connected.

A manually configured VPN gets you a route. You still need to coordinate who may use it, which services they can reach, their SSH credentials and when access should end. TELIPHONES makes those decisions part of the PBX workflow.

Approval

Pair a workstation.
Not a whole network.

A full FreePBX administrator approves one key-bound request, with web-only or explicitly authorised SSH access. The workstation gets a host route to that PBX.

How pairing works →
Identity

Open SSH.
Not a key-sharing exercise.

Managed SSH uses an approved existing account, pinned host identity and a temporary certificate for a fresh session key. No permanent administrator key needs to be handed to the workstation.

Inside managed SSH →
Authority

Set a lifetime.
Keep the decision on the PBX.

Choose temporary access or persistent approval until revoked. Reconnecting does not renew the original deadline. Removing a local profile does not revoke the PBX pairing.

Understand the lifecycle →
02 / Two complementary components

At your desk.
Under your control.

The Windows application handles the working connection. The FreePBX module handles the approval. A separately installed root broker carries out the narrow set of privileged server operations.

Windows / 0.8.0 development target

Your everyday administration tools.

Saved PBXs, preferred applications, health monitoring and a local session timeline. Pairing offers explicit Web access and Web + SSH access choices with inline copy feedback.

TELIPHONES for Windows →
FreePBX / 0.6.0 development target

A visible approval boundary.

Pair, inspect and revoke workstations from Connectivity > TELIPHONES. Open, Closed and Frozen control the workstation listener without discarding existing pairings.

TELIPHONES for FreePBX →
03 / A deliberate exchange

Request. Approve.
Connect. Work.

There is no background service deciding who should have access. Pairing is an explicit exchange between the workstation and a full administrator on the PBX.

  1. Request

    Generate a pairing request in Windows. Opt in to SSH only if you need it.

  2. Approve

    The PBX administrator sets the lifetime and, for SSH, deliberately selects an existing account.

  3. Connect

    Import the bound response and establish WireGuard to the PBX's reachable UDP endpoint.

  4. Work

    Open FreePBX or authorised SSH. Disconnect locally; revoke authority on the PBX when finished with the pairing.

Follow the complete starting sequence →
04 / A separate support workflow

A customer's support window.
Not your workstation pairing.

Remote Support is for temporary, customer-authorised engineer access. It uses separately operated Connect, Checker and Console integrations, with an absolute support deadline and independent reachability evidence.

Contracts and laboratory components exist. A complete production-validated service does not. No hosted gateway or relay is supplied.

Explore Remote Support →
05 / Read the engineering

Understand it before
you depend on it.

Security & current evidenceKeys, restrictions, failure modes and the limits of what has been demonstrated.Operational documentationInstallation, root bootstrap, troubleshooting and the source contracts.What comes nextReliability, lifecycle validation and completion of the experimental SSH console.