One platform. Run it your way.
IBeX4 deploys in almost any virtual environment. If it runs Debian 13, it runs IBeX4: a virtual machine, an LXC container or a dedicated server. How you run it depends on the infrastructure you have, the size of your system and how much you want us to handle.
Choose where IBeX4 runs
On your infrastructure
Already run VMware, Proxmox VE, Microsoft Hyper-V, KVM, a public cloud or your own Debian 13 servers? Install IBeX4 there, as a VM, an LXC container or directly on the server.
On a system we design
No suitable infrastructure yet? FTI supplies hardware that meets the required specifications, with the hypervisor and IBeX4 preinstalled, and hands it over ready to run, with training and implementation support. Each design fits the customer; there is no off-the-shelf box.
Hosted by FTI
Your own dedicated IBeX4 instance in FTI’s secure US data center on Tier 1 Internet, on infrastructure run by FTI.
Standard or custom installation?
Not sure which you need? Tell us about your environment and we’ll recommend one.
Standard installation
IBeX4 on your own hypervisor or Debian 13 server. Your team can install it, or FTI can carry out a full implementation: installation, configuration, dial plan, migration and cut-over. This suits many organizations, for example a university with an established virtualization team.
Custom installation
FTI designs the installation around your network, scale, interconnects and integrations. We can supply hardware that meets the required specifications with the platform preinstalled, and back it with training and implementation support. Most service providers need a custom installation, as do complex multi-site organizations. Carriers and high-volume providers usually start from one of FTI’s standard high-availability designs, which run on a hypervisor.
Connecting IBeX4 to the phone network
Bring your own provider
IBeX4 connects to SIP Trunking from the provider of your choice.
SIP Trunking from IBeXc
Or use SIP Trunking & IP Interconnection from IBeXc, including connections into the US for systems running anywhere in the world. One company for the software, the installation and the connection.
Legacy circuits
In a virtual machine or container, older T1/E1, PRI and analog connections attach through SIP gateways. On a dedicated Debian 13 server they may also connect through telephony cards.
Deployment questions
Do I need a custom installation?
Service providers almost always do, because IBeX4 has to fit their network, interconnects and billing. Many organizations, such as universities with their own virtualization team, run a standard installation. Either way, FTI can carry out the full implementation. We’ll tell you which fits after a short conversation.
Which phones work with IBeX4?
Works with any IP phone that supports the SIP standard, from any manufacturer, plus softphones and mobile apps.
What hardware do I need?
Any server that runs Debian 13 or a supported hypervisor, or FTI can supply hardware that meets the required specifications with IBeX4 preinstalled.
Can IBeX4 run in a public cloud?
Yes. IBeX4 installs on a Debian 13 virtual machine in public clouds such as Microsoft Azure and Google Cloud, in the region you choose.
Where do I get SIP Trunking for IBeX4?
From the provider of your choice, or from IBeXc, which offers SIP Trunking & IP Interconnection, including into the US.
Can we connect to the US phone network from outside the US?
Yes. IBeX4 systems outside the US can use SIP Trunking & IP Interconnection from IBeXc to connect into the US.
Let’s plan your installation
Tell us where you want IBeX4 to run and how many extensions it will serve.