https://retellai.com/?utm_source=discord&utm_medium=seo logo
Hi — I’m integrating Twilio Elastic SIP Trunking a...
# ❓・ai-evy-support
m
@AI Evy Hi — I’m integrating Twilio Elastic SIP Trunking and need inbound SIP origination enabled. My account only shows “Connect via SIP Trunking” with outbound credentials, but no inbound SIP URI is generated or visible anywhere in the UI. Can you enable inbound SIP origination (BYOC) for my account or provide the inbound SIP endpoint so Twilio can route calls into Retell?
a
Thanks for tagging me @Mcwblake. I'll look through relevant sources and get back to you shortly.
Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.
​ To learn more, see the sources I considered: [[1] Twilio](https://docs.retellai.com/deploy/twilio) [[2] Custom Telephony Overview](https://docs.retellai.com/deploy/custom-telephony) ​
### Answer For inbound SIP origination with Twilio Elastic SIP Trunking, you need to configure Retell's SIP server address in your Twilio trunk's origination settings. [(1) ]() Retell's Inbound SIP URI:
Copy code
sip:sip.retellai.com
, [(2) ]() Setup Steps: 1. In your Twilio Elastic SIP Trunk, go to the Origination settings (this handles inbound calls) [(1) ]() 2. Specify Retell's SIP server address as the origination SIP URI:
sip:sip.retellai.com
3. After configuring the trunk, import your phone numbers into Retell so the platform knows how to route incoming calls Transport Options (if needed) : - TCP:
sip:sip.retellai.com;transport=tcp
- UDP:
sip:sip.retellai.com;transport=udp
- TLS:
sip:sip.retellai.com;transport=tls
[(2) ]() The inbound SIP endpoint is the same for all accounts — it's Retell's central SIP server. No account-specific inbound URI needs to be generated. The routing is determined by the phone number you import into Retell and bind to an agent. [(1) ]() Check out these resources for more details: - [Twilio SIP Trunking Guide]() - [Custom Telephony Overview]()
u
@Mcwblake can you show me a screenshot of your UI?