2021.4 Release Notes

Integrations

You can now link Revolution to Honeywell CLSS to deliver auxiliary notifications for fire safety service detection and alarm systems. You will link your CLSS cloud account to Revolution and configure events to trigger Revolution notifications. See Honeywell CLSS Integration.

You can now link Revolution to Intrado School messenger to send Broadcasts to your School Messenger contact lists resulting from on-premises events. You will link Revolution to your School Messenger account and create new Services to be used as endpoints in your notifications. See School Messenger Integration.

When creating Direct Two-Way notifications, Revolution will only show endpoints that have receive and transmit capability. When creating Push To Talk notifications, it will only show Cisco endpoints.

You can limit a notification to only activate during a specific time period. See Enabling Active Hours.

When you activate a notification from the Revolution web UI, you can send location information by allowing or denying your browser location settings. See Include your Location in Web-Activated Notifications.

Use this new notification type to initiate Revolution Conferences with any trigger, rather than just a SIP trigger. See Conference Notification

When copying calendars, you can now define how the copy handles events, pause ranges, and settings. See Copying Calendars.
When importing events from an ICS file, events without a timezone will inherit the timezone of the parent calendar. If that calendar does not have a timezone, the event will inherit the local timezone. See Importing events from an ICS file.

The CAP module has a new setting for controlling whether self-signed certificates are accepted. See CAP Module Settings — Services and Triggers.

Revolution now supports CUCM 14.
When setting up a CUCM Call Manager, you now define the CUCM version via a drop-down menu, rather than a text entry box. See Call Manager.

When you are creating a status trigger to send a notification about module statuses, you can trigger off of module warnings, now in addition to missed heartbeats and errors. See Creating Status Type Filters.
You can now trigger status alerts based off of Revolution triggers that are in an Error or Warning state. See Creating Status Type Filters.
There is a new setting for status triggers that allows you to control how Revolution batches similar events into a single notification activation. See Status Trigger Settings.

When viewing existing SIP Registrations, their Status is now shown with a colored indicator.

The refresh button in the Desktop Notification Client triggers pane will now also update your site status in the case where your computer, most likely a laptop, has moved. See Sending Notifications from the DNC.
The DNC uses a new version numbering format: YY.Q.NNN (year, quarter, build number). The build numbers will vary for the OSX and Windows version.

For the iOS application, the application icon will display a badge count of notifications received.
You can now show any location accuracy information in notifications, as captured by the mobile device. See Sending Notifications Based on Mobile App Triggers.

The Endpoint Map of the Endpoints page now shows icons for sites that have been assigned coordinates. By selecting these site icons you can view a filtered list of endpoints associated with that site in the Endpoint List window. See Endpoint Map.
Inactive endpoints are automatically deleted after a specified number of days. You can change this behavior in Global Settings > Endpoints with the setting Automatically Delete Inactive Endpoints. See Endpoints.

You can set elevation, latitude, and longitude information when activating notifications from the API. See Notifications.
You can enter location information into the directory through the API. See Directory.

You can now view a unique ID associated with your cloud service triggers, which you can use with the Revolution API. See Create a cloud service trigger .