Engineering capabilities
- Multi-tenant deployment
- Add-on module selection
- High-availability pairing
- Backup and configuration versioning
VoIP
VitalPBX
Commercially maintained Asterisk distribution with a modular add-on model, used where a supported GUI and multi-tenant capability are required.
Security & hardening
- Role-based administrative access
- TLS/SRTP
- Intrusion detection and rate limiting
VitalPBX platform architecture
A supported Asterisk distribution with tenant separation, add-on modules and an optional high-availability pair for platforms that cannot be offline.
-
01
Carrier edge
- SIP trunks
- Per-tenant routes
- Failover carrier
Outbound routes scoped per tenant so cost and permissions never cross.
-
02
Border
- Firewall
- Intrusion detection
- Rate limits
Registration flood protection and source restriction on signalling ports.
-
03
VitalPBX core
- Tenants
- Add-on modules
- Queues & IVR
- HA pair
Active/standby nodes with synchronised configuration where availability requires it.
-
04
Operations
- Configuration backups
- CDR / reports
- Role-based admin
Backups taken before change windows and stored off the PBX.
Frequently asked questions
What does multi-tenancy actually give us?
Separate extension ranges, routes, IVRs and reporting per business unit or client on one platform, with administration delegated per tenant.
Is high availability worth it?
Only when call loss has a measurable cost. An HA pair adds licence and operational overhead; for many sites a documented rebuild and a spare host is the proportionate answer.
Can we migrate from FreePBX?
Yes. The engine is the same, so extensions, trunks and dial plan intent transfer u2014 but the configuration is rebuilt from an inventory and validated per call flow.
Scope the work before you commit budget
Send the environment details and get an engineered proposal with assumptions, risks and a rollback path.