Deployment
On-premise, at your site
The server sits on your network, in your building. Internal calls keep working when the line to the outside world does not, which for a hotel, a factory or a hospital wing is the whole argument.
How it fits together
-
on your own network
Your server
On your network, on a machine of its own. Installed and supported by us.
-
over the internet
Your office
Desk phones and computers on the same network. Calls between them never leave the building.
-
Staff elsewhere
The apps reach the system over an encrypted tunnel. Deskphones at a branch come in through a session border controller, so that site needs nothing opened.
Your numbers arrive on a SIP trunk from a licensed provider. If that link drops, calls between people in the building carry on as normal.
What the machine needs
Worth reading before you plan this, because it is where on-premise projects go wrong. 3CX installs its own web server and database, so it is not happy sharing a machine with something else that has opinions about ports 80 and 443.
- A machine of its own. Physical or virtual, but not one already running your file share or your accounting system.
- Debian Linux. We install and harden it; you do not need a Linux person on staff.
- A fully qualified domain name pointing at it. Take the name 3CX supplies and the certificate is issued and renewed for you; use one of your own and renewing it stays your job, which we will cover in the support plan if you would rather it were ours.
- Split DNS, so that name resolves correctly both inside the building and outside it. This is the single most common cause of "it works at my desk but not at home" — and it is also what lets internal calls carry on when the line to the outside world drops, because the phones can still find the server without asking the internet.
- SIP and RTP ports open to the trunk provider, and to nobody else. Remote staff and branch deskphones need their own ports on top of that, which we set up and lock down with your IT team.
- Power that does not flicker. A UPS. The phone system is the thing you need most in the ten minutes after something goes wrong.
What we do, and what happens afterwards
What we install
- The operating system and 3CX, built and hardened
- Certificates, firewall rules and the anti-fraud settings
- Your trunk and numbers, tested end to end
- Extensions, menus and call flows, and the desk phones configured
- Backups running off the machine, not onto it
Who looks after it
We do, under a support plan, working with whoever runs your IT. Updates are scheduled with you rather than applied on a Friday afternoon.
A server in your building is a thing that can fail, so the plan covers what happens when it does: where the backup is, how long a rebuild takes, and how calls reach people while it happens.
How long it takes, and what it costs
A straightforward office is usually a couple of weeks from order to live: a few days waiting on hardware, a day building and configuring, and a cutover we schedule with you rather than spring on a Tuesday morning. Numbers being ported from another provider set the pace more often than anything we do.
You pay for the server once, the 3CX licence each year, the setup, and then a support plan. Numbers and trunk minutes sit alongside. We put all of it in one quote, because the whole point of owning the machine is knowing what it costs.
See it on a real system
A 30-minute session on a live system, walked through in your own terms. No obligation, and prices in KES.
We confirm your slot within 24 hours.