> Attached to http://track.sipfoundry.org/browse/XX-5634 are the demo > screen shots for the E911 SMS messaging. > This allows specific alarms to send text messages to specific cellphone > numbers using the cellphone provider's email-to-SMS gateway. > > The Alarms Page provides Basic view of the alarm groups (we could call > the something else like "alarm class" if the term "group" seems > overused). The email contact "To" information was removed from this > screen. > The Alarms Page also provides an Advanced view of the alarm types with > a > drop-down list to select the alarm group. The alarm for the alarm type > can also be disabled here (previously there was a check box). > > The Alarm Group page allows the installer to configure email addresses > for SMS (it will use the cellphone providers email-to-SMS gateway). > User > names could be added in the future. > The Alarm Group page allows the installer to configure email addresses > plus user names for email alarms. I found it rather difficult to get > the > user's email address since it's stored with the voicemail data. > > Example Email message: > Subject: > Alarm SPX00005: Login failed > Text: > Message from sipXecs > Alarm: SPX00005 > Reported on: s1.bcmsl2101.ca.nortel.com > Reported at: 2009-08-04T17:03:46.652976Z > Severity: WARNING > Alarm Text: Login attempt as 'superadmin' failed several times in a > short period. > Suggested Resolution: If condition recurs, may indicate an attempt > to > break in. > > Example SMS message (basically a shortened version of the email): > Subject: > Alarm SPX00005: Login failed > Text: > WARNING: Login attempt as 'superadmin' failed several times in a > short period. > > Please let me know what you think. > Thanks... > Dave.
I really like this. It may seem over complex to some however as we add different notification types I don't see any better way to do this. My only comment is it may make sense to make notifications not 100% tied to alarms. Reason is there may be other things we want to add that send notifications (example: conference entry/exit). Would be nice if this was generic enough to accommodate things like that. > _______________________________________________ > sipx-dev mailing list [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
