A clean separation of concerns: UI, data, and call processing
MiRTA PBX promotes a predictable model: keep configuration and tenant state in a database, run Asterisk nodes as a pool, and scale horizontally with clear operational boundaries.
Multitenant model
Multiple customer environments operate on one platform instance while preserving logical separation of configuration and operational behavior per tenant.
Realtime model
Instead of relying only on flat config files and frequent reloads, Asterisk retrieves configuration dynamically from the database when needed—changes can apply immediately depending on the component.
Reference topology
A minimal diagram that matches how providers typically deploy.
Scale-out
Add Asterisk nodes for capacity. Keep configuration centralized in the database.
Failover
Operate nodes in a pool so a single node outage doesn’t imply service outage.
Operational clarity
Separate UI/provisioning from call processing and from persistent state.
Practical deployment notes
These are the decisions that usually matter most in production.
Database reliability
Use replication and backups; treat DB as critical shared state for tenants and realtime configuration.
Cache & performance
Use caching where appropriate to reduce DB load and keep latency predictable.
Network design
Keep SIP/RTP routing simple and measurable; segment management traffic from media traffic when possible.
Monitoring & OS support
Optional monitoring services help keep disk, MySQL health, security updates, and memory use under control.