Skip to main content
Biamp Systems

SageVue Deployment Guide

SageVue is Biamp's web-based monitoring and control software for Tesira and Devio products. This deployment guide covers the prerequisites for downloading and installing SageVue, as well as guides for installation, activation and basic configuration of SageVue.


Consider the following mandatory and optional prerequisites for SageVue setup and configuration.

Mandatory requirements

Only users who have completed Tesira, TesiraFORTE or TesiraLUX training will have download access to SageVue from All other users require approval from your Biamp account manager. Please register for access or contact Biamp sales representative. The same account or another new account may be used to register for SageVue activation.

Internet access is required for a one time SageVue activation via A account is required. New users can register at time of activation. SageVue does not require Internet access to operate after the activation is complete, however, accessing the Help documents within SageVue software requires Internet access.

The user account installing SageVue must have administrative privilege on the host machine. SageVue will check IIS (Internet Information Services) and .NET Core requirements during installation. The required components will be installed if not already present on the system.

SageVue system requirements

The host machine or virtual machine running SageVue must meet the following minimum requirements:

  • Windows 10, 32-bit or 64-bit (Windows Server not supported.)
  • 2 GHz Processor
  • 4GB RAM
  • 20GB drive space
  • Gigabit Ethernet 

Install Considerations

The Windows user account installing SageVue must have administrative access to the local machine. SageVue will configure IIS and .NET framework packages during the installation process. The installation or activation may not complete if the user account lacks sufficient access. 

Antivirus and security software may disrupt the SageVue installation configuration and activation process. It should be temporarily disabled during the installation and activation processes and enabled after the SageVue setup is complete. 

Tesira and Devio minimum firmware versions

Tesira and Devio devices not running the minimum supported firmware versions will not be available to SageVue. Tesira Software or the Devio SAU is required to upgrade the firmware to at least the SageVue compatible version.

  • Tesira 3.6 or newer 
  • Devio 1.3.4 or newer

Network discovery and control

SageVue is able to utilize one or more of the network interfaces of the host machine. At least one of the network interfaces of the machine must have access to the Tesira or Devio control subnet. If the SageVue host machine does not have access to the subnet, or is not able to broadcast discovery packets, devices will not automatically discover. The IP addresses of the Biamp devices can be directly configured in SageVue.

Refer to the SageVue Network Architecture article for more detailed information.

Tesira configuration and VoIP

Tesira configuration is managed via Tesira Software. Tesira devices must have a running configuration to be fully managed via SageVue. Tesira devices with VoIP interfaces must include VoIP Control/Status blocks in the Tesira configuration. SageVue will not show VoIP configuration if the device is missing the VoIP blocks on the Tesira configuration. 

The Tesira VoIP interfaces will apply changes from SageVue or Tesira Software. If VoIP settings are applied via SageVue and later a Tesira configuration is sent from Tesira Software, the Tesira configuration VoIP control/status block settings will overwrite the SageVue settings. The source of the most recent VoIP settings update takes precendence. 


Optional integrations available in SageVue: 

  • LDAP server connection and authentication account
  • Email alerts: SMTP server connection and optional SSL connection
  • Text alerts: SMS gateway server of wireless provider (requires SMTP server.)

HTTPS SSL Certificate

The SageVue setup will generate a local self-signed certificate for HTTPS and import it to IIS. Since the security certificate is self-signed, most web browsers or RESTful API connections will display warnings about an invalid or unverified certificate. As a normal part of secured web hosting, the trusted certificate authority or enterprise domain manager will need to generate a trusted certificate for IIS. The trusted certificate is imported via the SageVue gateway settings page or imported directly to IIS. See the Microsoft IIS documentation for more details. 


SageVue provides a fully featured RESTful API for integration to Network Management Systems and any other RESTful capable application. The SageVue web interface utilizes the RESTful API to communicate with the SageVue service on the host system. The API is always active but calls require user authentication. A valid signed certificate through HTTPS is generally required by most RESTful capable systems in order to post a login. See the SageVue help documents for more information on the RESTful API. 


Download of the SageVue setup application requires approval from your Biamp account manager if you have not completed Tesira, TesiraFORTE or TesiraLUX training. To download SageVue, go to

The Windows user account launching the SageVue setup must have administrative privileges to install IIS, .NET Core and the SageVue service on the local machine. The setup process may fail if the user does not have administrative access. 

Launch the installation application and follow the steps given by the setup wizard. The SageVue installation process will check for the necessary IIS and .NET Core Server Hosting components. The components are automatically installed if not present on the system. A reboot is required when prompted by the setup wizard. After installation is complete, the Activate SageVue application will run. 



After the installation is complete, the Activate SageVue application will automatically launch. The process will not complete without Internet access. Ensure Internet access is available and click the Activate Gateway button. 

Activate Gateway

The activate process will launch the default web browser and take the user to the Biamp Portal webpage. The user must login with their credentials or create a new account at this time.

Activate SageVue will contact the Biamp portal servers to automatically generate a gateway code.


Once logged into the Biamp Portal, the Gateway Activation message will appear. The activation number should match the Activate SageVue window. Click OK to begin activation and follow the steps through the process. 

Gateway Activation

The first page is the LDAP configuration. Directory services are optional and not required for SageVue. If directory services are desired later, LDAP is is configurable in the SageVue settings. 

Optional LDAP

The second page contains the admin user configuration. This is the only SageVue user created during activation. Other users are created after the SageVue gateway becomes active. 


Once configuration is complete, click the Quit button. Internet access is no longer required at this time for SageVue to operate. However, access to the SageVue gateway via and the online help files are not available without Internet access. 


The SageVue webpage is accessed from the https://localhost/BiampSageVue/ URL on the local machine. The hostname and SSL certificated are configurable via the SageVue gateway settings or directly through Microsoft IIS. Follow IIS best practices to configure the system. Hostname addressing generally requires support from the network administrator. 

First login and configuration

Use the admin account to log into SageVue the first time. Best practices are to use LDAP or create at least one alternative or backup account with administrator access. Other user accounts with monitor-only access or customizable maintenance levels should also be created. 

By default, SageVue attempts to discover Biamp devices on all active network interfaces. This is customized through the Network settings. Discovered devices will begin populating as soon as SageVue becomes active. Ensure devices are running at least the minimum required firmware versions and that SageVue has access to broadcast discover packets on the control subnet. If SageVue does not have broadcast access, IP addresses of the devices will need configured through the Network settings. See the Network section of the SageVue Help for further information.

VoIP settings applied via SageVue are overwritten if Tesira Software sends another configuration file. The best practice is to fully commission the audio system and apply VoIP settings via SageVue last. 

Once SageVue is fully configured, best practice is to backup the configuration via Settings page on the Import/Export tab. Click the Export button to backup the Manager.smd file. The Import button is used to upload a Manager.smd file on a restored installation. 

Administrator password recovery

If the password for the administrator account is lost then it can be recovered via the web portal Alternatively there is a reset password link if you run the "Activate SageVue" program that remains on your computer. This reset is only available until the first successful login to SageVue. The password recovery will no longer operate after the first successful login to SageVue.


  • Was this article helpful?