Octopush Alarm Notification

No reviews

Provides alarm notification via Octopush over SMS and calls. Supports SMS replies and calls keys pressed.

Demo

What's included

• Perpetual license per gateway
• Online activation (bound to your Ignition gateway)
• Compatible with Ignition 8.1, 8.3
• Updates included while under maintenance
• OperaMetrix technical support

Release notes

• v2.1.017 Sept 2026

  Voice acknowledgement by a single keypress, and audit logging of the whole notification lifecycle: send, delivery and acknowledgement. Requires Ignition 8.3.0 or later. BEFORE YOU UPGRADE Two changes affect callbacks and voice calls that already work today: - Delivery receipts are now authenticated. They are acted on (written to the audit log), so they must carry the X-Ignition-Octopush-Token header like acknowledgements do. If Octopush is not sending the header on delivery receipts, they are rejected with 403. Callbacks that carry nothing actionable are still accepted without it. - Voice recipients no longer key in a dictated code. The call asks them to press 1 to acknowledge. Let on-call staff know before the first alarm goes out. NEW - Voice acknowledgement by pressing 1. The keypress is matched to the alarm by the call's ticket number, so there is no code to remember. SMS keeps its numeric reply code. - Voice Repeat notification property: how many times the whole spoken message (alarm text plus any acknowledgement prompt) is played. Defaults to 3. - Delivery receipts are written to the audit profile as SMS Delivery or Voice SMS Delivery, Good when Octopush reports DELIVERED and Bad otherwise. The voice delivery record includes the keys pressed when With Reply is enabled. - Acknowledgements by reply or keypress are written to the audit profile as SMS Acknowledgement or Voice SMS Acknowledgement. - Audit records carry a structured JSON value (status, ticket, sms, cost and number fields), aligned across the send, delivery and acknowledgement records. The Originating System is notificationProfile:<profile name>, the Actor is the notified user, and the send action names its channel (SMS Request or Voice SMS Request). - An SMS reply acknowledges the alarm as the user the notification was sent to, instead of the anonymous system user. CHANGED - Disable Reply Callback is renamed Disable Callback, since the endpoint now also handles delivery receipts. Existing profile settings are preserved. FIXED - Acknowledging an alarm by reply or keypress now writes its audit record. Previously the alarm was acknowledged but no record (and no log line) was produced. - An SMS reply that matches no pending alarm is logged instead of silently ignored.