You can now import your contacts, via CSV, on a pre-defined interval from a local directory on your Revolution server. This allows you to maintain a single file of contacts that can be easily imported into Revolution.

Revolution has improved support for jack number information from Mitel MiVoice Connect. This is built into the Revolution and there is nothing you need to configure for this support.

You can now define the specific behavior of a Revolution trigger. Each trigger can either activate, deactivate, cancel, or toggle a notification. This allows you to have more fine-tuned control on which devices or actions can start or stop a notification.

Two changes to the DNC improve upon the security of activating notifications. When creating DNC triggers you can now require a user to enter a security code before activating a notification. You can also limit triggers to users who have used Revolution credentials to log in to their DNC.

You can now install Revolution on Windows Server 2022, increasing our support in addition to Windows Server 2016 and 2019.

Revolution has added support for additional models of Yealink phones.

You can now create dynamic tags based on CIDR notation to more easily group your network addresses.

Revolution now installs with SQL Server 2019 Express. When you upgrade to this release, the installation process automatically includes this version of SQL, there is nothing special for you to do.

With the addition of SQL Server 2019 Express, Revolution no longer supports Windows Server 2012 R2. If you attempt to install this upgrade onto a 2012 server, the installation will fail with an error. Windows Server 2016 and 2019 are still supported.

You can now easily migrate your DNC triggers to your Mobile configuration, and vice versa. This will allow you to create similar user experiences for your contacts across the DNC and mobile interfaces.

You can quickly copy many configuration actions to speed up your environment setup process.

For your notifications that allow contacts to respond, you can now set additional Revolution behavior for when a set number of responses are received. This can include stopping a continuous notification after a set number of responses or triggering an additional notification after reaching the quota.

For your notifications that are sent via email, you can define a From address, to which your contacts can reply. This can ensure that responses are sent to a particular recipient for that notification.

If your environment generates Secure Real Time Transport Protocol Requests (SRTP), you can now enable the SIP module to support this method.

You can now generate a report that contains setup information of your notifications, allowing you to view and analyze your notifications in a CSV file.

You can now bulk edit your IP Devices inputs, SIP Endpoints and Lines within the Revolution UI and also can export and import changes through a CSV.

You can now use multiple levels of floor plans for your Revolution endpoint location mapping.

You can now generate more types of reports about your Revolution environment, including sent notification reports, user tag reports, and notifications reports including associated triggers.

You can also generate notification summary reports for a specific notification.

Now if you enable WhatsApp in your Twilio account, you can configure Revolution to send notifications to contacts through WhatsApp.

You can now configure notification action types to send subsequent notifications when a notification ends with a partial success, where some, but not all, endpoints or contacts have a Success status.

When reviewing information about a sent notification, if the activating trigger had a location associated with it you can now view that location in a map view.

After Revolution DNC registers at least once with your local or VPN network, it can continue, with partial functionality, if you move to a location off the local or VPN network. This allows DNC users to work remotely and still connect to Revolution.

Intrado School Messenger allows you to send emergency, attendance and other alerts via text, voice, email and social media to parents and communities. You can now trigger and create School Messenger broadcasts from Revolution allowing you to combine in-building and community notification.

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

Location information is now available when you trigger a notification from the web browser or from the customer API.

Conferences can now be triggered from automated workflows, panic buttons and external systems. Immediately bring your security team together in a conference when an emergency, such as a 9-1-1 call occurs, or automatically start a conference at a specific time.

You now can set up notifications to trigger only during at certain times periods of the day. For example, you can configure different security teams to get a notification during business and after hours or only notify staff about weather alerts during the school day.

Revolution now allows you to delete inactive endpoints automatically which simplifies administration. You can select how long you wish to keep endpoints after they have gone inactive from the Global Settings page.

Now when you copy a scheduled calendar you can choose to copy the pause ranges and other settings to the new calendar in addition to the calendar events.

The Revolution customer API now supports adding to and editing the location directory.

We have redesigned the Revolution Configuration menu layout to be by function. This updated navigation menu makes it easier for you to find settings and configuration options.

