Track-TP integrates with what you already run on your network.
Open standards, inbound and outbound. Track-TP polls your devices as a monitoring manager and, at the same time, feeds your upstream NMS (Network Management System) as a data source: SNMP, syslog, REST API, MQTT, Modbus TCP, OPC UA, BACnet/IP, IEC 60870-5-104, DNP3, and LoRaWAN webhooks, without forcing you to change the tools you already use.
One product, two directions.
Track-TP doesn’t ask you to replace what you already have. It uses standard protocols to read your devices’ status and, when needed, acts as a source in turn: it exposes an SNMP agent and forwards traps, so the upstream supervision center keeps seeing everything from its own console.
No mandatory proprietary protocol: if a device uses SNMP, MQTT, Modbus TCP, OPC UA, BACnet/IP, IEC 60870-5-104, DNP3, syslog, or HTTP, it can be integrated into Track-TP.
Inbound
Reads your devices: SNMP polling, traps, syslog, telemetry via HTTP, MQTT, Modbus TCP, OPC UA, BACnet/IP, IEC 60870-5-104, DNP3, and LoRaWAN webhooks.
Outbound
Feeds your upstream NMS: a queryable SNMP agent and trap forwarding with full context.
SNMP in every direction, from polling to agent.
Track-TP covers the four functions of the SNMP (Simple Network Management Protocol) protocol: it polls devices, receives traps, forwards them to your upstream NMS, and exposes its own queryable agent. A single product, both manager and source.
Device polling
Periodic polling of telemetry, stored in the history and evaluated against your alarm rules.
GET · GETNEXT · GETBULK
Inbound traps
A built-in receiver takes in traps and matches them automatically to the manufacturers’ alarm tables.
reception and interpretation
Trap forwarding
Every alarm can be re-sent upstream as a trap, with the full context of alarm, device, and sensor.
to one or more NMS
SNMP agent
An external NMS queries Track-TP and reads the status of devices and alarms, with no ability to modify.
GET · GETNEXT · GETBULK
- Security levels
- NoAuthNoPrivAuthNoPrivAuthPriv
- Authentication
- MD5SHA
- Privacy
- DES3DESAES-128AES-192AES-256
Track-TP exposes a browsable MIB (a device-status table, a per-channel status table, and a values table) under its own enterprise OID. An upstream NMS reads status, the count of open alarms, and the highest priority.
- Enterprise OID
- 1.3.6.1.4.1.60076
- Agent version
- v2c
- Protected access
- IP list + community string
Access to the agent is restricted by an allowlist of permitted IP addresses and by community strings, so only authorized systems can query Track-TP.
From syslog messages to automation via API.
Beyond SNMP, Track-TP receives device logs and makes the entire REST API available to connect your systems and let devices register on their own.
syslog server
- Standard
- RFC 5424 and RFC 3164 over UDP
- Activation
- per-device opt-in, with severity filtering
- Retention
- configurable, with automatic cleanup
- Search
- messages stored and searchable per device
- Full REST APIThe same API (/api/*) that powers the entire product is available for your automation and for tailored integrations.
- API-key authenticationDedicated keys for each integration, separate per device and per service.
- Registration via HTTPTeleproject devices (CellX, RFX, VoIP) self-register via HTTP and send telemetry, location, and scan results, receiving a persistent API key.
MQTT and LoRaWAN, from sensors to the map.
Track-TP receives IoT device telemetry via publish/subscribe on an MQTT broker and integrates LoRaWAN sensors natively through ChirpStack. Readings flow into the history, battery and signal quality stay under control, and location updates on the map automatically.
MQTT
Receives IoT device telemetry via publish/subscribe on an MQTT broker.
ChirpStack webhook
A webhook secured by an API key receives the full range of LoRaWAN events.
Events reach the screen the instant they happen.
A WebSocket connection pushes events to connected clients the moment they occur: dashboards and the map update in real time, without reloading the page and without waiting for the next polling cycle.
New traps
received and interpreted, with the associated device
Device updates
online and offline state transitions
New telemetry
device and sensor readings just in
New syslog messages
from devices enabled for reception
If it uses standard protocols, we integrate it.
The Track-TP architecture is built to grow. New device types, manufacturer MIBs, and alarm tables are added on request, and for non-standard equipment we build tailored integrations. The rule is simple: if a device uses SNMP, MQTT, Modbus TCP, OPC UA, BACnet/IP, IEC 60870-5-104, DNP3, syslog, or HTTP, it can be integrated into Track-TP.
Go deeper into Track-TP connectivity.
From the devices that connect over these protocols to the alarms that come out of them.
- 01
Supported devices
Manufacturers, preconfigured models, and LoRaWAN sensors that connect over these protocols.
- 02
Alarms and notifications
How traps and telemetry become alarms, with trap forwarding to your upstream NMS.
- 03
Features
Monitoring, dashboards, maps, and platform administration in detail.
- 04
Track-TP overview
The platform in brief: architecture, protocols, and interface.
We connect Track-TP to your network.
With the protocols you already have.
Together we map the devices and sensors to supervise, check protocols and credentials, and integrate your upstream NMS. Design, installation, and technical support handled directly by Teleproject.