#I'm having issues setting up an inbound phone number with Telnyx SIP trunking. I followed the docs

1 messages · Page 1 of 1 (latest)

sonic fiberBOT
#
AI-generated Answer for arcticemerald

Based on our SIP trunking docs, a 407 from sip.rtc.elevenlabs.io typically points to an authentication/config mismatch between your Telnyx SIP Connection and the SIP trunk you imported in ElevenLabs. Here’s exactly what to verify:

  • Telnyx SIP Connection

    • Connection type: FQDN, with FQDN set to sip.rtc.elevenlabs.io. Select TCP for SIP Transport. Destination Number Format: +E.164. Assign your number to this SIP Connection. (elevenlabs.io)
    • Authentication: Under Authentication & Routing, set Outbound Calls Authentication to Credentials and provide a username/password (these must match what you configure on the ElevenLabs side). (elevenlabs.io)
  • ElevenLabs SIP trunk import (Phone Numbers → Import from SIP trunk)

    • Transport: TCP (or TLS if you enable it on both ends). UDP is not available for signaling. Ensure firewall allows 5060 (TCP) or 5061 (TLS). (elevenlabs.io)
    • Authentication: Set SIP Trunk Username/Password (digest). If you leave these blank, ACL auth is used instead and requires allowlisting at your provider; for most setups, provide digest credentials and ensure they exactly match Telnyx. (elevenlabs.io)
    • Dialing format: The INVITE must target sip:+E164Number@sip.rtc.elevenlabs.io:5060 (identifier required). The number format you call must match how you imported the number (including leading +). (elevenlabs.io)
  • Troubleshooting steps

    • Re-check the exact username/password on both sides; review Telnyx logs for auth errors; test with and without digest credentials to isolate auth vs ACL; and confirm your Address/hostnames are correct. (elevenlabs.io)
    • If your security policy needs IP allowlisting, Enterprise accounts can use our static-IP SIP endpoints (sip-static.rtc.elevenlabs.io). (elevenlabs.io)

If Telnyx still doesn’t resend the INVITE with credentials after the challenge, it almost always means the SIP Connection isn’t using “Credentials” auth for calls to sip.rtc.elevenlabs.io or the creds don’t match what you set on the ElevenLabs trunk. Reapply the settings above and retest. (elevenlabs.io)

Sources:
Telnyx SIP trunking | ElevenLabs Documentation
Telnyx SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
Telnyx SIP trunking | ElevenLabs Documentation

vapid minnow
#

The credneitals are identical. I've reset them multiple times

sonic fiberBOT
#
AI-generated Answer for arcticemerald

Understood. If credentials are correct, the next things to verify for Telnyx ↔ ElevenLabs SIP trunking are:

  • Transport must be TCP/TLS end‑to‑end. In Telnyx, set Inbound “SIP Transport Protocol” to TCP; UDP is not supported by ElevenLabs SIP at this time. On the ElevenLabs number, set Transport to TCP or TLS. (elevenlabs.io) (elevenlabs.io)
  • Telnyx connection type and auth: use a SIP Connection of type FQDN, set Outbound Calls Authentication to Credentials, then add FQDN sip.rtc.elevenlabs.io. This ensures Telnyx will answer the digest challenge with your username/password. (elevenlabs.io)
  • ElevenLabs SIP trunk record: in Phone Numbers → Import SIP trunk, enter the same SIP Trunk Username/Password (digest), and avoid ACL unless you can allowlist IPs. If you do use ACL, leave creds blank and allowlist ElevenLabs IPs; for static-IP SIP endpoints (enterprise) use sip-static.rtc.elevenlabs.io. (elevenlabs.io)
  • Identifier/number format must match exactly. If Telnyx dials sip:+15551234567@sip.rtc.elevenlabs.io:5060, you must import the phone number as +15551234567 (including the leading +). Mismatch prevents routing/ringback. (elevenlabs.io)
  • Dial URI and port: ensure Telnyx targets sip:+E164@sip.rtc.elevenlabs.io:5060 with transport=tcp (or 5061 for TLS). Don’t call sip@sip.rtc.elevenlabs.io without an identifier. (elevenlabs.io)
  • If calls still fail authentication, follow the docs’ troubleshooting: double‑check the digest username/password on both sides, test a simplified config (no custom headers), and try toggling TLS↔TCP to isolate transport issues. (elevenlabs.io)

References:

  • Telnyx SIP trunking setup (Telnyx UI steps, transport and auth) (elevenlabs.io)
  • ElevenLabs SIP trunking (SIP URI format, transport support, auth modes, number-format matching, troubleshooting, static-IP option) (elevenlabs.io)

Sources:
Telnyx SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
Telnyx SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation
Telnyx SIP trunking | ElevenLabs Documentation
SIP trunking | ElevenLabs Documentation

vapid minnow
#

I verified those settings. Still getting the same behavior