Yes. ElevenLabs supports handling both inbound and outbound calling through a single Telnyx SIP connection/trunk.
Telnyx setup: Create one SIP Connection, add the FQDN sip.rtc.elevenlabs.io, configure the Inbound tab (e.g., +E.164, TCP), configure the Outbound tab by selecting/creating an Outbound Voice Profile, then assign your number—all within the same connection. (elevenlabs.io)
ElevenLabs setup: Import the SIP-trunked number, set the outbound Address to your Telnyx termination host (e.g., sip.telnyx.com), choose transport (TCP/TLS) and auth (digest or ACL). ElevenLabs SIP trunking explicitly supports both inbound and outbound calls over one trunk. (elevenlabs.io)
For reference, the Telnyx integration page confirms this bidirectional flow on a single trunk. (elevenlabs.io)
the problem is that when elevenlabs sends a sip invite to telnyx telnyx thinks its an inbound call and routes it to elevenlabs because thats the fdqn in telnyx
red cosmos
pastel vector