TL;DR: ICTPBX is now generally available at ictpbx.com. It’s a white-label, multi-tenant PBX platform aimed at ITSPs, MSPs, and service providers, built on ICTCore (REST API and orchestration), FreeSWITCH (media engine), and Angular (web dashboard). Voice over SIP and fax over T.38 ship in this first release.
Why This Release Matters
ICTCore has been the orchestration backbone for ICT’s product family for years. ICTBroadcast, ICTContact, ICTDialer, ICTFax, and ICTCRM all run on the same control-plane foundation. ICTPBX extends that foundation into the hosted-PBX category, which is the part of the service-provider stack that most resellers have been buying from somebody else.
The pitch is simple: if you’ve been building voice on raw FreeSWITCH and writing your own multi-tenant control plane piece by piece, ICTPBX gives you the control plane already built. If you’ve been reselling a SaaS PBX and watching your margin compress every time a customer hires another five people, ICTPBX gives you a self-hosted, flat-cost alternative.
The Stack
Three components, all open and inspectable:
- ICTCore handles REST API and orchestration. Mature, multi-product, in production.
- FreeSWITCH handles SIP signaling, RTP, codecs, conferencing, and T.38 fax. The same media engine behind a meaningful share of the world’s hosted-PBX and contact-center traffic. If you want background on why a FreeSWITCH foundation matters here, the post on FreeSWITCH performance and optimization is a good companion read.
- Angular is the web dashboard framework. Modern single-page app, no softphone install for management, no legacy admin pages.
The architecture cleanly separates the control plane (ICTCore) from the media plane (FreeSWITCH), so a service provider can scale each independently. A single media node sized for 100 concurrent calls comfortably supports 800 to 1,000 extensions on typical busy-hour assumptions.
Multi-Tenant by Design
Every tenant on an ICTPBX instance has its own isolated extension number space, queues, IVRs, DID assignments, voicemail, call recording storage, and admin role. Two customers can both use extension 1001 without collision. Tenant administrators see only their organization. The system administrator (the service provider) sees the whole platform plus a tenant-management layer for provisioning, suspension, billing thresholds, and resource limits.
That’s the difference between a PBX with permissions and a PBX engineered for service-provider deployment. The architecture and tenant-isolation model are documented at the ICTPBX architecture overview.
White-Label Out of the Box
Branding is part of the base product, not an enterprise add-on. Replace the logo and favicon, set a brand color, configure email-notification templates per tenant, and point sub-domains (or your own custom domains) at the tenant view. Your customers see your service. There’s no “Powered by” footer to negotiate away.
Day-One Capabilities
- 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, queues with multiple strategies
- Voicemail with email notification, conferences, follow-me, music-on-hold, call block
- Per-tenant call recording with searchable metadata, full CDRs and usage reports
- White-label branding, custom domains, configurable email templates per tenant
What’s not in this release: SMS messaging and email modules. Both are on the active roadmap and neither is in production today. If your service offering depends on omnichannel from day one, plan to integrate a separate messaging layer through the REST API.
Where ICTPBX Fits in the Bigger Picture
For service providers running multiple ICT products, the consistency matters. Same ICTCore control plane, same REST API surface, same administration model across ICTBroadcast, ICTContact, ICTDialer, ICTFax, ICTCRM, and now ICTPBX. The integration story is meaningfully simpler when the products share a foundation.
The product overview on the parent site at ict.vision/ict-pbx shows where ICTPBX sits in the wider Vision portfolio. For a deeper read on the open source approach to scaling voice infrastructure overall, see building a scalable VoIP infrastructure with open source tools and the comparative analysis of open source SIP servers.
Getting Started
- Visit ictpbx.com for the platform overview and product documentation.
- Read the installation guide if you’ll self-host, or the architecture overview if you’re evaluating fit.
- Open a ticket at the ICT Vision support portal for pre-sales, evaluation environments, or managed-hosting requests.
FAQ
Is ICTPBX really multi-tenant?
Yes. Each tenant has an isolated extension number space, isolated CDRs, isolated recordings, and its own admin role. The architecture is engineered for service-provider deployment, not retrofitted with permissions on a single-tenant PBX.
What’s under the hood?
ICTCore for REST API and orchestration, FreeSWITCH for SIP signaling and media, Angular for the web dashboard. Three open components, no proprietary black box. Control plane and media plane scale independently.
Does ICTPBX support fax?
Yes. T.38 (FoIP) is part of the day-one feature set, properly negotiated rather than passed as G.711 audio. T.38 is what you want for fax over real SIP trunks.
Does ICTPBX support SMS or email?
Not in this release. Both are on the roadmap. If your offer requires omnichannel today, plan to integrate a separate messaging layer through the REST API.
How do I request an evaluation?
Open a ticket at service.ictvision.net. Pre-sales and evaluation requests both go to the same queue.