Configure your Yealink phones to register with our application to receive text and image notifications. (Images supported on HTML-capable Yealink phones.) Configure a multicast static stream to send audio to Yealink phones.

You can now, optionally, allow a non-live notification to queue when there is currently a higher priority notification active. Once the higher priority notification completes, the lower priority notification will be sent.

Now when you import your users and contacts from Active Directory you can use a secure LDAP connection.

Once you've connected your organization to G Suite, your users can log in to Revolution with their Google account. The login username must match the Google connected email address in order to use this feature.

You can now set up alarm data to be sent to 9-1-1 during an emergency which can be viewed by the 9-1-1 operator when a 9-1-1 call is received from your location. This is an optional feature that is not available in all areas. Please contact our sales team if you are interested in adding this feature to your system.

Details about sent notifications are now logged to a file in addition to being viewable on the sent notifications page.

You can now choose how you monitor status alerts. You can set up triggers to only notify you when errors occur, select specific modules to monitor, and decide what types of license warnings and errors you want to see.

You can now create and upload your own SIP audio prompts for use with Revolution. This includes customizing the voice and prompts to meet the needs of your users.

We've improved the text and image display on the larger Poly CCX displays to make it easier to quickly see and respond to a notification.

Configure your Mitel 5300 phones to download our application, which allows them to receive notifications. (Images are supported on only some models.)

Revolution now supports SIP registrations from any active server in a Revolution redundancy cluster which provides you more flexibility when configuring your system. You also can configure the RTP audio ports and range.

The Revolution DNC now supports triggering notifications directly from the DNC application. You can also configure the DNC to support a panic button in the Windows notification tray so that users can quickly alert key people in an emergency.

The Revolution DNC now supports sending notifications to multiple concurrent interactive sessions on Windows. Now, all logged in users will receive notifications from Revolution allowing you to reach more people when an event occurs.

You can now configure Revolution to forward audio from a notification to subsequent notifications. At the end of a live broadcast you can forward the audio to another notification allowing you to manage the priority and workload of notifications on your server.

When using an email address or phone number supplied by a user, it is important to verify the user is the owner. You can now configure Revolution to send a verification link or verification code when new email addresses and phone numbers are entered using the self-service portal.

You can now view and cancel active notifications from all servers in the cluster. In addition, Revolution is now able to perform notification busy detection for endpoints across the entire cluster.

The Revolution customer API now supports the creation of phone services for Cisco, Mitel, Avaya and Poly.

When you include response options in a notification, you can now view any responses received in real-time. Revolution will push content to connected web browsers as it happens, allowing you to react quickly in an emergency.

When you trigger a notification from the mobile app, you can now view notification responses directly from the app, allowing you to react quickly in an emergency to assistance requests.

Intrado Safety Shield leverages Intrado’s status as a 9-1-1 service provider to offer its users a faster connection to 9-1-1. Intrado Safety Shield passes critical data about callers on to 9-1-1 dispatch automatically, allowing for faster understanding and more accurate info sharing. You can now trigger Safety Shield events from Revolution and receive Safety Shield alerts on your in-building speakers and phones.

You can now create and import location information for any phone number or extension. This allows you to report a location in an emergency even for devices that are not supported endpoints in Revolution.

SNMPv1 is the original version of the protocol. More recent versions, SNMPv2c and SNMPv3, feature improvements in performance, flexibility, and security. Revolution now supports all three versions to allow SNMP traps from more devices.

To make configuration and navigation easier, the Manage Notifications, Sent Notifications, Users, and Contact pages will retain your search entry until you clear it or log out of Revolution.

Revolution will now use location information received in a SIP geolocation header. You can use this information to know the location that triggered a lockdown or other emergency notification in Revolution in SIP platforms that support geolocation.

You can now select which SMS or Dialer gateway to use on an individual notification basis. This allows you to send in different languages or use different phone numbers for different site locations.

