> For the complete documentation index, see [llms.txt](https://help.sipgate.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sipgate.de/cloud-telefonanlage/en/using-sipgate/allgemeine-losungen-beim-telefonieren-mit-sipgate/wie-kann-ich-probleme-wie-stoergeraeusche-hall-und-schlechte-sprachqualitaet-beh.md).

# How can I fix problems such as interference, echo, and poor voice quality?

Tips for improving voice quality in sipgate – eliminate interference, echo, and dropouts.

The first basic requirement for good voice quality is a **broadband internet connection**. The key factor is speed: a single phone call over the internet requires about **100 kbit/s** (for both upload and download). Insufficient bandwidth can cause dropouts.

* **Example**: Even a standard DSL connection with a download speed of 16,000 Mbit/s and an upload speed of 1 Mbit/s can support up to 10 simultaneous calls.

Is your internet connection fast enough, but the call is still choppy? Here’s a list of possible problems and solutions:

* **A cable is better than Wi-Fi:** It may sound like a rule of thumb, but it’s true in most cases. If your router and computer are connected to the internet via an Ethernet cable, you’ll get more out of your bandwidth.
* **The right headset:** There are many good Bluetooth headsets. Even so, wired headsets are generally faster.
* **Loud background noise on the line:** If your voice is accompanied by loud background noise, check your microphone settings under **Start -> System Settings -> Audio Settings.**
* **Audio input and output:** Your audio settings may not be quite right. For example, you may hear the call through your computer speakers even though you have a headset connected. You can usually select the appropriate audio input and output for your device and adjust the input level—the sensitivity of your microphone—in your operating system’s system settings.
* **Can you hear your own voice twice?** This is usually caused by the people you’re talking to. They have their volume turned up too high—perhaps they’re using computer speakers—so your voice is picked up by their microphone and sent back to you.
* **Still getting an echo?** Have you checked all the technical settings, but the other person still hears an echo? One option is to lower your microphone’s input level (in your operating system’s system settings). Another solution may sound a little obvious, but you might be calling from a room with poor acoustics. If your room is generally very reverberant, even the best technology will have trouble compensating for it.
* **Echo on the other person’s end?** Of course, the people you’re talking to might have the same issues described in the previous section. But they may also be using speakerphone. The phone’s microphone is often very sensitive so the person can set the phone down and still be heard. This also means that you’ll hear more of the room, including any echo.


---

# 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://help.sipgate.de/cloud-telefonanlage/en/using-sipgate/allgemeine-losungen-beim-telefonieren-mit-sipgate/wie-kann-ich-probleme-wie-stoergeraeusche-hall-und-schlechte-sprachqualitaet-beh.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.
