> For the complete documentation index, see [llms.txt](https://kb.hostednetwork.com.au/support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.hostednetwork.com.au/support/services/voice-over-ip-voip/technical-references/how-much-bandwidth-do-i-need-for-voip.md).

# How much bandwidth do I need for VoIP?

**With VoIP there are three main things that you need to look at:**

1. Upload Speed of the internet connection; the faster the upload the more concurrent calls the connection can handle.
2. Latency back to the hosted PBX; the lower the latency the better however, so long as it's under 100ms VoIP, calls should be fine.
3. Packet loss on the connection; if the connection is unstable and is dropping packets this will have a direct impact on call quality.

So how much bandwidth does a call use? Well this will depend on the codec being used, however, as a basic rule of thumb, a standard VoIP call with the default codec will run at 90Kbps, but can be as low as 30Kbps if the highest level of compression codec is being used. See the table below:

| **Codec Compression Level** | **Bandwidth**                | **Audio Quality** |
| --------------------------- | ---------------------------- | ----------------- |
| Normal (G.711)              | 64Kbps (kilobits per second) | High              |
| High (G.729)                | 8Kbps (kilobits per second)  | Average           |

In order to calculate how much bandwidth vs concurrent calls we recommend a simple calculator located at

* [https://www.bandcalc.com/](http://www.voip-toolbox.com/bandwidth)
* <https://planetcalc.com/3144/>
* <http://www.erlang.com/calculator/lipb/>


---

# 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://kb.hostednetwork.com.au/support/services/voice-over-ip-voip/technical-references/how-much-bandwidth-do-i-need-for-voip.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.