---
title: "Safeguards"
slug: "v22-safeguards"
updated: 2024-11-14T07:16:53Z
published: 2024-11-14T07:16:53Z
canonical: "docs.telosalliance.com/v22-safeguards"
deprecated: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.telosalliance.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Safeguards

> **Deprecated.** This document is obsolete and is retained for reference purposes only.  For current and supported documentation, please refer to the T[elos Infinity documentation home page.](https://docs.telosalliance.com/docs/telos-infinity)

Dashboard allows manual logical devices to be created on the Livewire+™ AES67 network. For example, an IFB or Auxiliary audio feed may need to be manually created within Dashboard and as part of the configuration, a multicast/channel number must be assigned. During this configuration, Dashboard will check to see if the number is outside the allocated range for Infinity, if it is, a warning message appears seeking clarification that this is really required.

If a destination channel number or AES67 multicast/channel number is manually changed on a device such as an xNode, and this was already allocated to a Dashboard instance (such as a Group, Partyline, IFP, virtual panel etc), then Dashboard will automatically disconnect the stream. This is to inhibit the effects of duplication of multicast/channel numbers on other Livewire+™ AES67 devices and stop the intercom feeds from appearing on the output of other devices.

![Figure 1 - Multicast or channel number safeguard](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/picture129(3).png)

Figure 1 - Multicast or channel number safeguard