# Remote alerting features

**URL:** <https://forum.inductiveautomation.com/t/remote-alerting-features/3333>\
**Category:** Ignition\
**Created:** [September 26, 2011, 2:36pm UTC](https://forum.inductiveautomation.com/t/remote-alerting-features/3333 "2011-09-26T14:36:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Greg.Buehler](https://avatars.discourse-cdn.com/v4/letter/g/ecc23a/32.png) [@Greg.Buehler](https://forum.inductiveautomation.com/u/Greg.Buehler)\
**Post date:** [September 26, 2011, 2:36pm UTC](https://forum.inductiveautomation.com/t/remote-alerting-features/3333/1 "2011-09-26T14:36:37Z")

</div>

Based on some issues with WIN911 by other users and upcoming hurdles for myself I’m putting some features out for consideration.

[ul]  
[li]1. Voice alerting. Eliminating the need for Win-911 would be a great selling point. TAPI modems would be the best starting point for what I need. [JTAPI](http://java.sun.com/products/jtapi/) should be pretty platform independent. SIP capability might be an option too.[/li]  
[li]2. Alerting groups with conditional escalation. Say I might want to alert local technicians if an alarm is triggered, but if the alarm is triggered X times during a 24 hour period it automatically gets dispatched to a regional technician.[/li]  
[li]3. Scheduled notifications of alarm states. I may have two shifts and only want to notify the personnel on duty of alarms.[/li][/ul]

---

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [September 26, 2011, 11:26pm UTC](https://forum.inductiveautomation.com/t/remote-alerting-features/3333/2 "2011-09-26T23:26:42Z")

</div>

Don’t worry, we’re already quite aware of the need for these features. An alerting-revamp is on the schedule that should cover all of these, and will probably happen sometime next year.

---

<div class="post-metadata">

**Author:** ![DaneOverfield](https://avatars.discourse-cdn.com/v4/letter/d/71c47a/32.png) [@DaneOverfield](https://forum.inductiveautomation.com/u/DaneOverfield)\
**Post date:** [January 5, 2012, 8:35pm UTC](https://forum.inductiveautomation.com/t/remote-alerting-features/3333/3 "2012-01-05T20:35:21Z")

</div>

Using Exele TopView, you can do this through OPC (requires using Kepware or similar OPCDA-OPCUA layter) or SQL (ODBC/OLEDB connections to Ignition tables). TopView has complete notificaiton features including voice (audible locally, remotely, and callout), alarm frequency notificaiton, escalation, schedules (of both alarm conditions and recipients) plus much more.

[exele.com/Products/TopView/topview\_about.htm](http://www.exele.com/Products/TopView/topview_about.htm)

---

<div class="post-metadata">

**Author:** ![DaneOverfield](https://avatars.discourse-cdn.com/v4/letter/d/71c47a/32.png) [@DaneOverfield](https://forum.inductiveautomation.com/u/DaneOverfield)\
**Post date:** [February 17, 2012, 1:02pm UTC](https://forum.inductiveautomation.com/t/remote-alerting-features/3333/4 "2012-02-17T13:02:10Z")

</div>

We have added some details of integrating TopView SQL to Ignition.  
[exele.com/Products/TopView/s … /index.htm](http://www.exele.com/Products/TopView/solutions/ignition/index.htm)

---

<div class="post-metadata">

**Author:** ![bryan\_cook](https://avatars.discourse-cdn.com/v4/letter/b/a8b319/32.png) [@bryan\_cook](https://forum.inductiveautomation.com/u/bryan_cook)\
**Post date:** [February 17, 2012, 1:19pm UTC](https://forum.inductiveautomation.com/t/remote-alerting-features/3333/5 "2012-02-17T13:19:10Z")

</div>

Definitely hackish, but there’s [Python Bindings for Google Voice](http://code.google.com/p/pygooglevoice/) available … although there’s some [dissatisfaction](http://stackoverflow.com/a/1717181) with the receiving SMS implementation. I also found an [Unofficial Java API for Google Voice](http://code.google.com/p/google-voice-java/) … perhaps I’ll tinker with a module during my downtime, (assuming I have any!).