Engineering capabilities
- Cloud or self-hosted deployment
- Softphone and mobile clients
- SIP trunk provisioning
- Call reporting
VoIP
3CX
Commercial UC platform for organisations that want integrated softphone, web client and provisioning with vendor support.
Security & hardening
- Secure SIP and tunnelling
- Access control per extension
- Managed update path
3CX deployment architecture
3CX can run self-hosted or in the cloud; the design decisions that matter are trunk placement, client connectivity and how remote users traverse the network.
-
01
Trunks & numbers
- SIP trunk provider
- DID ranges
- Emergency routing
Provider templates verified against the account's actual authentication and CLI requirements.
-
02
Network edge
- Firewall rules
- SIP tunnel / STUN
- Public FQDN + certificate
3CX firewall checker used as a gate before go-live; tunnelling for clients on restrictive networks.
-
03
3CX server
- Self-hosted VM or cloud instance
- Digital receptionist
- Queues & call groups
Sized by simultaneous calls, not user count; recording and reporting enabled per licence tier.
-
04
Clients
- Web client
- Desktop app
- Mobile app
- Provisioned IP phones
Welcome-email provisioning for users; supported phone models provisioned automatically.
-
05
Integration
- CRM connector
- Microsoft 365 contacts
- Call reports
Integrations limited to supported connectors to keep the upgrade path clean.
Frequently asked questions
Self-hosted or cloud-hosted 3CX?
Cloud suits distributed teams and removes local hardware dependency. Self-hosted suits sites with local PSTN gateways, strict data residency, or existing virtualization capacity. Both are supported; we size the choice against your call volume and connectivity.
How many simultaneous calls do we need?
Licensing is by concurrent call, not extension. We derive it from busy-hour call statistics from your existing system rather than guessing from headcount.
Do remote agents need a VPN?
Usually not u2014 the apps use the 3CX tunnel over a single port. VPN is reserved for cases where policy requires it or where deskphones must be reachable remotely.
Can we migrate from an existing PBX?
Yes. Numbers, IVR logic and extension mapping are documented from the current platform, rebuilt in 3CX, tested with a pilot group, then cut over with the old system kept ready for rollback.
Scope the work before you commit budget
Send the environment details and get an engineered proposal with assumptions, risks and a rollback path.