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

# DIDLogic SIP trunk

> Route DIDLogic numbers to the platform and allow current regional gateways

## Recommended profile

Set the DIDLogic destination to `+[number]@<platform-sip-fqdn>;transport=tcp`. Keep the exact `+E.164` DID on the platform trunk and choose **Provider source IPs**. DIDLogic credentials are used for platform-to-DIDLogic outbound calls; they do not document digest toward an arbitrary inbound SIP URI.

The official DIDLogic FAQ listed these unique signaling gateways on 22 August 2026:

```text theme={null}
89.149.192.7/32
23.19.63.1/32
5.150.254.205/32
157.230.96.24/32
159.8.84.235/32
188.42.84.76/32
119.9.12.222/32
131.203.181.17/32
161.202.135.82/32
102.130.116.205/32
138.197.143.154/32
23.83.156.0/32
192.241.183.87/32
169.57.132.146/32
```

DIDLogic recommends DNS-name firewall rules for resilience. The platform source-IP field accepts addresses/CIDRs, so refresh the official FAQ immediately before saving.

## Validate

Call the DID externally and confirm the platform created an inbound record, routed the assigned assistant, and carried audio both ways.

Sources: [LiveKit DIDLogic guide](https://docs.livekit.io/telephony/start/providers/didlogic/), [DIDLogic gateway FAQ](https://didlogic.com/faq/). Accessed 22 August 2026.