https://retellai.com/?utm_source=discord&utm_medium=seo logo
Urgent - Retell Bug
# ❓・bug-report
a
@AI Evy @Colin - Integrations @ Retell AI @Bing - cofounder@Retell AI @Joshua - Solutions Director @Shah - support @ Retell AI I've already contacted email support and received automated responses that don't address my infrastructure issue. This is URGENT and blocking production: Issue: SIP → LiveKit media bridge not processing inbound RTP from Twilio Evidence: - SIP signaling: ✅ Works - SDP: ✅ Correct (RTP port 59174, PCMU) - Media session: ❌ NEVER establishes (Twilio shows all metrics as "-") - Agent cannot hear caller Configuration verified: - All transport methods (UDP/TCP/TLS) tried - IP whitelisting complete - Symmetric RTP enabled - All credentials verified - Localized URI tried This is NOT a configuration issue. This is a Retell infrastructure problem. Email support sent me generic tutorials. I need engineering escalation NOW. Call SID: CAd8622da4da2d0d240a374e2ee5a8355a Full PCAP and evidence ready. Please escalate to SIP/telephony engineering team immediately.
a
Thanks for tagging me @at123456. I'll look through relevant sources and get back to you shortly.
### Answer I understand this is a production-blocking issue. Unfortunately, I'm not able to escalate tickets or contact engineering teams directly. For urgent engineering escalation, please: - Visit [Contact Sales]() for direct business support - Check [Retell AI GitHub]() for issue tracking Relevant context from similar reports: Other users have experienced RTP-related issues with Twilio SIP trunking. One suggestion from the community: check Twilio call logs with RTP debugging, ensure proper re-INVITE/SDP handling after transfers, and confirm codec compatibility (e.g., G.711) . [(1) ]() Additionally, from a SIP/RTP standpoint, RTP servers typically "force a call drop" when the RTP stream is gone for over 60 seconds—LiveKit does implement this behavior. [(2) ]() Since your SIP signaling works but media never establishes, and you've verified symmetric RTP and transport methods, this does appear to be beyond typical configuration issues. Your PCAP evidence should be valuable for the engineering team. I'd recommend re-contacting support with explicit reference to the Call SID and attaching the PCAP, emphasizing this is an infrastructure-level RTP bridging issue rather than a configuration question.
​ To learn more, see the sources I considered: [[1] 🛑 SIP Call Transfer Issue – No Audio Received, Charged Despite RTP Timeout](https://discord.com/channels/1186424376300679209/1382138392862785597) [[2] Livekit is not responding to BYE SIP messages](https://discord.com/channels/1186424376300679209/1432392693190889523) ​
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
o
Hello @at123456 , can you explain the problem you have instead of the chatpgt answers , because its not always right and the call id you shared is twilio call id , share a retell call id.
a
@Omar Ashraf | Community Lead Hi, thank you for responding. I have this one-way audio issue with my agent, I can hear it but it cant hear me. The call id: call_2da986db40f3094f669a32de1e0.
The issue could be on your phone
a
I am calling from GHL phone numbers, is that an issue ?
o
could be, try a normal phone.