The technology other providers run on.
Service providers around the world license IBeX to run their own communications services. IBeX4 installs anywhere Debian 13 runs, in your own VMs, containers or servers, installed and designed around your network by FTI.
A platform you run as your own
What do providers use IBeX4 for?
As the softswitch behind their own hosted phone services: the call engine, voicemail, queues and features their customers use, running on infrastructure the provider controls.
Is it white-label?
Yes. Your customers see your brand and your service. FTI never names the providers that run on IBeX.
Custom installation is the norm
Every provider network is different, so provider deployments are designed and installed by FTI around your interconnects, scale, redundancy and back-office systems.
The same licence as everyone
Providers pay the same published rate per configured device as every IBeX4 customer, billed monthly on peak usage, so the cost of the platform grows with your services. Standby, disaster recovery and lab instances are included.
Standard high-availability designs for carriers and high-volume providers
Standard high-availability designs
FTI has standard high-availability designs for carriers and high-volume providers: IBeX4 on clustered hypervisor hosts with standby instances, so a host or instance failure doesn’t take your services down.
Proven on our own service
FTI’s own IBeXc hosted phone service runs on IBeX4 with N+2 redundancy: two components can fail at the same time and service continues. Your design can go to whatever level of redundancy you need.
Built on a hypervisor
These designs normally require a hypervisor, such as Proxmox VE or VMware, because failover, live migration and snapshots come from the virtualization layer. FTI can supply and preinstall the hosts as part of a custom installation.
Tested at carrier scale
IBeX4 has been tested to 8,500 simultaneous calls on FTI’s virtual machine systems. It can go higher; the limit was our test equipment.
Updates without outages
Standby instances and the three-stage release process let you apply updates one node at a time while calls keep flowing.
Standby licences included
Standby and disaster-recovery instances are included in provider licensing, so the right design doesn’t cost extra licences.
AI management and configuration control
High-availability solutions can include AI-assisted management and configuration control, keeping every node consistent and changes tracked across the cluster.
Designed and priced with you
High-availability installations are complex, so we develop the design and pricing together with you, based on your sites, traffic and redundancy needs.
Built by FTI, proven by others
Your infrastructure, your regions
Run IBeX4 in your own data centers or cloud regions, close to your customers.
Built for uptime
Standby instances, hypervisor clustering and a three-stage release process keep services running through updates.
Any SIP phone, any brand
Works with any IP phone that supports the SIP standard, plus softphones and mobile apps, so your customers keep the phones they like and you are never tied to one manufacturer.
Connect into the US
Serving customers who need US connectivity? SIP Trunking & IP Interconnection is available through IBeXc.
Provider questions
Is IBeX4 a softswitch?
Yes. For service providers, IBeX4 is the softswitch and application platform behind their hosted phone services, installed on Debian 13 in the provider’s own VMs, containers or servers.
Which providers use IBeX?
Providers around the world license IBeX. We don’t name them.
How is IBeX4 licensed for providers?
The same way as every IBeX4 customer: per configured device (each configured SIP and IAX2 peer, including trunks; dial-plan numbers are not counted), billed monthly on the 25th for peak usage, stepping down about 10% per volume band. See licensing.
Does IBeX4 support high availability for carriers?
Yes. FTI’s own IBeXc service runs on IBeX4 with N+2 redundancy, and designs can go to whatever level of redundancy is required. FTI has standard high-availability designs for carriers and high-volume providers, built on clustered hypervisor hosts with standby instances, and they can include AI-assisted management and configuration control. These designs normally require a hypervisor, and each installation is designed and priced with the customer based on the sites’ needs.
Do providers need a custom installation?
Almost always. FTI designs the deployment around your network, interconnects and systems, then installs and supports it.
Can IBeX4 integrate with our billing and provisioning?
Integration is part of a custom installation.
Building or rebuilding a hosted phone service?
Run your own numbers in the provider profit calculator, then tell us about your network and we’ll design an IBeX4 deployment around it.