When sending notifications via SMS, email and mass dialer you can now receive responses. You can send out a health or safety check such as "Are you well?" and receive response options such as "I am well" or "I am unwell" on more types of endpoints, which allows you to reach more people.

You will now see an indicator in the Revolution message center when major updates are available.

You can now import custom names and locations by matching the destination code, this is in addition to IP Address or URN. This allows you to pull in location information from other systems for use within Revolution.

You can now send location information from Revolution notifications to webhooks. This allows you more options when setting up integrations with external systems. External systems can know the exact location of the person triggering an urgent alert, which will allow responders to help more quickly.

You can upload customer floor plans and match them to your location. This allows you to see and place your endpoints more accurately making it easier for your team to respond in an emergency.

You can now set a default location for each configured site. Revolution will use the Site location information for an endpoint in that site if there is not a specific location set for that endpoint.

You can now use multiple criteria to filter your endpoints when searching on the endpoint page. For example, you can find endpoints that are Inactive AND on subnet 192.168.10.

You can now receive important Revolution notifications on Windows PCs that are not currently logged in allowing you to reach more people with your urgent alerts.

Revolution now shows your endpoints on a map if they have location data set. You can quickly find out where endpoints are located and see their status. You can also fine tune endpoint locations by moving them on the map to their exact location.

Revolution now shows endpoints that have location information on a map which helps to quickly customize the endpoints in a notification. Use the map to select recipients based on their location and quickly target notifications to the right endpoints and contacts.

Administrators can now set up dashboard buttons and quick send notifications for all of their users. This will give users a standard set of notifications on their dashboard so that they can quickly start using Revolution to activate notifications. Users can still add their own custom buttons in addition to the global ones.

Revolution can optionally play the audio file selected in a Stored Audio notification instead of using Twilio Text-to-Speech. Use your own voice in your notifications for a more natural and custom feel for your Mass Dialer notifications.

For customers who require audio in a different language, you can now configure your Mass Dialer Notifications to use another language in the module settings.

Revolution now supports Cisco multiplatform phones. You can send text, images, and audio to these phones. These phones can be used with cloud PBX platforms and other non-Cisco PBX systems.

High priority notifications now set the importance flag for email endpoints so that recipients can quickly open these emails and see the message.

To set up  site views more easily , Revolution now supports a site view mode. You can select "Browse as Single Site" to display a banner from which you can select the site you want. If you've customised Revolution to restrict endpoints, notifications, and tags to a specific site then you verify these settings using this feature.

You can now use Revolution's Scheduler Bulk Delete feature to remove events quickly from your schedules. Bulk Delete by clicking the new pencil icon in the upper-right of the Schedule page and selecting "Bulk Delete." Select and deselect the events you want within a date range and choose if you want to delete the entire series of events or just single instances.

You can now create location-based dynamic tags to target your notifications to specific areas. Areas can be used along with other endpoint filters to correctly target the correct recipients for a notification automatically.

Get a list of all the events that happened in Revolution on a scheduled basis. See who logged in, who made changes, and who activated notifications. You can send reports  as a scheduled event or on demand.

You can now use multiple authentications methods in your webhook integrations. Revolution supports basic, digest, and OAuth authentication methods.

Revolution can now seamlessly use location information from different types of endpoints and mobile triggers. Use this endpoint location data in Dial Monitoring or any notification where the activating endpoints location is available. Optionally add the location of a mobile users when they activate a notification. You also can optionally automatically import your location information from CUCM, MiVoice Connect, MiVoice Business or a CSV file.

You can now assign Revolution users to multiple Revolution sites. Multiple site assignment allows administrators more control over which notifications, endpoints and triggers users can see and use.

Now Revolution allows you to an additional action based on a notification response or status, for example:

• Escalate security issues to a security team
• Send an all clear notification at the end of a lockdown
• Send notification responses to an incident response team

You can also use actions to split up larger notifications into subgroups to make sure critical personnel get the information first.

Revolution now supports Avaya J-Series phones. Configure your Avaya phones to register with our application to receive text and image notifications. (Images supported on some models.)

