Cisco Server Requirements
This provides information for all Cisco server requirements.
Format
Downloadable setup file
Listening Network Ports
80, 443, 8443, 9443 (SSL nginx proxy)
Database
BlueDB
Web Server
Apache Tomcat
User Interface
Web Interface and Chronicall Desktop Application
Server Requirements
- Windows 10 or higher, Windows Server 2016 and higher, 32/64 bit Linux
- 250 GB Hard Drive (Minimum)
- 4 GB RAM (Minimum, see below for recommended RAM based on call volume.)
- Quad Core CPU
RAM Requirements
- Increase Memory by 2 GB for every 10,000 Calls a Day
Example: 10,000 Calls a Day = 6GB of RAM
- 20,000 Calls a Day = 8GB of RAM
- 30,000 Calls a Day = 10GB of RAM
- 50,000 Calls a Day = 14GB of RAM
Cisco Call Manager
Release 7, 8, 9, 10, 11, 12, and 6k
Cisco Call Manager Connection
CDR
Unity Monitoring
Monitor Output
Virtual Machine Support
Yes
User Computer Requirements (Web Interface)
- Any computer with a modern browser
- 1280 x 720 or higher screen resolution
User Computer Requirements (ACR Desktop)
- Windows 7+ (64 bit)
- Mac OS X 10.7.3+ (Intel-based)
Server Requirements for Linux
The following metrics and specifications assume the server is dedicated to hosting Chronicall and that no other resource-intensive software is running. Virus and security scanning software should be configured to not actively scan the Chronicall database; otherwise disk IOPS requirements will be higher than what is listed.
Baseline Server Requirements
| System Type | Architecture | CPU Speed | Network Requirements |
|---|---|---|---|
| Server Linux* (CentOS 7+ or Ubuntu 14+) | 64-bit | 2+ GHz | reliable, low-latency |
*Other Linux distributions may work, but Chronicall/ACR is only validated on CentOS and Ubuntu.
Storing Required CDR Fields Only
| Reporting Users | 1-250 | 251-1000 | 1001-2000 | 2001-3000 | 3001-4000 | 4001-5000 | 5001-6000 | 6001-7000 |
| System Specs | ||||||||
| Physical Server RAM (GB) | 2 | 3 | 4 | 5 | 6 | 7 | 9 | 11 |
| Configured Java Heap Max Size (GB) | 0.5 | 1 | 1.5 | 2 | 2.5 | 3 | 4 | 5 |
| Total CPU Cores | 1 | 2 | 2 | 3 | 4 | 4 | 6 | 8 |
| Disk Size (GB)** [can last for about three years] | 3.5 | 8.75 | 16.25 | 27.5 | 41.25 | 57.5 | 76.25 | 95 |
| Disk IOPS Write | 68.75 | 77.5 | 87.5 | 125 | 175 | 212.5 | 250 | 375 |
| Disk IOPS Read | 1.25 | 50 | 57.5 | 65 | 87.5 | 125 | 187.5 | 250 |
| Total Minimum IOPS | 70 | 127.5 | 145 | 190 | 262.5 | 337.5 | 437.5 | 625 |
| Disk IOPS Write Burst*** | 75 | 85 | 100 | 140 | 195 | 238 | 288 | 425 |
| Disk IOPS Read Burst*** | 375 | 625 | 1,125 | 1,625 | 2,125 | 2,625 | 3,125 | 3,625 |
| Total Recommended IOPS (to support burst operations without degradation of performance) | 450 | 710 | 1,225 | 1,765 | 2,320 | 2,863 | 3,413 | 4,050 |
*The listed disk size is a starting point only. Over time more disk space will be needed. Please see "Additional Database Storage."
**Burst IOPS refers to the total disk operations required when using disk-intensive functionality (e.g., running reports and loading Realtime wallboards).
Storing All CDR Fields
| Reporting Users | 1-250 | 251-1000 | 1001-2000 | 2001-3000 | 3001-4000 | 4001-5000 | 5001-6000 | 6001-7000 |
| System Specs | ||||||||
| Physical Server RAM (GB) | 2 | 3 | 4 | 5 | 6 | 7 | 9 | 11 |
| Configured Java Heap Max Size (GB) | 0.5 | 1 | 1.5 | 2 | 2.5 | 3 | 4 | 5 |
| Total CPU Cores | 1 | 2 | 2 | 3 | 4 | 4 | 6 | 8 |
| Disk Size (GB)* [can last for about three years] | 28 | 70 | 130 | 220 | 330 | 460 | 610 | 760 |
| Disk IOPS Write | 550 | 620 | 700 | 1000 | 1400 | 1700 | 2000 | 3000 |
| Disk IOPS Read | 10 | 400 | 460 | 520 | 700 | 1000 | 1500 | 2000 |
| Total Minimum IOPS | 560 | 1020 | 1160 | 1520 | 2100 | 2700 | 3500 | 5000 |
| Disk IOPS Write Burst** | 600 | 680 | 800 | 1,120 | 1,560 | 1,900 | 2,300 | 3,400 |
| Disk IOPS Read Burst** | 3,000 | 5,000 | 9,000 | 13,000 | 17,000 | 21,000 | 25,000 | 29,000 |
| Total Recommended IOPS (to support burst operations without degradation of performance) | 3,600 | 5,680 | 9,800 | 14,120 | 18,560 | 22,900 | 27,300 | 32,400 |
*The listed disk size is a starting point only. Over time more disk space will be needed. Please see "Additional Database Storage."
**Burst IOPS refers to the total disk operations required when using disk-intensive functionality (e.g., running reports and loading Realtime wallboards).
Server Requirements for Windows
The following metrics and specifications assume the server is dedicated to hosting Chronicall and that no other resource-intensive software is running. Virus and security scanning software should be configured to not actively scan the Chronicall database, otherwise disk IOPS requirements will be higher than what is listed.
Baseline Server Requirements
| System Type | Architecture | CPU Speed | Network Requirements |
|---|---|---|---|
| Windows* 7+ or Server 2008+ | 64-bit | 2+ GHz | reliable, low-latency |
*Must be a genuine copy of Windows and activated by Microsoft
Storing Required CDR Fields Only
| Reporting Users | 1-250 | 251-1000 | 1001-2000 | 2001-3000 | 3001-4000 | 4001-5000 | 5001-6000 | 6001-7000 |
| System Specs | ||||||||
| Physical Server RAM (GB) | 3 | 4 | 5 | 6 | 7 | 8 | 10 | 12 |
| Configured Java Heap Max Size (GB) | 0.5 | 1 | 1.5 | 2 | 2.5 | 3 | 4 | 5 |
| Total CPU Cores | 1 | 2 | 2 | 4 | 4 | 6 | 8 | 10 |
| Disk Size (GB)* [can last for about three years] | 3.5 | 8.75 | 16.25 | 27.5 | 41.25 | 57.5 | 76.25 | 95 |
| Disk IOPS Write | 300 | 375 | 425 | 525 | 625 | 800 | 1050 | 1500 |
| Disk IOPS Read | 12.5 | 50 | 57.5 | 65 | 87.5 | 125 | 187.5 | 250 |
| Total Minimum IOPS | 312.5 | 425 | 482.5 | 590 | 712.5 | 925 | 1237.5 | 1750 |
| Disk IOPS Write Burst** | 325 | 413 | 475 | 588 | 700 | 900 | 1,175 | 1,675 |
| Disk IOPS Read Burst** | 500 | 750 | 1,250 | 1,750 | 2,250 | 2,750 | 3,250 | 3,750 |
| Total Recommended IOPS (to support burst operations without degradation of performance) | 825 | 1,163 | 1,725 | 2,338 | 2,950 | 3,650 | 4,425 | 5,425 |
*The listed disk size is a starting point only. Over time more disk space will be needed. Please see "Additional Database Storage."
**Burst IOPS refers to the total disk operations required when using disk-intensive functionality (e.g., running reports and loading Realtime wallboards).
Storing All CDR Fields
| Reporting Users | 1-250 | 251-1000 | 1001-2000 | 2001-3000 | 3001-4000 | 4001-5000 | 5001-6000 | 6001-7000 |
| System Specs | ||||||||
| Physical Server RAM (GB) | 3 | 4 | 5 | 6 | 7 | 8 | 10 | 12 |
| Configured Java Heap Max Size (GB) | 0.5 | 1 | 1.5 | 2 | 2.5 | 3 | 4 | 5 |
| Total CPU Cores | 1 | 2 | 2 | 4 | 4 | 6 | 8 | 10 |
| Disk Size (GB)* [can last for about three years] | 28 | 70 | 130 | 220 | 330 | 460 | 610 | 760 |
| Disk IOPS Write | 2400 | 3000 | 3400 | 4200 | 5000 | 6400 | 8400 | 12000 |
| Disk IOPS Read | 100 | 400 | 460 | 520 | 700 | 1000 | 1500 | 2000 |
| Total Minimum IOPS | 2500 | 3400 | 3860 | 4720 | 5700 | 7400 | 9900 | 14000 |
| Disk IOPS Write Burst** | 2,600 | 3,300 | 3,800 | 4,700 | 5,600 | 7,200 | 9,400 | 13,400 |
| Disk IOPS Read Burst** | 4,000 | 6,000 | 10,000 | 14,000 | 18,000 | 22,000 | 26,000 | 30,000 |
| Total Recommended IOPS (to support burst operations without degradation of performance) | 6,600 | 9,300 | 13,800 | 18,700 | 23,600 | 29,200 | 35,400 | 43,400 |
*The listed disk size is a starting point only. Over time more disk space will be needed. Please see "Additional Database Storage."
**Burst IOPS refers to the total disk operations required when using disk-intensive functionality (e.g., running reports and loading Realtime wallboards).
Additional Database Storage
Required CDR Fields Only
Number of years to fill additional database storage (assumes six calls per hour, eight hours per working day)
| Additional Database Storage | 100 Users | 500 Users | 1,000 Users | 2,000 Users |
|---|---|---|---|---|
| 10 GB | 10 | 2 | 1 | 0.5 |
| 100 GB | 100 | 20 | 10 | 5 |
| 500 GB | 500 | 100 | 50 | 25 |
| 1,000 GB | 1,000 | 200 | 100 | 50 |
All CDR Fields
Number of years to fill additional database storage (assumes six calls per hour, eight hours per working day)
| Additional Database Storage | 100 Users | 500 Users | 1,000 Users | 2,000 Users |
|---|---|---|---|---|
| 80 GB | 10 | 2 | 1 | 0.5 |
| 800 GB | 100 | 20 | 10 | 5 |
| 4,000 GB | 500 | 100 | 50 | 25 |
| 8,000 GB | 1,000 | 200 | 100 | 50 |
Updated almost 3 years ago