# Unintentional Channel “Linking” and Incorrect SIP Safe Behavior

**URL:** <https://forums.allen-heath.com/t/unintentional-channel-linking-and-incorrect-sip-safe-behavior/30227>\
**Category:** dLive Troubleshooting\
**Created:** [5 November 2025 04:00 UTC](https://forums.allen-heath.com/t/unintentional-channel-linking-and-incorrect-sip-safe-behavior/30227 "2025-11-05T04:00:55Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![theotherdave](https://avatars.discourse-cdn.com/v4/letter/t/bbe5ce/32.png) [@theotherdave](https://forums.allen-heath.com/u/theotherdave)\
**Post date:** [5 November 2025 04:00 UTC](https://forums.allen-heath.com/t/unintentional-channel-linking-and-incorrect-sip-safe-behavior/30227/1 "2025-11-05T04:00:55Z")

</div>

I’ve got a weird one… I’m trying to setup SIP safes, and inputs 67 & 75, 69 & 77, 71 & 79, 81 & 89 and 83 & 91 are linked somehow. Like, if I SIP safe 67 then 75 is also safed, and the other way around, too. They don’t share sockets, groups, DCAs (with a couple exceptions), gangs, or anything else I can think of.

Additionally, input 57 is behaving as if it is SIP safed even though it isn’t.

Anyone got any ideas?

Edit: I’m running firmware v2.11

---

<div class="post-metadata">

**Author:** ![RST](https://avatars.discourse-cdn.com/v4/letter/r/e8c25b/32.png) [@RST](https://forums.allen-heath.com/u/RST)\
**Post date:** [5 November 2025 08:02 UTC](https://forums.allen-heath.com/t/unintentional-channel-linking-and-incorrect-sip-safe-behavior/30227/2 "2025-11-05T08:02:12Z")

</div>

I would open a ticket with A&H support and send them the show file to check.

---

<div class="post-metadata">

**Author:** ![jackah](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.allen-heath.com/jackah/32/2711_2.png) [@jackah](https://forums.allen-heath.com/u/jackah)\
**Post date:** [6 November 2025 12:01 UTC](https://forums.allen-heath.com/t/unintentional-channel-linking-and-incorrect-sip-safe-behavior/30227/3 "2025-11-06T12:01:41Z")

</div>

Hey,

Did you get a chance to open a ticket regarding this? I’ve been unable to reproduce it here at A&H HQ.

---

<div class="post-metadata">

**Author:** ![theotherdave](https://avatars.discourse-cdn.com/v4/letter/t/bbe5ce/32.png) [@theotherdave](https://forums.allen-heath.com/u/theotherdave)\
**Post date:** [8 November 2025 09:33 UTC](https://forums.allen-heath.com/t/unintentional-channel-linking-and-incorrect-sip-safe-behavior/30227/4 "2025-11-08T09:33:42Z")

</div>

Not yet. I figured they’d want a show file and I don’t have access to the board for another day. I’ll open a ticket as soon as I can.

---

<div class="post-metadata">

**Author:** ![theotherdave](https://avatars.discourse-cdn.com/v4/letter/t/bbe5ce/32.png) [@theotherdave](https://forums.allen-heath.com/u/theotherdave)\
**Post date:** [16 November 2025 17:42 UTC](https://forums.allen-heath.com/t/unintentional-channel-linking-and-incorrect-sip-safe-behavior/30227/5 "2025-11-16T17:42:38Z")

</div>

In case anyone’s googling the symptoms and comes across this, it’s officially a bug in FW 2.11. FW 2.03 works correctly in this regard, though. Personally I’ll take the new features in 2.11 over a bug-free SIP system, but hopefully A&H will have time to fix it soon enough.

---

<div class="post-metadata">

**Author:** ![RST](https://avatars.discourse-cdn.com/v4/letter/r/e8c25b/32.png) [@RST](https://forums.allen-heath.com/u/RST)\
**Post date:** [16 November 2025 19:08 UTC](https://forums.allen-heath.com/t/unintentional-channel-linking-and-incorrect-sip-safe-behavior/30227/6 "2025-11-16T19:08:38Z")

</div>

Thanks a lot for letting us know! 👍