> For the complete documentation index, see [llms.txt](https://docs.mikopbx.com/mikopbx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mikopbx.com/mikopbx/english/readme/system-requirements.md).

# System requirements

Discription of system requirements for the MikoPBX system

### Network Channel Requirement

An example of calculating the required channel bandwidth for different codecs for 30 simultaneous calls. PBX supports the most popular codecs:

* **G.711** - 4.67 Mbps
* **GSM** - 1.68 Mbps
* **G.722** - 4.67 Mbps
* **G.729** - 1.38 Mbps

{% hint style="info" %}
The calculation is approximate, when using the same codec on all devices connected to the PBX. Read more [here](https://www.asteriskguru.com/tools/bandwidth_calculator.php).
{% endhint %}

### Minimum system requirements

{% hint style="warning" %}
We recommend using two hard drives for PBX deployment.
{% endhint %}

* **800 Mb** hard disk for the main system
* A **50+ Gb** hard drive for recording conversations
* 1 (2 cores) **x86-64** processor
* **2 GB** of RAM
* Network Adapter

{% hint style="success" %}
A PC with such parameters, in our tests, holds **38 simultaneous incoming calls** under the conditions:

* 10 agents are connected to the queue (all online)
* Every second a new call comes in
* Music (MOH) is played to the client while waiting
* Modules on the PBX is not installed
  {% endhint %}

{% hint style="warning" %}
Approximately, **1 hour** of conversation takes up **14MB** of disk space. The recommended size for the disk storing call recordings is at least 50 gigabytes.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mikopbx.com/mikopbx/english/readme/system-requirements.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.