Vonage

​

Prerequisites

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

​

Configure the trunk

1

Create a SIP trunk

In the Vonage dashboard, open Voice → SIP Trunks and click Create New. Give the trunk a name and a domain name; the trunk is where you configure inbound routing and link your numbers.

2

Point the trunk's SIP URI at Daily

Open the trunk’s Inbound Calling section.First, under Select Region, choose the region where all inbound PSTN calls to numbers linked to this trunk will be handled. Pick a US region — Daily’s trunk host is sip-us, so a US region keeps the call on the shortest path. Save the region before adding URIs.Then, under Add URI, add a row pointing at your Daily trunk host:

• URI — examplecorp-supportvonage.siptrunk.sip-us.daily.co. Host only, no sip: scheme and no user part. Vonage places the dialed number in the user part of the request URI; Daily routes on the host label and ignores it, so nothing on your side depends on its format.
• Priority — 10 is fine for a single destination. Lower is tried first when you have several.
• Timeout — optional, in milliseconds (2000–20000). The default is fine: Daily answers with 180 Ringing almost immediately, so no generous timeout is needed.
• Transport — UDP on port 5060, or TCP/TLS (TLS on port 5061). Daily accepts all three, so prefer TLS for production signaling.
• SRTP — tick it if you want encrypted media. Vonage offers AES_CM_128_HMAC_SHA1_80, which Daily negotiates. Vonage exposes this independently of the transport, so set Transport to TLS when you tick it — SDES sends the media key in the SDP, and over UDP that key is in the clear. Left unticked, media is plain RTP.

Click + to save the URI. Vonage confirms with “Your trunk is ready to receive calls.”

3

Add your number

Under Link numbers, find the Vonage number that should route to Daily and click Link. Its status changes from Not linked, and inbound calls on that number now go to the SIP URI you configured.Use Buy more numbers if you don’t have a voice-enabled number yet, or Link all numbers to attach every number on the account to this trunk.

4

Secure the trunk

Add Vonage’s published SIP signaling subnets to the Daily trunk’s trunk_config.allowed_ips so it accepts calls from Vonage 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": ["216.147.0.0/18", "168.100.64.0/18"]
    }
  }'

​

Codecs

​

Pass caller context (optional)

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

​

Test

{
  "event": "sip_trunk.incoming",
  "trunk": {
    "id": "6edf339d-e0cd-46b0-bb9e-d327bbee88ef",
    "description": "this is my first trunk",
    "trunk_name": "supportvonage"
  },
  "room": {
    "name": "Kw6s695OcGIKrU4JHcdi",
    "url": "https://examplecorp.daily.co/Kw6s695OcGIKrU4JHcdi",
    "exp": 1788421609
  },
  "call": {
    "sipCallIdHeader": "1f94d95555c1fdc510d48bca18ea9608@sip.nexmo.com",
    "From": "sip:15551234567@sip.nexmo.com",
    "To": "sip:15550001111@examplecorp-supportvonage.siptrunk.sip-us.daily.co",
    "requestUri": "sip:15550001111@examplecorp-supportvonage.siptrunk.sip-us.daily.co",
    "sourceIp": "216.147.2.1",
    "fromDomain": "sip.nexmo.com",
    "fromDisplayName": "EXAMPLE CALLER CA",
    "pAssertedIdentity": "\"EXAMPLE CALLER CA\" <sip:15551234567@sip.nexmo.com>",
    "sipHeaders": {}
  },
  "domain": "examplecorp",
  "timestamp": 1788418009894
}

• sourceIp falls inside 216.147.0.0/18, one of the Primary Subnets from the allowlist above — a quick way to confirm the call arrived from Vonage’s SIP infrastructure.
• sipCallIdHeader and fromDomain carry sip.nexmo.com — Vonage’s SIP infrastructure still signs its signaling as Nexmo. Use fromDomain if you want to branch on carrier.
• pAssertedIdentity keeps the quoting from the SIP header, so it arrives as "EXAMPLE CALLER CA" <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. Compare the signaling IP Vonage used against the Primary Subnets you configured.
• 404 from Daily — the SIP URI host doesn’t match a trunk. Re-copy the host from the sip_uri in the API response rather than typing it.
• Call is rejected with 488 — Vonage did not offer a codec the trunk room can negotiate (by default only PCMU, or the one room_template.sip.codecs.audio names).
• Call connects but there’s no audio — if the URI has SRTP ticked, check that its transport is TLS on 5061.