### 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.