MiRTA PBXMultitenant · Realtime · Asterisk

Architecture

Multi-tenant Asterisk PBX architecture

The MiRTA PBX web layer manages provider and tenant operations. MySQL holds shared configuration and state; Asterisk nodes process calls.

MiRTA PBX reference architecture Operators and APIs use the MiRTA PBX web and services layer. The services layer reads and writes tenant state in MySQL. Asterisk nodes retrieve realtime configuration from MySQL. SIP endpoints and trunks exchange signaling and media with the Asterisk node pool. CONTROL AND CONFIGURATION Operators and APIs Admin · Tenant UI APIs · Automation MiRTA PBX services Tenant logic · Provisioning Provider and tenant UI MySQL state Tenant state · Realtime config Operational data HTTPS / API SQL Orchestration Realtime configuration CALL PROCESSING AND MEDIA Voice network SIP trunks · Phones WebRTC · PSTN routing Asterisk node pool Add licensed nodes for capacity and resilience Asterisk node 1 Asterisk node 2 Additional nodes SIP / RTP

Tenants have logically separate configuration, dialplans and permissions within shared application, database and call-processing layers. Manage access through user profiles and tenant assignments.

Deployment and resilience

Single node

Start with one call-processing node and local database where the workload and availability requirements permit.

Multiple nodes

Pool Asterisk nodes with shared realtime configuration. Plan database replication, SIP routing and failure handling together.

High availability depends on database replication, SIP routing and tested failure handling. Active calls may end when a node fails; test call routing and database recovery in your topology.

Installation and cluster requirements · Server licensing

Who operates what?

MiRTA PBX capabilityProvider responsibility
Tenant administration and access controlsCreate tenants, assign permissions and support your customers.
SIP routing and call flowsSupply carriers and numbers; configure and test signaling, media and interoperability.
Shared database and node configurationProvide compute, storage and networking; secure, monitor, back up and recover the service.
Single-node and clustered deploymentSize and test physical or virtual infrastructure for concurrency, codecs, recordings, queues and integrations.

Server capacity depends on workload and infrastructure. Software and Asterisk integration support are included; operational services are arranged separately. See inclusions and exclusions.

Plan your evaluation

Bring expected concurrency, carrier layout and availability goals to review the topology and pilot tests.

Book a 30-minute technical reviewSend a question