ACS Server – WISPGate Documentaion

The ACS Server module in WISPGate provides ISPs and network administrators with a powerful, centralized platform to manage TR-069-compliant devices. With real-time visibility and configuration capabilities, this module simplifies device onboarding, monitoring, and maintenance at scale.

ACS Server Settings

The ACS Server Settings allows you to configure and manage the connection between your devices and the Auto Configuration Server (ACS). These settings are critical for enabling remote provisioning, firmware upgrades, and device monitoring over the TR-069 or TR-369 (USP) protocol. ACS must be enabled initially.

Enabling ACS Server

Navigate System Management
Under General, select System Settings
Under the ACS Server Settings, modify accordingly, as shown.
Then save.

Configuration Options

ACS Enabled
Toggle to enable or disable ACS integration. When set to “Yes”, the device will attempt to communicate with the configured ACS endpoint.
ACS Server Address
The URL of the ACS server your devices will connect to. This should include the protocol (http or https), domain name or IP address, and the port number.
Example: http://crm.testacs.com
Username
The ACS authentication username. This is required if your ACS server enforces HTTP basic authentication.
Password
The password associated with the ACS username. Enter the correct credentials to allow secure access and communication with the ACS server.

Dashboard Overview

The ACS Dashboard gives you an at-a-glance view of your network’s TR-069 device ecosystem.

Key Metrics

Total Devices
Displays the total number of TR-069 devices connected or previously connected to the ACS server.
Online Devices
Number of devices currently online and actively communicating with the server.
Online in Past 24 Hours
Tracks devices that have communicated with the server in the last 24 hours, providing quick insight into recent activity.
Configured Today
Shows how many devices were configured or provisioned on the current day.

Provisioning

This section is used to define provisioning rules and workflows that automate how customer premises equipment (CPEs) are configured and managed through the ACS platform. In WiSPGate, provisioning is a flexible, rule-based system designed to simplify and streamline device onboarding, firmware upgrades, parameter configuration, and service activation.

Provisioning:

Click on Provisioning
Click the add Provisioning

Add the Provision name
Add the necessary script
Then, save.

Provisioning (ACS) State

There are two Provisioning states to look out for:

Provisioned – indicates that the particular device has been provisioned (in green)
Unprovisioned – indicates that the particular device hasn’t been connected or provisioned to WISPGate.

Presets

Presets are a versatile and powerful feature designed to automate device management and configuration. They enable administrators to define condition-based actions that are executed automatically, allowing for scalable, hands-free control over a large number of devices.

Presets can be used to push configurations, trigger provision scripts, or schedule routine maintenance tasks. They help ensure consistency, reduce manual effort, and improve the efficiency of network management.

Capabilities of Presets

Conditional Execution
Presets can be triggered based on specific conditions such as device parameters (e.g., model, firmware version), tags, or connection status. For instance, you can configure a preset to:
- Automatically upgrade firmware for devices with a specific model name.
- Apply a configuration only to devices marked with a certain tag (e.g., “new-install”).
- Reboot devices when a particular parameter is detected.
Scheduling with Cron Syntax
Presets support cron-style scheduling, which allows them to run at specific times or intervals. This is ideal for:
- Nightly or weekly device reboots.
- Periodic configuration checks and corrections.
- Maintenance tasks such as log cleanups or status polling.
Integration with Provision Scripts
Presets can trigger custom provisioning scripts written in JavaScript, enabling advanced logic and automation. These scripts can:
- Modify multiple parameters in a single transaction.
- Perform complex calculations or validations.
- Interact with external APIs or services as part of the provisioning workflow.
Bulk Operations
Presets make it easy to perform actions across large groups of devices simultaneously. Whether you need to push a firmware update to hundreds of routers or reset configurations on all offline devices, presets provide a scalable way to do so with minimal effort.

How to Set Up a Preset

Step 1: Define Conditions
Specify the criteria that must be met for the preset to trigger. This may include:

Specific parameter values (e.g., Device.DeviceInfo.ModelName)
Tags associated with devices
Presence or absence of certain events

Step 2: Set Actions
Determine what action(s) should be taken when the condition is met. Actions can include:

Applying configuration changes
Rebooting a device
Adding or removing a tag
Triggering a provision script

Step 3: Schedule the Preset (Optional)
If the preset needs to run periodically or at a specific time, set a cron expression like:

0 3 * * * — Runs every day at 3 AM
*/30 * * * * — Runs every 30 minutes

Step 4: Link to a Provision Script (Optional)
For more complex scenarios, you can link the preset to a custom JavaScript provision script. This allows for dynamic, rule-based configurations or conditional workflows based on the device’s status and metadata.

Step 5: Save and Test
Once configured, save the preset and test it on a small number of devices. You can manually trigger the preset to ensure it behaves as expected before applying it to your entire fleet.

See examples

Here’s an example of a preset configuration:

{

“name”: “Firmware Upgrade”,

“weight”: 0,

“precondition”: “Device.DeviceInfo.SerialNumber = ‘1234567890’”,

“configurations”: [

{

“type”: “provision”,

“name”: “firmware-upgrade”

}

“schedule”: “0 3 * * *”

}

Adding Presets

Click Present
Click Create New Presets
Add required information as needed

Discovered Devices Interface

This section lists all discovered TR-069-enabled devices with detailed metadata.

Device Table Columns

Manufacturer – Displays the OEM or vendor name (e.g., REALTEK, Huawei, TP-Link).
Product – Device model identifier.
Serial Number – Unique hardware identifier used for device recognition.
Last Seen – Timestamp of the device’s last communication with the server.
Status – Real-time online/offline indicator with a color badge.
Actions – Control buttons for:
- Device info
- Provisioning
- Refresh/Force sync
- Delete device

Filtering & Search

Quickly search for devices using serial numbers or product names.
Use checkboxes to perform batch operations on multiple devices.

Features & Functionalities

TR-069 Protocol Support
Ensures standardized device communication and remote management capabilities.
Auto Discovery
Detects and displays any TR-069-compatible device on the network without manual configuration.
Live Status Updates
See which devices are currently online and when each was last active.
Actionable Controls
Provision, refresh, or remove devices from the network directly from the interface.
Analytics Integration
Integrated charts for visualizing device statistics across manufacturers and network behavior over time.

Use Cases

ISPs and WISPs managing large fleets of CPE (Customer Premises Equipment).
Network admins automating device provisioning and reducing manual maintenance.
Support teams troubleshooting offline or misconfigured units with visibility into last-seen logs.

File Tab – Managing ACS-Associated Files

The File tab is used to manage and store all ACS (Auto Configuration Server)-related files associated with a service, device, or configuration.

This tab allows you to upload and organize necessary ACS files, such as configuration templates, firmware, or scripts used for automated provisioning and remote device management.

How It Works:

Simply upload the associated ACS files directly through the File tab.
Provide the required metadata or configuration details (e.g., file type, description, etc).
Once uploaded, these files are stored in an organized manner and can be easily referenced or applied within ACS operations.

Key Benefits:

Centralized Management: Keep all ACS-related files in one place for easier access and tracking.
Simplified Provisioning: Ensures the correct files are available when provisioning or updating devices via ACS.
Efficiency: Reduces setup time by allowing pre-uploaded files to be reused across multiple configurations or devices.

Click the File Upload button

Enter the required information

Save

Device Groups – Organizing Devices in ACS

Device Groups in the ACS module are used to organize and manage network devices more efficiently by grouping them based on common characteristics, such as model, location, customer type, firmware version, or service plan.

This feature is essential for simplifying large-scale device management, enabling bulk operations, and applying consistent configurations across similar devices.

Add Device Groups