28 November 2025 · 6 min read
Most growing businesses reach a point where WhatsApp and a shared mobile number are no longer sufficient. Calls get missed. There is no call recording. Routing incoming calls to the right person requires someone to manually transfer. Reporting on call volumes is impossible. The solution is a PBX — a Private Branch Exchange — which handles routing, extensions, voicemail, and call management for the organisation. The question is which type.
A hosted PBX (also called a cloud PBX or VoIP service) is a phone system delivered by a third-party provider over the internet. The hardware and software are managed by the provider; you pay a monthly fee per user or per line. Examples include Exotel, Knowlarity, Ozonetel in India, and international providers like RingCentral or Twilio Flex. Setup takes hours. Maintenance is handled by the vendor. Costs are predictable.
FreeSWITCH is an open-source telephony platform that you install and run on your own infrastructure. It is the underlying engine behind many commercial PBX products and some hosted services. FreeSWITCH gives you complete control over call routing logic, recording, integration with other systems, and scaling — but requires a technically competent team to deploy and maintain.
For most businesses, hosted PBX is the correct answer. The reasons are practical:
If your team is under 50 people, your call volume is moderate, and you don't need deep integration with custom internal systems, a reputable hosted PBX is almost certainly the better choice.
FreeSWITCH becomes the right answer when your requirements exceed what hosted PBX providers can deliver:
FreeSWITCH is free to download and run. The costs are elsewhere:
Initial deployment: a production-grade FreeSWITCH installation requires server infrastructure, network configuration (particularly around NAT traversal and firewall rules), SIP trunk provisioning, codec selection, and security hardening. An experienced telephony engineer typically spends two to four weeks on a clean deployment. This is not a weekend project.
Ongoing maintenance: FreeSWITCH requires OS-level maintenance, version updates, monitoring for call quality issues, and debugging when edge cases in SIP signalling cause problems. Voice quality issues — jitter, echo, one-way audio — are often difficult to diagnose and require someone with specific telephony experience to resolve.
SIP trunk management: you will need agreements with one or more SIP trunk providers for PSTN connectivity (making and receiving calls to regular phone numbers). Managing these relationships, monitoring trunk capacity, and handling number porting adds administrative overhead that hosted PBX providers absorb.
Security: internet-exposed SIP infrastructure attracts automated scanners and toll fraud attempts constantly. A misconfigured FreeSWITCH installation can result in fraudulent calls billed to your trunks within hours of deployment. Security hardening, fail2ban configuration, rate limiting, and ongoing monitoring are non-optional.
Some organisations run both: a hosted PBX for general office use, and a FreeSWITCH instance for specific high-volume or integration-heavy use cases. This is more complex to manage but preserves the simplicity of hosted PBX for the majority of users while enabling custom capabilities where they matter.
Start with hosted PBX unless you have one or more of the following:
If none of these apply, the simplicity, reliability, and vendor support of a hosted PBX will deliver better outcomes than the control and flexibility of a self-hosted system. The freedom FreeSWITCH offers is real — but it comes with real operational responsibility. That responsibility is only worth taking on when the requirements genuinely demand it.