Pelco C1553M-B - page 223

C1553M-B (4/05) 223

d. Send action to all: If you want to send notiﬁcation simultaneously to every member of the recipient group who is logged in when an

alarm or event in this category is triggered, select “Send action to all available user/groups.” In this case, the order of the members in

the recipient group’s Members list is irrelevant.

e. Notify via E-mail: If you want recipients to be sent an e-mail message notifying them when an alarm or event in this category is

triggered, click this ﬁeld. E-mail notiﬁcation is done in addition to the other methods of notiﬁcation.

E-mail notiﬁcation is sent to every member of the recipient group who has an e-mail address conﬁgured, regardless of whether the

member is logged in when the alarm or event occurs. The e-mail message is broadcast simultaneously to all recipients, regardless of

whether you have selected “Send action to ﬁrst available user/group” or “Send action to all available user/groups.” An alarm/event

e-mail message includes the following information:

•The name of the server the alarm or event is deﬁned on

•The alarm/event category

•The alarm/event type

•The date and time the alarm or event occurred

In addition to selecting “Notify via e-mail” for the alarm/event category, you must complete the following additional steps:

•Conﬁgure the e-mail server on the E-mail tab of the Project Properties dialog box. Refer to Project Properties - E-mail Tab for

instructions.

•Conﬁgure an e-mail address for each recipient. If a user belongs to a recipient group for an alarm/event category that uses

e-mail notiﬁcation, but the user does not have an e-mail address conﬁgured, the user will not receive email notiﬁcation. Refer to

Users for instructions on conﬁguring user accounts.

5. Attributes:

a. Priority: Assign a priority to the category if you want some or all of the alarms and events in the category to inherit their priority from

the category. The category priority overrides the priority for a particular alarm or event only if “Use category priority” is selected for

that alarm or event.

VMX300(-E) uses priorities to resolve situations in which two or more objects attempt to control a particular device at the same time.

The object with the higher priority number is given control of the device. The highest priority you can assign to an object is 99. The

lowest is 1. System events have priority 100. Users, schedules, and alarms and events all have a priority. The scripts associated with

these objects inherit the object’s priority.

b. Color: Select a color to signify that the alarm or event has been triggered. Alarm/event icons and Session Manager entries for alarms

and events in this category display in the alarm color.

c. Default color: Select a color to signify that the alarm is not in an alarm state. Alarm/event icons and Session Manager entries for

alarms and events in this category display in the default color once the alarm or event has been acknowledged, or, if it does not

require acknowledgement, once it becomes complete. The icon for an alarm or event that has never been triggered displays in the

default color.

d. Sound: If you want a sound to play on recipients’ workstations when the alarm or event is triggered, select Sound.

e. Sound ﬁle: Click Sound File to select the ﬁle for the sound you want to play on a recipient’s workstation when the alarm or event is

triggered. VMX300(-E) supports one ﬁle format for sound ﬁles: .wav. Test the selected sound ﬁle by clicking the speaker button.

f. Play sound continuously: If you want the selected sound to play repeatedly, select “Play sound continuously.” The sound plays until

the operator stops it by clicking the Silence Alarm button on the Session Manager tool bar.

6. Behavior:

a. Requires acknowledgement: To require that a recipient acknowledge an alarm or event in this category, select “Requires

acknowledgement.” An alarm or event that requires acknowledgement will remain active in the Session Manager until it has been

acknowledged, after which it has status Complete. If more than one user is notiﬁed of an alarm or event, only one user needs to

acknowledge it for it to be considered complete.

b. Suppress subsequent alarms: Under some circumstances, an alarm or event can be triggered more than once in quick succession.

For example, a door alarm could be set off several times in quick succession if someone opens and closes the door repeatedly. In this

case, it is only meaningful to deal with a single instance of the alarm, since there is a single cause to the multiple occurrences of the

alarm.