System Installation Requirements

Here are the minimum system and network requirements necessary to run Revolution.

  • Microsoft Windows Servers 2016, 2019, and 2022 are supported. You must have a fully licensed installation.

    If you are using the evaluation license after Installing Revolution on a Virtual Appliance, you must upgrade the license before it expires, see Upgrade to a production license after eval period.

    Note: After installing and configuring Revolution, if you need to upgrade Microsoft Windows Server you should contact Revolution Support before beginning the upgrade process to discuss a project plan. See Contacting Support.

    We recommend the following when joining the Windows Server to a domain or installing secondary software such as antivirus software:

    • Wait until after the Revolution software has been configured and tested before joining the server or installing secondary software.
    • Backup the OS prior to joining the server or installing secondary software.
    • We recommend you install Revolution on its own server. Specifically, do not install Revolution on mission-critical systems, such as those containing a domain controller, Exchange server, or PBX server. If you install Revolution on a server where other programs reside, there may be port, IIS, security policy, or SQL configuration conflicts.
  • Minimum server requirements are:
    • 8 gigabytes system memory for Windows 2016 and above.
    • 10 gigabytes disk space above any OS requirements
    • 2-core processor

      • Note: Environments that need to send to a large number of endpoints at the same time may require a server with more memory and CPU cores. Please consult your technical support for more information on setting up a large-scale deployment.

      Important: Make sure your Windows server is current on updates before you install the product.

  • VMware ESXi 7.0 or newer and VMware Workstation 10 or newer are supported. Microsoft Hyper V 2016 on a host Windows 2016, 2019, 2022 server are supported.

    • Note: A VM requires a static MAC configured on the network cards. Please see Microsoft and VMware for configuration procedures.

  • SIP-compliant phones – A list of supported phones is provided in the configuration topic for your specific phone system.

Multicast can significantly reduce network traffic when sending audio with notifications.

Important:
  • If you are keeping more than 200 endpoints licensed for use with Revolution, it is highly recommended that your network use multicast instead of unicast transmission.
  • Multicast is required if you're using Honeywell X-618 speakers or Poly phones.

Multicast can be configured on your network (consult your network administrator) or you can use a Paging Relay to convert unicast to multicast (refer to the Paging Relay topic).

You should specify these ports only if you want to use the online installer or any of the following services: mobile, self-service portal, mass dialing, SMS and/or receive public alerting system messages. If you don't require these services, then Revolution does not require any Internet access.

Outbound ports to the Internet for the Online installer

Port Direction Server Protocol Description
443 Outbound saa-license-api.syn-apps.com HTTPS For online installation. Connects to the Syn-Apps server.

Outbound ports to the internet for Mobile, CloudConnect, and Self-Service Portals

Port Direction Server Protocol Description
3478 Outbound Public STUN Server Name TCP If you use SIP Session Traversal Utilities for NAT

The CloudConnect plugin is responsible for notification responses, mobile registrations and authentication, the sent notification view for mobile devices, geo-fencing, and stop actions and triggers for mobile devices. You can view the status of the plugin in the System Status page.

Outbound ports to the internet for Mass Dialer and SMS

Port Direction Server Protocol Description
443 Outbound api.twilio.com HTTPS If you use Twilio Mass Dialing/SMS
443 Outbound api.clickatel.com HTTPS If you use Clickatell SMS
443 Outbound api.us1.corvisa.io HTTPS If you use Mitel SMS
443 Outbound sannouncetwilio.cloudapp.net HTTPS If you use Mass Dial and SMS
443 Outbound stsmscallback.azurewebsites.net HTTPS If you use Mitel SMS
8443 Outbound mitel.syn-apps.com HTTPS If you use external media and email invitations for Mitel

Outbound ports to the internet for Public Alerts

Port Direction Server Protocol Description
443 Outbound amberalert.syn-apps.com HTTPS Amber Alerts
443 Outbound apps.fema.gov HTTPS IPAWS Alerts
443 Outbound alerts.weather.gov HTTPS National Weather Service Alerts
443 Outbound m.syn-apps.com HTTPS Updating FIPS.db file for CAP county and zone codes.

You should specify these ports for the specific features you are using.  Outbound port requirements are not listed in the table because they are typically open for traffic on your local internal network.

