2021.2 Release Notes

Notifiers and Activators

You can now send notifications to Mitel 53xx series devices, which, in most cases, support text and images (no audio). See Legacy Phones for information about the devices and their limitations. See Configure Mitel 53xx Devices for information on setting up the phones for use with Revolution.

Revolution now supports SIP registrations from any active server in a Revolution redundancy cluster which provides you more flexibility when configuring your system. See Add a SIP registration.
When creating SIP Endpoints you can define that a SIP registration should be used for initiating rather than the SIP URI. See Creating SIP Endpoints.

You can now track responses to notifications that are still active. Previously, you could only see responses for notifications that had completed. These responses will update in real time.

When creating a notification using the Send Notification Notification Action Types, you can now instruct the notification to pass through any audio with the original notification. See Sending a notification based on an event for information about the Forward audio to linked notification setting.

In a redundant environment, you can view and cancel active notifications from any server in the cluster. Revolution is also able to perform busy detection for notifications on endpoints across the cluster. See Cancel notifications and Setting the priority.
When logged into any server in a redundant environment, you can access information about each module in the cluster by selecting the server at the top of the page. Previously, the primary server only showed information about all the servers.

You can now trigger notifications directly from the DNC on both Windows and macOS. On Windows, there can also be a panic button available from the Windows notification tray. See Desktop Triggers for information about creating the triggers and Sending Notifications from the DNC for information about using the DNC.
If your Microsoft Windows system allows for multiple users to log in simultaneously, each user can receive notifications through the DNC. An administrator installs the DNC once on a machine, which makes it available to all users of the machine. See Using the DNC on Multi-user systems.
The Manual Server List is now a machine-wide setting. Revolution administrators can edit this list in the DNC configuration file. See Configuring DNC Settings on Windows and Configuring DNC Settings on macOS.

Contacts must now verify new or edited phone numbers and email addresses before Revolution sends a notification to those contact methods. See Verifying Email Addresses and Phone Numbers.

Note: This does not apply to phone numbers and email addresses added to Revolution before this release.
When importing contacts through Active Directory, Revolution will also import additional external phone numbers. See Active Directory Contact Property Mapping.

When updating endpoints in bulk through the use of a CSV, you can now update Site information. See Bulk Add or Update Devices from a CSV File.

You can now control the logging level (Debug, Info, Warn, Error, or Fatal) on a module-by-module basis. See Controlling Log Settings.

When creating Dynamic Endpoint and Dynamic Contact Tags you can now filter by the Site system tag. See Creating and Using Dynamic Tags.

You can now Configure the port range used by Revolution to limit the number that must be open in your firewall. Use the Port Range Start and Port Range End settings in Global Settings > Network. See Network.

You can customize licensing limits for when Revolution sends notifications through Status Alerts or via the GUI. See Licensing.

Added support to create, update, read and delete phone service trigger actions. Including:
- Cisco – Dial monitor and phone service trigger and dialer. See Cisco Actions.
- Mitel – Phone service trigger and dialer. See Mitel Actions .
- Avaya – Phone service trigger and dialer. See Avaya Actions .
- Poly – Dial monitor and phone service trigger and dialer. See Polycom Actions.