For customers who use multiple CESIDs per building, you can now trigger a single notification for CESIDs that match a pattern.​

Protect mobile triggers from accidental activation by using a security code. When activating, the mobile user will be prompted to enter the code before the alert will be sent out.

You can now save yourself the effort of recreating schedules by importing schedules from a standard iCalendar file. You can import an iCal file directly into Revolution using the Import calendar events feature.

Revolution can now initiate and receive notifications from Slack or Teams. The Syn-Apps Slack and Microsoft Teams apps allow you to send a notification from Slack or Teams that is broadcast to any selected endpoint. When a Revolution notification is sent to a Slack or Teams channel group, the members will receive details about the situation taking place and can discuss the incident in the channel and have the option to activate another notification.

Revolution Redundancy is enhanced to offer full-redundancy by allowing multiple Revolution servers to work together as a single notification platform. You can now set up a cluster of Revolution servers to deliver advanced load balancing and fault tolerance by sharing message delivery and notification responsibilities. You have full control over which server will activate a notification during normal operation and failover.

Revolution now allows you to post critical information, such as weather closures, schedule changes and updated bus routes, to your school or business Facebook and Twitter accounts. You can update everyone from within Revolution with no need to copy this information manually to social media.

For customers who don't have internet access, there is now a Global Setting in Revolution to disable attempts to connect to the Syn-Apps cloud servers. Please note that mobile, SMS and Twilio mass dialer are not available in this mode.

Many customers use the phone user jack number in MiVoice Connect for location information. Revolution now allows this information to be sent in a notification. Customers can use this field to help them comply with Kari's Law when setting up Dial Monitoring of 911 calls.

Customers can now specify an end time for their notifications. This allows you to run a notification for a specific amount of time or to clear the screen for a Text and Image notification after a specific time.

We've had customer requests to allow more than 5 items in the Quick Notifications list on the Revolution Dashboard. You are no longer limited on how many items you have in your Quick Notifications list which gives you easy access to your notifications.

The Revolution Email Activator allows you to trigger notifications based on specific emails received to individual inboxes. The Email Activator supports Microsoft Exchange and the Internet Message Access Protocol (IMAP). You can set up filters to only trigger notifications based on certain criteria – to or from a particular email account, a particular subject, or keyword matches in the body of the email.

Revolution now supports sending HTTP requests like GET & POST to external systems. You can use the HTTP endpoints you configure to integrate to external HTTP services. Information from your notifications can be passed through to the external system allowing you to extend the reach of Revolution notifications.

Revolution now will automatically updates your Active Directory imported Contacts and Users on a timer schedule. This allows you to spend less time updating your servers. See the Help for more details.

We have further enhanced the Revolution scheduler to now allow you to create an entire event schedule using our wizard. Setting up your school bells, shift schedules and other repeating alerts can now be configured to repeat a pattern of day templates on a weekly or multi-weekly pattern. You can also specify ranges of time you would like to pause your scheduled events which is useful for holiday breaks in your organization.

Revolution now allows you to source audio for your notifications from another system that sends a static multicast stream. You can configure your notification to play the static stream as the audio broadcast of your notification. See the Stream Activator and Direct One Way Notification topics in the help for details.

Our customers have been requesting a way to override text and audio when using the Revolution API HTTP GET to activate a notification. We have updated our API to include this option. Please see the Revolution API specification in the help for more information.

Revolution Conference notifications allow users to create a conference that automatically joins predefined users, and allows additional users to be added on-the-fly. Conference notification is triggered by dialing an assigned SIP line number. See the Help for more details.

Setting up a calendar schedule just got easier with two new functions. Create day templates to automatically create events. Create multiple day templates and apply them to the appropriate schedule days. Right-click on a day of events, select Copy Day, and copy all of that day’s events to another day on the same or different calendar. Delete an entire day of events. See the Scheduler Help topic for all the details.

