Topology
Last updated
Last updated
Usually, for a PBX, if there are many simultaneous calls, meetings, queue calls, or IVR calls, the PBX will consume massive hardware resources such as CPU, Memory, and bandwidth, therefore, we need to deploy the PBX as a cluster to handle this scenario.
PortSIP makes it easy to do so by allowing a central Call Manager server to process only the SIP signaling while media servers, meeting servers, queue servers, and IVR servers are deployed as a cluster to handle media, recording, ACD, and other call processing tasks.
The below topology of the PortSIP PBX Cluster can support up to 1M+ users, ~50,000 online users(registered users/signed-in users), and ~10,000 simultaneous calls. If you are a large service provider that needs to handle more than 50,000 online users, please consider our PortSIP UCaaS solution.
The diagram below illustrates the PBX cluster architecture. Here’s how each component works:
Call Manager Server The main server is deployed with the PBX Call Manager, Database, and Load Balancer. It primarily handles SIP signaling and database operations.
Media Servers Media Servers can be deployed as a single server or in a cluster. The Call Manager dynamically load-balances calls across the available media servers. As your business scales, you can easily add more media servers.
IVR Servers IVR Servers function similarly to Media Servers. They can be deployed individually or as a cluster. The load balancer assigns IVRs to the available servers. Additional servers can be added as needed.
Queue Servers Queue Servers, like Media and IVR servers, can be deployed as a single server or a cluster. The load balancer ensures that call queues are managed across the available servers. More servers can be added as your needs grow.
Meeting Servers Meeting Servers handle virtual meetings, and like the other servers, they can be scaled by adding more servers to the cluster. The load balancer ensures meetings are distributed effectively.
IM Servers IM Servers, while typically deployed on a single server, can support up to 50,000 online users with powerful server hardware.
For customers requiring enhanced reliability, the HA architecture provides high availability by deploying multiple Call Manager Servers and ensuring fault tolerance.
Call Manager Server In this architecture, three Call Manager servers are deployed with high availability (HA) support. A Virtual IP is exposed for access by other server components, client apps, and IP phones. This setup provides seamless SIP signaling management and guarantees continuous service in case of server failure. The diagram below provides detailed information about the Call Manager HA component, as referenced in the above PortSIP PBX HA Cluster diagram.
Further details can be found in the PortSIP PBX High Availability Architecture documentation.
Media Servers Media Servers in the HA cluster are managed by the Call Manager, which dynamically reassigns calls from any failed media server to available ones. If a media server becomes unavailable, the call manager will automatically reassign the calls of this server to another available media server.
IVR Servers IVR Servers are deployed similarly to Media Servers. If an IVR server is down, the system administrator is notified via email and can disable that server through the PBX web portal. The load balancer will then reassign IVR tasks to other active servers.
Queue Servers Queue Servers follow the same behavior as IVR Servers. In case of a server is down, the system sends an email alert to the administrator. The PBX web portal allows administrators to disable the failed server, with the load balancer reassigning tasks to another available server.
Meeting Servers For Meeting Servers, it operates similarly. If a Meeting Server fails, the administrator receives an alert and can disable it via the PBX web portal. Meetings are automatically reassigned to other active servers in the cluster.
IM Servers The IM Server can handle up to 50,000 online users when deployed on high-performance hardware. In an HA configuration, IM servers ensure that messaging services remain uninterrupted, even in the event of server failure.
