Telnyx

​

Prerequisites

• A Daily SIP trunk — note its sip_uri from the create call, for example sip:examplecorp-supporttelnyx.siptrunk.sip-us.daily.co.
• A Telnyx account with a phone number.

​

Configure the connection

1

Create a SIP Connection

In the Telnyx Mission Control Portal, open SIP Trunking from the side menu and click + Create SIP Connection.Under Details, set Name to something memorable (for example examplecorp-support) and pick FQDN as the Type — the option recommended for SIP devices that route inbound calls to FQDNs. Click Create.Telnyx opens a six-step wizard. You only need 1. Details, 2. Authentication and routing, and 6. Numbers — Configuration, Inbound, and Outbound can stay at their defaults for inbound-only routing to Daily.

2

Route inbound calls to Daily

On 2. Authentication and routing, find the FQDNs panel and click + Add FQDN. In the dialog:

• DNS record type — A, which is what you want for a plain hostname. (SRV is there if you’d rather point at an SRV record.)
• FQDN — the host from your sip_uri, with no sip: scheme and no user part: examplecorp-supporttelnyx.siptrunk.sip-us.daily.co. Telnyx fills the user part with the dialed number; Daily routes on the host label and ignores it either way.
• Port — 5060 for UDP/TCP, or 5061 for TLS.

Click Save. The FQDN appears in the panel’s table, and Telnyx will resolve it to route inbound calls on this connection to Daily.The Inbound calls routing fields below the table — Routing Method and the Primary / Secondary / Tertiary FQDN selectors — order multiple FQDNs. With a single FQDN you can leave them as they are.To use encrypted media, enable SRTP on the connection and set the port to 5061 with TLS. SDES carries the media key in the SDP body, so SRTP is only worth having alongside TLS signaling. Plain RTP on 5060 works too.

3

Assign your number

On 6. Numbers, the Assign numbers table lists the numbers on your account. Use the link action on the number that should route to Daily, then click Complete. A number delivers inbound calls to whichever connection it is assigned to.

4

Secure the trunk

Add Telnyx’s published signaling IP ranges to the Daily trunk’s trunk_config.allowed_ips so it accepts calls from Telnyx and nobody else — see Securing the trunk below.

​

Securing the trunk

curl --request PUT \
  --url https://api.daily.co/v1/sip-trunk/$TRUNK_ID \
  --header 'Authorization: Bearer $DAILY_API_KEY' \
  --header 'Content-Type: application/json' \
  --data '{
    "trunk_config": {
      "allowed_ips": ["192.76.120.10", "64.16.250.10"]
    }
  }'

​

Pass caller context (optional)

"sipHeaders": { "X-Account-Id": "acct_42", "X-Department": "billing" }

​

Test

{
  "event": "sip_trunk.incoming",
  "trunk": {
    "id": "855c9f1a-733c-4097-9bf0-35f905a8688f",
    "description": "my support trunk",
    "trunk_name": "supporttelnyx"
  },
  "room": {
    "name": "7YYuwnCSFvZc5tHVUP7A",
    "url": "https://examplecorp.daily.co/7YYuwnCSFvZc5tHVUP7A",
    "exp": 1788367277
  },
  "call": {
    "sipCallIdHeader": "a7df745c-a8d6-4ee3-b39c-23260c16c0e2",
    "From": "sip:15551234567@sip.telnyx.com",
    "To": "sip:15550001111@examplecorp-supporttelnyx.siptrunk.sip-us.daily.co:5060",
    "requestUri": "sip:15550001111@examplecorp-supporttelnyx.siptrunk.sip-us.daily.co:5060",
    "sourceIp": "192.76.120.10",
    "fromDomain": "sip.telnyx.com",
    "fromDisplayName": "15551234567",
    "pAssertedIdentity": "\"15551234567\"<sip:15551234567@sip.telnyx.com;verstat=TN-Validation-Passed>",
    "sipHeaders": {}
  },
  "domain": "examplecorp",
  "timestamp": 1788363677507
}

• sourceIp is 192.76.120.10, the US region’s primary signaling IP from the allowlist above — a quick way to confirm which Telnyx region served the call.
• To and requestUri carry the :5060 port, because that’s the port set on the FQDN entry in step 2. A TLS connection on 5061 shows up the same way.
• pAssertedIdentity carries a verstat parameter — TN-Validation-Passed is Telnyx’s STIR/SHAKEN attestation result for the caller.
• pAssertedIdentity keeps the quoting from the SIP header, so it arrives as "15551234567"<sip:…> including the quote characters — it is the raw header value. fromDisplayName is unquoted, so you can show it to a user as-is.
• sipHeaders is empty unless your upstream attaches X-* headers to the INVITE.

​

Troubleshooting

• Call fails immediately, nothing reaches your webhook — the source IP isn’t in allowed_ips. Check the signaling IP in the Telnyx call detail record against the list you configured.
• 404 from Daily — the FQDN doesn’t match a trunk host. Re-copy the host from the sip_uri in the API response rather than typing it, and make sure you left off the sip: scheme.
• Call connects but there’s no audio — confirm your connection offers a codec Daily negotiates, and that it reaches Daily on the port you configured (5060, or 5061 for TLS). If you enabled SRTP, the FQDN entry needs 5061/TLS rather than 5060.