Multitenant Realtime Asterisk PBX
The MiRTA PBX is an interface written in PHP using Mysql as backend to manage a multitenant PBX built over the Asterisk Open Source PBX. An easy to use interface allows you to manage one or more Asterisk PBX in a multi tenant, load sharing and high availability configuration. All configurations are stored in a database to be easily integrated into existing CRM or billing software. All features usually embedded in a professional PBX can be found in Asterisk and in MiRTA PBX interface.
Our VoIP expert is ready to answer to your questions and to help you to solve any of the problems you can find in running your business.
Got something new in mind?
Don't worry - we can code it!
A Multitenant PBX is capable of serving multiple distinct clients with a single instance of the software. In other words, each client has a dedicated PBX, but all of them share the same server and the same asterisk instance. With a multitenant architecture, a software application is designed to virtually partition its data and configuration, and each client works with a customized virtual application instance. Using the same asterisk instance for all the clients is a real cost and resource saving solution.
A common Asterisk based PBX stores configuration data in plain files. Every time a change in the configuration has to be made, the configuration file is changed and asterisk has to be instructed to reload its config. This scenario can be comfortable for a single instance, single client installation. When the number of clients raises, the "reload" action starts to hammer Asterisk, decreasing its performance and decreasing the call quality for all the clients or even locking it. A Realtime PBX uses a database instead of plain files and configuration is read in real-time, from the database, only when needed. Every change to the configuration is made in the database and it is immediately active, without the need for a reload.
The MiRTA PBX can be hosted on a single server or it can be ran on multiple servers achieving both Scalability and High Availability. Each component of the system can be ran on a distinct server and you can increase the overall capacity and resilience by just adding more servers. Each asterisk server can be used by any client, so you can power off any server of the pool without disrupting the services. No info is stored in the single asterisk server, as all the data is pulled from the database servers. A smart caching system, if needed, will save on bandwidth and database servers' CPU power.