# AllowedAddresses filter on SIP Trunk

**URL:** <https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833>\
**Category:** Telephony\
**Tags:** sip-trunking\
**Created:** [April 10, 2026, 3:08pm UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833 "2026-04-10T15:08:13Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![nestor.morales](https://avatars.discourse-cdn.com/v4/letter/n/a88e4f/32.png) [@nestor.morales](https://community.livekit.io/u/nestor.morales)\
**Post date:** [April 10, 2026, 3:08pm UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833/1 "2026-04-10T15:08:13Z")

</div>

Hello,

I’m trying to increase security for my SIP trunk so I just allow receiving calls coming from a specific IP. My understanding is that I can use the AllowedAddresses field for that.

So I have the following:  
$ lk sip inbound list  
Using default project [\*\*\*\*\*\*]  
`┌─────────────────┬───────┬───────────────────────────────────────────────┬──────────────────┬────────────────┬────────────────┬────────────┬─────────┬──────────┐`  
`│ SipTrunkID │ Name │ Numbers │ AllowedAddresses │ AllowedNumbers │ Authentication │ Encryption │ Headers │ Metadata │`  
`├─────────────────┼───────┼───────────────────────────────────────────────┼──────────────────┼────────────────┼────────────────┼────────────┼─────────┼──────────┤`  
`│ ST_ ******│ Tests │ +34********* , *********,+34********* , ********* │ 1.2.3.4/32 │ │ │ DISABLE │ │ │`  
`└─────────────────┴───────┴───────────────────────────────────────────────┴──────────────────┴────────────────┴────────────────┴────────────┴─────────┴──────────┘`

With this configuration, I would expect a call to be rejected, but I am still receiving it. Am I doing anything wrong?

---

<div class="post-metadata">

**Author:** ![CWilson](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/cwilson/32/135_2.png) [@CWilson](https://community.livekit.io/u/CWilson)\
**Post date:** [April 10, 2026, 3:24pm UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833/2 "2026-04-10T15:24:13Z")

</div>

What is the trunk ID (starts with ST\_)? Or better a call–id. It can the the SIP call-id or LiveKit call id that starts with “SCL\_”

With that I can take a look at the config and ses what might be happening and why we passed the call that is not allowed in the allow list.

---

<div class="post-metadata">

**Author:** ![nestor.morales](https://avatars.discourse-cdn.com/v4/letter/n/a88e4f/32.png) [@nestor.morales](https://community.livekit.io/u/nestor.morales)\
**Post date:** [April 10, 2026, 7:10pm UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833/3 "2026-04-10T19:10:40Z")

</div>

Hello CWilson,

For the example provided, you can check the calls **SCL\_w3Frck9y7DnB,** SCL\_iDCKLsZ5X4db, \*\*SCL\_jtb8XvhJfRf2  
\*\*  
This corresponds to a local deployment in my local machine, for testing. I also did an equivalent test in a diferent Livekit project in some machine on the cloud, just in case it had relation, with equivalent results. For this other experiment, you can check calls **SCL\_vCeWEpnLW7VM, SCL\_5bcSjV64uggA**

---

<div class="post-metadata">

**Author:** ![darryncampbell](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/darryncampbell/32/20_2.png) [@darryncampbell](https://community.livekit.io/u/darryncampbell)\
**Post date:** [April 14, 2026, 12:58pm UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833/4 "2026-04-14T12:58:19Z")

</div>

@nestor.morales can you please try now, our eng team report that the issue you were seeing has been resolved.

---

<div class="post-metadata">

**Author:** ![nestor.morales](https://avatars.discourse-cdn.com/v4/letter/n/a88e4f/32.png) [@nestor.morales](https://community.livekit.io/u/nestor.morales)\
**Post date:** [April 14, 2026, 1:58pm UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833/5 "2026-04-14T13:58:45Z")

</div>

Hello Darryn, I checked and now it works!

Many thanks for your prompt answer!

---

<div class="post-metadata">

**Author:** ![PC](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/pc/32/1312_2.png) [@PC](https://community.livekit.io/u/PC)\
**Post date:** [May 12, 2026, 1:52pm UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833/6 "2026-05-12T13:52:28Z")

</div>

Hello ,  
I have today the same issue :

I set `allowedAddresses` on my inbound trunk to `1.2.3.4/32` just for testing(Same as Nestor), but I can still call the LiveKit SIP URI directly from MizuDroid and the call gets established.

### Inbound trunk config

```auto

{
  "sipTrunkId": "ST_XXXXXXXXXX",
  "name": "test-trunk",
  "allowedAddresses": [
    "1.2.3.4/32"
  ],
  "authUsername": " ************",
  "authPassword": " ************",
  "includeHeaders": 3
}

```

### Dispatch rule config

```auto
{
  "sipDispatchRuleId": "SDR_XXXXXXXXXX",
  "rule": {
    "dispatchRuleIndividual": {
      "roomPrefix": "call-"
    }
  },
  "trunkIds": [
    "ST_XXXXXXXXXX"
  ],
  "name": "test-dispatch",
  "roomConfig": {
    "agents": [
      {
        "agentName": "xxxxx"
      }
    ]
  }
}

```

### Logs

```auto

2026-05-12 13:21:35,438 [INFO] agent joined room=xxxxx storage=xxx
2026-05-12 13:21:36,874 [INFO] SIP audio track unsubscribed room=xxxxxx participant=xxx

```

I was using:

lk version 2.16.2 when setting up the config.

---

<div class="post-metadata">

**Author:** ![darryncampbell](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/darryncampbell/32/20_2.png) [@darryncampbell](https://community.livekit.io/u/darryncampbell)\
**Post date:** [May 12, 2026, 2:04pm UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833/7 "2026-05-12T14:04:39Z")

</div>

@PC which project is this? I see two projects under your account

---

<div class="post-metadata">

**Author:** ![PC](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/pc/32/1312_2.png) [@PC](https://community.livekit.io/u/PC)\
**Post date:** [May 12, 2026, 2:09pm UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833/8 "2026-05-12T14:09:55Z")

</div>

(post deleted by author)

---

<div class="post-metadata">

**Author:** ![PC](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/pc/32/1312_2.png) [@PC](https://community.livekit.io/u/PC)\
**Post date:** [May 12, 2026, 2:11pm UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833/9 "2026-05-12T14:11:19Z")

</div>

Hello Darryn.  
Its the XXXXX project.

---

<div class="post-metadata">

**Author:** ![darryncampbell](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/darryncampbell/32/20_2.png) [@darryncampbell](https://community.livekit.io/u/darryncampbell)\
**Post date:** [May 12, 2026, 2:25pm UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833/10 "2026-05-12T14:25:13Z")

</div>

@PC Please try now, it should work

---

<div class="post-metadata">

**Author:** ![PC](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/pc/32/1312_2.png) [@PC](https://community.livekit.io/u/PC)\
**Post date:** [May 12, 2026, 2:31pm UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833/11 "2026-05-12T14:31:54Z")

</div>

Hello Darryn.

It works now 🙂  
Is this an issue that will happen again if i create a new project or ? Since currently this is a test project.

Thank you !

---

<div class="post-metadata">

**Author:** ![darryncampbell](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/darryncampbell/32/20_2.png) [@darryncampbell](https://community.livekit.io/u/darryncampbell)\
**Post date:** [May 12, 2026, 2:33pm UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833/12 "2026-05-12T14:33:30Z")

</div>

@PC if you need it enabled on another project, please DM me in this community and I’ll make sure it gets enabled.

I know this situation isn’t ideal and we will make improvements in the future, but for now I’ll make sure you get unblocked.

---

<div class="post-metadata">

**Author:** ![yves.schuetz](https://avatars.discourse-cdn.com/v4/letter/y/a8b319/32.png) [@yves.schuetz](https://community.livekit.io/u/yves.schuetz)\
**Post date:** [May 13, 2026, 7:29am UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833/13 "2026-05-13T07:29:48Z")

</div>

@darryncampbell We are selfhosting livekit and livekit sip bridge. What have we to do, that the AllowedAdresses filter is working again ?

---

<div class="post-metadata">

**Author:** ![CWilson](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/cwilson/32/135_2.png) [@CWilson](https://community.livekit.io/u/CWilson)\
**Post date:** [May 13, 2026, 6:10pm UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833/14 "2026-05-13T18:10:59Z")

</div>

What do you mean you are self hosting. You mean you are self hosting LiveKit server or self hosting LiveKit agents?

If you are using LiveKit cloud what is your project ID? What trunk is it not working on? If you are self hosting LiveKit server I am not sure how to help you.

---

<div class="post-metadata">

**Author:** ![michaelcortado](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/michaelcortado/32/1638_2.png) [@michaelcortado](https://community.livekit.io/u/michaelcortado)\
**Post date:** [June 8, 2026, 10:28pm UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833/15 "2026-06-08T22:28:15Z")

</div>

Hi @darryncampbell ,

We seem to be seeing the same issue on two LiveKit Cloud projects:

- `dbel` (`p_2pkq8rnuokg`)

- `Beta` (`p_2v5wfdo3kqm`)

We have inbound SIP trunks with `allowed_addresses` configured, but calls from non-allowlisted IPs are still being accepted and routed.

Could you please confirm whether the fix/enforcement is enabled for these projects, or if there is anything else we should verify?

Thanks.

---

<div class="post-metadata">

**Author:** ![darryncampbell](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/darryncampbell/32/20_2.png) [@darryncampbell](https://community.livekit.io/u/darryncampbell)\
**Post date:** [June 9, 2026, 8:28am UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833/16 "2026-06-09T08:28:44Z")

</div>

@michaelcortado you should now be good to go

---

<div class="post-metadata">

**Author:** ![michaelcortado](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/michaelcortado/32/1638_2.png) [@michaelcortado](https://community.livekit.io/u/michaelcortado)\
**Post date:** [June 11, 2026, 11:43pm UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833/17 "2026-06-11T23:43:57Z")

</div>

Thanks @darryncampbell - it works!

Does the enforcement fix also make unmatched calls reject when a catch-all dispatch rule exists?

---

<div class="post-metadata">

**Author:** ![darryncampbell](https://sea1.discourse-cdn.com/flex001/user_avatar/community.livekit.io/darryncampbell/32/20_2.png) [@darryncampbell](https://community.livekit.io/u/darryncampbell)\
**Post date:** [June 12, 2026, 8:05am UTC](https://community.livekit.io/t/allowedaddresses-filter-on-sip-trunk/833/18 "2026-06-12T08:05:42Z")

</div>

> [@michaelcortado](#):
>
> Does the enforcement fix also make unmatched calls reject when a catch-all dispatch rule exists?

`allowed_addresses` works at the trunk level, so it would be enforced before any dispatch rules are evaluated
