Advanced Search
Search Results
211 total results found
Inventory scripts
Overview Inventory scripts are Python-based automation tools that execute operations on managed Devices in CONTROL. These scripts can target devices through user-configured filters or process data from CSV files. Use inventory scripts to gather device informat...
Metric collection for Parameters
Overview Metric collection allows you to store historical information for Parameter values received from managed devices. When enabled, CONTROL automatically captures and stores data points over time, enabling trend analysis and historical reporting. Enabling ...
Processing scripts for Parameters
Overview Processing scripts enable advanced logic integration within communication flows between managed devices and the CONTROL platform. These Python-based scripts implement business logic to transform parameter values before they are processed and stored by...
Special objects for scripts
Overview Special objects are available within processing scripts to provide enhanced management capabilities for Devices and their Settings. These objects can be referenced directly in your scripts to perform various operations and modify device attributes. T...
Alfred Assitants
Introduction An Assistant is an advanced AI-based entity capable of performing specific tasks autonomously based on the rules and instructions provided during its configuration. Assistants in CONTROL allow you to define and customize behavior, capabilities, an...
Service Status Cards
Service Status Cards Overview The Service Status Cards feature in CONTROL enables real-time monitoring of device services and WAN interface status through customizable dashboard cards. These cards display operational data retrieved from TR-181 or TR-098 parame...
Configuring a CPE to become managed through CWMP/TR-069
Overview To configure a Customer Premises Equipment (CPE) device for management through the CWMP/TR-069 protocol, you must enable TR-069 management on your CPE device and configure it to communicate with the CONTROL platform. Required CPE Configuration Fields ...
TR-069 Connection Request
Overview TR-069 is a CPE-originated communication protocol, meaning that the CPE (Customer Premises Equipment) initiates connectivity toward the ACS (Auto Configuration Server) using a pre-agreed ACS URL, username, and password. In a standard TR-069 communica...
CPE Configuration for XMPP Connection Request
Overview The Connection Request feature enables the ACS (Auto Configuration Server) platform to initiate communication with CPE devices to retrieve or modify parameter values and perform OAM (Operations, Administration, and Maintenance) operations. Prerequisit...
CONTROL ACS - Interoperability List
Overview This document lists all customer premises equipment (CPE) devices that have been validated for interoperability with CONTROL ACS as of September 2020. Device Categories The following device types are included in this compatibility list: eMTA - Embed...
Install RouterOS in a virtual machine and connect it to CONTROL
Overview This guide walks you through installing RouterOS in a VirtualBox virtual machine and connecting it to CONTROL using the TR-069 protocol. Prerequisites VirtualBox installed on your system Internet connection to download RouterOS files Basic familiarit...
IPsec Configuration
Overview This guide explains how to configure an IPsec VPN tunnel between RouterOS and CONTROL. The configuration process involves setting up both endpoints to establish a secure site-to-site connection. Part 1: RouterOS Configuration Initial Access Log in t...
Setting up TR-069 client on mikrotik hAP ac2
Prerequisites Before configuring the TR-069 client, ensure your MikroTik hAP ac2 device has an active internet connection. Required Configuration Parameters You will need the following credentials and settings to configure the TR-069 client in CONTROL: ACS U...
Ejabberd API
Overview The Ejabberd API provides RESTful endpoints for managing and monitoring XMPP server operations within CONTROL. All requests require HTTP basic authentication and use JSON for request/response payloads. Authentication All API endpoints require basic au...
ACS Operational Launch Checklist
Overview This checklist ensures a successful ACS operational launch for CONTROL. Complete each step in sequence before deploying devices to end-customers. Prerequisites Checklist 1. Device Testing and Integration All devices must be tested and integrated in t...
Configuring STUN (UDP-based connection request)
Overview STUN (Session Traversal Utilities for NAT) is a TR-069 connection-request helper protocol that enables the ACS (Auto Configuration Server) to reach CPE (Customer Premises Equipment) devices that cannot be accessed via direct HTTP requests. STUN is typ...
FAQ ACS | MVNO ALTAN
Plataforma ACS Zequenze para MVNO ALTAN Preguntas Frecuentes ¿Qué es y para qué sirve la plataforma ACS Zequenze? La plataforma ACS Zequenze permite al MVNO gestionar y operar los dispositivos de cliente (por ejemplo, módems) de forma remota, segura y automat...
How to onboard devices into zequenze CONTROL ACS
Overview Onboarding devices into Zequenze CONTROL is a straightforward process. This guide provides the key considerations and steps to successfully connect your devices to the CONTROL Access Control Server (ACS). Key Concepts Before beginning the onboarding ...