Telnyx calls fail
# support
m
Callid:
438cf130-9378-43f4-8ee6-e11fa3772344
Seems very similar to this issue: https://discord.com/channels/1211482211119796234/1372606009595658352 We can hear the assistant voice well. But caller is not audible (voice quality is too low so assistant does not understand): see at 30s on the given call.
v
Suggestion: Check if any recent changes were made to your SIP trunk or webhook configurations, as misconfigurations here are a common cause of audio issues like the one you described. If possible, revert to a previous working configuration or carefully review your SIP settings for errors. If the problem persists, consider reaching out to Vapi support with your call ID and a description of the issue for further investigation. This approach is based on similar cases discussed in the Vapi Discord community, where SIP misconfigurations were often linked to caller audio problems. Source: - [Vapi Discord: Outbound call not executed and no webhooks sent](https://discord.com/channels/1211482211119796234/1372358449761091584)
Suggestion: Check if any recent changes were made to your SIP trunk or webhook configurations, as misconfigurations here are a common cause of audio issues like the one you described. If possible, revert to a previous working configuration or carefully review your SIP settings for errors. If the problem persists, consider reaching out to Vapi support with your call ID and a description of the issue for further investigation. This approach is based on similar cases discussed in the Vapi Discord community, where SIP misconfigurations were often linked to caller audio problems. Source: - [Vapi Discord: Outbound call not executed and no webhooks sent](https://discord.com/channels/1211482211119796234/1372358449761091584)
m
v
Suggestion: Try specifying the codec in your Vapi actions/answer request to resolve the audio issue. For example, you can attempt to set the preferred codec to PCMU as follows:
Copy code
json
{
  "preferred_codecs": "PCMU,PCMA,G722"
}
If this parameter is not currently supported in your Vapi setup, please contact Vapi support with your call ID and this codec information for further assistance. Source: - [Vapi Discord: Outbound call not executed and no webhooks sent](https://discord.com/channels/1211482211119796234/1372358449761091584)
Suggestion: Try specifying the codec in your Vapi actions/answer request to resolve the audio issue. For example, you can attempt to set the preferred codec to PCMU as follows:
Copy code
json
{
  "preferred_codecs": "PCMU,PCMA,G722"
}
If this parameter is not currently supported in your Vapi setup, please contact Vapi support with your call ID and this codec information for further assistance. Source: - [Vapi Discord: Outbound call not executed and no webhooks sent](https://discord.com/channels/1211482211119796234/1372358449761091584)
At this time, there is no documented way in Vapi to set the
stream_codec
or
preferred_codecs
for SIP calls via the API or dashboard.
The best next step is to share the Telnyx recommendation and your call details directly with Vapi support, as this may require a platform update or internal configuration. Please include the call ID and the codec details from Telnyx in your support request for faster resolution. Source: - [Vapi Server URL and SIP Integration Documentation](https://docs.vapi.ai/server-url/setting-server-urls)
At this time, there is no documented way in Vapi to set the
stream_codec
or
preferred_codecs
for SIP calls via the API or dashboard.
The best next step is to share the Telnyx recommendation and your call details directly with Vapi support, as this may require a platform update or internal configuration. Please include the call ID and the codec details from Telnyx in your support request for faster resolution. Source: - [Vapi Server URL and SIP Integration Documentation](https://docs.vapi.ai/server-url/setting-server-urls)
v
At this time, Vapi does not support setting the
stream_codec
or
preferred_codecs
for SIP calls via the API or dashboard.
The best next step is to contact Vapi support with your call ID and the codec details from Telnyx, as resolving this may require a platform update or internal configuration. Please include all relevant information to help expedite the investigation. For reference, see the [Vapi Server URL and SIP Integration Documentation](https://docs.vapi.ai/server-url/setting-server-urls). Source: - [Vapi Server URL and SIP Integration Documentation](https://docs.vapi.ai/server-url/setting-server-urls)
s
looking into it.
@marem I went through your messages. Find out this is what you are asking for, and this is what we need to change before we proceed ahead. I want to confirm this with you, and I also request you share more credible resources and information available because this is in dev chain, and don't want it to be for one of the chances to be sure before we proceed ahead. ### What I Found You're Asking For: 1. **Current Issue**: Vapi hardcodes
stream_bidirectional_codec: 'PCMU'
in Telnyx answer events, ignoring the
connection_codecs
from the
call.initiated
event 2. **Proposed Change**: Instead of hardcoding PCMU, dynamically select the optimal codec from the
connection_codecs
field (e.g., "PCMA,PCMU,VP8,H264") 3. **Expected Outcome**: Better audio quality by using PCMA when available (which is higher quality than PCMU in European/international contexts) and avoiding unnecessary transcoding ### What We Need to Change: 1. Extract
connection_codecs
from Telnyx
call.initiated
webhook payload 2. Implement codec preference logic (PCMA > PCMU > others) 3. Replace hardcoded 'PCMU' with dynamic codec selection ### Confirmation Needed: 1. Is this the correct understanding of the audio quality issue you're experiencing? 2. Should we always use the first preferred codec from
connection_codecs
, or implement a quality-based preference order? 3. Are there specific codec combinations that are causing issues in your environment? ### Additional Information Requested: To ensure this change is safe for production, please provide: 1. Telnyx Support Documentation or official guidance on codec selection best practices 2. Sample
call.initiated
webhook payloads
showing the actual
connection_codecs
values you're seeing 3. Audio quality metrics or logs demonstrating the current PCMU vs desired PCMA performance This is a critical audio pipeline change that affects call quality, so I want to ensure we have complete validation before proceeding with implementation.
m
1. Telnyx Support Documentation or official guidance on codec selection best practices I found this: https://developers.telnyx.com/docs/voice/programmable-voice/media-streaming#rtp-stream-codec 2. Sample
call.initiated
webook payload (in the following message) 3. Audio quality metrics or logs demonstrating the current PCMU vs desired PCMA performance, I don't know I understand this is critical and according to Marcin response this might affect only European users: > Call is established using PCMA which is standard in Europe. > However seems like the 3rd party expects PCMU, thus the weird sound. May I suggest you put in contact with Telnyx support directly? It's not my expertise area so I am only reporting back what Telnyx staff answered me in their slack channel Maybe you can have some direct connection with Telnyx support? https://cdn.discordapp.com/attachments/1377284786099585034/1377639938006188043/Screenshot_from_2025-05-29_15-10-51.png?ex=6839b2ac&is=6838612c&hm=96494998a9c96fd0f4b43dec72a1fdd3b954a87887f86cb4ac80d1076db8e14e&
v
Thank you for providing the Telnyx documentation and contact details. We will review the codec selection guidance and reach out directly to Telnyx support to ensure any changes to our audio pipeline are fully validated. Your input is very helpful for moving this issue forward. We will keep you updated as we coordinate with Telnyx and progress on a solution. Source: - [Telnyx Programmable Voice Media Streaming Documentation](https://developers.telnyx.com/docs/voice/programmable-voice/media-streaming#rtp-stream-codec)
Thank you for providing the Telnyx documentation and contact details. We will review the codec selection guidance and reach out directly to Telnyx support to ensure any changes to our audio pipeline are fully validated. Your input is very helpful for moving this issue forward. We will keep you updated as we coordinate with Telnyx and progress on a solution. Source: - [Telnyx Programmable Voice Media Streaming Documentation](https://developers.telnyx.com/docs/voice/programmable-voice/media-streaming#rtp-stream-codec)
Thank you for providing the Telnyx documentation and contact details. Currently, Vapi does not support user-configurable codec selection for SIP calls via the API or dashboard, and engineering is considering a platform update to address this ([Vapi Server URL and SIP Integration Documentation](https://docs.vapi.ai/server-url/setting-server-urls)). To help us validate the codec negotiation logic: Could you please share a sample
call.initiated
webhook payload (with the
connection_codecs
field) from a recent problematic call? This will help ensure the fix is tested against real-world data. Thank you for your collaboration! Sources: - [Vapi Server URL and SIP Integration Documentation](https://docs.vapi.ai/server-url/setting-server-urls) - [Telnyx Media Streaming Documentation](https://developers.telnyx.com/docs/voice/programmable-voice/media-streaming#rtp-stream-codec)
Thank you for providing the Telnyx documentation and contact details. Currently, Vapi does not support user-configurable codec selection for SIP calls via the API or dashboard, and engineering is considering a platform update to address this ([Vapi Server URL and SIP Integration Documentation](https://docs.vapi.ai/server-url/setting-server-urls)). To help us validate the codec negotiation logic: Could you please share a sample
call.initiated
webhook payload (with the
connection_codecs
field) from a recent problematic call? This will help ensure the fix is tested against real-world data. Thank you for your collaboration! Sources: - [Vapi Server URL and SIP Integration Documentation](https://docs.vapi.ai/server-url/setting-server-urls) - [Telnyx Media Streaming Documentation](https://developers.telnyx.com/docs/voice/programmable-voice/media-streaming#rtp-stream-codec)
v
Thank you for providing the Telnyx documentation and context. Currently, Vapi does not support setting
stream_codec
or
preferred_codecs
for SIP calls via the API or dashboard, and the team is reviewing a possible change to support dynamic codec selection based on
connection_codecs
([Vapi Docs](https://docs.vapi.ai/server-url/setting-server-urls), [Telnyx Docs](https://developers.telnyx.com/docs/voice/programmable-voice/media-streaming#rtp-stream-codec)). To help us validate and prioritize this change, could you please confirm if the main issue is that European calls default to PCMA, but your third-party system only supports PCMU, resulting in audio problems? This will ensure we address the most critical scenario first. Sources: - [Vapi Server URL and SIP Integration Documentation](https://docs.vapi.ai/server-url/setting-server-urls) - [Telnyx Media Streaming Documentation](https://developers.telnyx.com/docs/voice/programmable-voice/media-streaming#rtp-stream-codec)
Thank you for providing the Telnyx documentation and context. Currently, Vapi does not support setting
stream_codec
or
preferred_codecs
for SIP calls via the API or dashboard, and the team is reviewing a possible change to support dynamic codec selection based on
connection_codecs
([Vapi Docs](https://docs.vapi.ai/server-url/setting-server-urls), [Telnyx Docs](https://developers.telnyx.com/docs/voice/programmable-voice/media-streaming#rtp-stream-codec)). To help us validate and prioritize this change, could you please confirm if the main issue is that European calls default to PCMA, but your third-party system only supports PCMU, resulting in audio problems? This will ensure we address the most critical scenario first. Sources: - [Vapi Server URL and SIP Integration Documentation](https://docs.vapi.ai/server-url/setting-server-urls) - [Telnyx Media Streaming Documentation](https://developers.telnyx.com/docs/voice/programmable-voice/media-streaming#rtp-stream-codec)
At this time, Vapi does not support setting the
stream_codec
or
preferred_codecs
for SIP calls via the API or dashboard.
The best next step is to contact Vapi support with your call ID and the codec details from Telnyx, as resolving this will likely require a platform update or internal configuration. Please include all relevant information to help expedite the investigation. Reference: [Vapi Server URL and SIP Integration Documentation](https://docs.vapi.ai/server-url/setting-server-urls) Source: - [Vapi Server URL and SIP Integration Documentation](https://docs.vapi.ai/server-url/setting-server-urls)
At this time, Vapi does not support setting the
stream_codec
or
preferred_codecs
for SIP calls via the API or dashboard.
The best next step is to contact Vapi support with your call ID and the codec details from Telnyx, as resolving this will likely require a platform update or internal configuration. Please include all relevant information to help expedite the investigation. Reference: [Vapi Server URL and SIP Integration Documentation](https://docs.vapi.ai/server-url/setting-server-urls) Source: - [Vapi Server URL and SIP Integration Documentation](https://docs.vapi.ai/server-url/setting-server-urls)
a
@marem1859 yeah you can add me in cc with Telnyx support directly.
a
Hey @marem, thanks for cc'ing me in the email. I will look at it later, verify it within our codebase, check with the team, and then let you know the next steps and the ETA for the changes.
m
Hi @Shubham Bajaj did you manage to reach Telnyx support about this issue?
a
Hey @marem, there's no confirmation from the Telnyx team in the email thread, so I can't proceed with your requests. can you directly ask the questions in the above thread to the Telnyx team and let me know their response.?
m
Sorry but I don't know how can I can do more. I have no reply from Telnyx since. Vapi Telnyx integration is not functional for Europe users. Period. Why don't you reach the support yourself? I am not owner of this feature, It would be much easier than having me in the middle reporting the issue on both sides with no way to fix it. If you don't want to support it, then add a disclaimer somewhere in the app so that users uses another phone provider.
s
> If you don't want to support it, then add a disclaimer somewhere in the app so that users uses another phone provider. > REFERENCE:
a
Hey, first of all, if I or our team never wanted to support this, there was no reason for me to check the codebase against your claims and validations. Find out what needs to be done, how it needs to be done, and what will be the score for work. But I did because we want to do it for you. We have a process to follow with different teams when it comes to integration - respect their boundaries. If I don't get a reply within a day, I reach out to them directly. That's my process. I'm in direct connection with them, I'll reach out, share all of the documentation and resources for their better understanding. Coming to another point where you are mentioning that it's not functional for Europe users. I don't think it's functionally or technically true. If that was the case, all of Europe users would have reached out to us. But honestly, we have received a single complaint from you only (as a power user), and taking your complaint seriously, I'm working on it. If it was something which we had to ignore, I could have done it easily, but that's not the case, I believe so. So I'll do the follow-up from here onwards, and I'll let you know the update soon.
m
> Coming to another point where you are mentioning that it's not functional for Europe users. I don't think it's functionally or technically true. If that was the case, all of Europe users would have reached out to us. But honestly, we have received a single complaint from you only (as a power user) Hard to make a generality out of it, but there is another complaint about the exact same issue: https://discord.com/channels/1211482211119796234/1372606009595658352 Thanks for taking it seriously and sorry if you felt offended. It's quite frustrating on my side because I have no idea of current implementation so I'm just reporting to you what telnyx says and vice versa.
a
Hey, thanks for sharing this thread. I'll look into it. I didn't mean I feel offend. I was just expressing my thoughts similar as you have done. We're all in this together, so everything's fine. We are here to work collaboratively to achieve our goals. My goal is to help you and ensure everything works for you.
s
Hey there, thanks for reaching out. We will get to this issue after resolving the current Telnyx problem for some other customer. Once that's done, I'll outline the necessary changes for our team's reference, and we'll proceed to fix it next.
@marem Just to let you know, you are an important customer for us. We genuinely appreciate your usage of VAPI.
m
Ok thanks @Shubham Bajaj . Do you have an ETA for this? Do you know if it's a matter of 1 week? 1 monh?
a
Sorry, but we don't any timeline which we can share with you at the moment. We are trying our best to get it resolved asap.
s
@marem , I apologize, but I can't provide you with a timeline at the moment. I need to get some commitments and proper communications first.
2 Views