---
title: "Algo 8300 Provisioning and Server Management Guide"
slug: "8300-provisioning-and-server-mgmt-guide"
updated: 2025-12-11T01:35:05Z
published: 2025-12-11T01:35:05Z
canonical: "docs.algosolutions.com/8300-provisioning-and-server-mgmt-guide"
---

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

# Algo 8300 Provisioning and Server Management Guide

# Introduction

This guide outlines the steps required to configure the 8300 Controller as an HTTP or HTTPS provisioning server. Besides being capable of monitoring and supervising hundreds of Algo IP Endpoints (see the [User Guide](https://www.algosolutions.com/product/8300-controller) for more details), the 8300 may be used as a provisioning server for mass deployments and firmware upgrades. Furthermore, it is possible to send API requests to one or multiple monitored devices to perform different actions.

# Adding Devices to the Dashboard

The **Dashboard**is where users can check the status of monitored endpoints and set **Device Actions**to update settings, reboot monitored devices, and more.

- Browse to the 8300 web interface, log in, and go to **Dashboard**→ **Locator**tab.
- Add the Algo endpoints to be monitored by navigating to the **Locator**subtab.
- The locator will find all Algo IP endpoints in the network. You can also add them manually.

> [!NOTE]
> Note
> 
> - The locator is not able to find endpoints in different subnets or VLANs, even if routing is in place. These must be added manually.
> - The following Algo first generation IP endpoints may not be visible through the 8300 locator. You may need to add them manually.
>   - 8180 SIP Audio Alerter (G1)
>   - 8128 SIP Strobe Light (G1)
>   - 8028 SIP Doorphone (G1)
>   - 8061 IP Relay Controller

# Configure RESTful API

Enable RESTful API for the 8300 to send API commands to the monitored devices.

**To configure RESTful API:**

1. Go to **Basic Settings** →**Features** tab.
2. Set the **Remote Device Admin Password** and **Remote Device RESTful API Password** (default is ***algo***).

![Text Description automatically generated with low confidence](https://cdn.document360.io/f6f5e62d-d280-487f-9da7-5926ffd53b5f/Images/Documentation/8300-provisioning-and-server-mgmt-guide-image-j2qcxrx5.png)
3. Save the changes.
4. Go to **Dashboard** → **Devices**, and use the **Device Actions** dropdown box to:
  - Enable SNMP (not required but recommended)
  - Enable REST

> [!NOTE]
> Note
> 
> Wait for remote device(s) to reboot after each of the above steps. The reboot process takes about 1 minute.

# Configure Provisioning

All Algo IP devices support provisioning, which is detailed on the [Algo Provisioning](https://www.algosolutions.com/resources/guides/provisioning-guides/) webpage. The 8300 can act as an HTTP or HTTPS provisioning server to host firmware files, configuration files, tone files (WAV or MP3), and certificates for mutual authentication. This is a simple and effective method to configure multiple endpoints.

![Text Description automatically generated with low confidence](https://cdn.document360.io/f6f5e62d-d280-487f-9da7-5926ffd53b5f/Images/Documentation/8300-provisioning-and-server-mgmt-guide-image-togmpt7x.png)

**To configure provisioning:**

1. Log in to the 8300 web interface and navigate to B**asic Settings** →**Features** tab.
2. Go to the **Provisioning Server Settings** section.
3. Enable Provisioning by selecting **HTTP**or **HTTPS**mode.
4. Set the provisioning server **Auth Username**and **Auth Password**.
5. Optional: **Partial Provisioning** may be configured. See the [Algo Provisioning Guide](https://www.algosolutions.com/resources/guides/provisioning-guides/) for details.

> [!NOTE]
> Note
> 
> 1 GB of storage is available on the 8300. Firmware files may be as large as 100MB. Make sure to manage available storage and delete old files as required.
6. Navigate to **Dashboard**→**Devices**and **Enable Provisioning**from **Device Actions**.

#### Adding or Deleting Provisioning Files

After you enable provisioning, a folder named **prov**is available in **System**→ **File Manager**. You can add or delete provisioning files.

All file names must be formatted as described in the [Algo Provisioning Guide](https://www.algosolutions.com/resources/guides/provisioning-guides/).

**To add a provisioning file:**

1. Go to **System**→**File Manager** → **prov** folder.
2. To add a provisioning file, drag and drop the file into the **prov**folder.
3. Once the configuration file has been added to the **prov** folder, the endpoint can be rebooted.

If the steps above have been completed, the endpoint will load the configuration file from the 8300.
4. Go to the **Status**page of the endpoint and check the **Provisioning Status**. This should be listed as **Successful**.

If it shows as **None Found****then please check that all previous steps have been completed or contact Algo Support.

**To delete a provisioning file:**

1. Go to **System**→**File Manager** → **prov** folder.
2. Select the **Delete******icon ![](https://cdn.document360.io/f6f5e62d-d280-487f-9da7-5926ffd53b5f/Images/Documentation/delete_24dp_373737_FILL0_wght400_GRAD0_opsz24.png) of the desired file.

# Device Actions Options

From the main dashboard (**Dashboard**→ **Devices**tab), several **Device Actions** can be selected and pushed to one or multiple devices.

![](https://cdn.document360.io/f6f5e62d-d280-487f-9da7-5926ffd53b5f/Images/Documentation/8300-provisioning-and-server-mgmt-guide-image-63bgtuce.png)

| - Reboot Selected | - Enable REST on Selected |
| --- | --- |
| - Enable SNMP on Selected | - Push Single Config to Selected |
| - Disable SNMP on Selected | - Enable Provisioning |
| - Enable REST on Selected | - Back up Config |
| - Update Group on Selected |  |