Skip to main content
Version: 8.3

Teltonika

Overview

The Teltonika Alarm Notification module enables SMS alarm notifications through Teltonika cellular routers. It integrates with Ignition's Alarm Notification system, allowing operators to receive alarm alerts via SMS — and, optionally, to acknowledge those alarms by replying to the SMS — through your existing Teltonika infrastructure.

The module registers a Teltonika Notification alarm notification profile type. It sends SMS by calling the router's REST API (default) or a legacy URL-based API, and supports the SMS contact type only.

Features

  • Two API Modes - A modern token-based REST API (default) or a legacy URL-authenticated API, selected by a Legacy checkbox on the profile.
  • Two-Way Messaging (SMS-reply acknowledgement) - Optionally appends a reply code to each SMS; the recipient texts the code back and the router forwards the inbound SMS to the gateway, which acknowledges the alarm on behalf of the notified user.
  • Router Forwarding Auto-Configuration - In REST mode, the module can automatically configure the router's SMS→HTTP forwarding rule so replies reach the gateway.
  • SMS-Channel Health Monitoring - In REST mode, the module periodically probes the router and reports channel health (signal, SIM, network, and authentication status).
  • Automatic Modem Discovery - The modem is optional; when left blank the module auto-discovers the router's primary modem (REST mode).
  • Dynamic Message Templates - Expression-based Message and Throttled Message templates with access to alarm variables.
  • Per-Alarm Custom Messages - Override the notification message at the alarm level via extended configuration (CustomTeltonikaMessage).
  • Token Caching - REST authentication tokens are cached (~299 seconds) and reused.
  • Audit Integration - Logs SMS requests and acknowledgements to an optional audit profile.
  • International Number Normalization - Automatically normalizes phone numbers (e.g. +CC…00CC…).

Technical Specifications

SpecificationValue
Module IDcom.operametrix.ignition.teltonika
Module NameTeltonika Alarm Notification
Module FileTeltonika-Alarm-Notification.modl
Current Version2.1.0
Minimum Ignition Version8.3.0
Required ModuleAlarm Notification (com.inductiveautomation.alarm-notification)
ScopeGateway
Profile TypeTeltonika Notification
Supported Contact TypeSMS only
LicenseProprietary — © 2026 OperaMetrix SAS (paid, with trial; signed)
Hard Dependency

This module has a hard dependency on the Ignition Alarm Notification module (com.inductiveautomation.alarm-notification). If that module is not present and running, the Teltonika module will fault.

Licensing

The Teltonika Alarm Notification module is a paid module and participates in Ignition licensing. It runs in trial mode until licensed.

Trial expiry stops notifications silently

When the trial expires the profile stops dispatching: each notification is logged as Trial expired, notifications will not be sent. and marked done without being sent. The alarm pipeline sees no failure, so there is no retry and no fallback — alarms simply stop reaching recipients. The profile itself keeps running.

Activating a license resumes sending immediately, with no gateway restart. Activate a license or reset the trial from Platform > System > Licensing. Licenses are available from the OperaMetrix marketplace.

Supported Routers

The module targets Teltonika routers with an active SMS-capable SIM. REST mode requires firmware exposing the RUTOS REST API; Legacy mode requires older firmware exposing /cgi-bin/sms_send.

Architecture

When an alarm triggers a Notification Block that uses a Teltonika Notification profile:

  1. The alarm event is received by the notification profile.
  2. The recipient's phone number is taken from their first SMS contact and normalized to international format.
  3. The Message (or Throttled Message, for batched events) expression is evaluated with the alarm context.
  4. In REST mode, the module authenticates against /api/login (caching the token ~299 s) and sends via /api/messages/actions/send; in Legacy mode it sends via /cgi-bin/sms_send with credentials in the URL.
  5. If Two-Way Messaging is enabled, a reply code is appended and, when the recipient replies, the router forwards the inbound SMS to the gateway servlet /system/teltonika, which acknowledges the alarm.
  6. The outcome is logged to the optional audit profile.
All Router Communication Is Plain HTTP

Every request to the router uses http://<host>/.... There is no HTTPS path in the module. If the router listens on a non-default port, embed the port directly in the Host field (e.g. 192.168.1.1:80).

Download

Download Teltonika Module