Frequently asked questions about Track-TP.

Track-TP is a multi-manufacturer monitoring and alerting platform for telecom, power, and IoT infrastructure. It supervises devices and sensors, receives SNMP traps and syslog messages, evaluates the alarm rules, and alerts your control room in several ways, all on customizable dashboards and a real-time map.

Track-TP queries devices with SNMP v1, v2c, and v3, including v3 authentication and encryption with MD5/SHA and DES/3DES/AES. The built-in trap receiver accepts v1 and v2c traps and can forward alarms as v2c traps to your upstream NMS. For switches, routers, and microwave links it also reads the traffic counters on every port (IF-MIB, 64-bit), with per-port historical charts.

The platform doesn’t stop at SNMP and syslog. Track-TP receives telemetry via MQTT and reads PLCs, energy meters, and industrial equipment through Modbus TCP, OPC UA, and BACnet/IP; for electrical substations and SCADA systems it supports IEC 60870-5-104 and DNP3. Rounding out the picture are the REST API with telemetry over HTTP and the ChirpStack webhook for LoRaWAN sensors.

Yes. Track-TP includes an SNMP agent (GET/GETNEXT/GETBULK) published under its own enterprise OID: an external network management system can query device status, alarm counts, and priorities directly. Access is protected by an allowlist of authorized IP addresses and a community string.

Over 50 device models from several manufacturers, including Teleproject (RFX, CellX, CVVX, VoIP), RFC 1628 standard UPS from Riello, Socomec, Eaton, APC, and Vertiv, Benning and Microset (DC power), Cisco and Extreme Networks (switches), MikroTik (routers), Cambium/Ceragon and SIAE (microwave links), Ubiquiti (wireless), Teltonika (cellular routers), Meinberg (GPS/NTP time servers), Elenos (FM transmitters), RadioActivity/Kairos (radiation detectors), Funktronic (multi-channel consoles), Kenwood (radios), and Moxa, plus a generic SNMP/ping profile. New device types are added on request.

Yes. Track-TP integrates natively with ChirpStack through a secured webhook and acquires uplink, status, join, and location events. It keeps battery level, signal quality, and geolocation under control, and evaluates sensor readings against your thresholds.

In five ways: Email, Telegram, WhatsApp via the official Meta Cloud API, SNMP trap forwarding, and real-time in-app notifications. Each user chooses how they want to be reached.

Yes. You can build multiple dashboards and tabs on a draggable, resizable grid with 13 widget types, plus an interactive map with geofences, routes, marker clustering, and several map themes.

Yes. The map is Track-TP’s main view, with geolocation, geofences, group routes, and grouping by site: the platform is designed specifically for distributed, unmanned installations such as remote technical shelters.

Yes. It stores the history of every measurement, offers device import and data export to Excel filtered by date range, keeps a log of configuration changes, and lets you configure the data-retention period.

Yes. It provides role-based access, with three distinct profiles (Administrator, Operator, and Viewer), and an interface available in 6 languages.

Yes. It can run an optional syslog server (RFC 5424 and RFC 3164) that stores messages from the devices you enable, with configurable retention and per-device activation.

Yes. The platform is built on a REST API, with key-based authentication for integrations, device registration, and telemetry sent over HTTP.

Often, yes. If your device uses SNMP, MQTT, Modbus TCP, OPC UA, BACnet/IP, IEC 60870-5-104, DNP3, syslog, or HTTP, it can usually be integrated. New manufacturer profiles and alarm tables are added on request.