#Here’s what I’ve configured:✅ SIP Trunk username/password are set on both sides.✅ My Telnyx SIP

1 messages · Page 1 of 1 (latest)

spare oliveBOT
#
AI-generated Answer for .blackbird0016

Short answers, all from ElevenLabs’ official docs:

  • Does ElevenLabs accept SIP calls from Telnyx FQDNs or require IP authentication?

    • ElevenLabs accepts inbound SIP calls over TCP/TLS to sip.rtc.elevenlabs.io and supports either digest (username/password) or ACL/IP-based authentication. IP authentication is not required if you use digest auth. The Telnyx guide explicitly uses an FQDN connection and points Telnyx at sip.rtc.elevenlabs.io. (elevenlabs.io)
  • Is there any IP allowlisting or TLS certificate requirement you may be missing?

    • Not if you use digest auth. If you choose ACL/IP allowlisting, ElevenLabs’ SIP servers are distributed; a static-IP SIP endpoint is available for Enterprise and requires allowlisting an entire /24 when enabled. TLS is supported (port 5061) and recommended; ensure valid certificates on your provider side. UDP transport is not available. (elevenlabs.io)
  • Are there logs available on the ElevenLabs side for debugging inbound SIP calls?

    • Yes. Use the Call History page in Agents; failed calls show a red error explaining why the call didn’t connect. If no error is shown, contact Support. (help.elevenlabs.io)

Quick checks that often resolve “inbound INVITE not reaching ElevenLabs”:

  • Make sure Telnyx is sending to a full SIP URI with an identifier, e.g. sip:+15551234567@sip.rtc.elevenlabs.io:5060 (or :5061 for TLS). Calling sip@sip.rtc.elevenlabs.io without an identifier will not route. The imported phone number must match the exact formatting (+ or no +) used in the INVITE. (elevenlabs.io)
  • Transport must be TCP or TLS; UDP is not supported. If using TLS, verify port 5061 and certificate validity. (elevenlabs.io)
  • For outbound-from-ElevenLabs (which you said works), the “Address” should be your Telnyx hostname (FQDN) only—no sip: prefix. (elevenlabs.io)

If you still don’t see inbound attempts in Call History after the above, confirm on the Telnyx side that the SIP connection’s destination/origination is set to sip.rtc.elevenlabs.io and that the number format is +E.164 as per the Telnyx setup guide. (elevenlabs.io)

Sources:
SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
Where can I locate the reason for my call failing? – ElevenLabs
SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
Telnyx SIP trunking | ElevenLabs Documentation

worn canopy
#

does a free account have restriction on inbound sip trunking ?