Audio Quality Issues
Track down robotic voices, choppy audio, echo and noise: voice choice, your carrier and trunk, the network path and the caller's device.
Showing instructions for Xebit VoiceCloud.Showing instructions for Xebit VoiceKit, on your own infrastructure. Switch with the selector at the top. Updated 22 October 2026.
Poor audio usually comes from one of four places: the voice you chose for the agent, the network between your carrier and Xebit, your trunk's settings, or the caller's own phone. The first step is always the same: listen to a few affected recordings and work out whether the problem is on every call or only some.
First checks
- Sign in to the Xebit VoiceCloud dashboard at
voice.xebit.aiand open the calls list. - Sign in to the Xebit VoiceKit admin console on your own host and open the calls list.
- Open several affected calls and play the recordings. Note which leg sounds bad: the agent, the caller, or a person who joined.
- Check whether it happens on every call, on one carrier or trunk, or on only a few numbers.
Codec mismatches are rarely the cause. The audio bridge transcodes between G.711 and Opus automatically, so your trunk and the agent do not need to use the same codec. See Audio Bridge.
Robotic or unnatural voice
What it usually means: the voice does not suit the language or accent of your callers, or the audio is breaking up (see the next section).
- Open the agent's settings and listen to other voices, ideally in the language your callers speak.
- Choose one and save.
- Start a test call to hear it in a real conversation.
If you use your own text to speech component, check its voice and language settings there.
Choppy or breaking audio
What it usually means: packet loss or jitter on the network path.
- Only some numbers: the problem is most likely the caller's signal or network. Nothing to fix on your side.
- Every call: check the path between your carrier or SBC and Xebit. Ask your carrier about packet loss and jitter on the trunk, and check firewalls are not throttling media traffic.
- One carrier or trunk only: raise it with that carrier, with the call times and numbers.
- On Xebit VoiceKit: check the network inside your data centre between your SBC and the Xebit VoiceKit hosts, and node capacity. An overloaded node can break audio up; per node metrics in Observability show it.
Echo during the call
What it usually means: the caller's phone is picking its own speaker back up through the microphone, often on speakerphone.
- If it is only some callers, it is their device. A headset or turning off speakerphone usually fixes it.
- If it is on every call, check echo cancellation settings on your SBC and with your carrier, then contact us.
Background noise
- Listen to the recording to find which leg the noise is on.
- Noise on the caller's leg is their surroundings. Barge in means the agent may react to loud noises as speech; if that happens often, tell us.
- Noise on the agent's leg should not happen. Contact us with the call ID.
- For a person who joined through the audio bridge from a browser, the audio depends on their own microphone and network. A headset helps.
Still need help?
Email hello@xebit.ai or use the contact page, with call IDs of two or three affected calls and the carrier or trunk they used.
Support is included in your Xebit VoiceKit licence.