List of Figures ................................................................................................................................................ 4
RMS Server Specifications ............................................................................................................................. 7
Base Operating Mode ............................................................................................................................... 9
Data Inputs .......................................................................................................................................... 10
Data Outputs ....................................................................................................................................... 10
Data Connections ................................................................................................................................ 10
Glossary of Terms........................................................................................................................................ 11
Installation of RMS ...................................................................................................................................... 16
Configure Static IP Address ..................................................................................................................... 16
Discover the RMS Using WaveWare Discover and Reset Tool ........................................................... 16
Log Into RMS ....................................................................................................................................... 18
Configuration of RMS Server ...................................................................................................................... 20
Rules and Filters .................................................................................................................................. 31
LED Display .......................................................................................................................................... 34
Mass Notification Msgs ....................................................................................................................... 36
Messaging Groups ............................................................................................................................... 37
Data Inputs .......................................................................................................................................... 45
Data Outputs ....................................................................................................................................... 49
Data Connections ................................................................................................................................ 51
LED Displays ........................................................................................................................................ 60
Digital Alert Viewers ........................................................................................................................... 62
Inovonics User Experience with Event Processing Enabled .............................................................. 105
Appendix G – HTTP Data Input Protocol ............................................................................................... 106
Appendix H - Honeywell Notifier NWS-3 Web Server Fire Panel Integration....................................... 107
Update History ...................................................................................................................................... 107
List of Figures
Figure 1 - RMS System Architecture ............................................................................................................. 9
Figure 57 - General Settings System Configuration .................................................................................... 96
6
RMS Server Specifications
• Intel NUC computer, with an AC/DC power adapter
• Linux operating system
• 8 GB RAM
• 80 GB solid state drive
• Ethernet port
• 4 USB ports
• Belkin USB-to-Serial Portable Adapter, as required, per serial port connection
• MySQL database
• Apache web server
Overview
The Rauland Responder 5000 Messaging Server (RMS) is designed to perform alert detection, alert event
processing, alert annunciation, logging, and reporting. RMS uses serial port and Ethernet
communications to perform these functions, as well as a web server, Android app, and various methods
of alert annunciation. In addition, RMS can perform protocol conversion, data filtering, data translation,
data output splitting, and data input combining.
RMS is configured via a web browser.
RMS data inputs can include the following:
7
• Alert messages via serial port and/or Ethernet , using a variety of protocols, including:
o COMP1
o COMP2
o Inovonics central receiver
o Messaging Client (browser based messaging)
o R5000 (Rauland Responder
tm
5000)
o SMTP
o TAP
o HTTP
RMS can be configured to detect alert activation using the above types of data inputs, and also using the
following methods:
• WaveTrac sensor related events delivered through WaveTrac Tracking/Control devices,
including proximity, wander proximity, caregiver call, and exit risk
• Contact closure events at WaveTrac Tracking/Control devices
RMS can output information via the following methods:
• Responder 5000 Messaging App (Android)
• Alert Client (browser based alerting)
• Digital TV, using HDMI port and the Digital Alert Viewer (DAV) protocol
• On-Site Radio Pagers, using a radio paging system, and Ethernet or serial port protocols,
including:
o TAP
o COMP2
• Walkie Talkies, using an Audio Gateway Device with Ethernet and Radio Interface
• E-mail
• Adaptive LED display model 4080 RGB MNS, via Ethernet
RMS reports can be delivered via schedule or generated manually. A MySQL based third party reports
API is also available.
RMS has two main operating modes: a Base mode, and a Base Mode plus Event Processing Mode (See
Fig. 1 below). The Base mode of operation includes:
• Device drivers (interface protocols)
8
• Protocol conversion functions
• Data logging
The Event Processing Mode includes all Base Mode functions, plus:
• Alert event life cycle processing functions
• Zone based alert notification routing
• Alert escalation notification routing
• Schedule based alert notification routing
Figure 1 - RMS System Architecture
Base Operating Mode
Configuration of the RMS Base Mode of operation consists of defining the following:
9
• Data Inputs
• Data Outputs
• Data Connections
Note that any RMS operations require the definition of the appropriate Data Connections, with each
Data Connection associated with the appropriate Data Input and Data Output. Note that the Data Input
and Data Output relationships are defined by the Data Connections, which can create one-to-one, oneto-many, many-to-one, and many-to-many data processing relationships.
Data Inputs
Data Inputs define how to monitor for alerts in incoming data streams, using a variety of protocols and
methods. Two specialized and protected Data Input types are:
• Event Processing System – The RMS Event Processing System, when enabled, can act as a Data
Input as it can generate specific types of system level alerts, including:
o Caregiver call signal from a WaveTrac sensor
o Proximity detection event for either WaveTrac or Inovonics sensors
o Wander Proximity detection event for WaveTrac sensors assigned Wander class
monitoring
o Exit Risk detection event for WaveTrac sensors assigned Wander class monitoring
o Maintenance class alerts, such as low battery on Inovonics and WaveTrac sensors, and
tamper on Inovonics sensors
• Messaging Client – The RMS browser based Messaging Client can act as a Data Input. The
population of the Messaging Client Recipients list is dependent upon how the Data Outputs and
Data Connections are configured into the system.
Data Outputs
Data Outputs define how to deliver alerts to outbound data streams, using a variety of protocols and
methods. A specialized and protected Data Output type is the Event Processing System, where alert
events detected from a particular Data Output can be routed to the Event Processing System for further
processing and routing.
Data Connections
Data Connections both associate Data Inputs with Data Outputs and they define how detected alerts
should be routed to the appropriate Data Outputs. Note that any RMS operations require the definition
of the appropriate Data Connections, with each Data Connection associated with the appropriate Data
Input and Data Output.
10
Event Processing Operating Mode
Sensor
A device designed to sense alert conditions or specific environmental
Sensor Monitoring
A system designed to collect and route sensor information to a head-end
Data Input
A feature that allows monitoring and processing alert messages generated by
Data Output
A feature that allows output of alerts using various protocols
Data Connection
A relationship between a Data Input and a Data Output, such that alerts
Event Activation
A condition detected in Data Input alert messages that allows the system to
Event Cancellation
A condition detected in Data Input alert messages that allows the system to
Event Processing
An RMS sub-system that allows data input to cause processing, alerting, and
Text Input Alert
A component of the Event Processing System where a specific data input
The Event Processing mode of operation requires configuration of the Base Operating Mode, including
defining one or more Data Connections that use the Event Processing System Data Output, to ensure
alert data gets delivered to the Event Processing System for alert processing and routing.
The system configuration items associated with the Event Processing System are marked in this manual
with an
EP
superscript.
Glossary of Terms
conditions and interface to a sensor monitoring infrastructure. Examples are
an Inovonics sensor or a WaveTrac sensor.
Infrastructure
system for processing of the sensor information. Examples are Inovonics
repeater networks and WaveTrac receiver networks.
typical alert interface protocols, such as TAP, COMP2, and COMP1, where the
alert contains an address value and a message. The Data Input alert messages
are processed to try to detect both event activation and event cancellation
conditions.
arriving on a Data Input can be routed to the associated Data Output defined in
the Data Connection.
mark that alert message as triggering an Event Activation condition. All Data
Input alert messages are, by default, treated as Event Activation conditions
mark that alert message as triggering either an Event Cancellation condition.
Some input protocols provide Event Cancellation signaling, while others may
require use of the Cancel Prefix or Cancel Suffix method defined in Data Input
configuration.
System
logging of alert events. The Event Processing System is a standard Data
Output, allowing you to link a Data Input directly to the Event Processing
System when configuring a Data Connection
unique event is configured to trigger alert event processing for that data input
unique event
11
Inovonics Echostream
A wireless sensor monitoring infrastructure manufactured by Inovonics that
requires no radio license to install, and uses 900 MHz band frequency hopping
WaveTrac Sensor
A Bluetooth Low Energy transmitter that uses regular Bluetooth advertisement
WaveTrac Gateway
A wireless sensor monitoring infrastructure that requires no radio license to
TAP
Telocator Alphanumeric Protocol, used for radio paging system control and
COMP2
Used for radio paging system control and alert system interface
RTLS
Real-Time Locating System, supports tracking of mobile humans and
Proximity-Based
Proximity-based Locating is a pseudo-RTLS that does not perform triangulation
Point-of-Interest
A physical point inside a facility, where an RTLS system is trained to recognize
LAN
Local Area Network
WLAN
Wireless Local Area Network
Momentary vs
Momentary alerts are alerts that are reported once and are not tracked for an
technology
transmissions to communicate its status to the WaveTrac sensor monitoring
infrastructure
install, senses WaveTrac sensors, and uses WiFi to deliver the signals to the
head-end system
alert system interface communications on a serial port or via Ethernet
communications on a serial port or via Ethernet
equipment and alert events associated with mobile humans and equipment.
The humans and equipment need to have an Inovonics sensor or a WaveTrac
sensor attached to them in order to allow tracking to occur.
Locating
calculations and does not require the definition or training of Points-ofInterest. Proximity based locating works well with WaveTrac sensors because
the WaveTrac sensors output a check-in advertisement signal often enough to
allow WaveTrac Gateways to sense their proximity, and to report those
proximity events to the head-end system. Proximity-based RTLS provides the
benefits of being able to receive alert messages and to look up the last known
location of a sensor without being required to maintain Points-of-Interest
tables or to perform real-time triangulation calculations.
when mobile humans and equipment are nearest that point, to aid in providing
location information in alert messages. Points-of-interest are required to be
both defined and trained in order to be able to perform triangulation
calculations to determine where a sensor is located. Proximity-based Locating
eliminates points-of-interest configuration and management.
Latching Alerts
alert cancellation event. Latching alerts are alerts that can be reported both on
alert initiation and then on alert cancellation. Latching alerts are tracked for
cancellation events, and logged so that alert response performance reports can
12
be generated.
Receivers
Receivers are used by both the Inovonics infrastructure as well as the
WaveTrac Sensor infrastructure. All receivers need to be registered with the
WaveTrac Receiver
A receiver that performs the purpose of sensing WaveTrac sensor signals and
Inovonics Receiver
A receiver that performs the purpose of sensing Inovonics sensor signals and
Elopement Sensor
A receiver that is installed and configured to perform doorway elopement
Zone
A system reference that allows configuration of relationships between sensors,
Alert Type
A reference for a given sensor to allow alert message formatting and to allow
Alert Client
An application or browser page that allows a system user to observe active
Digital Alert Viewer
A feature that allows a list of active alerts to be viewed in either a desktop
Slow Response
A time value that is compared to the length of time that an alert has been
Backup Zone
A zone that is designed to be notified if an alert ages beyond the Slow
system for purposes of helping to perform basic alert location calculations
when alerts occur, by identifying which receiver was closest to a sensor when
an alert is generated. Inovonics receivers can be in the form of a central
receiver with serial port output, or in the form of a wireless repeater.
WaveTrac gateways can be used for both basic location services as well as
Proximity Based Locating services.
routing those signals to the head-end system for processing. WaveTrac
receivers can be configured to perform autonomous signal processing and
include the monitoring of dry contact inputs and the control of open collector
outputs as a means of providing additional sensing as well as autonomous
operating behavior at the receiver location.
routing those signals to the head-end system for processing.
sensing with WaveTrac sensors, while also monitoring for door opening events
and while controlling local audible/visual annunciation
residents, rooms, and alert recipients, to allow proper alert message routing,
schedule based alert delivery, and management of the system by operating
shift
an alert recipient the ability to better understand the context of the alert
alerts from a desktop browser or from a mobile device.
browser or on a digital TV
Threshold
active, such that when the Slow Response Threshold time value is exceeded by
an active alert’s age, the alert can be marked as a slow response alert to aid in
prioritizing attention to active alerts, and can also trigger notification of the
alert recipients assigned to any backup zones assigned to the affected zone
Response Threshold time
13
Audio File
An audio representation of a portion of an alert message, where the system
can concatenate audio files and deliver those to alert recipients in an audio
Report Template
A predefined template for delivery of scheduled standardized reports via e-
Audio Gateway
A device that allows Ethernet based audio output to PA systems, speakers, and
Messaging Client
A function that allows users to manually generate messages to be sent to
Messaging Groups
A function that allows creation of groups of Messaging Client recipients, for
Pager ID
A numerical value that defines how alerts are routed through the system.
Whitelist
A Settings field parameter that can be used to help the system filter the
Blacklist
A Settings field parameter that can be used to help the system filter the
Maintlist
A list of one or more Pager ID values, defined as a parameter in a Settings field
fashion. The audio files can be delivered to desktop browser Digital Alert
Viewer, to walkie-talkies via two way radio interface, and to PA systems or
amplified speaker systems
mail.
two-way radio systems
pagers, e-mail, and/or XMPP apps, by selecting one or more recipients that are
associated with those types of outputs
ease of multi-selecting recipients in the Messaging Client function
Synonyms to Pager ID can include Address, Extension, Capcode, PIN, and
UserID
routing of messages. The Whitelist contains a list of one or more Pager ID
values and tells the system to route messages to all listed Pager ID values. The
Whitelist can be used with Data Inputs that use the COMP1 or Inovonics
protocol. The Whitelist can be used with all Data Outputs. The Whitelist and
Blacklist cannot be both in the same Settings field, as they contradict each
other. An example Whitelist is whitelist=101;105;223, or whitelist=101
routing of messages. The Blacklist contains a list of one or more Pager ID
values and tells the system to route messages to all Pager ID values other than
the listed Pager ID values. The Blacklist can be used with Data Inputs that use
the COMP1 or Inovonics protocol. The Blacklist can be used with all Data
Outputs. The Whitelist and Blacklist cannot be both in the same Settings field,
as they contradict each other. An example Blacklist is blacklist=101;105;223,
or blacklist=101
for a Data Input configuration record, when that Data Input uses the Inovonics
protocol. The Maintlist tells the system to route maintenance related
messages to all listed Pager ID values. Those maintenance related messages
can include Battery and Tamper notifications for Inovonics sensors. An
example Maintlist is maintlist=221;145, or maintlist=221
14
15
Installation of RMS
To install RMS, you may need the following:
• RMS Unit
• One or more WiFi Access Points
• One or more Android smartphones with Responder 5000 Messaging App
• Windows PC running the WaveWare Discover and Reset Tool, connected to LAN, for purposes of
discovering the RMS on the LAN (only required if using DHCP to assign an initial IP address to the
RMS, or if the static IP address is incompatible with the LAN the RMS is connected to.
• An Inovonics central receiver, and zero or more Inovonics repeaters, to process Inovonics signals
• An Ethernet controlled paging system and/or up to four serial port controlled paging systems or
downstream devices that process TAP protocol. Note: When connecting WaveWare paging
systems to the RMS USB ports, you will need a Belkin USB-to-Serial Portable Adapter for each
paging system.
The RMS should be installed using the following procedure:
• Before powering up the RMS, make all of the connections, including:
o Ethernet
o One Belkin USB-to-Serial Portable Adapter per serial port connection
• Connect power to the RMS, then press the button on top of the RMS to launch the boot-up
process. Wait a few minutes for the RMS to boot up.
Configure Static IP Address
The RMS ships with DHCP enabled, so that it can obtain a dynamically assigned IP address when it is
connected to a LAN. The RMS requires a static IP address assignment in order to have uninterrupted
operation monitoring the Responder alerts. Use the following procedures to set a static IP address in
the RMS.
Discover the RMS Using WaveWare Discover and Reset Tool
The WaveWare Discover and Reset Tool is designed to make it simple to install and configure an RMS.
Simply connect the RMS to your LAN, then run the Discover and Reset Tool’s Discovery function to
discover the RMS on the LAN.
You can download the WaveWare Discover and Reset tool at the following link:
Install the Discover and Reset Tool. Note: WaveWare Discover and Reset Tool requires Microsoft .NET
runtime files to be installed on the PC that will be used to run the app.
Connect a Windows PC running the WaveWare Discover and Reset Tool to the LAN that the RMS is
connected to. Launch the Discovery function to open the Discover WaveWare Systems screen. Click on
the Discover button (magnifying glass icon) to start the discovery process. Any RMSs and WaveWare
systems on the LAN should appear in the list within a second or two.
16
Note that the RMS should be displayed in the list with a Model value of R5000. Click on the displayed
record of a discovered RMS to launch the default browser and to pull up the RMS configuration page.
Figure 2 – WaveWare Discover and Reset Tool - Discovery
Figure 3 – WaveWare Discover and Reset Tool - Configure
17
Note: If the RMS is configured with DHCP disabled and the IP address assigned to the RMS is
incompatible with the LAN that the RMS is connected to, when you click the the record of the
discovered RMS, a popup window will occur that tells you that you need to reset the RMS to DHCP
mode.
Note: The RMS ships with DHCP enabled. If the LAN that the RMS is connected to does not allow UDP
broadcast packets, then the WaveWare Discover and Reset Tool will not discover the RMS. Refer to
Troubleshooting section for how to address this issue.
Log Into RMS
Once you click on the discovered RMS, if there are no IP address configuration problems, you should be
prompted for userid and password in the browser. The Master Userid value is defined by a label on the
RMS unit, and the default password value is blank. In addition, the RMS ships with a default userid value
of admin and a default password RMSpass1234.
A successful login will cause display of the RMS main page
in the browser. The drop down menus and main page
contents are filtered by the Role assigned to the user
account. The default user account is assigned a Role
value of Super, which provides full configurability. Any
other Role assignment only causes display of the drop
down menu bar.
Configuration is described in more detail below. You are
also offered a link for downloading the RMS manual,
which requires internet access.
You can identify the system version number by clicking About in the RMS web config menu. You can
observe the Master Userid value once you log in by opening the General Settings web config page.
18
Figure 4 – RMS Main Page
19
Configuration of RMS Server
The RMS is configured via a browser based configuration page that can be located at the current IP
address of the RMS. Reference the configuration sequence defined on the main page. The primary
means of navigating in the RMS configuration interface is the drop down menus. The drop down menus
are organized based upon the following primary factors:
• Role of Logged in User (User, Admin, or Super)
• Event Processing
is disabled. The menu items and associated functions that are marked with
when the Event Processing system is activated in the General Settings config page.
Setup
• General Settings
• E-mail Input Server
• E-mail Output
• Rules and Filters
• LED Display
• LED Display Priority Msgs
• Messaging Groups
• Predefined Messages
• Test Data Outputs
• System Events
EP
EP
System Activation/Deactivation. The default setting is that Event Processing
EP
are only available
• Utilities
Inputs/Outputs
• Data Inputs
• Data Outputs
• Data Connections
• Messaging Client
Facility
• Rooms
• Residents
EP
EP
20
• Zones
EP
• Wireless Receivers
• LED Displays
• Digital Alert Viewers
• Audio Gateways
• Audio Files
EP
Alert Sources
• Alert Types
• WaveTrac Sensors
• Inovonics Sensors
• Text Input Alerts
Alert Recipients
• User Accounts
EP
EP
EP
EP
• Pagers
EP
• Alert Client
Zone Assignments EP
• Zones
• Zones/WaveTrac Sensors
• Zones/Inovonics Sensors
• Zones/Text Input Alerts
• Zones/Residents
• Zones/Rooms
• Zones/User Accounts
• Zones/Wireless Receivers
• Zones/Data Outputs
• Zones/LED Displays
EP
EP
EP
EP
EP
EP
EP
EP
EP
EP
• Zones/Backup Zones
EP
21
Schedules EP
Reports
• Report Templates
• Scheduled Reports
• Generate Reports
Notes:
1. All configuration edits are directly saved to the database when you are operating in the grid
view. A successful database update is indicated by the selected row flashing green. A failed
database update is indicated by the selected row flashing red. If an update is not allowed, you
may see a popup message in addition to the row flashing red.
2. The grid view may offer read-only fields, text editing fields, numeric editing fields, drop-down
lists, and checkboxes. When you edit text and numeric fields, simply click on the cell you want
to edit, then hit the Enter key or Tab key to cause the new value to be written to the database.
On the other fields, the database edits are made immediately when you make your selection, as
indicated by the row flashing green. On drop lists, you can type the first character(s) of the
selection you want to make and the selection is automatically written to the database when a
single match is found.
Setup
General Settings
The General Settings page allows general configuration of the RMS system. It also indicates the
authorized features available with the system. A Generate Request Key button is available to allow you
to communicate with your distributor using a Request Key to adjust authorizations.
Toggling the Event Processing checkbox changes how the General Settings page is displayed. You must
refresh the page to see the effect of the checkbox toggle. The items required for configuring Event
Processing operation are displayed only when Event Processing is enabled. Note that toggling Event
Processing also affects the display of RMS web configuration menu items.
22
Figure 5 – General Settings Configuration when Event Processing is Disabled
Figure 6 - General Settings Configuration when Event Processing is Enabled
Following are the components of General Settings page with a description of how they affect system
operation. Items marked with
EP
are displayed only if Event Processing is enabled.
System Name
Defines a value that the system uses to respond to the Discovery and Reset Tool, to allow easy
identification of the system on the network.
23
Site Password
Defines a value that wireless receivers and other system level devices use as a password to log into the
server.
Time Zone
Defines the time zone that the system uses. When Time Zone is adjusted, the system may be nonresponsive for up to 30 seconds.
Event Processing
If checked, the Event Processing System will be enabled, offering the ability to configure for the
management of alert life cycles, logging, and reporting. Otherwise, only data protocol conversion, data
filtering, data translation, data input combining, and data output splitting functions will be available, via
the Inputs/Outputs functions.
IP Address
If non-blank, this is the IP address that the system will be assigned, as a static IP address. If blank, the
system will use DHCP to obtain an IP address.
Default Gateway
If non-blank, this is the default gateway value that the system will be assigned. This setting will only be
applied upon restart of the system.
Subnet Mask
If non-blank, this is the subnet mask value that the system will be assigned. This setting will only be
applied upon restart of the system.
Time Server
If non-blank, this is the URL to a time server. The system will, by default, attempt to connect to time
servers on the internet. If this field is non-blank, this URL will be added to the list of time servers to
attempt to connect to. This setting will only be applied upon restart of the system.
Shift 1 Start EP
The time that shift 1 operations start, to help the system perform shift based operations, formatted as
HH:MM in 24 hour format, e.g. 08:00. If the update fails, modify your entry to match the HH:MM format
and try again.
Shift 2 Start EP
The time that shift 2 operations start, to help the system perform shift based operations, formatted as
HH:MM in 24 hour format, e.g. 16:00. If the update fails, modify your entry to match the HH:MM format
and try again.
24
Shift 3 Start EP
The time that shift 3 operations start, to help the system perform shift based operations, formatted as
HH:MM in 24 hour format, e.g. 24:00. If the update fails, modify your entry to match the HH:MM format
and try again.
Freq Call TH EP
The minimum time, in minutes, between the time of deactivation of a call for a particular sensor and
reactivation of that call, at which that call should be marked as a frequent call, for use in the Frequent
Calls report
Slow Resp TH EP
The minimum time, in minutes, between the time of activation of a call for a particular sensor and
deactivation of that call, at which that call should be marked as a slow response call, for use in the
system reports. The Slow Response Threshold is also used to determine when to route the active call to
any defined Backup Zones, or if no Backup Zones are defined for the affected zone, to determine when
to escalate the active call to supervisory level. A value of 0 indicates that this feature is disabled.
Backup Resp TH EP
The Backup Response Threshold is used to determine when to escalate an active call to supervisory
level, after that call has been routed to any defined Backup Zones. A value of 0 indicates that this
feature is disabled.
Sec/Repeat Paging EP
The time, in seconds, that should occur between radio paging based repeat notifications of an active
alert. Applies to both POCSAG and audio file based radio paging.
Page Cancel EP
When checked, radio paging output includes a cancel notification when an alert is deactivated. This
setting is only applied within the event processing system. Cancel notification can also be configured for
each Data Output in the data output’s Settings field.
Default Zone EP
The Zone that newly detected sensors should be auto-assigned to. If Unassigned is selected, newly
detected sensors will not be auto-assigned to a Zone. Selecting a Default Zone makes zone to wireless
receiver assignments and zone to sensor assignments much easier to accomplish due to the autoassignment process.
Include Location
When checked, alert notification text will include information defining the location where the alert was
generated, for sensors that can be mobile.
25
OOP Timeout EP
The amount of time, in seconds, required to trigger an out-of-proximity event once an in-proximity
signal is no longer detected from a WaveTrac sensor
Motion OOP Timeout EP
The amount of time, in seconds, required to trigger an out-of-proximity event once an in-proximity
signal is no longer detected from a WaveTrac sensor, and a motion signal has been detected within the
OOP timeout period
Audio Preamble EP
If the Audio Preamble is not Unassigned, the server will play an audio preamble each time an assigned
audio file is played.
Audio Postamble EP
If the Audio Postamble is not Unassigned, the server will play an audio postamble each time as assigned
audio file is played.
Max Log Age EP
The maximum number of days that the call logs should be retained, in days. 60 days is recommended.
Auto Compl TH EP
The Auto Completion Threshold, in units of minutes, is used to determine when the system should
automatically mark an active call as complete. The primary use of this feature is when the system is
primarily deployed with alerts that do not signal completion/cancellation and/or when alert notification
methods do not support telling the server when an alert is completed, e.g. e-mail, radio pager, audio
output. A value of 0 indicates this feature is disabled.
Install Mode EP
If checked, Install Mode causes the system to provide additional information to the Alert Client app and
to the Digital Alert Viewer, to aid the technician during the installation of the system. In addition, you
can assign a Network Template to a WaveTrac receiver in the Wireless Receivers page.
Demo Mode EP
If checked, the server will auto-generate and auto-cancel sensor based alerts as a means of
demonstrating how the system works. The system should also process alerts normally while in demo
mode
Source Prefix EP
If checked, the server will prepend the name of the associated Data Input to outgoing messages, which
is pulled from the Source field of Text Input Alerts. This feature only applies to messages generated in
the Event Processing System.
26
Reg Key
The registration key provided by the distributor to define activation of system features and any system
scalability limits. The Authorizations table on the General Settings page indicate what is allowed to
function. Inserting a new Registration Key value into the Reg Key field, and pressing the enter key will
adjust the Authorizations. To refresh the Authorizations table, reload the General Settings page.
Registration
The Registration value defines if the Registration Key has successfully been processed by the system,
allowing the system to operate, with the Authorizations section of this page defining the authorized
functions allowed by the Registration Key. This value updates each time this page is refreshed.
System IP
The System IP value identifies the current IP address assigned to the RMS. Note that the editable IP
Address field defined above, could be blank, to cause DHCP processing to occur. Otherwise, both the IP
Address value and the System IP value should be the same, representing a static IP address assignment.
Master Userid
The Master Userid value identifies a Userid value that can gain master access to the system. This Master
Userid will work with any password value, including blank. The Master Userid value is unique to this
particular installation and is derived from the CPU serial number. The Master Userid should also be
printed on a label on the system housing.
Authorizations
The Authorizations table in the General Settings page displays the authorizations allowed by the
Registration Key.
Max Data Inputs
Defines the maximum quantity of Data Inputs that will be allowed to be configured
Max WaveTrac Sensors EP
Defines the maximum quantity of WaveTrac Sensors that will be allowed to be configured in the Event
Processing System, when it is enabled. This field only appears when Event Processing is enabled.
Max Inovonics Sensors EP
Defines the maximum quantity of Inovonics Sensors that will be allowed to be configured in the Event
Processing System, when it is enabled. This field only appears when Event Processing is enabled.
Max Text Input Alerts EP
Defines the maximum quantity of Text Input Alerts that will be allowed to be configured in the Event
Processing System, when it is enabled. This field only appears when Event Processing is enabled.
27
Max Data Outputs
Defines the maximum quantity of Data Outputs that will be allowed to be configured
Messaging Client Enabled
Identifies if the Messaging Client feature is enabled
Max Concurrent Browser Alert Client Connections
Defines the maximum quantity of Browser Alert Client connections that will be allowed to be
concurrently connected to the system. This field only appears when Event Processing is enabled.
EP
Update Registration Key Button
You can update your system Registration Key by either pasting a new Registration Key value into the Reg
Key field of the table, or you can click the Update Registration Key button. This button requires the
system to have access to the internet, as it attempts to automatically retrieve the latest Registration Key
from the wirelessmessaging.com server.
When you click the Update Registration Key button, you will see the Registration Key Update page as
shown below. If there is no internet access from the system, the response will be Registration Key
Update Failed.
When you click the Update Registration Key button, you will see the Registration Key Update page as
shown below. If there is no internet access from the system, the response will be Registration Key
Update Failed. The Request Key, Serial Number and Version values are for reference purposes only.
Figure 7 - Update Registration Key
E-mail Input Server
The E-mail Input Server page allows configuration of how e-mail input processing should be performed.
This is required only if you have enabled SMTP protocol on a Data Input.
28
Figure 8 - E-mail Input Server Configuration
IP Address/Domain
The domain name or IP address of the SMTP server that will process the incoming e-mail. Typically this
is the IP address of the system.
Address Filtering
If checked, the incoming e-mail will be rejected if the domain name or IP address portion of the To:
address does not match the IP Address/Domain value. Otherwise, only the first part of the To: address
will be matched against the Zone names, then against the User Account names in the system.
Sender In Msg
If checked, the From: address will be included in the message delivered by the system
Incl From Header
If checked, a header value of “From: “ will be included in front of the From: address value in the
message delivered by the system.
Subject In Msg
If checked, the Subject: value will be included in the message delivered by the system.
Incl Subj Header
If checked, a header value of “Subject: “ will be included in front of the Subject: address value in the
message delivered by the system.
Body in Msg
If checked, the Body: value will be included in the message delivered by the system.
Incl Body Header
29
If checked, a header value of “Body: “ will be included in front of the Body: address value in the message
delivered by the system.
E-mail Output
The E-mail Output page allows configuration of how e-mail output processing should be performed.
This is required only if you have enabled SMTP protocol on a Data Output, you have scheduled Reports,
or you intend to e-mail user generated reports.
Figure 9 - E-mail Output Configuration
Host
The URL or IP address of the SMTP server that will process and deliver the e-mail
From Name
The reference name used to identify who generated the e-mail, e.g. RMS
From Address
The e-mail address used to identify who generated the e-mail, e.g. RMS@somewhere.com
Subject
The subject line in the e-mail. This is used only if Msg In Subject is unchecked
Msg In Subject
If checked, the alert message will be in the subject line instead of in the e-mail body. If unchecked, the
alert message will be in the e-mail body and the Subject line will use the Subject value above.
User ID
The User ID value used to log into the e-mail server. Can be blank if the e-mail server does not require
authentication
30
Loading...
+ 77 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.