---
title: "VSet assigned to wrong Studio / No VX Audio at the Console"
slug: "vset-assigned-to-wrong-studio-no-vx-audio-at-the-console"
updated: 2024-12-19T07:26:15Z
published: 2024-12-19T07:26:15Z
canonical: "docs.telosalliance.com/vset-assigned-to-wrong-studio-no-vx-audio-at-the-console"
---

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

# VSet assigned to wrong Studio / No VX Audio at the Console

## Scope

This article is meant to help troubleshoot issues with getting VX audio to and from the Console.

## Description

If the VSet is logged into the wrong studio, it will send caller audio to an unexpected location. It will also get backfeed return audio sent to the caller from an unexpected location. As a result, the console channel where caller audio is expected is silent. You may also have issues with callers on hold hearing the wrong audio stream. This article will guide you towards finding and correcting this issue.

> [!CAUTION]
> This document assumes that there are no configuration issues with the network used to transport Livewire / AoIP audio (ie. switch configuration). If this is suspected, we recommend that this is addressed first and foremost.

## Step 1: Determine Which Studio is Used

> [!WARNING]
> In this example, we are using a **Fusion Console**. This procedure is identical with other console systems. **If you are not using an Axia console, skip to "C" below.**

#### A) Check the Console Source Profile

Navigate to your Console's **Sources** list and make note of the Livewire Channel number / address used for the **Phone** Channels:

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/3398ced8-19cb-4846-b9aa-8be0a04d4a8d.png)

> [!NOTE]
> Note that the channel number in our example is **15801** and it is showing "**Studio A**" in the advertisement.

> [!WARNING]
> For most of us, this is good enough to move on to **Step 2** below. If you like double checking things or if the advertisement is not showing the studio name, continue by checking the Console's Show Profile and the VX Studio itself:

#### B) Check the Console Show Profile

If you are using a console-based controller, navigate to the **Phone** section of the appropriate console **Show** to double check which **VX Studio** is being used:

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/391210d0-5a59-44d1-b2a4-4d924a4faeea.png)

> [!NOTE]
> Indeed, we can confirm that the console engine is logging into **Studio A.**

#### C) Check the VX Studio Information

Navigate to the **Information -> Studio** page in the VX for the appropriate VX Studio:

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/1d11a03f-ead5-4b5a-bcce-63af1c4aca4f-capture.png)

> [!WARNING]
> If you are not using an Axia console, the channel number listed here must match the channel used in the xNode's **Destination** for the appropriate output. In this example, output 1 is used:

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/06ea849c-b119-4479-8696-eb1fdb7ac6f4.png)

> [!NOTE]
> The Console is using VX **Studio A**, which is using channel number **15801** for caller audio.

## Step 2: Check / Assign the VSet to a Studio

- Press the **MENU** button on the VSet's front panel
- Press and hold the numbered line key next to **Engine Setup** for **4 seconds** and release
- Scroll down to **Select Studio** and make sure it's set to the correct value. (In this example, **Studio A**)

![](https://cdn.document360.io/57e3cd80-d493-453c-9672-ad1b043dadc3/Images/Documentation/f3b26533-dcf6-4ce8-b1bf-bd8971447c58.png)

- If the studio listed here is not correct, press the numbered line key next to **Select Studio** and choose the correct studio.
- Press the VSet's **MENU** button to exit.

## Let us know how we can help

If you have further questions on this topic or have ideas about how we can improve this document, please [contact us](https://www.telosalliance.com/support-request).