Enable allowed_addresses for SIP inbound trunk

Telephony
1

Hi, I need the allowed_addresses field enabled for SIP inbound trunks on my LiveKit Cloud project:

Project: lynxchat-production
Project ID: p_1j7cov42n99

We use Twilio Elastic SIP Trunking for inbound PSTN calls and want to restrict our LiveKit inbound trunk to Twilio’s published SIP signaling IP ranges.

Could the LiveKit team enable allowed_addresses for this project?

Thank you.

2

@jay, allowed_addresses does require per-project enablement, so your read is correct. The documented channel for it is a LiveKit support request: the docs state the field “must be enabled for your project before you can use it. Contact LiveKit support to request access” (inbound trunk). Sending it through support, with your project ID there rather than in a public post, is the reliable way to get it actioned.

Once enabled, you set it yourself on the inbound trunk as a list of IPs or CIDRs in the allowedAddresses field of the trunk JSON:

{
  "trunk": {
    "name": "My trunk",
    "numbers": ["+15105550100"],
    "allowedAddresses": ["203.0.113.0/24", "198.51.100.0/24"]
  }
}

Swap those CIDRs for Twilio’s published SIP signaling ranges and apply it with lk sip inbound create inbound-trunk.json. If you need to gate the trunk before enablement lands, credential auth is the self-serve alternative that needs no enablement: the same page requires an empty-numbers trunk to carry either a username and password or allowed_addresses, and the username/password path is available today.

3

@jay You :heart: 'd Muhammad’s reply but I didn’t see an active support request in our system for this so I went ahead and enabled allowed_addresses for you.

The advice above is correct, for Scale-tier customers like yourself contacting support directly will likely lead to a quicker turnaround but for the benefit of others who might find this topic, if you are on the free tier you can request access through this forum.