TL;DR: ICTPBX is now generally available. It’s a white-label, multi-tenant PBX platform designed for internet telephony service providers, MSPs, and resellers who want to launch a hosted voice service without building a softswitch from scratch. The stack is ICTCore for orchestration, FreeSWITCH for media, and an Angular dashboard for day-to-day management. Voice over SIP and fax over T.38 are live on day one.
What ICTPBX Is
ICTPBX is the platform you reach for when you’re an ITSP and you’ve decided you don’t want to keep duct-taping FreeSWITCH dialplans for every new customer. It gives you a multi-tenant control plane: every customer gets their own users, extensions, queues, IVRs, and call recordings, all isolated from every other tenant on the same instance. You sell the service. The platform handles the rest.
It’s white-label by default. Drop your logo on the portal, point a sub-domain at the tenant view, and your customers see your brand, not ours. There’s no “Powered by” footer you need to negotiate to remove.
The shortest description of who this is for: if you’ve been quoting SIP trunks and calling it a hosted PBX offer, ICTPBX is the product that turns that pitch into something real.
The Stack: ICTCore, FreeSWITCH, Angular
ICTPBX is built on three open standards-friendly components, and we want you to know exactly what’s running under the hood. There’s no proprietary black box.
- ICTCore handles the REST API and orchestration. It’s the layer that turns a click in the dashboard into a configured extension, a routed inbound DID, or a billable CDR. ICTCore has been in production across the ICT product family for years, so you’re not getting a v1 control plane.
- FreeSWITCH is the media engine. It runs SIP signaling, RTP, codecs, conferencing, and T.38 fax. FreeSWITCH is the same telephony engine behind a large share of cloud contact centers and hosted PBX services worldwide, which means there’s a deep talent pool if you ever need a contractor and a long history of carrier-grade deployments.
- Angular is the dashboard framework. Every screen your customer sees, and every screen your support team uses, is a modern single-page app that works on any modern browser. No softphone install for management. No Java applets. No IE-only admin pages.
If you want the deeper technical context on why a FreeSWITCH foundation matters, the ICT Innovations blog has a useful primer on how the open source SIP and media servers compare in production.
Multi-Tenant Architecture, Not Just “Multi-User”
This part matters, because there’s a meaningful difference between a PBX that lets you create lots of accounts and a PBX that’s actually designed for tenant isolation.
On ICTPBX, each tenant has its own:
- User accounts and roles, with no visibility into other tenants
- Extension number space (two tenants can both have extension 1001 without collision)
- Queues, ring groups, IVR menus, time conditions, and call flows
- Inbound DID assignments and gateway routing
- Voicemail, music-on-hold, call recording storage, and CDRs
- Billing and usage views
The tenant administrator sees only their own organization. The system administrator (you, the service provider) sees the whole instance, plus a tenant-management layer for provisioning, suspension, billing thresholds, and resource limits. The architecture documentation walks through how the control plane and media plane separate so you can scale them independently.
What You Can Run on Day One
ICTPBX ships with the modules a hosted PBX customer expects on the first day, not a roadmap that says “coming Q3.”
- SIP voice with internal extensions, external trunks, and standard codecs (G.711, G.722, Opus)
- Fax over T.38 / FoIP, properly negotiated rather than passed through as G.711 audio (which falls apart on most carriers)
- IVR menus and time conditions for after-hours routing
- Call queues with strategy options (ring-all, longest-idle, round-robin, fewest-calls)
- Ring groups for departments and sales teams
- Voicemail with email notification and audio attachment
- Conferences, follow-me, music-on-hold, and call block lists
- Call recording with per-tenant storage
- CDRs and usage reports for billing and audit
The call queue configuration guide and the IVR setup walkthrough are good starting points if you’re seeing the platform for the first time.
What’s Not in This Release (and Why We’re Saying So)
Honesty up front: ICTPBX does not currently ship with email or SMS messaging modules. Both are on the roadmap, both are being actively worked on, but neither is in production yet. If your offer depends on omnichannel today, you’ll want to wait or plan to integrate a separate messaging layer through the REST API.
For pure voice and fax, which is what most service-provider PBX deals are actually built around, you’re set.
White-Label by Default
The white-label work is something we deliberately put on the critical path. Too many “PBX platforms” treat branding as an enterprise add-on you pay extra for. On ICTPBX it’s part of the base product:
- Replace the logo, favicon, and brand color from the system admin panel
- Set custom email-notification templates per tenant
- Use sub-domains or your own custom domains for the tenant portal
- Configure your own support and contact information per tenant
The result is that your customers experience your service. Not ours. That’s the difference between selling a PBX and selling someone else’s PBX with your invoice attached.
Why Service Providers Are Looking at This Now
The hosted-PBX market has consolidated around two patterns, and both have problems.
The big SaaS PBX brands (you know the names) charge per seat, often $20 to $40 per user per month, and force you to resell at razor margins. Your customer’s bill goes up every time they hire someone, and so does yours. You don’t own the platform; you’re a reseller of someone else’s revenue stream.
The DIY route, where you self-build on raw FreeSWITCH or another open source softswitch, gives you control but burns engineering hours by the dozen on every new customer onboarding. By the time you’ve built tenant isolation, a billing layer, a customer portal, and a provisioning workflow, you’ve effectively built ICTPBX, just with more bugs and less documentation.
ICTPBX is the middle path. You get a multi-tenant platform with the control-plane work already done, the source code open and inspectable, and pricing that doesn’t scale per seat. The economics start to work for service providers somewhere around the 50-extension mark and only get better from there. The ICT Innovations writeup on building scalable VoIP infrastructure with open source tools covers this argument in more depth.
Where ICTPBX Fits in the Vision Product Line
ICTPBX joins a product family that already includes ICTBroadcast (call center and broadcasting), ICTContact (contact center), ICTDialer (auto dialer), ICTFax (fax server), and ICTCRM. They share the ICTCore foundation, which means a service provider running multiple ICT products gets a consistent administration model and a single REST API surface to integrate against.
The product overview on the parent site at ict.vision/ict-pbx shows where the PBX sits in the wider Vision portfolio if you’re evaluating a multi-product rollout.
Getting Started
If you’re an ITSP, MSP, or reseller looking at ICTPBX for the first time, here’s the shortest path to a working evaluation:
- Pick a server. A modest VPS (4 vCPU, 8 GB RAM) handles a single-tenant pilot or a small multi-tenant deployment. For production density, expect to size based on concurrent calls rather than extensions: a media node sized for 100 concurrent calls comfortably supports 800 to 1,000 extensions on typical busy-hour assumptions.
- Install the platform. The installation guide walks through the steps. If you want managed installation or hosting, the ICT operations team can do the deployment for you.
- Configure your first tenant. The tenant-management documentation covers provisioning, resource limits, and suspension workflows. Spin up a test tenant, add a few extensions, and place a real call.
- Connect a SIP trunk. Bring your own carrier (Twilio, Bandwidth, Telnyx, Flowroute, or any standard SIP provider). The gateway and inbound-route configuration are documented per tenant.
- Brand it. Drop your logo, set the portal sub-domain, and verify the customer-facing screens show your identity.
- Pilot with a friendly customer. A 10-extension pilot on a single tenant uncovers most operational questions you’ll have at scale. From there, the path to general availability is mostly capacity planning and support process.
FAQ
Is ICTPBX really multi-tenant, or just multi-user with permissions?
It’s multi-tenant. Each tenant has an isolated extension number space, isolated CDRs, isolated recordings, and its own admin role. Two tenants can share the same instance with no visibility into each other’s traffic, users, or configuration. The system administrator sees the whole platform; tenant administrators see only their organization.
What’s the underlying tech stack?
ICTCore for the REST API and orchestration, FreeSWITCH for SIP signaling and media, and Angular for the web dashboard. All three are mature components with active maintenance. The architecture cleanly separates the control plane from the media plane so you can scale them independently.
Does ICTPBX support fax?
Yes. Fax over T.38 (also called FoIP) is part of the day-one feature set, properly negotiated rather than passed through as G.711 audio. 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. SMS messaging and email modules are on the roadmap and being actively developed, but neither is in production today. If your offer requires omnichannel from the start, plan to integrate a separate messaging layer through the REST API.
How is ICTPBX priced?
The platform isn’t priced per seat or per extension. Service providers pay for the platform license and optional support, then add their own carrier minutes and infrastructure costs on top. The economics start to favor ICTPBX over per-seat SaaS PBX brands somewhere around the 50-extension mark and improve from there.
Can I white-label the customer portal completely?
Yes. Logo, favicon, brand color, sub-domain (or your own custom domain), email templates, and contact information are all configurable. There’s no “Powered by ICTPBX” footer that customers see by default.
Can I bring my own SIP trunk?
Yes. ICTPBX is carrier-agnostic. Configure your SIP gateway in the system admin panel, point inbound routes to the appropriate tenant, and you’re delivering calls. Most providers run separate trunks for outbound (rated minutes) and inbound (DIDs).
Where do I get support during evaluation or production?
Open a ticket through the ICT Vision support portal. Pre-sales questions go to the same queue. Paid support and managed-hosting options are available for production deployments.
Ready to Evaluate ICTPBX?
If you’ve been waiting for a multi-tenant PBX platform that you can actually brand as your own and run on your own infrastructure, the wait’s over. Visit the ICTPBX homepage for the platform overview, browse the documentation for the technical detail, or reach the team through the support portal to set up an evaluation environment.