Skip to content
Free IT audit

Business Telephony & VoIP

FreePBX & Asterisk: Self-Owned IP PBX

We install and support self-owned phone systems on FreePBX and Asterisk, with no per-extension charge and no dependency on a third party platform. You keep full control of the configuration, and we hand over documentation, configuration backups and scheduled security updates so the infrastructure genuinely belongs to you.

Request a site surveyAll services in this area

Who it is for

  • Businesses with many extensions, where per-user charging adds up
  • Companies with unusual call flow requirements
  • Organisations wanting control of their own infrastructure
  • Sites needing integration with other systems

When we are NOT the right choice

  • If a subscription service with no management is preferred
  • If there is no server or virtual machine to host it
  • If there is no support agreement covering security updates

PROCESS

The process

Indicative times from signature of the proposal, subject to hardware availability. Every project is shaped to the size and the needs of the client.

  1. 01Requirements analysis

    We record extensions, concurrent calls, queues, schedules and any integration with other systems.Time: 2-5 working daysDeliverable: Requirements and flow inventory

  2. 02Design and sizing

    We size the server or virtual machine against concurrent calls, and design the dial plan.Time: Alongside the studyDeliverable: Infrastructure design and dial plan

  3. 03Installation and hardening

    We install and harden. An IP PBX exposed to the internet receives abuse attempts from day one.Time: 1-2 weeksDeliverable: Configured PBX with limited exposure

  4. 04Integrations and devices

    We configure Grandstream IP handsets, softphones, queues and recorded prompts according to the designed flow.Time: During implementationDeliverable: Configured handsets and queues

  5. 05Handover and maintenance

    We hand over documentation and configuration backups. Security updates run on schedule under the support agreement.Time: On completion and ongoingDeliverable: Documentation, backups and updates

What is includedWhat is not included
Requirements analysis and dial plan designProvider fees and call charges
FreePBX or Asterisk installation on a server or virtual machineHandset costs and third party module licences
Hardening and exposure reductionCustom feature development beyond what is agreed
Handset, queue and schedule configurationSupport of an installation we neither built nor maintain
Configuration backups and documentation
Scheduled security updates

Technology and equipment

  • FreePBX
  • Asterisk
  • Grandstream
  • Yeastar
  • SIP trunks
  • Proxmox

From practice

The argument for a self-owned PBX is not ideological, it is arithmetic and operational. In companies with many extensions, per-user charging becomes the largest part of the cost, while unusual call flows are often unsupported by packaged platforms.

The corresponding burden is maintenance. A FreePBX that is not updated is a target, and abuse of an exposed PBX shows up first on the provider bill. That is why we do not hand one over without an update plan.

Prerequisites

  • A server or virtual machine to host it
  • A network with a voice VLAN and priority
  • Stable internet connectivity
  • An agreement covering security updates

Cost

Quoted as an installation project, with no per-extension charge. Maintenance, security updates and flow changes sit within the support agreement at a monthly charge that is independent of user count.

We do not publish a price list. Every proposal follows a site survey and separates hardware from labour.

What moves the cost

  • Number of extensions and concurrent calls
  • Complexity of the dial plan and queues
  • Whether integration with other systems is required
  • Whether hosting runs on your existing infrastructure

Frequently asked questions

Why self-owned rather than a subscription?

Mainly two reasons: there is no per-extension charge, which matters at scale, and the configuration is yours, so unusual call flows are not limited by what a platform permits.

What happens if we stop working together?

You keep the infrastructure, the configuration backups and the documentation. A self-owned PBX does not lock you to a provider, and that is part of why we recommend it.

Is it secure?

It is, provided it is hardened and kept updated. An IP PBX exposed to the internet receives abuse attempts from day one, which is why we do not take one on without an agreement covering security updates.

Will you support an existing installation?

After an inventory and findings report. We take it on once we agree on the condition we are inheriting, so we do not carry responsibility for settings we are not allowed to change.

Related services

Also connects with

NEXT STEP

Discuss a self-owned phone system

We record your requirements in extensions, flows and integrations, and show acquisition cost against subscription cost.

Request a site survey+30 210 598 9588

GET IN TOUCH

Tell us what you need

Four fields. An engineer replies, not a sales desk.

Fields marked * are required.

By sending this form you accept the processing of your details under our Privacy Policy.