Skip to content
Illustration: a small server rack locked with its key in the door, holding a compute unit with a fan, a database unit with drive bays and a telephony unit whose line card is cabled to a phone jack in the wall.

Open-source business phone systems: how to self-host one

How to self-host an open-source business phone system: the parts you run, five options compared, what providers charge and what you take on.

An open-source business phone system can run on servers you control, and most of the options below charge nothing per seat. What you can’t self-host is the phone network. Real numbers, and calls to ordinary phones, still come from a provider such as Telnyx or Twilio, and that provider bills you for every number, minute and text. In exchange, 911 setup, texting registration, security and updates all become your job.

Our view, up front: self-hosting is a good deal for a team that already runs servers. For a team that wants to stop thinking about phones, it’s a poor one.

What self-hosting a phone system means

Self-hosting means the software runs on a server or cloud account you control. It can route calls and store messages, but on its own it can’t reach a single phone number. For that you connect it to a provider, in one of two ways.

The first is a SIP trunk. SIP is the protocol that sets up, changes and ends internet calls, defined in RFC 3261. A trunk links your system to the public phone network for calls in and out on the provider’s numbers, as Twilio’s SIP trunking docs describe. PBX software uses this route.

The second is a telephony API: your app places and controls calls with the provider’s API keys. Chatwoot’s voice channel works this way, and its Twilio setup guide asks for a Twilio Account SID, Auth Token, API key and TwiML App.

Either way, the same pieces turn up.

The app or PBX is the software you run. FusionPBX, for example, lists extensions, voicemail to email, IVR and ring groups, and an app may add contacts and an inbox. Behind it sits a database for contacts, call logs and messages. Chatwoot, for one, recommends PostgreSQL 12 or later and Redis 6 or later in production (Chatwoot’s self-hosting docs).

Then come the phones. A browser dialer streams audio through WebRTC, with no plug-ins. SIP desk phones and softphones register with your system so it knows where to ring (RFC 3261). Our guide to web dialers, softphones and desk phones compares the three.

The numbers belong to the provider. You rent them by the month and assign them to your trunk or app (Twilio).

Last, webhooks: the requests a provider sends your server when a text arrives or is delivered. Telnyx needs a public HTTPS address that answers within 2 seconds, and it signs each webhook so you can verify it (Telnyx’s webhook docs).

The main open-source business phone systems

These five projects do different jobs, so the table doesn’t rank them.

Project License What it covers Where it runs Skills you need
Asterisk GPL v2, or alternative licenses from Sangoma A PBX and telephony toolkit. You build call handling in its dialplan Linux: current CentOS, RHEL, Fedora, Ubuntu and Debian Linux administration, SIP, dialplan
FreePBX GPL. Sangoma also sells commercially licensed modules A web interface that configures and manages Asterisk Debian 12, for FreePBX 17 Linux basics, SIP, the FreePBX interface
FreeSWITCH with FusionPBX MPL 1.1 for both FreeSWITCH is the call engine. FusionPBX adds a multi-tenant PBX with voicemail to email, IVR, ring groups and call distribution FreeSWITCH: Linux, Windows, macOS, BSD. FusionPBX: Debian, Ubuntu LTS, FreeBSD, CentOS Linux administration, SIP, FreeSWITCH and FusionPBX configuration
Chatwoot MIT, except its enterprise/ directory A support inbox for live chat, email, social channels, WhatsApp and SMS. Phone calls need Twilio and a paid tier A Linux server, Docker or Kubernetes, with PostgreSQL and Redis Running a web app and its database, plus Twilio
KNOQRA self-host edition AGPL-3.0, with additional terms Calls, SMS and the WhatsApp inbox, contacts, numbers and usage Your Cloudflare account and any Postgres database. No Docker setup yet Cloudflare, Postgres, and a Telnyx or Plivo account

Asterisk calls itself an open source PBX and telephony toolkit in its README. It’s distributed under GPL version 2, and also under licenses negotiated with Sangoma (LICENSE). The project tests and supports Linux distributions that haven’t reached end of life (supported platforms).

Want Asterisk with a web interface? That’s FreePBX, a GPL front end whose version 17 script installs on Debian 12 (install README). One catch: Sangoma’s commercially licensed modules are supported only on the FreePBX Distro (Sangoma).

FreeSWITCH runs on anything from a Raspberry Pi to a multi-core server (README), under the Mozilla Public License 1.1 (LICENSE). FusionPBX puts a single-company or multi-tenant PBX on top of it (README), under the same license (license header).

Chatwoot is a customer support platform first (README), MIT-licensed outside its enterprise/ directory (LICENSE). Calls come through Twilio Voice or WhatsApp Calling (voice calling guide). Voice isn’t in the free Community Edition; it comes with Premium Support at $19 per agent a month, or Enterprise at $99 (self-hosted plans).

