TL;DR: ICTPBX is now generally available at ictpbx.com. It’s a white-label, multi-tenant PBX platform for ITSPs, MSPs, and service providers, built on ICTCore for orchestration, FreeSWITCH for media, and Angular for the dashboard. ICTPBX joins ICTBroadcast, ICTContact, ICTDialer, ICTFax, and ICTCRM as the sixth product in the ICT Vision lineup.
What ICTPBX Adds to the Vision Portfolio
If you’ve been following ICT Vision’s product line, you’ve seen the contact center pieces (ICTContact), the predictive dialing pieces (ICTDialer), the broadcasting pieces (ICTBroadcast), and the fax pieces (ICTFax). The hosted PBX gap was the obvious one, and that’s the gap ICTPBX fills.
ICTPBX is built specifically for service providers who want to sell hosted voice as their own branded service rather than as a reseller of someone else’s SaaS. Multi-tenant by design, white-label by default, and self-hostable on infrastructure you control. There’s no per-seat license, which means the unit economics work for resellers in a way that the big SaaS PBX brands rarely allow.
The product page at ict.vision/ict-pbx covers where this sits in the Vision portfolio. The product site at ictpbx.com is where the documentation, downloads, and evaluation requests live.
The Stack: Three Open Components
One thing we want to be clear about: there’s no proprietary black box under ICTPBX. The platform is assembled from three components that have been in production for years:
- ICTCore for the REST API and orchestration. This is the same control plane behind the rest of the Vision product family, so service providers running multiple ICT products get a consistent administration model.
- FreeSWITCH for the media engine. SIP signaling, RTP, codecs, conferencing, and T.38 fax all run on FreeSWITCH. It’s the same engine carrying a meaningful share of the world’s hosted-PBX and contact-center traffic.
- Angular for the web dashboard. Modern single-page app, no softphone install, no Java applets, no legacy admin pages.
The architecture is documented in detail at the ICTPBX architecture overview. Worth reading if you’re evaluating the platform for production.
Multi-Tenant Means Multi-Tenant
This part deserves a callout, because the word “multi-tenant” gets used loosely in PBX marketing.
On ICTPBX, every tenant has its own isolated extension number space, its own queues and IVRs, its own DID assignments, its own voicemail and call recording storage, and its own admin role. Two tenants can both use extension 1001 without collision. A tenant administrator sees only their own organization. The system administrator (you, the service provider) sees the whole platform plus a tenant-management layer for provisioning, suspension, and resource limits.
That’s the difference between a PBX with permissions and a PBX designed for service-provider deployment.
Day-One Capabilities
The first release ships with the modules a hosted-PBX customer expects on day one:
- SIP voice with internal extensions, trunks, and standard codecs (G.711, G.722, Opus)
- Fax over T.38 / FoIP, properly negotiated rather than passed as G.711 audio
- IVR menus, time conditions, ring groups, and call queues
- Voicemail with email notification
- Conferences, follow-me, music-on-hold, call block lists
- Per-tenant call recording and CDRs
- White-label branding (logo, sub-domain, email templates, support links)
What’s not in this release: SMS messaging and email modules. Both are on the active roadmap but neither is in production today. If your service requires omnichannel from the start, plan to integrate a separate messaging layer through the REST API or wait for the upcoming releases.
Where ICTPBX Fits Against the Alternatives
The hosted-PBX market has been polarized for a while. On one side, the big SaaS PBX brands charge $20 to $40 per seat per month and give you no ownership of the platform. On the other side, you can self-build on raw FreeSWITCH and burn engineering hours by the dozen on every customer onboarding. ICTPBX is the middle path: a multi-tenant, white-label control plane already built, with the source code open and inspectable, and pricing that doesn’t compound with every new extension you provision.
For a deeper read on the open source approach to scaling voice infrastructure, the ICT Innovations writeup on building scalable VoIP infrastructure covers the technical and economic argument.
Who Should Look at This
You’re a likely fit if any of the following describes you:
- An ITSP or MSP that’s been quoting SIP trunks and wants to upsell hosted PBX
- A reseller currently paying per-seat to a SaaS PBX and watching margin compress as customers grow
- A service provider that needs control over the data plane (HIPAA, GDPR, country-specific data residency) and can’t accept third-party SaaS PBX
- A telecom operator launching value-added services on top of voice
- A systems integrator deploying multi-tenant voice for vertical markets (real estate, legal, healthcare)
You’re probably not a fit (yet) if you need omnichannel SMS and email from the start, or if your team has zero Linux operations capacity and doesn’t want managed hosting.
Getting Started
The shortest path from “this might be interesting” to “working evaluation” looks like this:
- Read the architecture overview to understand how control plane and media plane separate.
- Open the ICT Vision support portal with a pre-sales question. Whether you want to self-host or have ICT host the deployment for you, the same queue handles it.
- Once an evaluation environment is up, the tenant-management documentation walks through provisioning your first tenant, and the IVR and queue guides cover the customer-facing configuration.
FAQ
Is ICTPBX free or paid?
The platform license and support model is documented on ictpbx.com. Pricing is not per seat. Service providers pay for the platform and optional support, then add their own carrier minutes and infrastructure costs. The economics typically favor ICTPBX over per-seat SaaS PBX brands somewhere around the 50-extension mark and improve from there.
Where does ICTPBX fit alongside ICTContact and ICTBroadcast?
ICTContact is a contact-center platform (inbound, outbound, agent dispositions, IVR-driven workflows). ICTBroadcast is a voice and message broadcasting platform. ICTPBX is the day-to-day phone system: extensions, ring groups, voicemail, queues, conferences, fax. A service provider can run all three on the same ICTCore foundation if the customer demand justifies it.
Does ICTPBX support fax?
Yes. T.38 (FoIP) is a day-one feature, properly negotiated. T.38 is what you want if you’re carrying fax traffic over real SIP trunks; the audio-passthrough approach falls apart on most modern carriers.
Does ICTPBX support SMS or email?
Not in this release. Both are on the roadmap and being actively developed. If your offer needs omnichannel today, plan to integrate a separate messaging layer through the REST API.
Can I bring my own SIP carrier?
Yes. ICTPBX is carrier-agnostic. Configure your SIP gateway in the system admin panel, point inbound routes to the right tenant, and you’re delivering calls.
How do I request an evaluation?
Open a ticket at service.ictvision.net. Pre-sales, evaluation environments, and managed-hosting questions all go to the same queue.
