Cygentive
01/20/2026, 10:20 AMAI Evy
01/20/2026, 10:21 AMAI Evy
01/20/2026, 10:21 AMAI Evy
01/20/2026, 10:21 AMAI Evy
01/20/2026, 10:21 AMCygentive
01/20/2026, 10:34 AMCygentive
01/20/2026, 10:36 AMAI Evy
01/20/2026, 10:36 AMAI Evy
01/20/2026, 10:36 AMuser_hangup as the disconnection reason—this closely matches a known issue that was reported and resolved with Vonage SIP trunking, which may also apply to Telnyx. [(1) ]()
## What Likely Happened
A similar issue was reported where calls ended immediately with error_no_audio_received and user_hangup. Investigation revealed that Retell's SIP endpoint was sending a BYE (ending the call) before media started, and no RTP packets were being sent.
This was identified as a Retell-side issue, and a fix was rolled out.
## Recommended Steps
1. Verify Telnyx SIP Trunk Configuration
Ensure your inbound settings use:
- +E.164 as the number format
- G722, G729, OPUS as codecs
- TCP as the transport method (UDP is temporarily not supported due to a connectivity issue) [(2) ]()
2. Check Outbound Authentication
If you're making outbound calls, ensure the header X-Telnyx-Username: <username> is included when using credentials authentication.
3. Review Call Logs with Telnyx
Ask Telnyx to confirm whether RTP packets are being received from Retell. If Telnyx shows the call established but no audio from Retell, this points to the same issue that was previously fixed. [(1) ]()
4. Contact Retell Support
If the configuration is correct and the issue persists, this may require escalation. The previous similar issue was resolved after internal escalation.
Would you like help verifying your Telnyx SIP trunk configuration?AI Evy
01/20/2026, 10:36 AMAI Evy
01/20/2026, 10:36 AM