Deployment
On your own server or cloud
The system runs on a machine of your own: a server in your building, or one in your own cloud account with AWS or a Kenyan cloud provider. You pay for the machine. We can set the system up for you, and a support plan from us is optional.
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.
-
on your own network
Your server
On your network, on a machine of its own.
-
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 as router phones or through a session border controller, so that site needs nothing opened.
Outside calls arrive on a SIP trunk from the phone line provider you choose. If that link drops, calls between people in the building carry on as normal.
Or in your own cloud account
The same system runs inside your own cloud account, with AWS or a Kenyan cloud provider, on your own bill and under your own controls. Every office and every member of staff reaches it over the internet, so branches share extensions and transfer calls.
The account stays yours
The instance, the storage, the recordings and the logs are inside an account you own. Your security team audits it the way they audit everything else.
It sits with the rest of your estate
Same account, same network design, same monitoring, same tagging and cost reporting. Not a separate thing bolted on the side.
No lock-in to us
If you change partner, the system stays where it is, because it was never ours to move.
The cloud bill comes to you directly from your provider. We do not mark it up, because we never see it.
What the machine needs
Worth reading before you plan this, because it is where these 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, virtual or a cloud instance, but not one already running your file share or your accounting system.
- Debian Linux. We can install and harden it as part of the setup; you do not need a Linux person on staff for that.
- 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 a support plan from us can cover if you would rather it were ours.
- Split DNS for a server in your building, 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, for a server in your building. A UPS. The phone system is the thing you need most in the ten minutes after something goes wrong.
What we set up, and what happens afterwards
What the setup includes
- The operating system and 3CX, built and hardened
- Certificates, firewall rules and the anti-fraud settings
- Your SIP trunk, from the provider you choose, connected and tested
- Extensions, menus and call flows, and the desk phones configured
- Backups running off the machine, not onto it
Who runs it afterwards
The system is yours, so your IT team can run it. If you would rather we did, a support plan from us is optional: we then work with whoever runs your IT, and schedule updates with you rather than apply them on a Friday afternoon.
A server of your own is a thing that can fail, so plan for 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
We'll agree an installation date with you.
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. In a cloud account there is no hardware to wait for, and the time goes on access instead: a role provisioned in your account, and the network questions answered by the people who own them.
You pay for the machine, either a server once or your cloud provider's monthly bill, then the 3CX licence each year, the setup, and a support plan if you want one. Your numbers and calls are billed by your phone line provider. We put our part 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.
We confirm your slot within 24 hours. Prefer to write? Email or message us.