> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ouraicalling.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Vonage SIP Trunking

> Configure Vonage SIP URI delivery with the official source subnets

## Recommended profile

Configure the inbound Vonage route to the platform SIP FQDN. Keep the exact DID in `+E.164` and choose **Provider source IPs** in the platform. Vonage documents digest/ACL controls for customer-to-Vonage traffic, not digest from Vonage toward the customer SIP URI.

Vonage recommends allowing both primary platform subnets because SIP traffic can originate from either:

```text theme={null}
216.147.0.0/18
168.100.64.0/18
```

Vonage documents UDP/TCP on 5060 and TLS on 5061. Use the same transport at both ends and keep RTP/media rules separate from SIP signaling authentication. Recipient and caller identity use E.164.

## Validate

Call the routed DID externally and confirm a new inbound platform call, the assigned assistant, and two-way audio. If no inbound record appears, verify the Vonage destination URI and source subnet before changing number matching.

Sources: [Vonage SIP dashboard](https://developer.vonage.com/en/sip/sip-dashboard), [Vonage technical details](https://developer.vonage.com/en/sip/technical-details), [Vonage allowlist](https://api.support.vonage.com/hc/en-us/articles/360035471331-Which-IP-addresses-should-I-allow-when-using-Communication-APIs-and-SIP-Trunking). Accessed 22 August 2026.