Teltonika Alarm Notification

Aucun avis

Send alarm notification SMS via Teltonika gateways. Supports Teltonika's latest REST API and legacy POST/GET service.

Démonstration

Inclus

• Licence perpétuelle par gateway
• Activation en ligne (binding au gateway Ignition)
• Compatible Ignition 8.1, 8.3
• Mises à jour incluses pendant la maintenance
• Support technique OperaMetrix

Notes de version

• v2.1.017 sept. 2026

  Adds two-way messaging, so recipients can acknowledge an alarm by replying to its SMS, along with SMS-channel health monitoring and a round of reliability and security fixes. Requires Ignition 8.3.0 or later. BEFORE YOU UPGRADE - Recipient phone numbers are no longer rewritten blindly. Numbers stored as +<country> are converted to a 00 prefix and numbers already starting with 00 are sent as-is, as before. Any other format (a national number, for example) is now sent unchanged with a warning in the log, where it was previously corrupted. Store numbers in international format. - Run at most one profile with Two-Way Messaging enabled per gateway. The callback token and the pending acknowledgement codes are shared by every Teltonika profile, so a second two-way profile silently replaces the first. One-way profiles are unaffected. NEW - TWO-WAY MESSAGING - Recipients can acknowledge an alarm by replying to its SMS. When Two-Way Messaging is enabled, each alarm SMS carries a numeric code (for example "Send 48217 to acknowledge"). The router forwards the reply to the gateway, which acknowledges the matching alarm. - The acknowledgement is attributed to the recipient who was notified, not to the system user, and is written to the audit log as an SMS Acknowledgement record. - Auto-configure the router: set Auto-configure Forwarding Base URL to the gateway's base URL as the router reaches it (http://<gateway-host>:8088) and the module installs the router's SMS-forwarding rule when the profile starts. Leave it blank to configure the router by hand. Auto-configure requires REST API mode; legacy firmware is set up manually. - Auto-configure replaces any SMS-to-HTTP forwarding rule already on the router. RUTOS offers a single such rule, so one configured for another purpose is overwritten. Leave the base URL blank to keep it. - Reply SMS are deleted from the modem after forwarding, so acknowledgements no longer fill its storage. - Auto-configure Forwarding Verify Certificate makes the router validate the callback's TLS certificate. Leave it unchecked for plain HTTP or self-signed callbacks. - Unanswered codes expire after 24 hours. Codes never collide with one still pending; if no free code is available the SMS is sent without one, and a warning is logged. NEW - SMS-channel health monitoring in REST API mode. Every minute the profile checks that it can log in to the router and reads the modem status, then reports one of OK, WEAK SIGNAL, SIM NOT READY, NO NETWORK, LOGIN FAILED, UNAUTHORIZED, GATEWAY UNREACHABLE or MODEM QUERY FAILED. A brief outage does not flip the profile to Errored, and the log records changes of state only. - The Modem field is now optional. Left blank, the module picks the router's primary (or first) modem. - Throttled Message notification-block property. When the notification block groups several alarm events into one notification, this message is sent instead of the first event's Message. The default is "{alarmEvents.Count} alarm events have occurred." - Profile settings are reorganized: two-way options sit under Two-Way Messaging, and Modem has moved to Advanced. - A router account without the required permissions is reported as an HTTP 403 permission error, on send, on modem-status reads and on the auto-configure write, instead of a generic failure. SECURITY - A Callback Token can be set to authenticate SMS-reply callbacks. Without one, anyone who can reach the gateway could acknowledge alarms by guessing the short reply codes. Requests with a missing or wrong token are refused (HTTP 403). The token is encrypted at rest and masked in the form, and auto-configure adds it to the router rule. Two-way messaging without a token still works, but logs a warning at startup. - The router's bearer token is no longer written to the gateway log when debug logging is enabled. - A username or password containing a quote or backslash no longer produces a malformed login request. FIXED - The profile goes to Errored when the router password cannot be retrieved, instead of reporting Running while every login failed. - An unreachable or hung router can no longer stall notifications indefinitely. Requests to the router now time out (5 seconds to connect, 10 seconds to respond). - A blank recipient phone number is skipped with a clear log message instead of failing the whole notification without an audit record. - A notification with no alarm events no longer fails before it is audited. - Shutting a profile down waits for a send in progress to finish, up to 30 seconds. - Uninstalling or upgrading the module no longer leaves its license listener and the custom-message alarm property registered until the gateway restarts.