We are using a Telnyx number that we imported and it's giving a poor caller voice so the STT is struggling to interpret. It was ok at first. The assistant is fine with our Twilio numbers but we really wish to use Telnyx due to cost and "Quality". Here are a couple of call id's.. Please advise. CC: @AJH https://dashboard.vapi.ai/calls/0199d226-0f42-7ffb-8520-03fc4b44fe04 https://dashboard.vapi.ai/calls/0199d21c-665d-7dde-92a8-c9cd62f545aa

Hi there, Thank you for your message. Our team is currently out of the office. We operate Monday through Friday, from 9:00 AM to 8:00 PM Pacific Standard Time (PST). We’ll get back to you as soon as possible during our normal business hours. If your message is urgent, please mark it accordingly or include “URGENT” in the subject line, and we’ll do our best to respond promptly. Warm regards, Vapi Customer Support Team

I can help you figure out why the audio quality dropped on your Telnyx number and get it back to normal for clearer STT performance. This often happens due to codec settings, media routing, or how Telnyx handles audio packets. Could you share whether your setup uses SIP or WebRTC? @Ade

@Vercel Great, thanks. I set up using Telnyx number import using the Vapi>Create New Number>Import Telnyx Number. This method creates a Programmable Voice API Application in Telnyx. The only option I see for setting the codec's is for inbound calls. We are inbound and outbound and this problem is on the outbound for sure, I need to test inbound. Thoughts?

Glad you isolated the issue, that definitely points to how the Telnyx Programmable Voice API is handling outbound media through Vapi. I can help you dig into the SIP signaling and audio path to pinpoint what’s breaking in the API integration and get it stable again. Let’s take this to privately so we can go over your setup details and logs more closely.

@Shubham Bajaj What's your thoughts on the API?

@Ade are your calls in the US?

Hi @Vercel, I need a solution for the same: Telnyx recordings provide clear voice, but VAPI's same audio is so poor that the transcriber doesn't understand it, and call is ended. Is API codec still wrong, should SIP username /password be used to connect to Telnyx?

Are you using Telnyx for inbound or outbound calling?

Hey, I’ve worked on a few Vapi + Telnyx setups and faced similar audio quality issues before. I can help you diagnose whether it’s a codec mismatch or a SIP config issue — often it’s about how Vapi handles media negotiation. Could you share which codec you currently have set in your Vapi project (e.g., PCMU, Opus, G722)? @Balint

@Balint Pay attention to the following: when using Telnyx, you can "Pin Down" you media services geography, basically, asking Telnyx to make sure that your calls are handled in a specific area. As I receall, the LiveKit servers that service Retell are located in the West Coast, so try to ping that. In addition, change the codec settings on Telnyx to use G722. The default for telephony is G711, which is an 8Khz codec, while G722 is a 16Khz codec (unlike Opus which is a 24Khz codec). 16KHz is ample spectrum for providing high-definition audio, which the AI transcriber loves.

I could successfully connect Telnyx SIP, now VAPI hears clear user voice. The SIP issue was caused by that I wanted to enable Inbound as well, despite your guide showing Inbound : false https://docs.vapi.ai/advanced/sip/telnyx How to really handle Inbound then?

@Balint As long as you use full E.164 numbers - VAPI will accept your calls regardless, the inbound flag is pointless in that case.

For inbound, you have to create a separate gateway where outboundEnabled: false and protocol is UDP. It should work as long as its in the same trunk as the outbound gateway.