### Answer Since outbound works but inbound doesn't, check your Telnyx Elastic SIP Trunk inbound settings. [(1) ]() For inbound calls to work properly, verify these configurations in your Telnyx trunk: Inbound Setting requirements: - Number format:

+E.164

- Codec:

G722

,

G729

,

OPUS

- Transport method:

TCP

(UDP temporarily not supported due to a connectivity issue) - SIP region: Select your appropriate region Also confirm that you've moved your Telnyx numbers to the Elastic SIP Trunking you created. When you imported the number to Retell, you should have supplied Telnyx's FQDN as the termination SIP URI (based on your SIP region choice, e.g., sip.telnyx.com) , along with the username, password, and any additional SIP headers from your outbound authentication. [(1) ]() [(2) ]() If the number shows in your Retell dashboard but inbound still fails, the issue is likely in the Telnyx trunk configuration or the number not being properly moved to that trunk. [(1) ]()

​ To learn more, see the sources I considered: [[1] Telnyx](https://docs.retellai.com/deploy/telnyx) [[2] Import Phone Number](https://docs.retellai.com/api-references/import-phone-number) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.