KNOQRA’s code isn’t downloadable yet, because its public repository is still being prepared.

What it costs

The software is free, apart from paid extras such as Chatwoot’s voice tiers and Sangoma’s modules. The money goes on the phone side. Your provider bills numbers by the month, calls by the minute, texts by the message, and emergency calling as an add-on.

These are the published US rates for a SIP trunk and texting. Twilio dates its voice prices October 2026 and its SMS prices November 2026.

Telnyx Twilio
Local number, per month From $1.00, plus $0.10 to add SMS and MMS $1.15
Outbound call in the US, per minute From $0.005 $0.0100 to the 48 states
Inbound call to a local number, per minute From $0.0032 $0.0034
Emergency calling, per number per month $1.50 $0.75
Outbound SMS from a local number $0.004 a part, plus a carrier fee $0.0083, plus carrier fees

Sources: Telnyx SIP trunking, number and SMS pricing; Twilio SIP trunking and SMS pricing.

Calls through an API cost more. Twilio’s Programmable Voice charges $0.0140 a minute out and $0.0085 in on a local number, and Telnyx adds $0.002 a minute for its Voice API (Telnyx).

An example. Picture a five-person team sharing five local numbers. In a month they make 3,000 minutes of calls, take 2,000 and send 1,000 one-part texts. At Telnyx’s starting rates, that’s $5.50 for numbers with texting, $7.50 for emergency calling, $15.00 outbound, $6.40 inbound and $4.00 for texts. Carrier fees add about $3.80, using the $0.0038 blended rate in Telnyx’s own example. The total comes to about $42.20 a month, before taxes, texting registration, your server bill and your time.

Now put the same team on Quo, which was called OpenPhone until September 2025 (Quo’s announcement). Starter costs $19 per user a month, or $15 billed yearly: $95 or $75 for the five of them, with a number per user and calling and texting to US and Canadian numbers (Quo pricing).

On paper, self-hosting saves this team $33 to $53 a month. A few hours of upkeep can wipe that out. The gap grows, though, with every seat that calls little, which is why the sums work best for a large team that doesn’t phone much.

What you become responsible for

Emergency calls

These are US rules. Check them with a lawyer before you go live.

The rules have a name for a shared business phone system: a multi-line telephone system, or MLTS, and the term includes VoIP and PBX systems. Its manager is whoever oversees it after installation, and may also be its installer (47 CFR 9.3). If you self-host for your staff, that can be you. Under 47 CFR 9.16, whoever installs, manages or operates an MLTS must make sure that:

  • Every phone can dial 911 directly, with no prefix such as 9.
  • A notification reaches someone likely to see or hear it, if the system can send one without new hardware or software.
  • Each 911 call carries a dispatchable location: automatically for fixed phones on site, and where technically feasible for other devices.

Selling phone service to other people raises the bar. You may then count as an interconnected VoIP provider, and those providers must send every 911 call with location information. They must also warn every subscriber in plain language when 911 may fail, such as after a move or during a power cut, and keep a record of each subscriber’s acknowledgement (47 CFR 9.11).

At your provider, you register an emergency address for each number and pay the monthly fee in the table. Don’t skip the address. Twilio charges $75 for a 911 call from a number with no registered address (Twilio).

US texting registration

Running your own server doesn’t exempt you from the texting rules. Twilio’s guide says anyone sending SMS or MMS from a 10DLC number through an application to the US must register for A2P 10DLC, individuals and hobbyists included. The Campaign Registry asks anyone registering with it to be a Campaign Service Provider, so your brand and campaigns go through your provider. Read what A2P 10DLC is before your first text.

Security: toll fraud and SIP attacks

Calls cost money. That alone makes a phone system on the internet a target. Asterisk’s security notes warn that a badly configured system can be used by others and run up substantial charges. Its best-practices guide gives examples: a device named 1000 with the password 1000 invites brute-force attacks, and unfiltered dialplan input can let an outsider call out through your provider.

The losses add up. Twilio describes number ranges set up only to receive fraudulent calls, whose owners earn money for every minute. It calls this International Revenue Sharing Fraud and puts industry-wide losses at $10 billion a year (Twilio).

Our advice: tick off all five of these before the system takes a real call.

  • Give every SIP device a long, random password, and don’t name devices after extension numbers (Asterisk).
  • Restrict web access to your PBX, and review access logs regularly (Telnyx).
  • Allow calls only to the countries you need, and block high-risk ranges (Twilio).
  • Set a daily spend limit and a maximum per-minute rate at your provider. Telnyx rejects calls to destinations above your rate (Telnyx).
  • Check webhook signatures, so a forged request can’t pass as your provider (Telnyx).

Updates and backups

