> ## 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.

# Wavix SIP trunk

> Route a Wavix DID to the platform using the current gateway allowlist

## Recommended profile

Configure the Wavix DID destination as `[did]@<platform-sip-fqdn>;transport=tcp`. In the platform, enter the exact DID in `+E.164` and choose **Provider source IPs**. Credentials described for platform-to-Wavix calls are outbound credentials, not proof of digest on inbound FQDN delivery.

Wavix's official integration guide showed these gateways on 22 August 2026:

```text theme={null}
95.211.82.14/32
209.58.144.243/32
173.234.106.26/32
23.108.101.90/32
```

<Warning>
  Wavix says the current complete gateway list at the bottom of the customer portal's **Trunks** page is authoritative. Compare the portal list before every new setup; do not assume this dated snapshot is permanent.
</Warning>

## Validate

Call the Wavix DID from an external phone and verify the inbound call record, assigned assistant, and two-way audio. If no call appears, compare the current portal gateway list and the DID sent in the Request-URI before changing the trunk.

Sources: [LiveKit Wavix guide](https://docs.livekit.io/telephony/start/providers/wavix/), [Wavix gateway and portal guidance](https://docs.wavix.com/sip-trunking/guides/vapi). Accessed 22 August 2026.