The weather service utilizes both NWS county feeds (FIPS6 codes) and zone feeds. Revolution’s NWS service has been updated to utilize both feeds based on your settings. Since the weather service determines at the time the alert is created whether to use zones or geocodes, we recommend you set up both. Also, weather events and zone codes have been updated. Please review the National Weather Service Alerts Help topic and review your existing feeds.

Broadcast a message to multiple IP phones (and speakers) asking for an answer. Once a recipient presses the “Accept” soft-key on a phone, all other endpoints are dropped from the notification. Caller and recipient are now in a two-way communication.

In large scale systems, managing which endpoint licenses need to be enabled or disabled can be time consuming. Revolution now allows you to run a daily check to automatically enable or disable endpoint licenses based on their use in notifications. This is an optional feature that must be enabled in Global Settings.

You can now configure a service URL with a background music stream. (The music stream must be provided by an external source.) Once the streaming source is active, phones can subscribe to the service and activate the background music by selecting the service button.

Revolution now can emulate a walky-talky, push-to-talk conference, on Cisco XML enabled IP phone endpoints. Push-to-talk notifications require multicast.

Revolution can now use JTAPI to determine if a Cisco phone is in a call. JTAPI Busy Detection is used when several phone lines are shared. Shared lines appear busy in the XML interface. Using JTAPI provides more accurate busy detection.

To support system resiliency, Revolution can now be configured to auto-deploy Cisco endpoints in the multicast sub-net, or a specific User Tag, to a Paging Relay. This keeps the Paging Relay device list up to date so that one-way notifications can be sent using Paging Relay if Revolution is unavailable.

The Revolution dashboard now uses push notifications to dynamically update dashboard content so you can see all notifications are being sent and what items are scheduled to occur in the near future.

We're moving Call Alert type functionality into Revolution. Now Cisco customers can monitor dialed phone numbers and trigger an alert when numbers matching your filter criteria are dialed from any phone on the network. Notifications include caller ID, date and time, along with text sent to designated personnel to help reduce response time in an emergency.

Revolution now will check if the notification's site setting matches the destination code that the user enters when dialing a dynamic notification and will not add endpoints that do have the correct site. See the Revolution Help for details.

You can now start a continuous notification from a panic button and end it with a phone call giving you the flexibility you need to create notifications that meet your day to day needs.

We've had lots of requests to reduce the continuous mode repeat interval to zero to allow notifications to loop without pausing.

You now get detailed status on what state a running notification is in so you can easily tell what is happening with your notifications.

Customers can now monitor system status by triggering a notification. Send notifications to support personel about service interruptions, license thresholds and expirations, and endpoint inactivity.

The Android mobile application now supports Chromebooks and Chromeboxes that have Google playstore enabled. Chromebook users can now register to receive notifications and can receive notifications even when remote.

You can now trigger notifications in Revolution based on receiving an SNMP trap from external hardware. Simple Network Management Protocol (SNMP) is an Internet-standard protocol for managing devices on IP networks. Devices that typically support SNMP include routers, switches, servers, workstations, printers, modem racks, and more.

IP Speakers now allow you to set a maximum, minimum and default volume for each speaker allowing you to tune your speaker volumes to the environment they are placed in. We have also added the ability to customize text scrolling speed for devices that support text scrolling.

A backup and restore tool is now available to make migrating servers easier. Refer to the user guide for details on usage.

We've made it easier to use and configure the application with the following enhancements:

• Optional custom login message
• Additional Tag column to distinguish standard vs dynamic tags
• Option to initially mute two-way notifications for privacy

Redundancy is now supported to provide high availability for your emergency alerts. Notifications can be set up to automatically fail over to a secondary server should the primary server by unreachable. Redundancy allows the application to maintain notification functionality during server fault scenarios. Please contact our sales team if you are interested in adding Redundancy to your system.

IP phone services now supported to allow you to browse and send notifications from Cisco, Mitel, Polycom and Avaya IP phones that support this functionality.

More details are now provided on notification status. Click on the pie chart in the notification status details to see a table which summarizes all of the endpoints, contacts, gateways, and Paging Relay broadcaster success and failure status.

