Information contained in this document is believed to be accurate and reliable at the time
of printing. However, due to ongoing product improvements and revisions, AudioCodes
cannot guarantee accuracy of printed material after the Date Published nor can it accept
responsibility for errors or omissions. Updates to this document can be downloaded from
This document is subject to change without notice.
Date Published: February-04-2021
WEEE EU Directive
Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed of
with unsorted waste. Please contact your local recycling authority for disposal of this product.
Customer Support
Customer technical support and services are provided by AudioCodes or by an authorized
AudioCodes Service Partner. For more information on how to buy technical support for
AudioCodes products and forcontact information, pleasevisit our websiteat
AudioCodes continually strives to produce high quality documentation. If you have any
comments (suggestions or errors) regarding this document, please fill out the Documentation
Feedback form on our website at https://online.audiocodes.com/documentation-feedback.
Stay in the Loop with AudioCodes
Related Documentation
Document Name
Mediant 500 MSBR User's Manual
Mediant 500L MSBR User's Manual
Mediant 500L Gateway and E-SBC User's Manual
- ii -
Notice
OVOC | IOM
Document Name
Mediant 800B Gateway and E-SBC User’s Manual
Mediant 800B MSBR User’s Manual
Mediant 1000B Gateway and E-SBC User’s Manual
Mediant 1000B MSBR User’s Manual
Mediant 2600 E-SBC User's Manual
Mediant 3000 User’s Manual
Mediant 4000 SBC User's Manual
Mediant 9000 SBC User's Manual
Mediant Software SBC User's Manual
Migration from EMS and SEM Ver. 7.2 to One Voice Operations Center
One Voice Operations Center IOM Manual
One Voice Operations Center Product Description
One Voice Operations Center User’s Manual
Device Manager Pro Administrator's Manual
One Voice Operations Center Alarms Monitoring Guide
One Voice Operations Center Performance Monitoring Guide
One Voice Operations Center Security Guidelines
One Voice Operations Center Integration with Northbound Interfaces
Device Manager for Third-Party Vendor Products Administrator's Manual
Device Manager Agent Installation and Configuration Guide
ARM User’s Manual
- iii -
Notice
OVOC | IOM
Document Revision Record
LTRTDescription
94172Updated Sections: Managed VoIP Equipment; OVOC Server Requirements;
Installing OVOCon Dedicated Hardware; Upgrading OVOC Server on
Dedicated Hardware; OVOC Server Restore; OVOCServer Platform; Viewing
Process Statuses; Deploying OVOC Image with VMware vSphere Hypervisor
(ESXi); Supplementary Security Procedures; Internet Explorer; Configuring
OVOC as the Email Server on Microsoft Azure
New Sections: Connecting Mediant Cloud Edition (CE) SBC Devices in Azure
Deployment; Configuration Restore; Full Restore; OVOC Cloud Architecture;
Configuring Firewall for Cloud Architecture; Cassandra Password; Virtual
Appliance and Cloud Options
Removed Section:Disable Statistical Report Web page Secured
Communication
94173Updated Sections:OVOC Server Requirements; Performance and Data
Storage; OVOC Software Deliverables; Starting and stopping Web servers;
Viewing Process Statuses; Viewing General Information; Application
Maintenance; License; HTTP Security Settings; Configuring the Firewall;
Firewall Configuration Schema; OVOCServer Users; Step 2:Configuring the
OVOCServer (OVOC Server Manager) on Azure Cloud; Upgrade procedures
for DVDand ISOfile on Dedicated machine; Upgrade procedure for Virtual
machine; Configuring RAID-0; NTPand Clock Settings
Added Sections:Analytics API; Upgrading the OVOCServer on Cloud
Platforms
94174Correction to the OVOC Server Requirements table
94175Added Sections: Configuring the Virtual Machine on AWS; Configuring the
OVOC Server on AWS; Configuring Mediant Cloud Edition (CE) Devices on
AWS; Deploying Devices Behind a NAT; Configuring Firewall for NAT
Deployment
Updated Sections: NTP; NAT (Configuring OVOC Server with Public IP Address);
Installing OVOCServer on Cloud-based platforms; Upgrading the OVOC
Server on Amazon AWS and Microsoft Azure (removed step for OVOC
IPaddress configuration); Upgrading OVOC Server on VMware and Microsoft
Hyper-V Virtual Machines (removed step for OVOC IPaddress configuration);
Configuring RAID-0 (divided into two procedures)
94176Added Sections:Specifications for Service Provider Cluster Mode; Service
Provider Cluster Mode; Viewing Process Statuses in Service Provider Cluster
Mode; Viewing General Information in Service Provider Cluster Mode;
Configuring Firewall for Service Provider Cluster Mode; Deploying OVOC
- iv -
Notice
OVOC | IOM
LTRTDescription
Image with VMware vSphere Hypervisor (ESXi) in Service Provider Cluster; ;
Step 2-1 Run the VQM Server Upgrade Script; Step 2-2 Run the PM Server
Upgrade Script; Configuring AWS SES Service; Self-signed certificates
(Microsoft Edge); Start and Restart in Service Provider Cluster Mode
Updated Sections:Managing VoIPEquipment; OVOC Server Requirements;
Standard Capacities; OVOC Software Deliverables; Launching Public OVOC
Image on Amazon Web Services (AWS); DVD2: Oracle DB Installation; DVD3:
OVOC Server Application Installation; Installing OVOCon VMware Version 6.5;
Deploying OVOC Image with VMware vSphere Hypervisor (ESXi); Connecting
OVOC Server to Network on VMware; Upgrading OVOC Server on Amazon
AWS and Microsoft Azure; Upgrading OVOC Server on VMware and Microsoft
Hyper-V Virtual Machines; Connecting to OVOC Server on VMware; Step 2:
Run the OVOC Server (Management Server) Upgrade Script; Upgrading the
OVOC Server-DVD; Upgrading the OVOC Server using an ISO File; OVOC
Server Backup Processes; Full Restore; 19 Viewing Process Statuses; Viewing
General Information; Collecting Logs; Server IP Address; OVOC Voice Quality
Package SBC Communication Server Manager option text updated from SEMAudioCodes Device Communication
94177Added Section:Connecting Mediant Cloud (CE) Devices to OVOC with Internal
IP
Updated Section:Specifications for Service Provider Cluster Mode; OVOC
Software Deliverables; Deploying OVOC Image with VMware vSphere
Hypervisor (ESXi) in Service Provider Cluster; Configuring OVOC Cloud
Architecture mode; Specifications for Service Provider Cluster mode;
Configuring Mediant CE Communication Settings Using Web Interface (AWS);
Creating OVOC Virtual Machine on Azure; Configuring Mediant CE OVOC
Public IP Connection Settings using Web Interface; OVOC Server Backup
Processes; OVOC Server Restore
Step 6: Reset Device to Apply the New Configuration282
- xi -
Content
OVOC | IOM
Cleaning up Temporary Files on OVOC Server282
31 Transferring Files283
32 Verifying and Converting Certificates284
33 Self-Signed Certificates285
Mozilla Firefox285
Google Chrome285
Microsoft Edge286
34 Datacenter Disaster Recovery287
Introduction287
Solution Description287
Initial Requirements288
New Customer Configuration288
Data Synchronization Process288
Recovery Process289
- xii -
Content
OVOC | IOM
This page is intentionally left blank.
- xiii -
CHAPTER1 Overview
1Overview
The One Voice Operations Center (OVOC) provides customers with the capability to easily and
rapidly provision, deploy and manage AudioCodes devices and endpoints. Provisioning,
deploying and managing these devices and endpoints with the OVOC are performed from a
user-friendly Web Graphic User Interface (GUI). This document describes the installation of the
OVOC server and its components. It is intended for anyone responsible for installing and
maintaining AudioCodes’ OVOC server and the OVOC server database.
OVOC | IOM
- 1 -
PartI
Pre-installation Information
This part describes the OVOC server components, requirements and deliverables.
CHAPTER2 Managed VoIP Equipment
2Managed VoIP Equipment
The following products (and product versions) can be managed by this OVOC release:
Table 2-1:Managed VoIP Equipment
ProductSupported Software Version
Gateway, SBC and MSBR Devices
OVOC | IOM
Mediant 9000 SBC
Mediant4000 SBC
Mediant4000B SBC
Mediant 2600 E-SBC
Mediant 2600B E-SBC
Mediant Software (Server Edition) SBC
Mediant Software(Virtual Edition) SBC
Mediant3000 (TP-8410 and TP-6310)Versions 7.0 and 6.6
Mediant Cloud Edition
Mediant 2000 Media GatewaysVersion 6.6
Versions 7.4, 7.2 (including
support for MTC ), 7.0, 6.8
Versions 7.4, 7.2, 7.0 and 6.8
Version 7.4, 7.2, 7.0
Versions 7.4, 7.2, 7.0 and 6.8
Version 7.4, 7.2 and 7.0
Versions 7.4, 7.2, 7.0 and 6.8
Versions 7.4, 7.2 (including
support for MTC), 7.0 and 6.8
Version 7.4, 7.2
1
Mediant 1000 GatewayVersion 6.6 (SIP)
Mediant 1000B Gateway and E-SBC
Mediant 800BGateway and E-SBC
Mediant 800C
Mediant 1000B MSBRVersion 6.6
Mediant800 MSBRVersions 7.2, 6.8 and 6.6
Mediant500 MSBRVersion 7.2 and 6.8
1
This product does not support Voice Quality Management.
- 3 -
Versions 7.4, 7.2, 7.0, 6.8 and
6.6
Versions 7.4, 7.2, 7.0, 6.8 and
6.6
Version 7.4, 7.2
CHAPTER2 Managed VoIP Equipment
Mediant 500L MSBRVersions 7.2 and 6.8
OVOC | IOM
ProductSupported Software Version
Mediant 500Li MSBR
Mediant 500 E-SBC
Mediant 500L E-SBC
1
Mediant 600Version 6.6
Version 7.2, 7.20AN.4xx
Version 7.4, 7.2
Version 7.4, 7.2
MediaPack MP-11x seriesVersion 6.6 (SIP)
MediaPack MP-124Rev. D and E – version 6.6 (SIP)
MP-202Version 4.4.9 Rev. B, D and R
MP-204Version 4.4.9 Rev. B, D and R
MP-1288
2
SBA
Version 7.4, 7.2
Mediant 800B SBA Skype for BusinessSBA version 1.1.12.x and later
and gateway Version 7.2
Mediant 800C SBA Skype for BusinessSBA version 1.1.12.x and later
and gateway Version 7.2
Mediant 1000BSBA Skype for BusinessSBA version 1.1.12.x and later
and gateway Version 7.2
Mediant 2600B SBA Skype for BusinessSBA version 1.1.12.x and later
and gateway Version 7.0
Mediant800B SBA Lync ServerSBA version 1.1.12.x and later
and gateway Version 6.8
Mediant 1000B SBA Lync ServerSBA version 1.1.12.x and later
and gateway Version 6.8
Mediant 2000B SBA devices Lync ServerSBA version 1.1.12.x and later
and gateway Version 6.8
1
As above
2
As above
- 4 -
CHAPTER2 Managed VoIP Equipment
OVOC | IOM
ProductSupported Software Version
CloudBond
1
CloudBond 365 Pro EditionVersion 7.6 with
MediantServer version 7.2.100
and later
CloudBond 365 Enterprise EditionVersion 7.6 with
MediantServer version 7.2.100
and later
CloudBond 365 Standard+ EditionVersion 7.6 with
Mediant800BMediant 800CGX800C version 7.2.100 and later
CloudBond 365 Standard EditionVersion 7.6 with Mediant 800B
version 7.2.100 and later
User Management Pack 365 ENTVersion 8.0.0
User Management Pack 365Version 7.8
CloudBond 365Version 8.0.0 (Skype for
Business 2019 and Microsoft
Teams)
User Management Pack 365 SPVersion 8.0.0
CCE Appliance
2
Mediant 800 CCE ApplianceVersion 2.1 with Mediant 800B
Mediant Server CCE ApplianceVersion 2.1 with Mediant
Server
Other Applications
SmartTAP360○Recording
Version 4.3, Version 5.0,
Version 5.1
IP Phones
Supported Software
Versions/Models
1
To support Voice Quality Management for these devices, customers must add the SBC/Media
Gateway platform of these products as standalone devices to OVOC. Once this is done, the
SBC/Gateway calls passing through the CloudBond 365 /CCE Appliances can be monitored.
2
As above.
- 5 -
CHAPTER2 Managed VoIP Equipment
Skype for BusinessFrom Version 3.0.0: 420HD,
OVOC | IOM
ProductSupported Software Version
430HD 440HD and 405HD
From Version 3.0.1: 420HD,
430HD 440HD, 405HD and
450HD
From Version 3.0.2: HRS 457
(with Jabra firmware support)
Native Teams
Third-party Vendor Devices
Spectralink
From
Version 3.1.0
: 445HD,
430HD 440HD, 405HD, 450HD
and HRSFrom
From Version 3.2.0: C450HD
From Version 3.2.1: C450HD,
445HD, 430HD 440HD,
405HD,450HD and HRS
From Version 3.4.2: RX50 Con-
ference Device
1
From Version 1.5: C448HD,
C450HD
From Version 1.8:C470HD
(including Android support)
Spectralink 8440
Polycom
Jabra Headset Support
1
This device is not yet supported
Polycom Trio 8800
Polycom VVX 410
Jabra BIZ, Jabra Coach, Jabra
DIAL, Jabra Eclipse, Jabra Elite,
Jabra Engage, Jabra Evolve,
Jabra Handset, Jabra LINK, Jabra
Motion, Jabra Pro, Jabra Pulse,
Jabra SPEAK, Jabra Sport, Jabra
STEALTH, Jabra Steel, Jabra
SUPREME. For a complete list of
supported Jabra phones, see
- 6 -
CHAPTER2 Managed VoIP Equipment
●All versions VoIP equipment work with the SIP control protocol.
●Bold refers to new product support and version support.
OVOC | IOM
ProductSupported Software Version
document Device Manager for
Third-Party Vendor Products
Administrator's Manual.
- 7 -
CHAPTER3 Hardware and Software Specifications
3Hardware and Software Specifications
This section describes the hardware and software specifications of the OVOC server.
OVOC Server Requirements
This table below lists the minimum requirements for running the different OVOC server
platforms.
Table 3-2:OVOC Server Virtual and Cloud Platform Minimum Requirements
ResourceSpecification
Platform
Type
Operating
System
Platform
Details
AWSAzureVirtual OVOC
Linux CentOS Version 7.7 64-bit
AWSEC2
Instance Type:
c4.4xlarge
■ High
Profile:VMSize:F16s
■ Low Profile: VM Size
D4s_v3
■ VMware: ESXi 6.7;
VMware HA cluster:
VMware ESXi 6.5
■ Microsoft Hyper-V
Server 2016;
Microsoft Hyper-V
Server 2016 HA
cluster
Memory30GiB
(c4.4xlarge)
■ High Profile:32 GB RAM
(F16s)
■ Low Profile: 16 GB RAM
(D4s_v3)
- 8 -
■ High Profile:32 GB
RAM
■ Low Profile:16
GBRAM
CHAPTER3 Hardware and Software Specifications
ResourceSpecification
OVOC | IOM
Disk SpaceAWS EBS:
General
■ High Profile: 2 TB SSD
■ Low Profile: 500 GB SSD
■ High Profile: 1.2 TB
■ Low Profile:500 GB
Purpose SSD
(GP2) 2TB
Processor16 vCPUs
(c4.4xlarge)
■ High Profile:16 vCPUs
(F16s)
■ Low Profile: 4 vCPUs
(D4s_v3)
■ High Profile: 6 cores
with at least 2 GHz
■ Low Profile: 1 core
with at least 2.5 GHz
■ Low Profile: 2 core
each with at least
2.0 GHz
■ The OVOC server works with the Java Development Kit (JDK) version 1.8 (JDK 1.8 for
Linux™).
■ The Oracle database used is version 12.1.0.2.
●The JDK and Oracle database component versions mentioned above are provided
as part of the OVOC installation image.
●The installation and upgrade scripts validate the minimum requirements for the
Virtual CPU, Memory and Disk components as shown in the table above. Failure
to meet these requirements will lead to the aborting of the scripts.
Specifications for Service Provider Cluster Mode
This Appendix describes the specifications for supporting an enhanced customized platform
for service providers. Additional manual operations are required to be performed by
customers to support this enhancement (Required Updates). The following table describes the
machine specifications for this platform.
The table below describes the specifications for the Service Provide Cluster including three
servers:Management Server, VQMserver and PMserver. It is based on 50,000 devices with
3000 CAPs . For other parameters, refer to the tables below.
Table 3-3:Service Provide Cluster Mode Server Configuration
ItemMachine Specification
ServerVMware: ESXi 6.7; VMware HA cluster: VMware ESXi 6.5
Memory256 GB
CPU24 cores at 2.60 GHz
- 9 -
CHAPTER3 Hardware and Software Specifications
ItemMachine Specification
OVOC | IOM
Disk
■ SSD 20TB for Management Server
■ SSD 10TB for VQM/PM Servers
Ethernet
■ 1x10GB + 4x1 GB ports (through and through)
Note the following recommendations:
■ Use jumbo frames
■ Create a dedicated vswitch with dedicated uplinks
■ For software ISCSI, use 1 vmkernel nic per 1 physical NIC
■ In case of multiple vmkernel NICs and physical NICs, use port binding
Table 3-4:Service Provide Cluster Mode Capacities
ItemCapacity
Topology-Management
OVOC managed devices50,000
Tenants5000
Devices per region500
Links10,000
Operators25
Managed devices per tenant5,000
Alarms– Management
Steady state100 alarms per second
Total alarms50,000,000
Performance Monitoring– Management
PMs per OVOCinstance (per polling interval)
■ 5,000,000 for Version 7.4
devices (REST interface)
■ 500,000 for Version 7.2
devices (SNMP interface)
PMs per device500,000
- 10 -
CHAPTER3 Hardware and Software Specifications
ItemCapacity
Storage timeOne year
Voice Quality– applicable for QoE license only
CAPS per device1000
OVOC QoE managed devices25000
OVOC | IOM
CAPS per OVOC instance (SBC and Skype for Business
2500
and RFC SIP Publish 6035)
Call Details Storage - detailed information per call400,000,000 or one year
Calls Statistics Storage - Statistic information storage
(per five minute interval).
1
750,000,000 or one year
QoE Call Flow (for SBC calls only)– applicable for QoE license only
CAPS per OVOC instance1,000
CAPS per device300
Maximum number of calls10,000,000
Lync and ADServers– applicable for QoE license only
MS Lync serversUp to 2
AD Servers for Users syncUp to 2
Users syncUp to 150,000
Devices Management (Device Manager Pro)
Number of managed devices
■30,000
■4,000 Team devices
Disk space allocated for firmware files20GB
OVOC Client Requirements
The table below lists the minimum requirements for running an OVOC web client.
1
For each managed entity: Device, Link, Site, Endpoint, User and URI. In addition to the
relevant number of statistics in corresponding hourly and daily summary tables per entity.
- 11 -
CHAPTER3 Hardware and Software Specifications
Table 3-5:OVOC Client Minimum Requirements
ResourceOVOC Client
HardwareScreen resolution: 1280 x 1024
Operating SystemWindows 7 or later
Memory8 GB RAM
OVOC | IOM
Disk Space
Processor-
Web Browsers
Scripts
-
■ Mozilla Firefox version 39 and higher
■ Google Chrome version 79 and higher
■ Microsoft Edge Browser version 80 and higher
■ PHP Version 7.4
■ Angular 7.0
Bandwidth Requirements
This section lists the OVOC bandwidth requirements.
OVOC Bandwidth Requirements
The bandwidth requirement is for OVOC server <- > Device communication. The network
bandwidth requirements per device is 500 Kb/sec for faults, performance monitoring and
maintenance actions.
Voice Quality Bandwidth Requirements
The following table describes the upload bandwidth speed requirements for Voice Quality for
the different devices. The bandwidth requirement is for OVOC server <- > Device
communication.
Table 3-6:Voice Quality Bandwidth Requirements
SBC Sessions
Device
SBC
MP-118__
(each session has two
legs)
- 12 -
Required Kbits/sec or Mbit/sec
CHAPTER3 Hardware and Software Specifications
OVOC | IOM
SBC Sessions
Device
(each session has two
Required Kbits/sec or Mbit/sec
legs)
MP-124__
Mediant 800 Mediant
850
Mediant 1000150330 Kbits / sec
Mediant 2000__
Mediant 26006001.3 Mbit/sec
Mediant 300010242.2 Mbit/sec
Mediant 40004,0008.6 Mbit/sec
Gateway
MP-118815 Kbits/sec
60135 Kbits/sec
MP-1242445 Kbits/sec
Mediant 800 Mediant
850
Mediant 1000120220 Kbits/sec
Mediant 2000480880 Kbits/sec
Mediant 2600__
Mediant 300020483.6 Mbit/sec
Mediant 4000__
Endpoints_56 Kbits/sec
60110 Kbits/sec
Standard Capacities
The following table shows the performance and data storage capabilities for the OVOC
managed devices for Voice Quality.
- 13 -
CHAPTER3 Hardware and Software Specifications
Table 3-7:Standard Capacities
OVOC | IOM
Machine
Specifications
HP DL360p Gen10
VMware/Microsoft
Hyper-V – High
Profile
VMware/Microsoft
Hyper-V - Low Profile
OVOC Management Capacity
Managed devices5,0005,000100
Device Manager Pro
Managed devices
■ 10,000
Microsoft
Lync/Skype
for Business
and thirdparty vendor
devices
■ 30,000 Microsoft
Lync/Skype for
Business and
third-party
vendor devices
1
■ 4,000 Microsoft
Teams devices
1,000
2
■ 4,000
Microsoft
Teams devices
Disk space
10 GB10 GB5 GB
allocated for
firmware files
Alarm and Journal Capacity
History alarmsUp to 12 months or ten million alarms
Journal logsUp to 12 months
Alarm forwarding
Up to 1000 alarms
aggregation in a
single email
Performance Monitoring
1
Including phones, headsets and Conference Suite devices
2
In normal operation (when devices are remotely managed) 30,000 devices send Keep-alive
messages at five minute intervals; however, when managing devices behind a firewall or NAT
using the Device Manager agent, a 10% factor (3,000 devices) is deducted for the allocation for
these devices. In this case, 90% of the configuration (27,000) is checked every 15 minutes (for
remotely managed devices)and 10% is checked every five minutes (for devices managed
behind a firewall or NAT).
- 14 -
CHAPTER3 Hardware and Software Specifications
OVOC | IOM
Machine
Specifications
Polled
HP DL360p Gen10
100,000100,00050,000
VMware/Microsoft
Hyper-V – High
Profile
VMware/Microsoft
Hyper-V - Low Profile
parameters per
polling interval
per OVOCmanaged device
Polled
500,000500,00050,000
parameters per
polling interval
per OVOC
instance
QoE Call Flow (for SBC calls only)
Managed devices10010010
CAPS (calls
100256
attempts per
second) per
OVOCinstance
OVOC QoE for Devices
QoE for managed
devices
QoE for devices
per region
QoE for number
of links
CAPS (calls
attempts per
second) per
device
CAPS per OVOC
instance (SBC and
Skype for
Business)
3,0001,200100
500300100
6,0002,400200
16012030
30012030
QoE concurrent30,00012,0003,000
- 15 -
CHAPTER3 Hardware and Software Specifications
OVOC | IOM
Machine
Specifications
sessions
Call Details
Storage - detailed
information per
call
Calls Statistics
Storage statistics
information
storage
OVOCQoE for Endpoints
CAPS for
managed
endpoints
HP DL360p Gen10
Up to one year or
80 million calls.
Up to one year or
150 million
intervals.
1051
VMware/Microsoft
Hyper-V – High
Profile
Up to one year or 80
million rows.
Up to one year or 150
million rows.
VMware/Microsoft
Hyper-V - Low Profile
Up to one year or 6
million rows.
Up to one year or 12
million rows.
QoE Capacity with SBC Floating License Capability
CAPS (calls
attempts per
second) per
OVOCinstance
with SIP call flow
CAPS (calls
attempts per
second) per
OVOCinstance
without SIP call
flow
Managed devices
with floating
license
90225
27010827
1,000500100
Skype for Business Monitoring SQL Server Prerequisites
The following are the Skype for Business Monitoring SQL Server prerequisites:
The server must be defined to accept login in 'Mix Authentication' mode.
- 16 -
CHAPTER3 Hardware and Software Specifications
■ The server must be configured to collect calls before the OVOC can connect to it and
retrieve Skype for Business calls.
■ Call Detail Records (CDRs) and Quality of Experience (QoE) Data policies must be
configured to capture data.
■ Network administrators must be provisioned with the correct database permissions (refer
to the One Voice Operations Center User's Manual).
■ Excel macros must be enabled so that the SQL queries and reports can be run; tested with
Excel 2010.
■ Detailed minimum requirements for Skype for Business SQL Server can be found in the