# Ignition’s VoIP module: acknowledge all alarms in a consolidated call **URL:** \ **Category:** Ignition\ **Tags:** ignition83\ **Created:** [November 12, 2026, 5:10pm UTC](https://forum.inductiveautomation.com/t/ignition-s-voip-module-acknowledge-all-alarms-in-a-consolidated-call/117821 "2026-11-12T17:10:53Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![mori.luca](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mori.luca/32/13424_2.png) [@mori.luca](https://forum.inductiveautomation.com/u/mori.luca)\ **Post date:** [November 12, 2026, 5:10pm UTC](https://forum.inductiveautomation.com/t/ignition-s-voip-module-acknowledge-all-alarms-in-a-consolidated-call/117821/1 "2026-11-12T17:10:53Z")
Hi everyone, I’m using Ignition’s VoIP Notification Module with alarm consolidation enabled. During routine or unplanned maintenance, one of my customers sometimes gets 50–100 alarms at once, and they can’t predict exactly when that will happen. Consolidation works as expected. The operator receives a single call, and the opening prompt announces how many alarms are waiting to be acknowledged. The customer says the call takes too long when they have to listen to each message. They’ve asked for an “Acknowledge All”option, ideally by pressing a key at the opening prompt to acknowledge all the alarms included in that call. My understanding is that the Voice Notification Module handles keypad input internally. For example, pressing `1` acknowledges the current alarm. Does Ignition expose the key pressed by the operator to the alarm notification pipeline? If so, could I handle a different key at the opening prompt and use it to acknowledge the alarms included in that specific call? I realize this is a fairly specific request from one customer. Before I tell them it can’t be done, I’d like to check whether there’s a built-in option or a supported way to implement it. Thanks for any pointers! ---
**Author:** ![Nol](https://avatars.discourse-cdn.com/v4/letter/n/8e8cbc/32.png) [@Nol](https://forum.inductiveautomation.com/u/Nol)\ **Post date:** [November 12, 2026, 6:00pm UTC](https://forum.inductiveautomation.com/t/ignition-s-voip-module-acknowledge-all-alarms-in-a-consolidated-call/117821/2 "2026-11-12T18:00:50Z")
Is this a situation they encounter during normal operations or is it solely related to maintenance? If so you could consider looking at adding the ability to bypass or turn off callouts related to that equipment package. ---
**Author:** ![Greyship](https://avatars.discourse-cdn.com/v4/letter/g/898d66/32.png) [@Greyship](https://forum.inductiveautomation.com/u/Greyship)\ **Post date:** [November 12, 2026, 6:03pm UTC](https://forum.inductiveautomation.com/t/ignition-s-voip-module-acknowledge-all-alarms-in-a-consolidated-call/117821/3 "2026-11-12T18:03:47Z")
Honestly this sounds like an alarm management issue rather than an acknowledgement issue. If these alarms are "nuisance" alarms, generated by a single event or equipment condition, the alarms should be adjusted to not activate on that condition (or have some kind of time delay/hysteresis). What's the point of having an ack-all (which is what all the operators will do for every call) if somewhere buried in those alarms is something that requires real attention? I'm not sure on the topic of the question, but it probably warrants investigation into the underlying issue rather than a sledgehammer approach. ---
**Author:** ![mori.luca](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mori.luca/32/13424_2.png) [@mori.luca](https://forum.inductiveautomation.com/u/mori.luca)\ **Post date:** [November 13, 2026, 8:17am UTC](https://forum.inductiveautomation.com/t/ignition-s-voip-module-acknowledge-all-alarms-in-a-consolidated-call/117821/4 "2026-11-13T08:17:11Z")
Thanks, @Nol and @Greyship, for taking the time to reply. The points you raised are the same ones I brought up with the customer when they first asked. I suggested disabling callouts for the affected equipment during maintenance or reviewing the alarm configuration to reduce the number of alarms that come in at once. I also raised the concern that acknowledging an entire call without hearing the individual alarms could mean missing one that needs attention. The customer has asked me to look into whether the feature is possible in Ignition. The difficulty is that these maintenance events can’t be scheduled in advance. Under certain conditions, dozens of alarms can trigger at the same time. Each represents a real condition that needs to be reported, so we can’t suppress the alarms or combine them into a single alarm. A bit of context on the retrofit may help explain why I’m asking. This is a roughly 15-year-old plant owned by the customer. Our only interface to the existing system is an OPC UA server that we use to bring the alarms into Ignition. We don’t have access to the original source code, and we can’t make changes to the PLC program. The customer needs to replace their custom VoIP software quickly because it isn’t compatible with Windows 11. We proposed Ignition and are now installing it. The old system let operators acknowledge all the alarms in a call without listening to each message, and the customer has asked whether we can carry that feature over. Given those constraints, is there a built-in option or a supported way for an operator to press a key at the opening prompt and acknowledge all the alarms included in that specific consolidated call? Thanks in advance for any pointers!