Document Control

Change Control

The document and its associated procedures, templates and diagrams are created and maintained by the Cirrus Document Owner. When a change must be made, the Cirrus Document Owner will record and agree the change and a note will inform all in the distribution list that a change has occurred. The Cirrus Document Owner will periodically update this document to reflect agreed changes.

The issue level of this document is indicated by a 2-part issue number consisting of a major issue number and a minor revision number (m.n). Major revisions to the document are identified by a minor revision number zero (1.0, 2.0, etc.).  Draft issues are indicated by an alphabetic revision level (e.g., 0a, 0b, etc. or 1.0a, 1.0b etc. or 1.1a, 1.1b etc.).  The alphabetic revision level reflects the progress of the document through draft stages.  Once a draft revision has been reviewed and approved for issue at a minor or major revision level, the document is created at that revision level and approvals recorded.

Amendment Record

Cirrus Pre-Requisites Purpose

Document Purpose

The purpose of the Pre-Requisites document is to confirm the recommended specification and configuration of the customers environment for Cirrus Connect to operate smoothly within the live environment. 

Customer Instructions

The Cirrus Solution Delivery Consultant and / or Project Manager will arrange a call to go through the document and ensure that all items have been understood and will be implemented as part of the Cirrus deployment. We will also request that the document is updated with screen shots to confirm that the required changes have been met. (We also store these for our third line teams and our ISO audits for due diligence on client interaction.)

Workstation Requirements

The below details the minimum specifications and versions required for a Desktop running Cirrus application.

Computer / Processor

• Computer with a 1.8 gigahertz (GHz) 32-bit (x86) or 64-bit (x64) processor
• Dual core > 2.5 GHz
• 4GB RAM
• Hard disk (Available space > 500 MB)
• Video 1280 x 720 minimum (1650 x 1050 or better recommended)
• Input Devices Mouse and standard keyboard
• Network cards 100Mbps, full duplex

Operating System

• Windows 10 32-bit or higher
• Windows 10 64-bit or higher
• Windows 11 32-bit or higher
• Windows 11 64-bit or higher

Software

• Google Chrome
• Microsoft Edge
• .NET Framework 4.7.2
• Microsoft Visual C++ 2015 Redistributable (x64)
• Network cards - At least one, Ethernet or Fiber, 1 Gbps or up, full duplex 
• Microsoft .NET Framework 4.7.2 
• Vcredist_x64.exe (MSVisual C++ 2013 Redistributable)

Memory

• Windows 10 – 32-bit – 512 MB (Minimum)
• Windows 10 – 64-bit – 512 MB (Minimum)

Hard Disk Space

• Windows 10 - 32-bit – 4.5 GB
• Windows 10 - 64-bit – 4.5 GB

*Business grade headset for our application will be required* 

*All clients can be used under Citrix (no softphone supported under Citrix) *

Sound Settings

To ensure continued performance, the headset’s microphone and speakers must be the only default device in use so that no other program can change settings throughout the day, such as YouTube, Skype, News Streaming Channels, BBC iPlayer etc, please ensure that the microphone does not allow third party applications to take exclusive control of the device, and that any soundcards or devices that have an Enhancements tab, should have this feature disabled. We recommend Epos and Jabra headsets. These features can be found in the advanced settings tab of the microphone and speaker’s properties (example below)

Bandwidth Requirements

Wi-Fi connectivity can be unreliable as the number of variables may affect the stability and quality of the voice traffic. Our recommendation is all Desktops running Cirrus be connected through structured cabling into your LAN. 

Bandwidth requirements

• WebRTC using G711 per call + HTTPS (40-200kbps & 100kbps)
• Typical wallboard 100Kbps - per wallboard

Web Connectivity Requirements

Cirrus Network IP's

IP Breakdown

The Cirrus network is hosted within Microsoft Azure, under “London South”. 

The below IP address ranges need to be added onto your firewall depending on the method of call handling, and certain ports need to be opened depending on firewall restrictions (see grids below for ports).

20.26.109.144/28

20.77.162.144/28

• WebRTC is applicable to customers using our WebRTC services only.
• HTTP/(S)FTP is only applicable to customers who use Cirrus services which send data from the network, such as HTTP requests nodes, scheduled (S)FTP reports or Multimedia integrations etc, which may be restricted on your firewall. 

Port Usage Server

Target Machine indicates that this machine(s) is listening on the defined port.

All are inbound and outbound.

Port Usage Client

When used in combination with a Cirrusconnects tenant on the local network or via VPN, the clients allocate free ports only. 

All are inbound and outbound.

The following ports are allocated on the target machine:

In combination with a hosted Cirrusconnects tenant on the internet, a proxy is used, and the above ports are allocated on the Cirrusconnects tenant.

When using the integrated softphone in addition following ports are used:

Email Server Requirements

Calendar Server Integration

Note that for Exchange connection an account (username/password) is required. For Office 365 the administrator needs to give consent to the application to have full mailbox access.

Customer Acknowledgement

This Pre-Requisites Document defines the customer dependencies for a successful installation of Cirrus Services, a failure on the customer’s part to meet any of these pre-requisites may result in project delivery delays and could impact desired go live dates.

Click here to download PDF