All system actions are now logged for auditing purposes. You can view the date, time, action, and user account name for all actions done within the application.

Sending to Mitel SIP phones that support the XML API is now supported. Refer to the Mitel Notifier topic for a list of newly supported phone models.

Static streams can now show the endpoints that received audio and the timestamp for the start of audio packets from speakers that support RTCP responses. Please note that RTCP must be enabled and configured in the speaker in order to provide this information to the application.

There’s a new View History button on the Sent Notification Detail page. Customers can view the sent notification, along with any attached images, and can play attached audio. Note: Audio for Direct Two-Way notifications is not saved at this time. Notifications are saved for 7 days by default. This is configurable.

The DNC installer is now 32-bit, which runs in either 32-bit or 64-bit environments.

We now offer an API that allows third-party services to activate notifications in the application. We've also released a Basic Configuration API to streamline the configuration process for first-time users!

We've introduced a new feature that allows Polycom & Mitel Connect customers to monitor dialed phone numbers and trigger an alert when numbers matching your filter criteria are dialed from any phone on the network. Notifications include caller ID, date and time, along with text sent to designated personnel to help reduce response time in an emergency.

Our mobile geofence feature has been enhanced and now offers customers the ability to create multiple geofences. Automatically send your mobile recipients relevant information for their area by adding geofences to your notifications. Geofence Mapping has been moved to Areas in the Configuration menu.

You can create filter criteria to automatically assign new endpoints and contacts to a site when they are added to the application.

Now you can set up user accounts from Active Directory groups or CVS file import.

We've added bulk delete of IP devices and bulk license/unlicense for endpoints.

Extension reassignment for Mitel Connect is now supported.

We've made it easier to use and configure the application with many workflow improvements.

• Link to Help moved from submenu to header, next to date/time
• Save & Send button added to Notifications New/Edit page
• Send Again button added to Sent Notification Detail page
• Users now preview notifications before sending them
• Click on an endpoint or tag name to open the edit page
• Notifications with text and audio can loop text while audio is playing
• Added admin password reset tool

We've introduced a web portal where people external to the application can register their phone numbers, mobile devices, email addresses, and other off-site contact information using a token sent via email through the application.

With this release, we now have full support for sites. For single-site organizations, everything works the same. For multi-site organizations, you create sites and control which sites, triggers, endpoints, schedules, and notifications your users have access to.

Allow recipients of your notifications to send a response. In an emergency, you can know at a glance who is safely sheltered and who needs assistance.

You can now use SSL to communicate securely to Cisco phones.

Our application now conforms to the Web Content Accessibility Guidelines (WCAG) 2.0 AA.

Upload custom-designed, full-screen images and then assign them to notifications for use with all of your image capable phone endpoints.

You can now forward your Polycom group audio through our Syn-Apps Paging Relay.

You can now modify an individual event within a series to handle days when your schedule changes.

You can optionally send audio in your email notifications. Live audio is recorded and forwarded for users in remote locations, or for later playback.

Configure your Polycom phones to register with our application to receive text and image notifications. (Images supported on HTML capable Polycom phones.) Configure Polycom group paging to send audio to Polycom phones.

There's now a separate tab on the Sent Notification detail page for Contacts so you can see which contacts were recipients and which communication methods were used.

Add a descriptive custom name to endpoints so it's easier to identify them when assigning endpoints to notifications.

Adding a notification and looking for a trigger that isn't there? Create it on the fly. Simply select the type of trigger (Mobile, Scheduler, SIP, etc.) and then select new from the Trigger drop-down list.

AtlasIED & AND customers leveraging Syn-Apps' legacy IP speaker API can now receive text messages sent from the application. This is an extension to existing functionality, which allows users to broadcast audio to legacy IP speakers.

You can optionally allow users to include images from their mobile device and record content when sending a notification to our application from the Syn-Apps Mobile Client. Handy when a user needs to send a pic of a spill or building damage with the mobile notification.

You now can filter by Mitel sites and user groups when creating dyanmic tags or searching for endpoints to assign to notifications.