The four terms

Each answers a different question.

The table below clears up the commonest confusion: believing you must choose between VoIP and cloud, when they sit on different planes.

TermWhat it isWhere it livesWho operates it
PBXA traditional telephone switchboardIn your premisesYou, or an installer
IPBXThe same device, in IP technologyIn your premisesYou, or an installer
VoIPThe technology carrying voice over the internetEverywhere: it is a protocolNot applicable
SIP trunkThe IP connection from an IPBX to the networkBetween your device and the operatorYour operator
Cloud telephonyThe switchboard hosted and run by a third partyAt the providerThe provider
PBX

The switchboard in your premises.

The historic setup: a cabinet in a technical room, physical lines, cards to add when you want more extensions. Every change goes through an intervention. The hardware depreciates over years, which makes the migration decision rarely urgent — and often late.

IPBX

The same device, in IP.

An IPBX performs the PBX function but carries voice in IP across the company network. You gain configuration flexibility and can connect to the operator by SIP trunk instead of analogue lines. But the device stays with you: its maintenance, updates, backup and replacement remain your responsibility. This is the commonest confusion — going IP is not going cloud.

SIP trunk

The pipe, not the switchboard.

A SIP trunk is the IP connection between your device and the telephone network. It replaces physical lines. It does not replace the switchboard: it feeds it. A company with an IPBX and a SIP trunk is doing VoIP, and is not in cloud telephony.

Cloud telephony

The switchboard run by a third party.

Here the device leaves your premises. The switchboard, routing rules, queues and numbers live at the provider, who handles operation and availability. You administer everything from an interface and your desks connect over the internet.

  • No switchboard hardware and no site visit to add an extension.
  • Configuration becomes online: opening hours, forwards, voice menus, queues.
  • Numbers detach from places — they become virtual numbers routed to the team you choose.
  • In exchange, everything depends on the network. An unstable connection becomes a single point of failure.
Choosing

Which one for which situation.

Your situationThe sensible option
Recent, depreciated hardware, teams on one siteKeep the IPBX, possibly move to a SIP trunk
Distributed teams, remote work, several sitesCloud telephony
High call volume, supervision neededCloud with call center software
Local numbers in several countriesCloud with virtual numbers
Unstable internet with no backupSecure the network first, migrate after
Next step

Still hesitating between keeping and migrating?

Describe your current setup and we will tell you frankly whether migration is justified, and on what horizon.

No commitment · Reply within 24 working hours

FAQ

Frequently asked questions

Can you do VoIP without moving to the cloud?

Yes, and it is very common. An IPBX in your premises connected by a SIP trunk is doing VoIP: the voice travels in IP. What changes with cloud is not the transport technology but where the device lives and who operates it.

Is cloud telephony the same as VoIP?

No. VoIP is a technology for carrying voice; cloud telephony is a way of operating the switchboard. All cloud telephony uses VoIP, but not all VoIP is cloud.

Do we have to change numbers when migrating?

Not necessarily. Porting lets you keep existing numbers; it is assessed case by case by operator, country and number type. Treat it first because it sets the timetable.

Is an IPBX cheaper than a cloud solution?

The comparison only means something in whole-life cost: on top of the hardware come installation, maintenance, updates, end-of-life replacement and an intervention for every change. Cloud turns that investment into a predictable subscription — see our pricing.

What happens if the internet goes down?

In cloud telephony, no network means no telephony. That is the honest trade-off. It is handled with a second link, a mobile fallback or automatic forwarding to mobiles, planned from the design stage.

Chat on WhatsApp