> For the complete documentation index, see [llms.txt](https://support.portsip.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.portsip.com/v16.x-maintenance-mode/pbx-cluster/topology.md).

# Topology

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](broken://pages/-Mfkbk0i9gzj9bPzoXOL) solution.

Below is the architecture for the PBX cluster.

<figure><img src="/files/0N6aAHFIrFW15BqxexZR" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.portsip.com/v16.x-maintenance-mode/pbx-cluster/topology.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.