Port Direction Protocol Description
5060 Inbound TCP and UDP SIP protocol for call connections
80 Inbound HTTP IP Device Registration
162 Inbound UDP SNMP Trap
8008 Inbound HTTP Cisco Phone Authentication
8127 Inbound TCP Mitel Connect Dial Monitoring
8443 Inbound HTTPS Cisco Phone Authentication
4443 Inbound HTTPS DNC Registration
443 Inbound HTTPS User interface, and image and audio media
1433 Inbound TCP MS SQL for redundancy connection
1434 Inbound UDP MS SQL for redundancy connection
16384-32768 Inbound UDP RTP Audio
12000-12099 Inbound UDP RTP Audio

It is assumed that outbound ports to the local internal network are open by default.

netsh advfirewall firewall add rule protocol = TCP localport = 5060 name = SynApps_SIPTCP dir=in action=allow
netsh advfirewall firewall add rule protocol = UDP localport = 5060 name = SynApps_SIPUDP dir=in action=allow
netsh advfirewall firewall add rule protocol = TCP localport = 8008 name = SynApps_CUCMAuth dir=in action=allow
netsh advfirewall firewall add rule protocol = TCP localport = 8127  name = SynApps_MiDial dir=in action=allow
netsh advfirewall firewall add rule protocol = TCP localport = 8443 name = SynApps_SSLTCP dir=in action=allow
netsh advfirewall firewall add rule protocol = TCP localport = 4443 name = SynApps_DNCTCP dir=in action=allow
netsh advfirewall firewall add rule protocol = TCP localport = 443 name = SynApps_HTTPSTCP dir=in action=allow
netsh advfirewall firewall add rule protocol = TCP localport = 80 name = SynApps_HTTPTCP dir=in action=allow
netsh advfirewall firewall add rule protocol = UDP localport = 162 name = SynApps_SNMPUDP dir=in action=allow
netsh advfirewall firewall add rule protocol = TCP localport = 1433 name = SynApps_SQLTCP dir=in action=allow
netsh advfirewall firewall add rule protocol = UDP localport = 1434 name = SynApps_SQLUDP dir=in action=allow
netsh advfirewall firewall add rule protocol = UDP localport = 16384-32767 name="SynApps_RTP" dir=in action=allow
netsh advfirewall firewall add rule protocol = UDP localport = 12000-12099 name="SynApps_SIPRTP" dir=in action=allow
netsh advfirewall firewall add rule protocol = UDP localport = 1434 name = SynApps_SQLTCP2 dir=in action=allow
netsh advfirewall firewall add rule name="SQLDYN" dir=in action=allow program="%ProgramFiles%\Microsoft SQL Server\MSSQL19.SYNAPPS\MSSQL\Binn\sqlservr.exe" enable=yes
netsh advfirewall set allprofiles firewallpolicy blockinbound,allowoutbound
#The above command allows all outbound traffic from the Revolution server

Important: The database schema for Revolution is not public and Intrado does not support direct access to the database by customers. The only supported method is through the use of the Published APIs. See Revolution API

  • Microsoft .NET 4.5.2 or newer – The installer checks for the appropriate .NET version and automatically installs it if necessary.
  • Microsoft SQL Server 2019 Express – The installer checks for its presence and automatically installs it if necessary.
    • TCP Port 1433 is the default SQL port.

      • Note: If you use a different port, be sure to open your firewall for it. If you're setting up your environment for redundancy, be sure to open your firewall to the SQL port.

    • TCP/IP must be enabled.
    • You must be using Windows & SQL authentication.
  • Microsoft IIS is installed if it is not already present.
    • Notes:
    • Windows server 2016 has .NET 4.6 installed as a Feature that is already enabled. No .NET installation is required by the installer.
    • Windows server 2019 has .NET 4.7 installed as a Feature that is already enabled. No .NET installation is required by the installer.

IP devices and the Desktop Notification Client (DNC) automatically register with Revolution through DHCP option 72. Configure your DHCP server with the Revolution IP address. Once your IP device is plugged into your network, or the DNC is installed on your desktop, it requests an IP address from a DHCP server. DHCP works by sending the client at minimum an IP address and a subnet mask value when a DHCP request is made. Additional information can be sent to IP devices such as speakers if you have various DHCP options configured. Refer to your DHCP documentation.

If you do not have the ability to add option 72 to the DHCP server, or you don't have a DHCP server, IP devices and DNC apps must be manually configured with the Revolution IP address so they can register.

  • G.711 audio codec is supported.

  • Google Chrome 55.x and newer (recommended browser)

The following browsers should also work, but have not been fully tested:

  • Mozilla Firefox 50.x and newer
  • Safari 10.x and newer
  • Microsoft Edge for Windows 2016 and newer

To access localization of the Revolution interface, adjust the language or localization settings of your browser.