Security fixes are yours to apply now. Asterisk gives a long-term release 4 years of full support and 1 more of security fixes, while standard releases get at least 1 year, plus 1 of security fixes. Asterisk 24, the newest long-term release, came out on November 5, 2026 and reaches end of life on October 15, 2031 (Asterisk versions). Keep an eye on the operating system too. Upgrading your Linux distribution can stop older Asterisk versions from building (supported platforms).

Back up the database and your configuration, and test a restore. PostgreSQL’s manual says databases should be backed up regularly, and describes three ways: SQL dumps, file system backups and continuous archiving.

When self-hosting makes sense

It tends to fit when someone on your team already runs servers and wants this one too. It fits if you need call and message records on infrastructure you control, or you want to change the code and wire it into your own systems. And it fits a team with many seats and light calling, the case where the sums above look best.

A hosted service is simpler when nobody wants to own the phone system’s updates and security, or when you need desk phones, mobile apps or 911 working on day one. It’s also the easier call for a small team, whose per-seat fees are close to provider costs anyway, and for anyone who wants one company to answer for numbers, billing and support.

Our rule of thumb? If nobody would put their hand up to own the phone system, stay hosted.

KNOQRA’s self-host edition

We have a row in that table ourselves, so start with where it stands: the public repository is still being prepared, and the code isn’t downloadable yet.

The self-host edition is free and open source under the GNU AGPL-3.0, with additional terms. It handles calls, SMS and the WhatsApp inbox, plus contacts, numbers and usage, and it runs on your own Cloudflare account with any Postgres database. There’s no Docker setup yet. We recommend Telnyx as the provider because it covers calls, SMS and WhatsApp, and Plivo can be connected for calls and SMS. Your provider bills you directly, and KNOQRA adds no fee. Star the GitHub repository and you’re issued a free license key, which is checked offline. The KNOQRA name and the “Powered by KNOQRA” attribution stay, and white-labeling needs a commercial license. One hard limit, again: KNOQRA cannot call 911.

Rather not run a server at all? KNOQRA Cloud adds numbers it manages, bundled minutes and messages, billing and live call transcription (pricing). The open-source page has the details.

Sources

  1. RFC 3261: SIP, Session Initiation Protocol
  2. Twilio Docs: Getting started, configure your Elastic SIP Trunk
  3. MDN: WebRTC API
  4. Telnyx Developer Docs: Receiving webhooks for messaging
  5. Asterisk: README (GitHub repository)
  6. Asterisk: LICENSE
  7. Asterisk Documentation: Supported Platforms
  8. FreePBX: FreePBX 17 installation script for Debian 12 (README)
  9. Sangoma Knowledge Base: PBX GUI, Commercial Modules
  10. FreeSWITCH: README (GitHub repository)
  11. FreeSWITCH: LICENSE
  12. FusionPBX: README (GitHub repository)
  13. FusionPBX: license header in index.php
  14. Chatwoot: README (GitHub repository)
  15. Chatwoot: LICENSE
  16. Chatwoot Developer Docs: Self-hosted
  17. Chatwoot User Guide: Voice Calling in Chatwoot
  18. Chatwoot User Guide: Connecting Twilio voice channel
  19. Chatwoot: Self-hosted plans
  20. Telnyx: SIP Trunking pricing
  21. Telnyx: Global Numbers pricing
  22. Telnyx: SMS API pricing
  23. Twilio: Elastic SIP Trunking pricing in the United States
  24. Twilio: Programmable Voice pricing in the United States
  25. Twilio: SMS pricing in the United States
  26. Quo: OpenPhone is now Quo (September 23, 2025)
  27. Quo: Pricing
  28. 47 CFR 9.3, 911 requirements: definitions (eCFR)
  29. 47 CFR 9.11, E911 service for interconnected VoIP (eCFR)
  30. 47 CFR 9.16, multi-line telephone systems: direct 911 dialing, notification and dispatchable location (eCFR)
  31. Twilio Docs: Programmable Messaging and A2P 10DLC
  32. The Campaign Registry: Home
  33. Asterisk Documentation: Important Security Considerations
  34. Asterisk: Best Practices (README-SERIOUSLY.bestpractices.md)
  35. Twilio Docs: Protect your account with Voice Dialing Geographic Permissions
  36. Telnyx Developer Docs: Outbound Voice Profiles for SIP trunking
  37. Telnyx Help Center: Prevent Telnyx Account Fraud
  38. Asterisk Documentation: Asterisk Versions
  39. PostgreSQL Documentation: Backup and Restore

Fees and rules change: check the source before you rely on a number. This post is general information, not legal advice.

Apple, the Apple logo and iPhone are trademarks of Apple Inc., registered in the U.S. and other countries. App Store is a service mark of Apple Inc., registered in the U.S. and other countries. IOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used under license. Android, Google Play and the Google Play logo are trademarks of Google LLC.

Start with one conversation.

Create your account in a minute. Calls and texts on one number, with every conversation in one place.