@AI Evy I’m currently running inbound voice calls through Twilio Elastic SIP Trunking into a Retell agent. All of our customers are based in South Africa and are calling a South African Twilio number that is configured to our Retell agent. Right now our SIP setup is: Twilio Elastic SIP Trunk (US1) Origination SIP URI: sip:sip.retellai.com;transport=tcp Twilio routing region: United States (US1) Transport: TCP Symmetric RTP: enabled This setup is working correctly, but we’re consistently seeing ~2–3 seconds of latency before the agent starts speaking, which is noticeable for callers. We attempted switching Twilio routing to Ireland (IE1) to reduce geographic distance, but inbound calls fail unless US1 routing is used. That suggests Retell is currently only reachable via a US-based SIP ingress. Question: Do you offer (or plan to offer) a region-local SIP ingress and media edge for Europe (e.g., Ireland) or Africa that we can target from Twilio to reduce latency for South African callers? Specifically: Is there a region-specific SIP URI we should be using (e.g., something like sip:ie.sip.retellai.com;transport=tcp)? If so, what is the correct SIP URI and transport to use? Are there any required IP whitelisting, TLS/SRTP requirements, or trunk settings changes for a non-US SIP edge? Once available, would the correct Twilio configuration be: Switch Twilio routing region to IE1 Update the Origination SIP URI to the region-local Retell SIP endpoint Keep transport as TCP (or TLS if required)? Our goal is to minimize time-to-first-audio for inbound calls from South Africa. I would love to know what my options are and how I can go about this. Thankyou very much!

Thanks for tagging me @.sundancekid.. I'll look through relevant sources and get back to you shortly.

@AI Evy What would you suggest to reduce latency since from my research I understand changing my origination URI to an eu based server like Ireland and changing my routing region to ireland I can reduce latency for my inbound voice agent in Retell?

Thanks for the follow-up, @.sundancekid.. I'll get back to you soon.