One Voice Operations Center Users Manual Ver 76

User's Manual
AudioCodes One Voice Operations Center (OVOC)
One Voice Operations

Center
Version 7.6
Notice OVOC | User's Manual
Notice
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 can-
not 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
https://www.audiocodes.com/library/technical-documents.
This document is subject to change without notice.
Date Published: August-08-2019
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 for contact information, please visit our website at
https://www.audiocodes.com/services-support/maintenance-and-support.
Documentation Feedback
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
Mediant 800B Gateway and E-SBC User’s Manual
Mediant 800B MSBR User’s Manual
- ii -
Document Name
Mediant 1000B Gateway and E-SBC User’s Manual
Mediant 1000B MSBR User’s Manual
Mediant 2600 SBC User's Manual
Mediant 3000 User’s Manual
Mediant Software SBC User's Manual
One Voice Operations Center Server Installation, Operation and Maintenance Manual
One Voice Operations Center Product Description
One Voice Operations Center Integration with Northbound Interfaces Guide
Device Manager Pro Administrator's Manual
Device Manager Express Administrator's Manual
ARM User's Manual
One Voice Operations Center Security Guidelines
One Voice Operations Center Alarms Guide
Document Revision Record

LTRT Description
91036 Initial document release for Version 7.4.
91037 Version 7.4 GA
91039 Updated to patch Version 7.4.1000. Network Map page | SIP Call Flow | QoE Link -
regular expression | ARM SSO | RADIUS/LDAP SSO | Calls List – new columns |
'Location' field | Show Grid | New AudioCodes logo and login screen | Hover cursor
91040 Calls List – 3-hour call. Timer defaults (0). Session Inactivity Period. Adding an
Unprivileged User to MSSQL Server.
91041 Call Details page's PL parameter > 100%. Limitation note: Calls on HA devices
unsupported. Backed-up filename format explanation.
91043 Connect to Ext. Apps: ARM. Endpoints License Allocation. Use Internal Mail Server
(Alarms Forwarding) . FQDN (Add Device). 'IP Group Value' (Add Link)
- iii -
LTRT Description
91044 Max number of alarms to aggregate in single email. Email alarms aggregation time
interval. Connecting directly to the ARM. UMP. Sites. Device definition-generic
option. NAT. Mandatory parameters indicated by *. SBC QoE – identify call by leg ID.
SEM: Improved call identification, new call scenarios supported. AD users
authentication with SfB SQL server. New authentication mode. Slider in QoE
Thresholds and Status & Alarm Settings. Call Flow in Call Details: message (arrow)
selection sign. Alarm forward via mail - aggregate x alarms into a single mail.
Topology Map: when icon location is changed, ‘Save’ button is enabled and
highlighted orange. Fixed License Pool actions: Lock / Unlock, Reset Redundant,
Switchover and Show. System > Administration: Server Status and Info: new read-
only screen. System > License > Summary: New 'Load License File' button.
91045 Dashboard. Load License. PM. External Applications. Max Concurrent Calls. Save
Fixed LP Data to CSV. Force Operator Logout. Securing Connections with FQDN or
IP Address. Custom Time Filter. Adding AC Device Manually. More Filters. Alarm
Names. Backing Up. Restoring the Last Backup. Show Link. Adding an Active
Directory. 'LDAP Connectivity DN'. Adding a cli File. Calls List - Save calls.
SmartTAP. Floating License Server Address parameter (replaced DNS).
91046 User Defined Failure PM table
91047 ITSP Customer Multi-Tenant Architecture. 'Tenant Monitor Links User Group Name'
field. Forwarding Alarms whose Destination Type is 'Notification'. Phones reflected in
Journal page. Customizing Call Storage. Customizing max storage period.
Notifications display time (sec). Test SBC. MSRP. Voice AI Gateway Service.
Lync>Skype. Floating License parameters. Hide Link Labels. Revert Local Changes.
Search per IP/SN. Save Local Changes to Server. Combined Authentication Mode.
- iv -
Content OVOC | User's Manual
Table of Contents
1 Introduction 1
About the One Voice Operations Center 1
Benefits 2
Intended Audience 2
Network Architecture 2
ITSP Multi-Tenancy Architecture 3
Enterprise Multi-Tenancy Architecture 3
Non Multi-Tenancy Architecture 3
Elements in Multi-Tenancy Architecture 4
ITSP Customer Multi-Tenant Architecture 5
2 Getting Started 6
Logging in 6
Getting Acquainted with the Dashboard 6
Getting Acquainted with the Network Topology Page 10
Hovering Over a Cluster to Display Information 21
Hovering Over a Device to Display Information 22
Hovering over a Link to Display Information 23
Returning to 'Home' Page by Clicking the AudioCodes Logo 23
Getting Acquainted with the Network Map Page 23
Configuring Operator Authentication 27
Configuring Operator Authentication Centrally using an LDAP Server 28
Configuring Operator Authentication Centrally with a RADIUS Server 31
Viewing Operator Authentication in the Application Information Window 32
Testing Connectivity with the LDAP / RADIUS Server 33
Configuring Operator Authentication Locally, in the OVOC 34
Adding an Operator 36
How Multi Tenancy Impacts Operator Capabilities 36
Adding a 'System' Operator 37
Editing a 'System' Operator 42
Deleting a 'System' Operator 42
Deleting Multiple Operators 42
Suspending a 'System' Operator 42
Releasing a Suspended 'System' Operator 42
Forcing a Password Change 42
Forcing an Operator Logout 43
Adding a 'Tenant' Operator 43
Editing a 'Tenant' Operator 47
Deleting a 'Tenant' Operator 47
Deleting Multiple Operators 48
Suspending a 'Tenant' Operator 48
Releasing a Suspended 'Tenant' Operator 48
Forcing a Password Change 48
Forcing an Operator Logout 48
-v-
3 Configuring Global (System) Settings 50

Administration tab 51
Loading the OVOC Server License 51
Making Sure your License Provides the Capabilities you Ordered 52
Allocating Licenses to Tenants 53
Authenticating Operators 56
Determining OVOC Server Status 56
Securing Connections with FQDN or IP Address 57
Customizing Call Storage 58
Customizing Maximum Storage Period 62
Configuration tab 63
Configuring Templates 63
SNMP Connectivity 63
HTTP Connectivity 65
QoE Thresholds 65
QoE Status and Alarms 67
Configuring Alarms Settings 69
Adding Configuration Files to the OVOC's Software Manager 72
Adding the ini File 73
Adding a cmp File 74
Adding a cli File 75
Adding Auxiliary Files 75
Connecting Directly to External Applications 76
Device Manager 77
Reports 77
ARM 78
MasterScope 79
Enabling Automatic Device Backup Periodically 80
Tasks tab 81
Displaying the Status of Tasks Currently Under Execution 82
4 Defining your Network Topology 85
Adding a Tenant 85
Adding a Region 91
Adding AudioCodes Devices 92
Adding AudioCodes Devices Automatically 92
Adding AudioCodes Devices Manually 96
Enabling Initial Connection Provisioning 102
Before Enabling the Feature 104
Enabling the Feature 104
Making Sure First Time Provisioning was Successful 106
Adding a Generic Device Manually 108
Adding a Microsoft Skype for Business Device Manually 109
Backing up a Device's Configuration using Backup Manager 112
Manually Backing up a Device's Configuration 112
Saving the Last Backed-up Configuration to your PC 113
- vi -
Restoring the Last Backed-up Configuration to the Device 113

Adding Links 114
Adding Sites 118
Managing Endpoints 119
Dynamic Allocation of Endpoint Licenses 119
Configuring Endpoints 120
Monitoring Endpoints Status 121
Removing Endpoints from QoE Support 121
5 Managing SBC Licenses 122
Configuring SBC Floating License Monitoring 122
Configuring the OVOC for Floating License Monitoring 123
Adding an SBC to the Floating License 125
Performing Floating License Actions 128
Unmanage 129
Update 129
Reset 129
Register 129
Configuring OVOC-Floating License Service Communications 129
Viewing Floating License Summaries 130
Device Floating License Utilization Pane 130
Viewing Floating License Info 132
Viewing Device Info 132
Saving a Usage Data Report to your PC 133
Managing Device Licenses in the Fixed License Pool 134
Performing License Pool Actions 136
Applying a License to a Device from the Pool 136
Saving Fixed License Pool Data to CSV File 136
Before Performing 'Manage Device' / 'Update Device' 138
License Pool Alarms 139
6 Assessing Network Health 140
Assessing Health from the Network Summary 140
Assessing Health from the Network Topology Page 144
Filtering to Access Specific Information 147
Filtering by 'Time Range' 148
Filtering by 'Topology' 150
Filtering by 'Status' 152
Filtering by 'More Filters' 154
Determining Network Health from Alarms 155
Configuring Alarm Settings 155
Monitoring Active Alarms to Determine Network Health 155
Performing Management Actions on Active Alarms 155
Filtering by 'Severity' 158
Filtering by 'Source Type' 160
Filtering by 'Type' 162
- vii -
Filtering by 'Alarm Names' 163

Viewing Journal Alarms to Determine Operator Responsibility 163
Filtering the Alarms Journal by 'More Filters' 164
Viewing History Alarms 165
Filtering by 'Type' 166
Filtering by 'Alarm Names' 167
Forwarding Alarms 167
Forwarding Alarms whose Destination Type is 'SNMP' 173
Forwarding Alarms whose Destination Type is 'Mail' 176
Forwarding Alarms whose Destination Type is 'Syslog' 179
Forwarding Alarms whose Destination Type is 'Notification' 181
Viewing the New Rules in the Alarms Forwarding Page 184
Assessing Network Health in the Statistics Pages 184
Viewing Statistics on Calls over Devices 184
Metrics Bar Charts 185
Statistics Summary 187
Viewing Statistics on Streams over Links 187
Viewing Statistics on Calls over Sites 188
Viewing Statistics on Calls over Endpoints 188
Monitoring Performance 188
Adding a PM Template 189
Adding a PM Profile 193
Starting and Stopping PM Polling 196
Viewing PM Data Resulting from Polling 197
7 Managing your Network 206
Performing Management Actions 206
Updating Firmware 207
Updating Firmware on Multiple Devices 209
Resetting a Device 209
Locking or Unlocking a Device 209
Populating Links 211
Moving a Device 211
Backing Up 212
Restoring the Last Backup 213
Setting Configuration Factory Defaults 215
Saving a Device's Configuration File to Flash Memory 215
Saving a Device's Configuration File to the PC 215
Resetting Redundant 216
Performing Switchover 217
Changing Profile 217
Showing Device Information 219
Showing Link Information 220
Showing User Information 221
Editing a Device 223
Deleting a Device 223
Resetting a Device 224
- viii -
Refreshing a Device's Pool License 225

Monitoring Device-Level Backup and Performing Rollback 225
8 Obtaining Quality Statistics on Calls 226
Accessing the Calls List 226
Filtering by 'Quality' 228
Showing Call Details 232
Details of a Call Made over an AudioCodes SBC 232
Media 233
Signaling 236
Trends 237
SIP Call Flow 238
Details of a Test Call Made over an SBC 240
Call Details Page – Debug File Button 242
Details of a Call Made over Microsoft Skype for Business 242
Media 245
Signaling 246
Details of a Call Made over an Endpoint Using SIP Publish 247
Media 250
Managing QoE Thresholds Profiles per Tenant 252
Understanding the 3 Sensitivity-Level Profiles 252
Understanding How Call Color is Determined 253
Link Profile as Determinant 253
MOS Metric as Determinant 253
Adding a QoE Thresholds Profile per Tenant 254
Editing a QoE Thresholds Profile per Tenant 257
Deleting a QoE Thresholds Profile per Tenant 257
Managing QoE Status and Alarms per Tenant 258
Adding a QoE Alarm Rule per Tenant 258
Editing a QoE Alarm Rule per Tenant 261
Deleting a QoE Alarm Rule 261
9 Getting Information on Users Experience 262
Adding an Active Directory to the OVOC 262
Editing an Active Directory 265
Deleting an Active Directory 266
Synchronizing an AD with the AD Server 266
Assessing Overall End Users Experience 266
Assessing a Specific End User's Experience 268
Managing End Users 269
Filtering the User Details Page 270
10 Producing Reports 271
Using Reports Features 272
Producing a Network Status Report 275
Producing Trend Reports 279
- ix -
Producing Top Users Reports 280

Scheduling a Report 282
Viewing a Scheduler Generated Report 284
Saving the File of a Scheduler Generated Report 284
Deleting the File of a Scheduler Generated Report 284
Editing a Schedule 284
Deleting a Schedule 284
Manually Running or Pausing a Schedule 285
11 AudioCodes IP Network Telephony Equipment 286
12 Adding an Unprivileged User to MSSQL Server 291
-x-
CHAPTER 1 Introduction OVOC | User's Manual
1 Introduction
The AudioCodes One Voice Operations Center (referred to as ‘OVOC’ for short in this document) is
a web-based voice network management solution that combines management of voice network
devices and quality of experience monitoring into a single, intuitive web-based application.
Figure 1-1: AudioCodes One Voice Operations Center
OVOC enables administrators to adopt a holistic approach to network lifecycle management by

simplifying everyday tasks and assisting in troubleshooting all the way from detection to correction.
The OVOC’s clear GUI design allows network administrators to manage the full lifecycle of VoIP
devices and elements from a single centralized location, saving time and costs. Tasks that would
normally be complex and time-consuming, such as performing root cause analysis, adding new
devices to the VoIP network and initiating bulk software updates, can be carried out quickly and
easily.
The OVOC uniformly manages, monitors and operates the entire AudioCodes One Voice portfolio,
including Media Gateways, Session Border Controllers, Microsoft SBAs and IP Phones.
About the One Voice Operations Center

The OVOC enables customers to adopt an integrated approach to network lifecycle management
by simplifying everyday tasks and assisting in troubleshooting all the way from detection to cor-
rection. When deployed in Amazon Web Services (AWS), for example, the OVOC enables Audi-
oCodes partners and systems integrators to provide remote VoIP support and professional
services, covering AudioCodes session border controllers, IP phones and other devices, from the
cloud.
The OVOC combines several key functions together in a single pane of glass, including:
■ New device detection and configuration
■ Accurate inventory population
■ Automation and mass operation support
■ A central, correlated alarm dashboard
■ Group-based configuration and update management
■ Change documentation and device configuration backup and restore
■ Quality monitoring and RCA (root cause analysis)
In addition, the OVOC is fully integrated with AudioCodes Routing Manager (ARM). ARM is a hol-
istic, dynamic routing manager with a design based on software-defined networking principles. It
decouples the device layer from the network routing and policy layers, designs VoIP networks auto-
matically, and simplifies routing rules, monitoring and management configuration.
-1-
OVOC features:
■ Highly scalable to support thousands of devices
■ Multi-tenancy support for hosted and managed environments
■ Auto-provisioning and configuration for the entire AudioCodes portfolio
■ Real-time call quality monitoring and root cause analysis
■ Integration with AudioCodes Routing Manager (ARM) session routing solution
■ Centralized reporting and knowledge distribution
Benefits
Here are some of the benefits you'll get from the OVOC:
■ Facilitates easy and secure transition to VoIP deployments including UC, hosted business
services and contact centers
■ Reduces OpEx and TCO using centralized tools to remotely operate VoIP network
components
■ Simplifies and allows for more efficient device operation, administration and fault management
■ Provides an intuitive real-time network view, capturing entire network status in real time
■ Reduces MTTR with integrative detection and correction tools
■ Delivers powerful analytic reports for effective planning of future network expansion and
optimization
■ Streamlines network management and quality monitoring in a single application
■ Improves system availability with accurate troubleshooting and root cause analysis
■ Increases efficiency with centralized configuration and provisioning
■ Offers intelligent insights into network trends and performance to assist in planning and design
■ Supports Microsoft Skype for Business environments
Intended Audience
This User's Manual targets three audiences:
■ The ITSP administrator whose network features multi-tenancy architecture and whose OVOC
application will provide telephony management services to multiple enterprise customers
(tenants) in their network. See Network Architecture below for more information.
■ The enterprise administrator whose network does not feature multi-tenancy architecture and
whose OVOC application will enable management of the enterprise's distributed offices. See
also Network Architecture below.
The enterprise administrator whose network does not feature multi-tenancy architecture
can skip documentation related to multi-tenancy.
■ The enterprise administrator whose network features multi-tenancy architecture and whose
OVOC application will provide telephony management services to multiple regional branches
(tenants) in their network. See Network Architecture below for more information.
Network Architecture
The OVOC features three types of telephony network architecture:
■ Multi-Tenancy Architecture (see ITSP Multi-Tenancy Architecture on the next page and
Enterprise Multi-Tenancy Architecture on the next page)
■ Non Multi-Tenancy Architecture (see Non Multi-Tenancy Architecture on the next page)
-2-
ITSP Multi-Tenancy Architecture

ITSP multi- tenancy architecture allows an Internet Telephony Service Provider (ITSP)
administrator to deploy a single instance of the OVOC application to provide a telephony network
management service to multiple enterprise customers (tenants).
Figure 1-2: ITSP Multi-Tenancy Architecture
'Tenants' can be given the capability to customize parts of the OVOC application, for example, the
routing rules, but not to customize, for example, the OVOC server's roles.
Enterprise Multi-Tenancy Architecture

Enterprise multi-tenancy architecture allows an enterprise administrator to deploy a single instance
of the OVOC application in order to provide a telephony network management service to multiple
regional branches (tenants).
Figure 1-3: Enterprise Multi-Tenancy Architecture
'Tenants' can be given the capability to customize parts of the OVOC application, for example, the
routing rules, but not to customize, for example, the OVOC server's roles.
Non Multi-Tenancy Architecture

Non multi-tenancy architecture allows an enterprise's network administrator to define a single
tenant (themselves) in order to provide a network management service to the enterprise's
distributed offices.
-3-
Figure 1-4: Non Multi-Tenancy Architecture - Enterprise
Elements in Multi-Tenancy Architecture

The following table shows OVOC application elements defined in multi-tenancy architecture.
Table 1-1: OVOC Application Elements Defined in Multi-Tenancy Architecture
Element Description
System An ITSP managing multiple enterprises using a cloud-based or hosted 'global'

OVOC application.
Tenant ■ An ITSP's enterprise customer, using only a portion of the OVOC resources
and only some of the OVOC entities. Other tenants (the ITSP's other
enterprise customers) in the ITSP's multi-tenant network will be invisible to
this tenant.
■ An enterprise's regional branch, using only a portion of the OVOC resources
and only some of the OVOC entities.
■ An enterprise whose network administrator must define a tenant (that
enterprise) under which to define the enterprise's distributed offices.
Entity Any element which can be managed or used as a whole:

■ Tenant entity (managed/assigned by a specific OVOC tenant)
■ Global entity (managed by the OVOC system; applies to/affects all tenants)
■ System entity (managed /assigned only by the OVOC system)
Resource Any element that can be partly managed/assigned:

■ Global resource (managed by the OVOC system; applies to/affects all
tenants)
■ Tenant resource (portion of the resource)
-4-
ITSP Customer Multi-Tenant Architecture

This architecture enables every OVOC operator (assigned to the same tenant), whose operator
type is configured as ‘Tenant’ and whose operator security level is configured as ‘Monitor Links’, to
monitor a subset of links under that tenant.
When an ITSP deploys this architecture, one operator can then monitor (for example) all links con-
necting customer ‘A’ to trunk groups while another operator can monitor (for example) all links con-
necting customer B’s Microsoft Edge Server IP Group to its Skype for Business Front End IP
Group.
Figure 1-5: ITSP Customer Multi-Tenant Architecture
The architecture features non-bleeding partitions between each subset of links so operators cannot
monitor the links of one another.
OVOC operators in this architecture can monitor:
■ Sites configured as links’ destinations
■ Devices configured as links’ sources/destinations
■ Links in the Network Topology page
■ Link-related alarms and events
■ Link-related statistics
■ Link-related notifications for tasks and alarms
-5-
CHAPTER 2 Getting Started OVOC | User's Manual
2 Getting Started
Getting started with the One Voice Operations Center involves logging in and getting acquainted
with the management interface.
● Before getting started, make sure you have a correct OVOC license.
● For detailed information about the OVOC Server License, see Loading the OVOC
Server License on page 51.
Logging in
Logging in to the OVOC is a prerequisite to using the interface for network management.
➢ To log in to the OVOC:

1. Point your browser to the OVOC server's IP address: https://<IP Address>. You only need to
enter its IP address; the rest of the URL is automatically added. Logging in can optionally be
performed using FQDN rather than IP address.
Figure 2-1: Login
2. Enter your Username and Password:

● acladmin (default) (case-sensitive) (can be modified later after defining users)
● pass_1234 (default) (case-sensitive) (can be modified later after defining users)
3. The GUI by default displays the Dashboard.
It's recommended to change the password after initial login.
Getting Acquainted with the Dashboard

The Dashboard opens by default after logging in to the OVOC. The Dashboard gives the operator:
■ an uncluttered, operator-friendly summary of the entire IP telephony network
■ an aggregation of all IP telephony network information on a single page
■ quick access to every entity, status, QoE and alarm from one central point
It may be helpful to get familiar with the page before getting started.
-6-
Figure 2-2: Dashboard
Use the following table as reference:

Table 2-1: OVOC Dashboard
Cluster Icon Description
[Devices] Indicates the number of AudioCodes SBC / MSBR / Gateway

devices currently managed by the OVOC. Quickly accesses the Device
Manage page filtered to display only these devices and none other.
[Links] Indicates the number of links currently managed by the OVOC. Click to
access the Links page. See Adding Links on page 114.
[Sites] Indicates the number of sites currently managed by the OVOC. Click to
open the Sites page. See Adding Sites on page 118
[Endpoints] Indicates the number of endpoints currently managed by the

OVOC. Click to open the Endpoints page. See Monitoring Endpoints Status on
page 121.
[UMP] Indicates the number of User Management Packs (UMPs) 365

currently managed by the OVOC. For more information about the AudioCodes
UMP 365, see under AudioCodes IP Network Telephony Equipment on
page 286.
[Skype] Indicates the number of Microsoft Skype for Business entities, for
example, Front End Servers, currently managed by the OVOC. Click to
access the Device Management page.
[SmartTAP] Quickly accesses the OVOC's Device Management page filtered

to display only the SmartTAP Application server. The AudioCodes SmartTap
for Microsoft Skype for Business is an intelligent, fully certified and secured
enterprise interactions recording solution of voice, video and IMs. With
SmartTAP, enterprises can capture and index any customer or organizational
interaction across external and internal communication channels seamlessly.
Note that for OVOC-SmartTAP server connectivity, Microsoft's SNMP
Service must be disabled on the SmartTAP server.
-7-
Indicates (1) the total number of active alarms in the network and (2) the
number of active Critical, Major, Minor and Warning severity-level alarms.
■ Clicking the total number of active alarms in the network opens the Active
Alarms page.
■ Clicking the row of a severity level opens the Active Alarms page filtered
by that severity level, so operators can directly access only alarms whose
severity level is (for example) critical; the Alarms page opens displaying
only critical severity-level alarms. In the Alarms page, operators can select
any critical severity-level alarm to view its details.
■ Indicates (1) the total number of calls, in real time and (2) the average
MOS, Jitter, Delay and Packet Loss (%) scores:
✔ With a click, the operator can directly access the Statistics page
displaying statistics on all calls (Total Calls).
■ Indicates below left (1) Successful / Failed Calls and below right (2)
Quality Distribution (Good, Fair, Poor):
✔ [Refer to above left] With a click, the operator can directly access only
calls whose performance status is FAILED (for example); the Calls
List page opens displaying only failed calls. In the Calls List page, the
operator can select any call and show its details in the Call Details
page that opens.
-8-
✔ [Refer to above right] With a click, the operator can directly access
only calls whose quality is assessed to be Poor (for example); the
Calls List page opens displaying only poor quality calls. In the Calls
List page, the operator can select any call and show its details in the
Details dynamic tab that opens.
Each external application described next opens in a separate browser tab or

browser window depending on the operator's browser settings.
External
Applications
[Device Manager] Quickly accesses the Device Manager, the AudioCodes life
cycle management application for enterprise IP telephony deployments that
enables administrators to deliver a reliable desktop phone service within their
organization. With the ability to deploy and monitor IP telephony devices,
identify problems, and then fix them rapidly and efficiently, the application
enhances employee satisfaction, increases productivity and lowers IT
expenses.
[Reports] Quickly accesses reports-generation capability that operators can

utilize to distribute session experience data and comparative analysis to
responsible persons within the enterprise and to external authorities
associated with the enterprise's IP telephony network, for accurate diagnosis
and correction of degraded sessions and for general network optimization.
[Routing Manager] Quickly accesses the Routing Manager (ARM) for

managing the dial plan and call routing rules of multi-site, multi-vendor
enterprise VoIP networks. The ARM enables centralized control of all session
routing decisions. Through ARM’s graphical user interface, network
administrators can design and modify their voice network topologies and call
routing policies from a single location, resulting in significant time and cost
savings. Time-consuming tasks such as adding a new PSTN or SIP trunk
interconnection, adding a new branch office or modifying individual users’
calling privileges can be carried out simply and rapidly.
Note that the icon is never disabled even when the ARM is disconnected; if
the ARM is disconnected, the AudioCodes website page related to the ARM
opens instead.
[MasterScope] Applies only to operators who have acquired and installed

NEC's MasterScope. Enables connecting directly to MasterScope in order to
quickly and easily access the exact network equipment component
associated with a voice quality issue - if an issue is detected - and benefit from
root cause analysis.
Notifications Notifications can be configured to pop up in the uppermost right corner when a
task is performed or when an alarm is received. The bell icon indicates the
number of notifications that have not yet been viewed; the color indicates
highest alarm severity level. Clicking the bell opens the notifications list. In the
list, operators can delete a notification, delete all notifications or click a
notification to open the Tasks page or Alarms History page. The display time
can be changed. The feature can be switched off.
-9-
Getting Acquainted with the Network Topology Page

It may be helpful to briefly familiarize yourself with the OVOC's central page - the Network
Topology page - before getting started.
Figure 2-3: OVOC GUI – Network Page – Topology
The page is divided into three panes: left, middle and right.
In the left pane, the 'tree' displays network entities, up to the level of tenant (first-level navigation).
The middle pane displays a topological view of devices and links in the network on which operators
can quickly obtain basic device information and statuses and perform actions (second- level
navigation).
The right pane displays a summary of network statistics from which operators can determine
network health.
Each entity can be viewed in table view. The following table explains the entity icons in the
Network Topology page. Icon colors are propagated from the statuses of the entities. Entity status
is derived from management status, voice quality status and license status.
Table 2-2: Network Topology – Network Entities and Statuses
Network
Icon Explanation
Entity
Tenant For detailed information about multi-tenancy architecture,

see ITSP Multi-Tenancy Architecture on page 3.
= Tenant status is Error when one or more of the
following exists:
✔ management status of at least one region is Error
✔ voice quality status of at least one region is Error
✔ license status of at least one region is Error
✔ license status of the tenant itself is Error due to one
of these [Critical] alarms: QoE Devices Overload,
QoE Sessions Overload, QoE Endpoints Overload
or Endpoints Management Overload.
= Tenant status is Warning when one or more of the

following exists:
✔ management status of at least one region is
Warning
- 10 -
Network
Icon Explanation
Entity
✔ voice quality status of at least one region is Warning

✔ license status of at least one region is Warning
✔ license status of the tenant itself is Warning due to
one of these [Major] alarms: QoE Devices
Overload, QoE Sessions Overload, QoE Endpoints
Overload or Endpoints Management Overload.
✔ One of the tenant's AD is disconnected
= Tenant status is OK when one or more of the following

exists:
✔ management status of all regions is OK or
Unmonitored
✔ voice quality status of all regions is OK or
Unmonitored
✔ license status of all regions is OK or Unmonitored
✔ license status of the tenant itself is free of alarms
✔ All the tenant's ADs are connected
= Tenant status is Unmonitored when one or more of the
following exists:
✔ management status of all regions is Unmonitored
✔ voice quality status of all regions is Unmonitored
✔ license status of all regions is Unmonitored
Region
= Region status is Error when one or more of the
following exists:
✔ management status of at least one device or site is
Error
✔ voice quality status of at least one device or site is
Error
✔ license status of at least one device or site is Error
= Region status is Warning when one or more of the
following exists:
✔ management status of at least one device or site is
Warning
✔ voice quality status of at least one device or site is
Warning
✔ license status of at least one device or site is
Warning
= Region status is OK when one or more of the following

exists:
✔ management status of all devices and sites is OK or
Unmonitored
✔ voice quality status of all devices and sites is OK or
Unmonitored
✔ license status of all devices and sites is OK or
Unmonitored
- 11 -
Network
Icon Explanation
Entity
= Region status is Unmonitored when one or more of the

following exists:
✔ management status of all devices and sites is
Unmonitored
✔ voice quality status of all devices and sites is
Unmonitored
✔ license status of all devices and sites is
Unmonitored
Device Indicates an SBC belonging to AudioCodes communicating

with the OVOC.
Red = Device status is Error when one or more of the
following exists:
✔ management status is Error (if device alarms status
or connection status is disconnected)
✔ voice quality status is Error (if control status or
media status is Error, or if connection status is
disconnected)
✔ License status is Error only if license pool is failed or
expired
Orange = Device status is Warning when one or more of the
following exists:
✔ management status is Warning (if device alarms
status or administration status is Warning)
✔ voice quality status is Warning (if control status or
media status or connection status is Warning)
✔ license status is Warning (if a reset/apply action is
required in the license pool or if there is no
management license in the device or if there is no
voice quality license)
Blue = Device status is OK when one or more of the
following exists:
✔ management status is OK - Clear or Undetermined
(if device alarms status or connection status is OK -
Clear or Undetermined)
✔ voice quality status is OK - Clear or Undetermined
(if control status or media status or connection
status is OK - Clear or Undetermined)
✔ license status is OK - Clear or Undetermined (if
license pool status is OK - Clear or Undetermined)
Strikethrough = locked
No strikethrough = unlocked
UMP Indicates the AudioCodes User Management Pack 365

communicating with the OVOC.
Red = UMP status is Error when one or more of the
following exists:
- 12 -
Network
Icon Explanation
Entity
✔ management status is Error (if UMP alarms status

or connection status is disconnected)
disconnected)
expired
Blue = UMP status is OK when one or more of the following
exists:
(if UMP alarms status or connection status is OK -
Orange = UMP status is Warning when one or more of the
following exists:
✔ management status is Warning (if UMP alarms
management license in the UMP or if there is no
voice quality license)
Strikethrough = locked
No strikethrough = unlocked
Microsoft
Skype for = Microsoft Skype for Business Mediation Server
Business
= Microsoft Skype for Business Edge Server
Device
= Microsoft Skype for Business Front End Server
Generic Indicates a non-AudioCodes device or entity that is also part

Device of the OVOC network topology: IP PBX (shown on left), SIP
trunk, other vendors' SBC / gateway. These devices
participate in processing OVOC network calls and are
connected to devices.
Site Color and status are propagated from the endpoints under
the site.
Gray = Site status is Unmonitored when one or more of the
following exists:
✔ management status of all endpoints is Unmonitored
✔ voice quality status of all endpoints is Unmonitored
- 13 -
Network
Icon Explanation
Entity
✔ license status of all endpoints is Unmonitored

Blue = Site status is OK when one or more of the following
exists:
(if site alarms status or connection status is OK -
Orange = Site status is Warning when one or more of the
following exists:
✔ management status is Warning (if site alarms status
or administration status is Warning)
management license in the site or if there is no voice
quality license)
Red = Site status is Error when one or more of the following
exists:
✔ management status is Error (if site alarms status or
connection status is disconnected)
disconnected)
expired
Link A link joins two devices:

Red = Voice quality status is Error when one or more of the
following exists:
✔ 'Critical' Control Status
✔ 'Critical' Media Status
Orange = Voice quality status is Warning when one or more
of the following exists:
✔ 'Major' Control Status
✔ 'Major' Media Status
Blue = Voice quality status is OK/Clear when one or more of
the following exists:
✔ Control Status is OK/Clear
✔ Media Status is OK/Clear
✔ Control Status or Media Status is Unmonitored
Gray = Voice quality status is Unmonitored when both of
these exist:
- 14 -
Network
Icon Explanation
Entity
✔ Control Status is Unmonitored

✔ Media Status is Unmonitored
Note:
✔ If no voice quality license exists, status will be
Unmonitored.
✔ Link status does not impact device / region
✔ Under the link's name tag, a single arrow indicates
the link's direction: ingress (calls incoming to the
reporting device) or egress (calls outgoing from the
reporting device); if there are no arrows under the
link's name tag, the link is bi-directional. In the figure
below, the link is ingress, to NJ SBC.
✔ A double arrow located next to one of the devices
indicates that it is the reporting device. In the figure
below, the reporting device is NJ SBC.
Device Indicate aggregated clusters of devices (AudioCodes

clusters devices as well as non-AudioCodes devices). The numbers
indicate how many devices are in the cluster.
■ Red = at least one entity in this cluster has a status of
Error – see above in this table for the one or more
conditions that need to exist for status to be Error
■ Orange = at least one entity in this cluster has a status
of Warning – see above in this table for the one or more
conditions that need to exist for status to be Warning
■ Blue = at least one entity in this cluster has a status of
OK – see above in this table for the one or more
conditions that need to exist for status to be OK
■ Gray = at least one entity in this cluster has a status of
Unmonitored – see above in this table for the one or
more conditions that need to exist for status to be
Unmonitored
Link Square icons indicate aggregated clusters of links. The link

clusters indication can be on a line representing a link (left upper) or
adjoined to a device cluster (left lower). The number in each
square indicates how many links are in the cluster.
■ Red square = at least one link in this cluster has a voice
quality status of Error – see above in this table for the
one or more conditions that need to exist for voice
quality status to be Error
■ Orange square = at least one link in this cluster has a
voice quality status of Warning – see above in this table
for the one or more conditions that need to exist for voice
quality status to be Warning
- 15 -
Network
Icon Explanation
Entity
■ Blue square = at least one link in this cluster has a

status of OK – see above in this table for the one or more
conditions that need to exist for status to be OK
■ Gray square = at least one link in this cluster has a voice
quality status of Unmonitored – see above in this table
for the two conditions that need to exist for voice quality
status to be Unmonitored
SmartTAP Indicates the AudioCodes SmartTAP communicating with

the OVOC.
■ Red = SmartTAP status is Error when management
status is Error (if SmartTAP alarms status or connection
status is disconnected)
■ Orange = SmartTAP status is Warning when
management status is Warning (if SmartTAP alarms
■ Blue = SmartTAP status is OK when management
status is OK - Clear or Undetermined (if SmartTAP
alarms status or connection status is OK - Clear or
Undetermined)
■ Gray = SmartTAP status is Unmonitored when
management status is unmonitored
The following bar of icons is displayed on the right side of the Network Topology page.
From top to bottom:

■ Click + or - to zoom in or out of the map.
■ Click the Center Map button to center the map in the page - useful if the previous operator
dragged it off center.
■ Click the Save Local Changes to Server button after making a change to the network
topology, for example, after dragging a device to a different location. The button is only
displayed if a change is made. It's highlighted orange. After saving the change, the button
disappears.
■ Click the Revert Local Changes button after making a change to the network topology, for
example, after dragging a device to a different location. This button is only displayed if a
change is made. It's highlighted orange. It allows you to revert to the network topology that
existed before you made the change instead of saving the changed network topology. After
reverting, the button disappears.
■ Click the Create Links button to create a link.
- 16 -
■ The Show Grid button allows operators to display gridlines; the background of the Network
Topology page is by default white.
■ The Hide Link Labels button allows operators to hide the labels of the links in the Network
Topology and Network map pages; this reduces clutter for more effective management,
especially in networks with many devices and links.
■ Show Clusters. If more than 200 devices and sites (aggregated) are defined, the button will
not be available and the page will automatically be displayed in clusters. The button will only be
available if fewer than 200 devices and sites (aggregated) are defined. The feature reduces
clutter and improves operational efficiency.
● When the clusters feature is activated, enter in the 'Search' field the name or a part of the
name of an entity to locate; the circumferences of the clusters containing an entity with
that name segment are colored purple. You can hover over each to determine from a pop-
up which one contains the entity you're after. In clusters containing too many entities to
scan through, you can use the pop-up's 'Search' feature to facilitate the search (see also
under Hovering Over a Cluster to Display Information on page 21).
Select an area: Press the Shift key and press the mouse.
The Network Topology page lets you quickly drill down from a tenant to the core of an issue. Fast
access to very specific information makes network management efficient. This capability earns
OVOC the title of 'expert system'.
Specific information related to device, user and call is automatically dynamically tabbed on the
menu bar, facilitating quick and easy future access and troubleshooting:
Figure 2-4: Dynamic Tab for Fast Access to Specific Information
For more information about the dynamic tab that is created for call details, see Showing Call Details
on page 232.
For more information about the dynamic tab that is created for user details, see Assessing a
Specific End User's Experience on page 268.
A dynamic tab lets you quickly access a specific page that is automatically dynamically tabbed on
the menu bar after for example drilling down in the Topology page from a tenant to the core of an
issue. The tab allows quick and easy future access to specific information related to device, user,
call, etc., displayed in the page. It can be deleted from the menu bar at any time. The feature
simplifies troubleshooting management.
The right pane of the Network Topology page summarizes device statuses and alarms in the
network.
- 17 -
The following figure shows the OVOC's menu bar.

Figure 2-5: Menu Bar
Use the following table as reference to the preceding figure. See also Getting Acquainted with the
Dashboard on page 6.
Table 2-3: Menu Bar
Menu Tab Description
Network Topology The tab's page lets you:

■ Assess at a glance the topology of the network
■ Perform multiple configuration and maintenance actions
■ Select multiple devices (Ctrl+) and perform multiple actions
simultaneously (Ctrl+ to deselect)
■ Select multiple links (Ctrl+) and perform multiple actions
simultaneously (Shift+ to deselect)
■ Filter out unwanted information to facilitate quick access to
specific information
The page features two 'modes':
■ Real Time mode. The page continuously refreshes,
presenting up-to-date network information.
■ Time Filter. The page presents network information valid for
the time defined in a Time Filter but invalid in real time. See
Filtering to Access Specific Information on page 147 for
information about time filters.
Map The tab’s page lets you:

■ Assess at a glance the enterprise network's global
distribution
■ Filter
The page features two 'modes':
■ Real Time mode. The page continuously refreshes,
presenting up-to-date network information.
■ Time Filter. The page presents network information valid for
the time defined in a Time Filter but invalid in real time. See
Filtering to Access Specific Information on page 147 for
information about time filters.
Devices The tab lets you:

■ Add a network component:
■ Perform a device action
■ Show device
Links Lets you add, edit or delete links.
Sites Lets you:

■ add a set of endpoints based on a network subnet
■ edit or delete the SIP clients (phones)
- 18 -
Endpoints From the tab's drop-down you can select:

■ Status. Lets you view and monitor the status (Quality of
Experience) of phones (for example).
■ Configuration. Lets you directly access the Device Manager
to configure phones.
Alarms Active Always displays all the active alarms in the network, in real
time.
Journal Displays only the operator activity alarms in the network.
History Displays time frame historical alarms (default), according to the

filter.
Forwarding For detailed information about forwarding alarms, see Filtering

by 'Alarm Names' on page 167.
Statistics Devices Displays the Devices Statistics page. Filters on the page allow
operators to specify which call quality metrics to display. Quick
access to specific information lets operators quickly and
effectively maximize users' QoE.
Links Displays the Links Statistics page. Filters on the page allow
operators to specify
■ which call quality metrics to display (Successful/Failed
Streams, Max Concurrent Streams, Streams Quality
Utilization Distribution, Avg Call Duration (ACD), MOS,
Packet Loss, Jitter, Delay and Echo)
■ which links to display (per Topology or Time Range)
Quick access to specific information lets operators quickly and
Sites Displays the Sites Statistics page. Filters on the page allow
operators to specify
■ which sites to display (per Topology or Time Range)
Endpoints Displays the Endpoints Statistics page. Filters on the page

allow operators to specify
■ which endpoints to display (per Topology or Time Range)
- 19 -
PM Profiles Facilitates setup of Performance Monitoring capability.
Reports Provides operators with essential reports-generation capability

which they can utilize to distribute session experience data and
comparative analyses quickly and effectively to responsible
persons within the enterprise, and to external authorities
associated with the enterprise's network, for accurate
diagnosis and correction of degraded sessions and for general
network optimization. Opens in another Web page.
Calls Calls List Displays the Calls List page which presents all the calls made
in the enterprise. Filters allow operators to specify which calls
to display (Topology, Time Range, Source Type, Quality, etc.).
Quick access to specific information allows operators to
quickly and effectively maximize users' QoE.
QoE Lets you apply QoE Threshold profiles for voice quality metrics
Thresholds (MOS, Delay, Packet Loss, Echo and Jitter). A QoE Threshold
profile consists of threshold values set for each of these
metrics for the 'Poor', 'Fair' and 'Good' call quality categories.
QoE Status & Lets you configure Quality Alarms which are automatically
Alarms triggered and displayed in the Alarms page if the quality
analyzed falls below that defined in the rules. Also lets you
determine the status of the voice quality per entity.
Users Users Exper- Calls Count, Total Duration, Success / Failed, Call Quality,
ience MOS, Jitter, Delay, and Packet Loss.
Gives operators network health monitoring capability, including
alarms and diagnostics. Used to maximize the quality of
experience (QoE) of end users in the network.
User Details Displays contact information about the end users: Full Name,
User Name, Description, Department, Office, Mobile, Home,
MS Skype for Business Line URI, Email, Server, Country.
Filters allow quick access to specific users. These filters
impact the Users Experience page (see previous), so operators
can specify which users whose calls quality of experience they
want to assess.
Active Dir- Lets you add an AD. Displays existing ADs. Allows you to edit
ectories and to synchronize with the AD server.
System Administration Allows performing administration:

■ License
✔ Configuration
✔ Tenants Allocations
✔ Floating License
■ Security
✔ Authentication
✔ Operators
■ OVOC Server
- 20 -
Configuration Allows performing OVOC administration:

■ Templates (SNMP Connectivity, HTTP Connectivity, QoE
Thresholds, QoE Status & Alarms, Perf Monitoring)
■ Alarms
■ File Manager (Software Manager)
■ External Applications
■ Device Backup
Tasks Only displays asynchronous actions performed by the OVOC

operator.
Hovering Over a Cluster to Display Information

When more than 200 devices and sites (aggregated) are defined, the Network Topology page will
automatically be displayed in clusters, reducing clutter and improving operational efficiency. The
Show Clusters button is displayed only when fewer than 200 devices and sites (aggregated) are
defined. When the clusters feature is activated, you can hover over a cluster for this pop-up to be
displayed:
Figure 2-6: Devices
The pop-up indicates the number of errors and warnings in the cluster. The pop-up also displays the
entities in the cluster. Click an entity in the list to view information about it in a Device Details pane
on the right side of the Network Topology screen (see the Device Details).
The 'Search by name' field enables you to enter the name or - a part of the name - of an entity to
search for in the cluster. In large deployments with hundreds of entities, this feature can help
operators quickly access a specific entity and view information about it.
Figure 2-7: Search by name
- 21 -
Figure 2-8: Device Details
Hovering Over a Device to Display Information

The following figure shows an example of information displayed when hovering over a device.
■ The pop-up displays a summary of device information and statuses.

■ The lower bar displays icons for actions that can be performed on the device; icons displayed
depend on device type.
- 22 -
Hovering over a Link to Display Information

The following figure shows an example of information displayed when hovering over a link.
■ The pop-up displays a summary of link information and statuses.

■ The lowermost bar displays icons of actions that can be performed on the link; icons displayed
depend on entity type.
Returning to 'Home' Page by Clicking the AudioCodes Logo

Each page of the OVOC displays the AudioCodes logo in the uppermost left corner:
■ The logo functions as a 'Home' page button.

■ Click it to return to the Network Topology page from any page.
■ The feature enhances quick and operator-friendly navigation in the OVOC.
Getting Acquainted with the Network Map Page

The Network Map page ( Network > Map ) allows operators to determine at a glance the
geographical global distribution of the enterprise's IP telephony network.
Figure 2-9: Network Map Page
- 23 -
With the exception of cluster icons, entity icons in the Network Map page are identical to those in
the Network Topography page described in the table in Getting Acquainted with the Network
Topology Page on page 10. A cluster is based on geographical locations of devices in the Network
Map page. Clusters show aggregated numbers of devices . Cluster status is unrelated to region
and/or tenant status. Region and/or tenant status are only reflected in the Network Map tree and
Network Topology tree. Selecting a tenant in the Network Map page's tree impacts the Network
Map page in the same way as selecting a tenant in the Network Topology page's tree.
Table 2-4: Cluster Icons in the Network Map Page
Cluster
Description
Icon
Cluster status is Error when the status of at least one device or site is Error. Click a
cluster to zoom in and view the entities under it.
Cluster status is Warning when the management status of at least one device or site
is Warning. Click a cluster to zoom in and view the entities under it.
Cluster status is OK when the management status of all devices and sites is OK or
Unmonitored. Click a cluster to zoom in and view the entities under it.
Cluster status is Unmonitored when the management status of all devices and sites
is Unmonitored. Click a cluster to zoom in and view the entities under it.
The only difference between Network Map page and the Network Topology page is that in the
Network Map page there is no Show Grid button. All other buttons are the same. You can hover
your cursor over a network entity in the Network Map page to determine its details:
Figure 2-10: Hovering the Cursor over a Network Entity in the Network Map Page
In the pane on the right side of the Network Map page, the Network Summary lets you:
■ Determine on how many Devices, Links, Sites and Endpoints, alarms are active.
■ Determine which Devices, Links, Sites and Endpoints' status is currently Error / Warning (from
the color-coded number). If you click the color-coded number of:
● Devices then the Device Management page opens displaying all devices whose status is
Error / Warning
● Links then the Links page opens displaying all links whose status is Error / Warning
● Sites then the Sites page opens displaying all sites whose status is Error / Warning
● Endpoints then the Endpoints page opens displaying all endpoints whose status is Error /
Warning
- 24 -
Figure 2-11: Example: Endpoints - 99 Warnings
The Active Alarms pane allows you to determine the total number of Critical, Major, Minor and
Indeterminate active alarms (color-coded) currently active in the network. Click any severity level's
total to display only alarms of that severity level in the Alarms page. Example: Under Minor in the
Active Alarms pane above, click 34:
Figure 2-12: Alarms Filtered by Severity Level
In the Active Alarms pane, you can select an alarm in the page to view detailed information about it
in the All Alarm Details pane on the right side of the page.
In the Network Summary window, the Devices | Links | Endpoints tabs display the:
● total # of calls over devices | streams over links | calls over endpoints.
● maximum # of concurrent calls over devices | streams over links.
● average MOS measured over devices | links | endpoints in the network.
● average Jitter measured over devices | links | endpoints in the network.
● average Delay measured over devices | links | endpoints in the network.
● average Packet Loss measured over devices | links | endpoints in the network.
The Quality Distribution pie chart in the Network Summary window allows you to point your cursor
over a green, yellow or red segment; a pop-up indicates the # and % of calls over devices | streams
over links | calls over endpoints in the network whose quality was measured to be good, fair or poor
respectively:
- 25 -
Click any color-coded voice quality segment to open the Calls List filtered by that voice quality
score (Good, Fair or Poor).
The Successful/Failed Streams pie chart in the Network Summary window allows you to point your
cursor over a green or red segment; a pop-up indicates the # and % of calls over devices | streams
over links | calls over endpoints in the network whose performance was measured to be successful
or failed respectively:
Click any color-coded segment to open the Calls List filtered by that call performance evaluation
(Successful or Failed).
- 26 -
Configuring Operator Authentication

Authentication of OVOC operators can be configured in three ways:
■ Centrally, using an LDAP-compliant server such as Microsoft Active Directory (AD) (see
Configuring Operator Authentication Centrally using an LDAP Server on the next page)
■ Centrally, using a RADIUS server (see Configuring Operator Authentication Centrally with a
RADIUS Server on page 31)
■ Locally, in the OVOC (see Configuring Operator Authentication Locally, in the OVOC on
page 34)
The following figure shows the three different operator authentication options.
Figure 2-13: OVOC Operator Authentication Options
For operator authentication, it's recommended to implement a third-party LDAP or RADIUS server
in the network. When attempting to log in to the OVOC, the OVOC server then verifies the login
username and password with the AD server or RADIUS sever. Usernames, passwords and
access-level attributes are stored externally on these platforms. The OVOC server in this case
doesn't store the username and password for these users (they're not displayed in the OVOC
Users List) but but verifies them with the external authentication server.
- 27 -
Configuring Operator Authentication Centrally using an LDAP

Server
Authentication of OVOC operators can be centrally configured using a Lightweight Directory
Access Protocol (LDAP) server. If you already have centralized user authentication via an LDAP
server, it's recommended to implement it for OVOC operators as well. When an LDAP-
authenticated operator logs into the OVOC, they're assigned one of the OVOC's security levels,
e.g., 'Operator'. The equivalent names for these security levels on the LDAP server are shown
following. When one of these security levels is not defined on the LDAP server, the OVOC by
default allows access to the LDAP-authenticated operator with 'Operator' permissions.
➢ To centrally configure authentication of OVOC operators using an LDAP server:

1. In the OVOC, open the Authentication page (System > Administration > Security >
Authentication).
2. From the 'Authentication Type' drop-down, select LDAP.
Figure 2-14: Authentication - LDAP
3. Configure the 'LDAP Authentication Server IP'.

4. Configure the 'LDAP Authentication Server Port'.
5. Configure the 'LDAP Connectivity DN' parameter using an Active Directory Service Account
(mandatory), for example, MyServiceAccount@domain.
6. Configure the 'LDAP Connectivity Password' as required.
7. In the 'LDAP Server Number of Retries' field, enter the number of login attempts the operator
can make before they're suspended. When the number is reached, the operator is blocked.
Only the 'system' operator whose security level is 'Administrator' can then unblock them.
Default: 3 attempts.
8. Configure the 'User DN Search Base' as required.
9. Select the 'SSL' option to secure the connection with the LDAP server over SSL; the
'Certificate' drop-down is activated.
10. From the 'Certificate' drop-down (activated only if 'SSL' is selected), select the certificate file
that you want to use to secure the connection with the LDAP server over SSL.
● Not selected (Default). The connection with the LDAP server is non-secured.
- 28 -
● SSL With Certificate: An HTTPS connection between the OVOC and the LDAP server is
opened. The OVOC authenticates the SSL connection using a certificate. Make sure you
load the SSL certificate file, required by the LDAP Active Directory platform, to the
Software Manager. See Adding Configuration Files to the OVOC's Software Manager on
page 72.
Authorization Level Settings
When an operator connects to the OVOC, the OVOC (before allowing the operator
access) checks with the LDAP server if the User Group which the operator is
associated with in the OVOC, is defined in the LDAP server.
● The parameters below are used to define a User Group in the LDAP server.
● In the Tenant Details screen under the Multitenancy tab, the parameter 'LDAP
Authentication: Group Name' is used to define a User Group in the OVOC when a
tenant level is provisioned (see under Adding a Tenant on page 85).
If the LDAP validates OVOC's query, the operator is authenticated and allowed access.
Operators who are both 'System' and 'Tenant' type are checked in this way. See also
Adding a 'System' Operator on page 37 and Adding a 'Tenant' Operator on page 43.
11. In the 'System Administrator User Group Name' field, enter the name of the User Group of the
'System' type operator whose security level is 'Administrator'.
12. In the 'System Operator User Group Name' field, enter the name of the User Group of the
'System' type operator whose security level is 'Operator'.
13. In the 'System Monitor User Group Name' field, enter the name of the User Group of the
'System' type operator whose security level is 'Monitor'.
14. In the 'Tenant Administrator User Group Name' field, enter the name of the name of the User
Group of the 'Tenant' type operator whose security level is 'Administrator'.
15. In the 'Tenant Operator User Group Name' field, enter the name of the User Group of the
'Tenant' type operator whose security level is 'Operator'.
16. In the 'Tenant Monitor User Group Name' field, enter the name of the name of the User Group
of the 'Tenant' type operator whose security level is 'Monitor'.
17. In the 'Tenant Monitor Links User Group Name' field, enter the name of the User Group of the
'Tenant' type operator whose security level is 'Monitor Links'. When an LDAP operator is then
assigned to this group, they're logged in as a 'Tenant' type operator with a security level of
'Monitor Links'. Only ‘System’ type operators can configure this group; ‘Tenant’ type operators
can only view it.
18. From the 'Default Operator Type and Security Level' drop-down, select:
19. Select the Use LDAP Credentials for Device Page Opening option for the OVOC to sign
operators in to AudioCodes devices using the same credentials they used to sign in to the
OVOC. The AudioCodes device will then perform authentication with the LDAP server.
- 29 -
20. Under Combined Authentication Mode, select the Enable combined authentication option,
the 'Authentication Order' drop-down is enabled from which External First or Local First can
be selected.
If Enable combined authentication is selected and an operator attempts to log in to the
LDAP server but it's unavailable, the OVOC connects to the local database with the same
operator credentials.
● External First: If the LDAP server is unavailable when the LDAP-authenticated operator
attempts to log in, the OVOC connects with the same operator credentials to the local
(OVOC) operators database.
● Local First: If the operator is not found in the local (OVOC) operators database, the
OVOC connects with the same operator credentials to the LDAP server.
21. Click Submit.
- 30 -
Configuring Operator Authentication Centrally with a RADIUS

Server
You can centrally configure authentication of OVOC operators using a RADIUS (Remote
Authentication Dial-In User Service) server. If you already have centralized user authentication via
a RADIUS server, it's recommended to implement it for OVOC operators as well.
When the RADIUS-authenticated operator logs into the OVOC, they're assigned one of the OVOC
security levels - for example - 'Operator'. If it's not defined on the RADIUS server, the OVOC by
default allows access for the RADIUS-authenticated operator, with 'Operator' permission.
➢ To centrally configure authentication of OVOC operators using a RADIUS server:

1. Open the Authentication page (System > Administration > Security > Authentication) and
from the 'Authentication Type' drop-down, select RADIUS.
Figure 2-15: Authentication - RADIUS
2. Configure the parameters:

● 'RADIUS retransmit timeout' (Default: 3000 milliseconds). If this timeout expires, local
authentication is performed.
● 'RADIUS auth number of retries' (Default: 1)
Note that these parameters will be used for each RADIUS Server.
3. Select the Enable display of RADIUS reply message option. Default: Cleared.
4. From the 'Default Authentication Level' drop-down, select either Operator (default), Amin,
Monitor or Reject.
5. For each of the three RADIUS servers, define the server's IP address, port and secret. At least
one server must be provisioned. 'Server Secret' defines the shared secret (password) for
authenticating the device with the server. Must be cryptically strong. Also used by the server to
verify authentication of RADIUS messages sent by the device (i.e., message integrity). See
the device's manual for more information.
6. Select the Use RADIUS Credentials for Device Page Opening option for the OVOC to sign
operators in to AudioCodes devices using the same credentials they used to sign in to the
OVOC. The AudioCodes device will then perform authentication with the RADIUS server.
7. Under Combined Authentication Mode, select the Enable combined authentication option,
the 'Authentication Order' drop-down is enabled from which External First or Local First can
be selected.
If Enable combined authentication is selected and an operator attempts to log in to the
RADIUS server but it's unavailable, the OVOC connects to the local database with the same
operator credentials.
- 31 -
● External First: If the RADIUS server is unavailable when the RADIUS-authenticated

operator attempts to log in, the OVOC connects with the same operator credentials to the
local (OVOC) operators database.
● Local First: If the operator is not found in the local (OVOC) operators database, the
OVOC connects with the same operator credentials to the RADIUS server.
8. Click Submit.
Viewing Operator Authentication in the Application Information

Window
When OVOC operator authentication is performed centrally using an LDAP-compliant server or a
RADIUS-compliant server, then after the LDAP-authenticated operator or RADIUS-authenticated
operator logs in to the OVOC, the application information window displays the operator's
authentication type.
The application information window always displays operator security level irrespective of how
authentication is performed.
- 32 -
Testing Connectivity with the LDAP / RADIUS Server

The OVOC allows you to test the settings you configured in the LDAP/RADIUS pages to make
sure your configuration is correct and that connectivity with the server has been established.
➢ To test the settings you configured in the LDAP/RADIUS pages:

1. In the LDAP or RADIUS authentication page, scroll down to Test Connectivity.
Figure 2-16: Test Connectivity
2. Click Test Connectivity; if prompted that the connection was successful, you configured the
page correctly; if not, you need to check the settings you configured.
3. [Optional] To test connectivity with a specific operator authentication:
● Select the option Test Connectivity with Username and Password and then enter an
operator's name in the 'User Name' field and their password in the 'Password' field.
● Click Test Connectivity; if the operator's credentials are recognized, you're prompted that
the connection was successful.
- 33 -
Configuring Operator Authentication Locally, in the OVOC

You can configure authentication of operators locally, in the OVOC. The feature allows the operator
with 'Administrator' security level to control other operators' access to system resources. In this
way, sensitive system information cannot be accessed without appropriate authorization, and
managed system elements cannot be disrupted by inexpert operators.
➢ To locally configure authentication of operators:

1. In the OVOC, open the Authentication page (System > Administration > Security >
Authentication).
2. From the 'Authentication Type' drop-down, select OVOC.
Figure 2-17: Authentication – OVOC
3. Configure the authentication parameters using the following table as reference.

Table 2-5: OVOC Authentication Parameters
Parameter Description
Number of login attempts Lets you configure the number of login attempts attempted by
before blocking the operator before the OVOC application blocks them.
When the number of login attempts is reached, the operator
is blocked from logging into the OVOC. Only the
Administrator can then unblock the suspended operator.
Default: 3 attempts.
Max number of simultaneous Lets you configure up to how many operator login sessions
login sessions can be performed simultaneously. Default: 5
- 34 -
Notifications display time Lets you configure for how long (in seconds) the notifications
(sec) pop-up window is displayed after performing tasks such as
adding a device or when alarms are received. Default: 3
seconds. Setting the parameter to 0 prevents notifications
from being displayed. All notifications are cleared from the
OVOC server after twenty minutes. See also Forwarding
Alarms whose Destination Type is 'Notification' on page 181.
Minimum password length Default: 8 characters. Maximum supported: 30 characters.
Non repetitive characters # Default: 0. Maximum supported: 10 characters.

from previous password
Password complexity rules From the drop-down, select either:

■ No complexity rules are applied (default)
■ Use Plain or Capital letters, Digits and Special
Characters
■ Use Plain and Capital letters, Digits and Special
Characters
Number of not reused previous Default: 5. Possible values: 0-10.

passwords
Dictionary check for password Select this option for the OVOC server to perform a
cracking simplicity password weakness check on the OVOC operator's
password.
Default: Disabled (unselected).
Enable Password Expiration Select the option to extend the password expiration; the
Extension following two parameters are activated.
Number of Additional Logins Defines the number of logins operators can perform after their
(after Password Expired) password expires. Range: 1-10.
Additional Logins Time Period Defines the period (in days) during which the operator can
(days) perform the number of additional logins defined with the
previous parameter. Range: 1-60.
- 35 -
Adding an Operator
You can add an operator to the OVOC. The operator can be of type:
■ 'Tenant' - or-
■ 'System'
The following table shows the capabilities permitted for each OVOC operator type and security
level. OVOC operators are allocated a security level of either Admin, Operator or Monitoring.
Table 2-6: Capabilities Allowed for Each Operator Type / Security Level
Manage Manage Monitor Monitor

Op Security Define Manage
system tenant system tenant
Type Level ops tenants
resources resources resources resources
System Admin Yes, all Yes Yes Yes Yes Yes

op
types
and
security
levels
Operator No No Yes Yes Yes Yes
Monitor No No No No Yes Yes
Tenant Admin Yes, in No No Yes, in No Yes

their their own
own 'tenant'
'tenant'
Operator No No No Yes, in No Yes

their own
'tenant'
Monitor No No No No No Yes
Tenant No No No No No Links
Monitor only
Links
How Multi Tenancy Impacts Operator Capabilities

The impact of multi tenancy architecture on the capabilities of OVOC 'system' operators is different
to its impact on OVOC 'tenant' operators.
Here are some examples that will help you deduce the principle. Use the table shown in Adding an
Operator above as reference. Examples also show how operator security level impacts the
capabilities of 'system' operators and 'tenant' operators.
■ A 'system' operator with a security level of 'Admin' will be permitted every capability.
■ A 'tenant' operator with a security level of 'Monitoring' will not be permitted any capability
except to monitor their own resources.
■ In the OVOC's Software Manager:
● A 'system' operator can add | delete files.
● A 'tenant' operator can only use files.
- 36 -
● A 'tenant' operator with Admin security level, however, can add | delete files if the files only
belong to that specific tenant and only devices in that tenant use them.
■ A 'system' operator with Admin security level can allocate licenses to tenants.
A 'tenant' operator with Admin security level can only distribute sessions within their own
tenant, across that tenant's devices, from that tenant's License Pool. A 'tenant' operator
cannot manage licenses for multiple tenants like a 'system' operator with Admin security level
can.
■ Multi-Tenancy impacts what operators view on OVOC pages. In the Network Topology page,
for example:
● a 'tenant' operator with a Monitoring security level will only see part of the network.
● A 'tenant' operator with Admin security level will only see network entities they are
permitted to see.
● A 'system' operator with an Admin security level will see all tenants and all devices under
each tenant.
Adding a 'System' Operator

You need to add a 'system' operator to the OVOC. The 'system' operator is typically the ITSP
administrator whose network features multi-tenancy architecture and whose OVOC application
provides management services to multiple enterprise customers (tenants) in their network. The
'system' operator can also be an enterprise network administrator whose network does not feature
multi-tenancy architecture but whose OVOC application enables management of the enterprise's
distributed offices ('tenants').
Only a 'system' operator with a security level of 'Admin' can perform tenant man-
agement operations (Add/Remove/Update).
➢ To add a 'system' operator:

1. In the OVOC, open the Operators page (System > Administration > Security > Operators).
2. Click Add and then select System Operator from the drop-down menu.
- 37 -
Figure 2-18: 'System' Operator Settings - Basic Info
3. Configure the new operator's basic information using the following table as reference. The
screen displays basic operator information and security settings.
Table 2-7: 'System' Operator Settings - Basic Info
User Name Enter the operator's name. Must be unique.
Password Enter the operator's password.
Confirm Confirm the operator's password.

Password
User Type [Read-only] System or Tenant depending on what you selected in step 2.
Security From the drop-down select:

Level ■ Monitoring (lowest security level)
■ Operator (medium security level)
■ Admin (highest security level)
- 38 -
■ Monitoring Links (Applicable only when adding a 'Tenant' type operator in a

deployment whose architecture is ITSP customer multi-tenant architecture -
see ITSP Customer Multi-Tenant Architecture on page 5. When adding this
operator to links, all links must have the same source SBC - except when
using LDAP authentication - and the links’ source and destination devices
must be in the operator’s tenant. Only SBC device links are supported;
Skype, SmartTAP, UMP and CloudBond links are not supported. The
operator will only be able to monitor information related to QoE (calls,
statistics and link alarms).
Valid IPs to Enter IP addresses of devices from which this operator will be allowed to log in.
Login From Login from any other IP address will be disallowed.
Full Name Enter the operator's full name. Facilitates more effective management of
operators.
Phone Enter the operator's phone number. Facilitates more effective management of
operators.
Email Enter the operator's email. Facilitates more effective management of operators.
Description Enter any information likely to facilitate more effective management of OVOC
operators.
4. Click Advanced Info.
- 39 -
Figure 2-19: 'System' Operator Settings – Advanced Info
5. Configure the new 'system' operator's advanced information using the following table as
reference. The screen displays advanced account and password settings.
Table 2-8: 'System' Operator Settings – Advanced Info
Suspend User Select this option to suspend the 'system' operator.
Suspension [Only available when 'Suspend User' is checked] Enter a reason

Reason explaining why the operator is suspended.
Suspension Time [Only available when 'Suspend User' is checked] Enter the time at which
the operator is suspended.
Account If the operator does not log into the OVOC for the number of days
Inactivity Period specified, their account will be suspended. Maximum: 10 days. Default: 0
(Days) (The operator can log into the OVOC at any time irrespective of how long
they've been logged off; even if they haven't logged in for an excessive
period of time their account will not be suspended).
- 40 -
Session Inactivity Defines how long an OVOC GUI page remains accessible despite
Period (Minutes) operator inactivity. If the period times out, the page locks and the operator
is prompted to reenter their password to re-access it; the same page that
the operator was on before the period timed out then opens. After the
operator logs in to the GUI, every time they interact with it, e.g., by
clicking a menu, the timer is reset.
Default: 0 (the GUI is always accessible irrespective of operator
inactivity).
Session Leasing Enter the session leasing duration, in hours. If it expires, the application
Duration (Hours) will close the client session / force the operator to reenter their password
in order to re-access the application. Default: 0 (the session leasing
duration will never expire and the application will never close the client
session). Note that the Device Manager inherits the value configured.
Password Update Specify a period, in hours. The operator's password cannot be changed
Min Period more than once within the period specified.
(Hours) Default: 24 hours. If 0 is specified, the password can be changed an
unlimited number of times, unrestricted by period.
Password Specify a period, in days. The operator's password must be changed

Validity Max within this number of days after the last password change. Default: 90
Period (Days) days. If 0 is specified, the password can be changed an unlimited number
of times, unrestricted by period, after the last password change.
Password Specify the number of days. The operator will receive a warning message
Warning Max this number of days before the date on which the password expires.
Period (Days) Default: 7 days (i.e., the operator will receive a warning message a week
before their password expires). If 0 is specified, the operator will receive
warning messages irrespective of the date on which the password
expires.
Allowed Login Provides the capability to define the number of login attempts the operator
Attempts can make before they're suspended, per operator. Enhances operator
security management.
6. Click OK. The operator is added to the OVOC.
- 41 -
Editing a 'System' Operator

You can edit the details of a 'system' operator if they change.
➢ To edit the details of a 'system' operator:

1. Open the Operators page (System > Administration > Security > Operators).
2. Select the 'system' operator whose details you need to edit and then click Edit; the Operator
Settings screen opens.
3. Edit the operator's details using the table as reference.
Deleting a 'System' Operator

You can remove a 'system' operator from the OVOC.
➢ To remove a 'system' operator:

2. Select the 'system' operator to remove and then click Delete.
Deleting Multiple Operators

You can delete multiple operators from the OVOC simultaneously.
➢ To delete multiple 'system' operators simultaneously:

2. Select the operators to remove and then click Delete.
Suspending a 'System' Operator

You can suspend a 'system' operator from the OVOC.
➢ To suspend a 'system' operator:

2. Select the 'system' operator to suspend and then click Actions.
3. From the drop-down, select Suspend; the operator is automatically logged out before
suspension.
Releasing a Suspended 'System' Operator

You can release a 'system' operator who was previously suspended from the OVOC.
➢ To release an operator who was previously suspended from the OVOC:

2. Select the suspended operator to release and then click Actions. Multiple operators can be
selected for release from suspension.
3. From the drop-down, select Release.
Forcing a Password Change

You can force an operator to change their password. The feature can be used if for example you
suspect information has been stolen from the enterprise.
- 42 -
➢ To force a password change:

2. Select the operator whose password to change and then click Actions. Multiple operators can
be selected.
3. From the drop-down, select Force Password Change.
The operator is automatically prompted to change their password the next time they log
in.
Forcing an Operator Logout
Applies only to OVOC operators with 'Admin' security level. See Adding an Operator on
page 36 for an explanation of the different security levels.
An OVOC operator with 'Admin' security level can force an active operator to be logged out, con-
forming to established management application standards. The operator with 'Admin' security level
may (for example) need to urgently remove an active operator before another mistake is made and
more damage is done.
➢ To force an active operator to be logged out:

Figure 2-20: Operators page
2. Select the active operator to log out; their 'Active' status is indicated in the Status column.
3. From the now enabled 'Actions' drop-down, select Force Logout.
4. Click Force Operator Logout to implement the action.
Adding a 'Tenant' Operator

You can add a 'tenant' operator to the OVOC. A 'tenant' operator is typically an enterprise's network
administrator whose network does not feature multi- tenancy architecture and whose OVOC
application enables management of the enterprise's distributed offices.
Only a 'system' operator with a security level of 'Admin' can perform 'tenant' man-
agement operations (Add/Remove/Update/Clone/Suspend.
- 43 -
➢ To add a 'tenant' operator:

1. In the OVOC, open the Operators page (System > Administration > Security > Operators).
2. Click Add and then select Tenant Operator from the drop-down menu.
Figure 2-21: 'Tenant' Operator Details – Basic Info
3. Configure the 'tenant' operator's basic info using the table 'System Operator Settings –
Advanced Info' as reference.
4. Click Advanced Info.
- 44 -
Figure 2-22: 'Tenant' Operator Details – Advanced Info
5. Configure the 'tenant' operator's advanced information using the following table as reference.
The screen displays advanced account and password settings.
Table 2-9: 'Tenant' Operator Settings – Advanced Info
Suspend User Select this option to suspend the 'system' operator.
Suspension Reason [Only available when 'Suspend User' is checked] Enter a reason
explaining why the operator is being suspended.
Suspension Time [Only available when 'Suspend User' is checked] Enter the time
at which the operator is being suspended.
Account Inactivity Period If the operator does not log into the OVOC for the number of days
(Days) specified, their account will be suspended. Maximum: 10 days.
Default: 0.
Session Inactivity Period Enter the session inactivity period, in minutes. If it expires, the
(Minutes) application will close the client session / force the operator to
reenter their password in order to reaccess the application.
Default: 0.
Session Leasing Duration Enter the session leasing duration, in hours. If it expires, the
(Hours) application will close the client session / force the operator to
reenter their password in order to reaccess the application.
Default: 0.
- 45 -
Password Update Min Specify a period, in hours. The operator's password cannot be
Period (Hours) changed more than once within the period specified.
Default: 24 hours.
Password Validity Max Specify a period, in days. The operator's password must be
Period (Days) changed within this number of days after the last password
change. Default: 90 days.
Password Warning Max Specify the number of days. The operator will receive a warning
Period (Days) this number of days before the date on which the password
expires. Default: 7 days (i.e., the operator will receive a warning
message a week before their password expires).
Allowed Login Attempts Provides the capability to define the number of login attempts the
operator can make before they're suspended, per operator.
Enhances operator security management.
6. Click Tenants.
Figure 2-23: 'Tenant' Operator Settings – Tenants
7. [The screen is only available for the 'tenant' operator]. From the 'Assigned Tenant' drop-down,
select a tenant for this operator from the list of tenants defined in the server. Multiple tenants
can be selected.
- 46 -
Figure 2-24: 'Tenant' Operator Settings – Tenant Assigned
8. Click OK; the tenant/s is/are assigned.
Editing a 'Tenant' Operator

You can edit the details of a 'tenant' operator if they change.
➢ To edit the details of a 'tenant' operator:

2. Select the 'tenant' operator whose details you need to edit and then click Edit; the Operator
Settings screen opens.
3. Edit the operator's details using the table describing the 'tenant' operator's advanced
information as reference.
Deleting a 'Tenant' Operator

You can remove a 'tenant' operator from the OVOC. After removal, the OVOC deletes the 'tenant'
operator's entities, frees its portion of license resource, and detaches any operator attached to it.
➢ To remove a 'tenant' operator:

2. Select the 'tenant' operator to remove and then click Delete.
- 47 -
Deleting Multiple Operators

You can delete multiple operators from the OVOC simultaneously. After deleting, the OVOC
deletes the operators' entities, frees their portion of license resource, and detaches any attached
operators.
➢ To delete multiple operators simultaneously:

2. Select the operators to remove and then click Delete.
Suspending a 'Tenant' Operator

You can suspend a 'tenant' operator from the OVOC.
➢ To suspend a 'tenant' operator:

2. Select the 'tenant' operator to suspend and then click Actions. Multiple operators can be
selected for release from suspension.
3. From the drop-down, select Suspend; the operator is automatically logged out before
suspension.
Releasing a Suspended 'Tenant' Operator

You can release a 'system' operator who was previously suspended from the OVOC.
➢ To release an operator who was previously suspended from the OVOC:

2. Select the suspended operator to release and then click Actions.
3. From the drop-down, select Release.
Forcing a Password Change

You can force an operator to change their password. The feature can be used if for example you
suspect information has been stolen from the enterprise.
➢ To force a password change:

2. Select the operator whose password to change and then click Actions. Multiple operators can
be selected.
3. From the drop-down, select Force Password Change.
The operator is automatically prompted to change their password the next time they log
in.
Forcing an Operator Logout
Applies only to OVOC operators with 'Admin' security level. See Adding an Operator on
page 36 for an explanation of the different security levels.
- 48 -
An OVOC operator with 'Admin' security level can force an active operator to be logged out, con-
forming to established management application standards. The operator with 'Admin' security level
may (for example) need to urgently remove an active operator before another mistake is made and
more damage is done.
➢ To force an active operator to be logged out:

Figure 2-25: Operators page
2. Select the active operator to log out; their 'Active' status is indicated in the Status column.
3. From the now enabled 'Actions' drop-down, select Force Logout.
4. Click Force Operator Logout to implement the action.
- 49 -
CHAPTER 3 Configuring Global (System) Settings OVOC | User's Manual
3 Configuring Global (System) Settings

After logging in, configuring operator authentication and then adding an operator, you can configure
the settings under the OVOC's System menu. These are the OVOC's global settings. They are
system-wide, as opposed to per tenant.
Three tabs are displayed under the System menu: Administration, Configuration and Tasks. The
following table describes the tabs, folders and items under the System menu.
Table 3-1: System Menu
Tab Folder Item Description
Administration License Configuration See Making Sure your License Provides the
Capabilities you Ordered on page 52 for
details.
Tenants See Allocating Licenses to Tenants on

Allocation page 53 for details.
Floating See under Managing SBC Licenses on

License page 122 for details.
Security Authentication Lets you configure LDAP/RADIUS

authentication. See Configuring Operator
Authentication on page 27 for details.
Operators Lets you add operators to the OVOC.

See Adding an Operator on page 36 for
details.
OVOC Status Lets you view information about the status of

Server the OVOC server
Info Lets you view information about the OVOC

server
Configuration Lets you configure the general OVOC server

settings. See Securing Connections with
FQDN or IP Address on page 57.
- 50 -
Tab Folder Item Description
Configuration Templates SNMP See SNMP Connectivity on page 63 for

Connectivity details.
HTTP See HTTP Connectivity on page 65 for

Connectivity details.
QoE See QoE Thresholds on page 65 for details.

Thresholds
QoE Status & See QoE Status and Alarms on page 67 for
Alarms details.
Perf See Adding a PM Profile on page 193 for

Monitoring details.
Alarms See Configuring Alarms Settings on page 69

for details.
File Software See Adding Configuration Files to the

Manager Manager OVOC's Software Manager on page 72 for
details.
External Applications See Connecting Directly to External

Applications on page 76 for details.
Device Backup See Enabling Automatic Device Backup

Periodically on page 80 for details.
Tasks See Tasks tab on page 81 for details.
Administration tab
Under the Administration tab's License folder you can view a summary of your license and
allocate licenses to tenants. See Making Sure your License Provides the Capabilities you Ordered
on the next page for more information.
Under the Administration tab's Security folder you can define authentication and add operators.
See Allocating Licenses to Tenants on page 53 for more information.
Loading the OVOC Server License

Before Version 7.6.1000, the OVOC Server License could only be loaded to the server using the
EMS Server Manager, described in the One Voice Operations Center IOM Manual. For operators'
convenience, the OVOC Server License as of Version 7.6.1000 can also be loaded from the OVOC
GUI to the OVOC server after it is obtained as a file from AudioCodes.
Only a 'System' type operator whose security level is defined as 'Admin' can load the
OVOC server license. See Adding an Operator on page 36 for more information.
➢ To load the license:

1. Open the License Configuration page (System > Administration > License >
Configuration).
- 51 -
Figure 3-1: License Configuration
2. Click the Load License button and in the browser window that opens, navigate to the txt file
containing the license on your machine.
3. Click Open for the load to be performed.
● The license is provided without installation media. To activate the product, follow
the activation instructions described in the One Voice Operations Center IOM
Manual.
● The Alarms Journal displays the Load License action as a server action. The
Alarms Journal also displays the values of the new license and the name of the
operator who performed the action.
Making Sure your License Provides the Capabilities you Ordered

The License Configuration page allows you to view the details of the capabilities which the license
that you ordered covers. Use the page to make sure the license you purchased provides the
capabilities you ordered.
➢ To view the details of your license:

1. Open the License Configuration page (System > Administration > License >
Configuration).
- 52 -
Figure 3-2: License Configuration
The License Configuration page displays only the parameters that exist in the License
Key provided by AudioCodes.
2. Make sure the license you purchased provides the capabilities you ordered.
Allocating Licenses to Tenants

After adding tenants as described in Adding a Tenant on page 85, you can allocate licenses to them
manually if your network administrator changed the default dynamic automatic allocation (see
Dynamic Allocation of Endpoint Licenses on page 119). The Tenants Allocation page lets you
manually allocate licenses to tenants.
➢ To allocate licenses to tenants:

1. Open the Tenants Allocations page (System > Administration > License > Tenants
Allocations).
- 53 -
Figure 3-3: Tenants Allocations
2. Select the tenant to whom to allocate licenses and then click Edit.
Figure 3-4: Tenant Allocations Details
- 54 -
Only parameters in the License Key provided by AudioCodes are displayed.
3. In the Tenant Allocations Settings shown in the figures above, you can allocate:
● Under Fixed License Pool
◆ CB analog devices
◆ CB PBX users
◆ CB user sessions
◆ CB voicemail accounts
◆ SBC Registrations (SIP endpoints that can register with the SBC)
◆ SBC sessions (media and signaling)
◆ SBC Signaling sessions
◆ SBC Transcoding sessions
● Under Voice Quality
◆ Devices
◆ Endpoints
◆ Sessions
◆ Users
● Under Endpoints Management
◆ Endpoints
- 55 -
Authenticating Operators
The 'Security' folder's Authentication item lets you configure LDAP and RADIUS authentication.
See Configuring Operator Authentication on page 27 for detailed information.
The 'Security' folder's Operators item lets you add OVOC operators. See Adding an Operator on
page 36 for detailed information.
Determining OVOC Server Status

The Server Status page (System > Administration > OVOC Server > Status) lets you determine
at-a-glance status information about the OVOC server, including processes status and open ports
status. The feature saves operators from having to log in to the EMS Server Manager. The same
information is presented, only in friendlier format.
Figure 3-5: Server Status page
The Server Info page (System > Administration > OVOC Server > Info) presents information
about the OVOC server including hardware info, components versions, NTP info, security info and
network info. The feature saves operators from having to log in to the EMS Server Manager. The
same information is presented only in friendlier format.
- 56 -
Figure 3-6: Server Info page
See Securing Connections with FQDN or IP Address below for information about the Server Con-
figuration page (System > Administration > OVOC Server > Configuration).
Securing Connections with FQDN or IP Address

Operators can optionally secure SSL connections with an IP address (default) or with an FQDN
hostname.
Supported connections are:
■ Device - OVOC server
■ OVOC - LDAP Active Directory
➢ To implement the feature:

1. Open the Server Configuration page (System > Administration > OVOC Server >
Configuration).
Figure 3-7: Server Configuration
2. From the 'SBC Devices Communication' drop-down list, select either IP Based (default) or
Hostname Based.
- 57 -
Customizing Call Storage

The OVOC's Server Call Storage page allows operators whose security level is configured as ‘Sys-
tem’ to customize the storage of calls on the OVOC server according to successful calls and/or
failed calls (call performance) and the quality of the calls (good, fair/poor and/or unknown) in these
two categories.
Operators can furthermore customize whether to include or exclude call flow and/or call trend.
➢ To customize call storage:

1. Open the Calls Storage page (System > Administration > OVOC Server > Calls Storage).
Figure 3-8: Calls Storage
2. From the 'Calls Storage Level' drop-down, select either:

● Custom (default) (see the figure above for the configured settings)
● Minimal (see the following figure for the configured settings)
● Maximal (all settings are selected)
● Recommended (see the figure after the following for the configured settings)
- 58 -
Figure 3-9: Calls Storage Level - Minimal
Figure 3-10: Calls Storage Level - Recommended
3. Use the matrices below as reference.

Table 3-2: Custom
Include
Call Performance Call Quality Save Include Call Flow Quality
Trend
Success Good Yes No No
Success Not Good Yes No Yes

(fair/poor)
Success Gray Yes No No
- 59 -
Include
Trend
Fail Good Yes Yes No
Fail Not Good Yes Yes Yes

(fair/poor)
Fail Gray Yes Yes No
Table 3-3: Minimal
Include
Trend
Success Good No No No
Success Not Good Yes No No

(fair/poor)
Success Gray No No No
Fail Good Yes No No
Fail Not Good Yes No No

(fair/poor)
Fail Gray Yes No No
Table 3-4: Recommended
Include
Trend
Success Good Yes No No
Success Not Good Yes No Yes

(fair/poor)
Success Gray Yes No No
Fail Good Yes Yes No

(fair/poor)
Fail Gray Yes Yes No
- 60 -
Table 3-5: Maximal
Include
Trend
Success Good Yes Yes Yes
Success Not Good Yes Yes Yes

(fair/poor)
Success Gray Yes Yes Yes
Fail Good Yes Yes Yes

(fair/poor)
Fail Gray Yes Yes Yes
● If Custom is selected but settings are changed, the changed configuration is

preserved and displayed during the next login.
● A change to call storage settings does not impact calls already saved on the OVOC
server.
● All calls previously stored on the OVOC server are stored according to the
previously configured settings and cleared using regular call clearing policy (time or
size based).
See Customizing Maximum Storage Period on the next page
- 61 -
Customizing Maximum Storage Period

The OVOC's Server Call Storage page allows operators whose security level is configured as ‘Sys-
tem’ to customize the maximum number of days call-related information will be stored on the
OVOC server before it is cleared.
➢ To customize the maximum storage period:

1. Open the Calls Storage page (System > Administration > OVOC Server > Calls Storage)
and locate the 'Max Storage Period (Days)' section of the page.
Figure 3-11: Max Storage Period (Days)
● Calls are checked daily and cleared from the OVOC server based on the values
you configure.
● Default: 365 days (the maximum number of days call-related information can be
stored on the OVOC server before it's cleared)
● Range: 1 day - 365 days
2. Drag and drop the 'Total Calls' slider to the maximum number of days you require all calls to be
stored on the OVOC server before they're cleared.
3. Drag and drop the 'Calls with Call Flow' slider to the maximum number of days you require
calls together with call flow to be stored on the OVOC server before they're cleared.
4. Drag and drop the 'Statistics' slider to the maximum number of days you require call statistics
to be stored on the OVOC server before they're cleared.
If you configure the maximum number of days to a value lower than that which was
previously configured (by another operator, say), all data will be cleared the next
clearing.
- 62 -
Configuration tab
The 'Configuration' tab lets you:
■ configure global system templates (see Configuring Templates below)
■ configure alarms settings (see Configuring Alarms Settings on page 69)
■ add software and auxiliary files (see Adding Configuration Files to the OVOC's Software
Manager on page 72)
■ open external applications (see Connecting Directly to External Applications on page 76)
■ back up (see Backing up a Device's Configuration using Backup Manager on page 112)
Configuring Templates
The Templates folder allows you to configure the following global, system-wide templates to
facilitate more effective network management:
■ SNMP Connectivity (see SNMP Connectivity below)
■ HTTP Connectivity (see HTTP Connectivity on page 65)
■ QoE Thresholds (see QoE Thresholds on page 65)
■ QoE Status & Alarms (see QoE Status and Alarms on page 67)
■ Performance Monitoring Template (see Adding a PM Template on page 189)
SNMP Connectivity
This template lets you configure an SNMP connectivity template whose parameter values can then
be applied system-wide (globally). The template facilitates more effective network management.
SNMP/HTTP templates are the default profile values for each defined tenant. The tenant
SNMP/HTTP profiles are used as default for the devices under them.
➢ To configure an SNMP Connectivity template:

1. Open the SNMP Connectivity screen (System > Configuration > Templates > SNMP
Connectivity).
Figure 3-12: SNMP Connectivity Template
2. Use the following table as a reference to the parameters in the figure above.
- 63 -
Table 3-6: SNMP Connectivity Template
SNMP v2
SNMP Read Community Enter an encrypted SNMP read community string. The
default value for the SNMP read community string is
'public'.
SNMP Write Community Enter an encrypted SNMP write community string. The
default value for the SNMP write community string is
'private'.
SNMP Trap Community Enter the Trap Community string to be received as part of
the Notification message.
SNMP v3
Security Name Enter a name for SNMP v3. Example: OVOC User.
Security Level From the drop-down, select either:

■ Authentication and Privacy (default)
■ No Security
■ Authentication
Authentication Protocol From the drop-down, select either:

■ SHA (default)
■ MDS
■ No Protocol
Authentication Key Enter an Authentication Key. Default: 123456789.
Privacy Protocol From the drop-down, select either:

■ AES 128 (default)
■ DES
Privacy Key Enter a Privacy Key. Default: 123456789.
3. Click Submit.
- 64 -
HTTP Connectivity
This option lets you configure an HTTP connectivity template whose parameter values can then be
applied system- wide (globally) when adding multiple AudioCodes devices, for example. The
template facilitates more effective network management for OVOC operators.
➢ To configure an HTTP Connectivity template:

1. Open the HTTP Connectivity screen (System > Configuration > Templates > HTTP
Connectivity).
Figure 3-13: HTTP Connectivity Template
2. Use the following table as a reference to the parameters in the preceding figure.
Table 3-7: HTTP Connectivity Template
Device Admin User Enter the device Web server user name.
Example: Admin. Password - "Admin".
Device Admin Password Enter the Web server password.

Example: Admin.
Default Connectivity From the drop-down, select either:

■ HTTP (default)
■ HTTPS
3. Click Submit.
QoE Thresholds
QoE Thresholds determine global (system-wide) voice quality thresholds templates.
[For information on how to configure QoE Thresholds profiles per tenant , see Managing QoE
Thresholds Profiles per Tenant on page 252]
Three QoE Thresholds templates (Low | Medium | High Sensitivity) for the voice quality metrics of
MOS, Delay, Packet Loss, Echo and Jitter are accessed in the page. In the page, you can add, edit
or delete a voice quality thresholds template.
- 65 -
➢ To access the global QoE thresholds templates:

1. From the System menu, open the QoE Thresholds page (System > Configuration >
Templates > QoE Thresholds).
Figure 3-14: QoE Thresholds Templates
In the page, you can see three global (system-wide) QoE thresholds templates displayed. Each
consists of threshold values set for the voice quality metrics of MOS, Delay, Packet Loss, Echo
and Jitter, for each call quality category of 'Poor', 'Fair' and 'Good'.
Use the following table as reference to the figure above.
Table 3-8: QoE Thresholds Templates
Template Description
Low Sensitivity Threshold values representing recommended data for the 'Low'
Threshold sensitivity level.
Medium Sensitivity Threshold values representing recommended data for the 'Medium'
High Sensitivity Threshold values representing recommended data for the 'High'
2. Select a template and then click Edit.
- 66 -
Figure 3-15: QoE Thresholds Settings
3. Provide an intuitive name for the profile. As a reference, use the names of the three QoE
Threshold Templates displayed in the table above.
4. Enter a description of the profile to facilitate effective intuitive management later.
5. Select the Device option to set the profile as devices default.
6. Select the Links option to set the profile as links default.
7. Select the Endpoints option to set the profile as endpoints default.
8. By default, All metrics are included in the profile. To exclude a metric, clear its check box. To
define the MOS metric, for example, click the bar or drag the markers. Each bar unit
increments or decreases the threshold by 0.1 (MOS, Packet Loss), or by 1 (Delay, Jitter,
Echo).
9. Do the same for the other metrics thresholds.
10. Click OK; the profile is displayed in the QoE Thresholds screen.
QoE Status and Alarms

The QoE Status and Alarms page determines the global (system-wide) QoE status of devices,
sites, links and endpoints. The page provides a centralized view of global QoE alarms and
statuses. For information on managing QoE Status per tenant , see Managing QoE Status and
Alarms per Tenant on page 258.
- 67 -
➢ To view the global QoE status:

1. From under the System menu, open the QoE Status and Alarms page (System >
Configuration > Templates > QoE Status & Alarms).
Figure 3-16: QoE Status and Alarms
2. Use the following table as reference to the figure above.

Table 3-9: QoE Status and Alarms
Page
Description
Indications
Defaults = displayed when the alarm rule applies to devices

= displayed when the alarm rule applies to links
= displayed when the alarm rule applies to sites

= displayed when the alarm rule applies to IP phones
Name Indicates the name of the alarm rule.
Last Indicates the last time the alarm rule was activated.
Runtime
Monitoring Indicates at least how often monitoring is performed.

Frequency Default: 15
Min
Minimum Indicates the minimum number of calls to analyze, per entity. Default: 50
Calls per
Entity to
Analyze
Failed x y indicates that green changes to orange ('Major' severity) when the x
Calls (%) percentage of failed calls is exceeded and orange changes to red ('Critical'
severity) when the y percentage of failed calls is exceeded.
indicates alarm issued – displayed if the Generate Alarm option is selected

in the Alarm Rule Details screen (see Adding a QoE Alarm Rule per Tenant on
page 258).
Poor x y indicates that green changes to orange ('Major' severity) when the x
Quality percentage of poor quality calls is exceeded and orange changes to red ('Critical'
Calls (%) severity) when the y percentage of of poor quality calls is exceeded.

page 258).
- 68 -
Page
Description
Indications
Average x y indicates that green changes to orange ('Major' severity) when x

Call seconds call duration is exceeded and orange changes to red ('Critical' severity)
Duration when y seconds call duration is exceeded.
(seconds)
page 258).
Bandwidth x y indicates that green changes to orange ('Major' severity) when x

Rule bandwidth is exceeded and orange changes to red ('Critical' severity) when y
(Kbps) bandwidth is exceeded.

page 258).
Maximum x y indicates that green changes to orange ('Major' severity) when x

Concurrent concurrent calls is exceeded and orange changes to red ('Critical' severity) when
Calls (#) y concurrent calls is exceeded.

page 258).
Configuring Alarms Settings

The Alarms screen allows you to configure how alarms and events are displayed in the Alarms
pages.
➢ To configure alarm settings:

1. Open the Alarms page (System > Configuration > Alarms).
Figure 3-17: Alarms Settings
2. Configure the alarms settings using the following table as reference.
- 69 -
Table 3-10: Alarms Settings
Setting Description
Alarms Automatic Select this option to clear all devices listed in the Alarms page of all
Clearing active alarms when the system starts up (cold start event): Critical,
Major, Minor, Warning or Info.
Use this setting to prevent historical, dated alarms from cluttering the
Alarms page.
Alarms Automatic [Only relevant if the 'Alarms Automatic Clearing' option is selected]
Clearing Period (Days) Clears old alarms after a defined period of days even though a Clear
alarm to stop displaying very old active alarms has not been received
from the device.
Events Automatic Select this option for device events (events originating from the
Clearing device) to be automatically cleared from the Alarms page when the
system starts up (cold start event).
Device events originating in the OVOC, e.g., adding a gateway, are
not cleared when the device is reset. The OVOC consequently
employs a mechanism to automatically clear these events from the
Alarms page. The feature prevents historical, dated events from
cluttering the Alarms page.
Events Automatic Events are by default cleared every three days. You can change the
Clearing Period (days) default to suit your requirements.
Max number of alarms If an alarms forwarding rule is configured (under Alarms >
to aggregate in single Forwarding), the alarms can be aggregated to be sent in a single
Email email. This parameter allows you to configure the maximum number
of alarms to aggregate in a single email. Default: 10. If, for example,
the number of alarms to aggregate is configured to 10 and the time
interval (see the next parameter) is configured to 60 seconds, then
after 60 seconds, five alarms will be raised according to the alarms
forwarding rule and five aggregated alarms will be forwarded.
Email alarms aggreg- If an alarms forwarding rule is configured (under Alarms >
ation time interval Forwarding) and the alarms are configured to be aggregated and sent
(seconds) in a single email, you can configure a time interval to determine how
often aggregated alarms are forwarded. Default: 60. If, for example,
the number of alarms to aggregate is configured to 10 (see the
previous parameter) and the time interval is configured to 60
seconds, then after 60 seconds, five alarms will be raised according
to the alarms forwarding rule and five aggregated alarms will be
forwarded.
Alarms Suppression Select this option for an 'Alarm Suppression' alarm to be generated
when the OVOC server identifies that the number of alarms of the
same type and from the same source, generated in a time period, is
greater than the number defined in the threshold. At this point, these
alarms are not added to the database and are not forwarded to
configured destinations.
- 70 -
Setting Description
Alarms Suppression [Only applicable if 'Alarms Suppression' is selected] Lets you

Counter Threshold configure a counter threshold (Default: 10 alarms) and interval
(Default: 10 seconds). For example, if 10 alarms are generated from
'Board#1/EthernetLink#2 in 10 seconds, then alarms from this source
are suppressed and the 'Suppression' alarm is generated. This alarm
is cleared if in the subsequent 10 second interval, less than 10
alarms are sent from this source. At this point, updating the OVOC
database is resumed (the last received alarm is updated).
Alarms Suppression During the time the suppression alarm is active, the OVOC server
Interval (seconds) updates the database with a single alarm (with updated unique ID)
database every minute, until the alarm is cleared.
OVOC Keep-Alive Select this option for the OVOC to generate SNMP Keep-alive traps
to 3rd-party applications, such as a Syslog server. This trap can be
sent to either the SNMP, Syslog or Mail server destination. You can
send the Keep-Alive trap to the target destination, according to an
existing configured forwarding destination rule.
OVOC Keep-Alive trap [Only applicable if 'OVOC Keep-Alive' is selected] Determines how
interval (seconds) frequently the trap is sent from the OVOC to the configured
destination. Default: Every 60 seconds. You can configure a different
interval to suit your requirements.
Internal Mail Server If your enterprise uses OVOC's internal email server for Alarms
From Address Forwarding, use this parameter to configure the internal mail server’s
'From Address'.
For example, if you configure [email protected]
for this parameter and you configure John Brown for the parameter
following in this table ('Internal Mail Server Real Name'), then all
alarms forwarded from OVOC by email from rules configured with
'Use Internal Mail Server' will be from address:
[email protected] < John Brown >
See related parameters 'Forward matching alarms/events', 'Prevent
forwarding matching alarms/events' and 'Enable/Disable Rule' under
Forwarding Alarms on page 167.
Internal Mail Server If your enterprise uses OVOC's internal email server for Alarms
Real Name Forwarding, use this parameter to configure the internal mail server’s
'Real Name'.
For example, if you configure John Brown for this parameter and
you configure [email protected] for the preceding
parameter in this table ( 'Internal Mail Server From Address'), then all
alarms forwarded from OVOC by email from rules configured with
'Use Internal Mail Server' will be from address:
[email protected] < John Brown >
See related parameters 'Forward matching alarms/events', 'Prevent
forwarding matching alarms/events' and 'Enable/Disable Rule' under
Forwarding Alarms on page 167.
- 71 -
Adding Configuration Files to the OVOC's Software Manager

You can add ini files, cmp firmware files, cli files, conf files and auxiliary files to the OVOC's
Software Manager in order to load them to devices.
The Software Manager page lets operators view, add or remove files. Filters facilitate quick and
easy access to device-specific files.
After defining a device in the OVOC, the OVOC connects to it and automatically determines its
version. Each new version, fix or software update provided to customers must be added to the
Software Manager, to enable upgrading device software.
Files per network device include:
■ SBC configuration files (ini, cli, conf)
■ MSBR (cli)
■ SBC software files (cmp)
■ MP-202 software files (rms/rmt)
■ IP phone firmware files
■ IP phone configuration files (templates)
■ MP-202 configuration files (conf)
■ Auxiliary files (prt, cpt, etc.)
Use the following table as a reference with respect to which operator type is permitted to perform
what file management.
Table 3-11: OVOC Software File Management per Operator Type
Operator Type Permitted to Perform this File Management
System (except operators ■ Add any global file that will not be assigned to any specific
with 'Monitoring' security tenant. These files will be visible to both 'tenant' and 'system'
level) operator types.
■ Add a file and assign it to a specific tenant. These files will be
visible to both 'tenant' and 'system' operator types.
■ Download any file visible by the tenant (Added by 'tenant' and
'system' operator types) to any device in the tenant.
■ Remove any file added by 'tenant' and 'system' operator
types.
Tenant (except operators ■ Add any file. This file will be assigned only to the tenant.
with 'Monitoring' security These files will be visible to both 'tenant' and 'system'
level) operator types.
■ Download any file visible by the tenant to the devices in the
tenant.
■ Remove any file added by a 'tenant' operator type.
● Only one SBC software file (cmp) with the same version for a specific product type
can be added to a tenant.
● Software files cannot be shared between tenants (except global). If an operator
assigned to multiple tenants adds a file, it can be downloaded only on devices in a
specific tenant and not to all tenants.
- 72 -
Adding the ini File

You can add the ini file to the OVOC's Software Manager in order to perform initial configuration of
device parameters which cannot be configured after defining the device in the OVOC. When
loading the ini file to the device, operators can choose either:
■ Full Configuration ini file download – with validation and apply (recommended)
■ Full Configuration ini file download – without validation and apply (for software upgrade)
■ Incremental ini file download (the previous configuration remains)
➢ To add the ini file to the OVOC:

1. Open the Software Manager page (System > Configuration > File Manager > Software
Manager).
Figure 3-18: Software Manager
2. Click Add and select Add Auxiliary File from the menu drop-down.
Figure 3-19: Add Auxiliary File – ini File
3. From the 'Tenant' drop-down, select the tenant under which the ini file will be added.
4. From the 'File Type' drop-down, select INI (default) if it isn't selected already.
- 73 -
5. Next to the 'File Name' field, click the folder icon and browse to the ini file's location.
6. Enter a description of the file in the 'File Description' pane for intuitive future file management,
and then click OK; the ini file is added to the Software Manager.
Adding a cmp File

You can add a firmware (cmp) file to the OVOC to later load to the device. With the exception of the
MP-20x media gateways, the cmp files are the devices' main software firmware image files. You
can add a cmp file to the OVOC in order (for example) to change the software version.
➢ To add a cmp file to the OVOC:

1. Open the OVOC's Software Manager page (System > Configuration > File Manager >
Software Manager).
2. Click Add and select Add Software File from the drop-down menu.
Figure 3-20: Add Software File
3. From the 'Tenant' drop-down, select the tenant under which the cmp file will be added.
4. Next to the 'CMP' field, click … and browse to the cmp file's location.
5. Enter a description of the file in the 'File Description' pane for intuitive future file management.
6. In the 'Software Version' field, enter the version of the software file. If left undefined, the field
will be automatically defined after adding the cmp or rmt/rms file.
7. From the 'Major Version' drop-down, select the device version (Default: 6.6).
8. From the 'Select Product' drop-down list, select the relevant product corresponding to the cmp
or rmt/rms file.
9. From the 'Select Protocol' drop-down, select the protocol. Default: SIP. MGCP and MEGACO
are also available.
- 74 -
10. Click OK; the cmp file is added to the Software Manager.
Adding a cli File

A cli file can be added to the OVOC to later load to the MSBR devices and SBC Linux devices.
➢ To add a cli file to the OVOC:

SoftwareManager).
2. Click Add and select Add Auxiliary File from the drop-down menu.
Figure 3-21: Add Auxiliary File
3. From the 'Tenant' drop-down, select the tenant under which the cli file will be added.
4. From the 'File Type' drop-down, select CLI.
5. Next to the 'File Name' field, click the browser icon to browse to the cli file's location.
7. Click OK; the cli file is added to the Software Manager.
Adding Auxiliary Files

Besides the ini file, you can add auxiliary files to the OVOC's Software Manager.
➢ To add an auxiliary file to the OVOC's Software Manager:

Software Manager).
2. Click Add and select Add Auxiliary File from the drop-down menu.
3. From the 'Tenant' drop-down, select the tenant under which to add the auxiliary file.
4. From the 'File Type' drop-down list, select the auxiliary file to be added.
- 75 -
Figure 3-22: Add Auxiliary File
● See the device's User's Manual for more information about device-related files.
● The CERTIFICATE file secures the following connections:
✔ Active Directory server (domain controller)
✔ MSSQL Front End server
✔ LDAP User Authentication
● The X.509 PRIVATE KEY, X.509 CERTIFICATE and X.509 TRUSTED ROOT
CERTIFICATE files are AudioCodes certificate files that secure the connection
between OVOC and the devices.
✔ The X.509 files are for all the security files, including LDAP.
● These files may be default AudioCodes certificate files or files generated by an
external CA. For more information about certification implementation, see the One
Voice Operations CenterSecurity Guidelines.
6. Next to the 'File Name' field, click … and browse to the file's location.
7. Enter a description of the file in the 'File Description' pane for intuitive future file management,
and then click OK; the file is added to the Software Manager.
Connecting Directly to External Applications

The OVOC features an external applications menu that allows operators to directly connect to IP
telephony network management applications, both of AudioCodes as well as of external vendors.
These applications enable comprehensive control over any enterprise or ITSP IP telephony
network, helping providers deliver the quality of service users require.
➢ To directly access the external applications menu:
1. On every page of the OVOC on the right of the title bar, click the icon.
- 76 -
● Click the relevant link for single sign-on to:

◆ Device Manager (see Device Manager below for more information)
◆ Reports (see for Reports below more information)
◆ Routing Manager (see ARM on the next page for more information)
◆ MasterScope (see MasterScope on page 79 for more information)
Device Manager
The external applications menu allows operators to directly access the Device Manager, a life
cycle management application for enterprise IP phone deployments that enables administrators to
deliver a reliable desktop phone service within their organization. With the ability to deploy and mon-
itor IP telephony devices, identify problems, and then fix them rapidly and efficiently, the applic-
ation enhances employee satisfaction, increases productivity and lowers IT expenses.
➢ To directly access the Device Manager:

1. Click the applications menu icon located on every OVOC GUI page on the right of the title bar,
and then click the Device Manager link.
● If your browser is configured to block pop-ups, a message will appear indicating

'Pop-ups were blocked on this page' (or similar). In this case, set your browser to
allow pop-ups.
● The status of the application as well as the statuses of other applications can be
viewed in the menu. The example in the figure above indicates that the network is
managed by Device Manager and that there are no alarms in the network managed
by Device Manager since the link is color-coded green.
2. View the Device Manager application which opens in a new browser tab.
Reports
The external applications menu allows operators to directly access reports-generation capability
that operators can utilize to distribute session experience data and comparative analysis to respons-
ible persons within the enterprise and to external authorities associated with the enterprise's IP tele-
phony network, for accurate diagnosis and correction of degraded sessions and for general network
optimization.
➢ To directly access the reports-generation application:

1. In the applications menu located on every page on the right of the title bar, click the Reports
link.
- 77 -

allow pop-ups.
● The status of the application as well as the statuses of other applications can be
viewed in the menu. The example in the figure above indicates that the network is
managed by AudioCodes Reports and that there are no alarms in the network
managed by the application since the link is color-coded green.
2. View the reports-generation application which opens in a new browser tab. See Producing
Reports on page 271 for more information.
ARM
The external applications menu lets operators directly access the Routing Manager (ARM) for
managing the dial plan and call routing rules of multi-site, multi-vendor enterprise VoIP networks.
The ARM enables centralized control of all session routing decisions. Through the ARM’s graphical
user interface, network administrators can design and modify their voice network topologies and
call routing policies from a single location, resulting in significant time and cost savings. Time-
consuming tasks such as adding a new PSTN or SIP trunk interconnection, adding a new branch
office or modifying individual users’ calling privileges can be carried out simply and rapidly.
➢ To enable a direct connection to the ARM:

1. Open the External Applications page (System > Configuration > External Applications) as
shown in the following figure, and then click the ARM option.
Figure 3-23: External Applications - ARM
2. In the field 'ARM Server FQDN / IP' under the General section, enter the FQDN (host name) or
IP address of the ARM server to connect to. You can obtain these from your enterprise's
network administrator if necessary.
3. Note that parameters 'ARM Status', 'ARM Version' and 'Unique Identifier' are provisional
placeholders. They will be automatically reconfigured with true values after connection with the
ARM is established.
4. Under the OVOC-ARM Communication section, you can select the Secure Communication
option for HTTPS secured communications between OVOC-ARM.
5. Under the same section, if an OVOC-ARM connection has already been established, you can
opt to configure the 'Change ARM Password' parameter value.
- 78 -
6. Under the ARM Single Sign On section, you can optionally configure direct sign-on to the
ARM. Admin and Operator types can configure this SSO connection. Note that the feature
applies only to ARM versions that support it. The logic is identical to the logic of a regular sign
on (see the previous two steps).
7. Under the ARM-OVOC Communication section, select an OVOC operator. This operator will
then be defined in the ARM in order to use the ARM.
8. Click Submit.
9. In any OVOC page, click the external applications menu icon displayed on the right side of the
title bar.

allow pop-ups.
● ARM status as well as the statuses of other applications can be viewed in the
menu. The example in the preceding figure indicates that the network is not
managed by the ARM (Not Connected) and that there is an alarm in the ARM-
managed network whose severity is Critical. If the color code had been green, the
indication would have been that the network is managed by the ARM and that there
are no alarms in the ARM-managed network.
10. In the external applications menu that opens, click the Routing Manager link.
11. View if you configured SSO the ARM's main screen which opens in a new browser tab. If you
didn't configure SSO, you'll be prompted to log in.
MasterScope
The External Applications page enables connecting directly to MasterScope in order to quickly and
easily access the exact network equipment component associated with a voice quality issue - if an
issue is detected - and benefit from root cause analysis. In this page, operators configure the con-
nection, a.k.a. Single Sign On (SSO), to MasterScope. A MasterScope link is then displayed on the
Call Details page.
Applies only to operators who have acquired and installed MasterScope.
➢ To enable connecting directly to MasterScope:

1. Open the External Applications page (System > Configuration > External Applications) as
shown in the figure below and then click the MasterScope option.
- 79 -
Figure 3-24: MasterScope
2. In the ‘MasterScope URL’ field, enter the MasterScope IP address or FQDN. This is a string
type parameter. Maximum size: 100 characters.
3. Click Submit; the MasterScope link for single sign-on is displayed in the applications menu
located on every OVOC page on the right of the title bar.

allow pop-ups.
● MasterScope status as well as the statuses of other applications can be viewed in
the menu. The example in the preceding figure indicates that the network is
managed by MasterScope and that there are no alarms in the MasterScope-
managed network since the link is color-coded green.
4. Click the MasterScope link; the application opens in a new browser tab.
Enabling Automatic Device Backup Periodically

The OVOC can be configured to automatically (daily) back up device configurations (ini, conf or cli
script files) according to the OVOC server application's time. The files are saved on the OVOC
server. They can be accessed and transferred using SSH and SFTP. The backup files are
managed by the Backup Manager.
➢ To configure automatic device configuration backup:

1. Open the Device Backup page (System > Configuration > Device Backup).
- 80 -
Figure 3-25: Device Backup
2. Select the 'Enable Periodic backup' option.

● When enabled, backup is automatically performed daily; all device configuration files (ini,
conf and cli) are backed up to the Backup Manager from all devices.
● When disabled, you can perform manual backup after making changes to a device's
configuration (see Backing up a Device's Configuration using Backup Manager on
page 112 for information about manually backing up a device's configuration).
3. Configure 'Number of backup files per device' to determine the number of latest backup files to
be stored for each managed device. Default: 5.
4. In the 'Number of retries' field, configure the number of retries to be made each connection
attempt to the device. Default: 2.
5. Click Submit.
Tasks tab
The Tasks page displays asynchronous actions performed by operators, currently under execution.
Tasks that are in progress are displayed irrespective of how long it takes for them to complete. The
OVOC continues to display them 20 minutes after they're completed. They are then removed from
the page.
If the operator is not a 'system' operator, onlytasks performedbythat operator are dis-
played in the Tasks page.
- 81 -
Displaying the Status of Tasks Currently Under Execution

Adding multiple AudioCodes devices to the OVOC can be configured. OVOC supports many types
of asynchronous actions. Adding multiple devices, described here, is just one example. As you can
see in the figure, the operator is adding 10 AudioCodes devices whose IP addresses range from
10.1.1.1 to 10.1.1.10, under the region US.
Figure 3-26: Task - Add Multiple AudioCodes Devices
■ [Optional] In the 'Address' field, enter the first letters of the name of the city / country in which
to locate the device, and then select the city / country from the list that pops up.
■ After clicking OK, a notification pops up in the uppermost right corner indicating the task
status.
- 82 -
Figure 3-27: Example of a Notification Pop-up Indicating Task Status
To configure the timeout of the notification pop- up, see Configuring Operator
Authentication Locally, in the OVOC on page 34 and refer to the parameter
'Notifications display time (sec)'. The default is 3 seconds. Configuring the parameter to
0 disables the notification pop-up feature.
■ Optionally, you can click a notification to open the Tasks page displaying the task about which
you were notified.
Figure 3-28: Tasks Page Showing Task Status - Adding Multiple AudioCodes Devices
The Tasks page allows the operator to determine if a task was performed successfully, or, if it's
incomplete, what percentage is complete and what percentage remains to be completed.
➢ To view the notifications history:

1. Click the bell icon in the uppermost right corner of the OVOC GUI.
The bell icon indicates the number of notifications that have not yet been viewed.
- 83 -
2. View the tasks history. In the list, you can delete a notification, delete all notifications or click a
notification to open the Tasks page.
3. Scroll down to view earlier notifications. Most recent notifications are listed first. Every
notification indicates how long ago it was listed, e.g., 4 minutes ago.
- 84 -
CHAPTER 4 Defining your Network Topology OVOC | User's Manual
4 Defining your Network Topology

The OVOC enables you to define the topology of your telephony network.
When configuring entities (for example, when adding a device):

● fields and tabs with missing or incomplete information are outlined in red
● fields currently being edited are highlighted yellow
● mandatory fields are marked with an asterix *
Adding a Tenant
See Network Architecture on page 2 for details on multi-tenancy vs. non multi-tenancy
architecture.
➢ To add a tenant:
1. In the Network page, click Add.
Figure 4-1: Add Tenant
2. Select Tenant.
Figure 4-2: Tenant Details - General
- 85 -
3. Use the following table as reference when configuring the tenant's General parameters.
Table 4-1: Tenant Details - General
Tenant Enter an intuitive name to facilitate effective management later.

Name
Is Default Defines the default tenant. Only one tenant can be the default. The default is
used for devices/endpoints auto-detection.
License This drop-down list shows all the 'tenant' operators with Admin privileges
Pool assigned to this tenant. To manage the Fixed License Pool, it is mandatory to
Operator select one of these 'tenant' operators from the drop-down (see also Managing
Device Licenses in the Fixed License Pool on page 134). After selecting a
'tenant' operator, the association cannot be removed (see also Adding a 'Tenant'
Operator on page 43) and they're automatically displayed under the Operators
tab (see following).
Description Enter a tenant description to facilitate effective management later.
Subnet Enter the tenant's subnet mask. Must be in prefix format x.x.x.x/y. For example:
(CIDR 255.255.0.0/16. For any region under the tenant, subnet mask is not mandatory,
Notation) but if it is configured, its subnet mask must be within the tenant's, for example,
255.255.0.0/1.
4. Click OK and then click SNMP.

Figure 4-3: Tenant Details – SNMP v2
5. Use the following table as reference when configuring the SNMP v2 parameters.
- 86 -
Table 4-2: Tenant Details – SNMP v2
SNMP Enter an encrypted SNMP read community string. The default value for the
Read SNMP read community string is taken from the SNMP main template.
Community
SNMP Enter an encrypted SNMP write community string. The default value for the
Write SNMP write community string is taken from the SNMP main template.
Community
Trap Enter the Trap Community string to be received as part of the Notification
Community message. The default value for the SNMP trap community string is taken from
the SNMP main template.
6. Use the following table as reference when configuring the SNMP v3 parameters.
Table 4-3: Tenant Details – SNMP v3
Security Name Enter a name for SNMP v3. Example: OVOC User.
Security Level From the drop-down, select either:

■ Authentication and Privacy (default)
■ No Security
■ Authentication
Authentication Protocol From the drop-down, select either:

■ SHA (default)
■ MDS
■ No Protocol
Authentication Key Enter an Authentication Key. The default is taken from main
SNMP template.
Privacy Protocol From the drop-down, select either:

■ AES 128 (default)
■ DES
■ The default is taken from main SNMP template
Privacy Key Enter a Privacy Key. The default is taken from main SNMP
template.
7. Click OK and then click HTTP.
Note to users of CloudBond 365, CCE Appliance, UMP and SmartTAP:

SNMPv2/SNMPv3 account credentials are not automatically configured so you need to
manually configure identical settings in the device's Web interface (see the device's
documentation for more information).
- 87 -
Figure 4-4: Tenant Details - HTTP
8. Use the following table as reference when configuring the HTTP parameters.
Table 4-4: Tenant Details - HTTP
Device Admin User Enter the device Web server user name.
Example: Admin. Password - "Admin".
The default is taken from the main HTTP template.
Device Admin Password Enter the Web server password.

Example: Admin.
The default is taken from the main HTTP template.
Connectivity From the drop-down, select either:

■ HTTP (default)
■ HTTPS
The default is taken from main SNMP template.
9. Click OK and then click Multitenancy.

Figure 4-5: Tenant Details – Multitenancy
10. Use the following table as reference.
- 88 -
Table 4-5: Tenant Details - Operators
Local From the drop-down, select an operator from the list of operators. Only
Authentication: operators configured as 'tenant' type operators are displayed. The list will be
Assigned empty if no such operator has been configured, in which case you can click
Operators the button described next, to add a 'tenant' type operator. The parameter lets
you assign an operator – or operators – to the tenant. See Adding a 'Tenant'
Operator on page 43 for more information about configuring 'tenant' type
operators.
Operator authentication can be configured locally, in the OVOC (see

Configuring Operator Authentication Locally, in the OVOC on page 34). Click
the button to add a new 'tenant' type operator; the 'Tenant Operator Details'
screen opens (see Adding a 'Tenant' Operator on page 43). The operator is
then assigned to the tenant and displayed in the drop-down list.
LDAP Applies to both 'system' type operators and 'tenant' type operators. When an
Authentication: operator logs in to the OVOC, the OVOC (before allowing the operator
Group Name access) checks with the enterprise's LDAP server if the User Group which
the operator is associated with in the OVOC, tallies with the User Group
defined in the LDAP server. If they tally, the operator is authenticated and
allowed access. See also Configuring Operator Authentication Centrally
using an LDAP Server on page 28.
11. Click OK and then click License.

Figure 4-6: Tenant Details - License
12. Use the following table as reference when configuring the License parameters.
- 89 -
Table 4-6: Tenant Details – License
License Pool Description
Devices Enter the total number of devices that can be managed by this tenant's
License Pool, i.e., CloudBond 365 devices, SBC devices, gateway
devices and MSBR devices allowed by your license. The parameter only
defines systems. It does not include phones.
SBC Registrations Enter the number of SIP endpoints that can register with the SBCs
allowed by your license.
SBC Sessions Enter the number of concurrent call sessions supported by the SBCs in
your deployment.
SBC Signaling Enter the number of SBC signaling sessions supported by the SBCs in
your deployment.
SBC Transcoding Enter the number of SBC transcoding sessions supported by the SBCs in
your deployment.
CB Analog Support pending. Currently unsupported.

Devices
CB PBX Users Support pending. Currently unsupported.
CB Users Enter the number of CloudBond 365 users per tenant. Divide the total
number of CloudBond 365 users allowed by your license, by the number
of tenants in your deployment. If you purchased a license for 1000
CloudBond 365 users and you have four tenants in your deployment, 250
users can be allocated to each tenant. You cannot exceed the total
number of CloudBond 365 users covered by your license. It's your
decision how to distribute them over tenants.
CB Voicemail Support pending. Currently unsupported.

Accounts
Voice Quality
Devices Enter the number of SBCs, gateways and MSBRs that can be monitored
in this tenant.
Endpoints Enter the number of endpoints that can be monitored in this tenant.
Sessions Enter the number of concurrent call sessions the SBCs deployed in this
tenant.
Users Enter the number of users supported by the SBC/s deployed in this ten-
ant.
Endpoints Management
Endpoints Enter the number of endpoints the Device Manager application supports
for this tenant.
13. Click OK; the new tenant is added.
- 90 -
Adding a Region
ITSPs or enterprises manage devices in regions. A region typically represents a geographical area
for the ITSP or the enterprise. Devices are added to the OVOC under a tenant, after defining one.
➢ To add a region:
1. Open the Network Topology page (Network > Topology).
2. Click Add and select Region.
Figure 4-7: Add Region
The Region Details screen opens:

Figure 4-8: Region Details
3. From the 'Tenant' drop-down, select a tenant that you configured previously.
4. Define the region's name and type in a description to facilitate operator-friendly management
later.
5. [Optional] Enter a subnet mask for the region. If a tenant’s subnet mask is 255.255.10.10/16,
then the subnet mask of a region under it – if configured – must be within that subnet mask, for
example: 255.255.10.10/1.
6. Click the now-activated OK button; the region is added to the OVOC.
- 91 -
Adding AudioCodes Devices

AudioCodes devices can be added to the OVOC by:
■ Adding Devices Automatically (full automatic detection with device-initiated connection)
(see Section Adding AudioCodes Devices Automatically below)
● Devices are automatically connected to OVOC and added to the default tenant
● Used predominantly for NAT traversal; allows SNMP communication with devices when
they're located behind NAT and OVOC is installed in the WAN
● Devices initiate the connection to the OVOC and send coldStart and Keep-alive traps to it;
OVOC then recognizes each device's IP address and port according to its serial number
■ Adding Devices Manually from OVOC (OVOC-initiated connection) (see Section Adding
AudioCodes Devices Manually on page 96‎)
● Predefined by IP address: Devices are manually added to the OVOC by IP address,
under the correct entity
● Predefined by Serial Number: Devices are manually added to the OVOC by serial
number, under the correct entity
■ Adding Devices with First Time Provisioning (semi-automatic) (see Section Enabling
Initial Connection Provisioning on page 102‎)
● Devices are provisioned with firmware and configuration files for initial connection to
OVOC
● Multiple devices are manually predefined with firmware and configuration files in OVOC
● Auto detection is then used to connect the devices to OVOC and provision them with
these files
Adding AudioCodes Devices Automatically

Before devices can be managed in the OVOC management interface, they must be added to the
OVOC's Network Topology. Devices can be added after acquiring them from AudioCodes, or, as
the case may be, after acquiring the OVOC from AudioCodes and adding the OVOC to an existing
deployment of devices.
The OVOC's Automatic Detection feature enables devices to be automatically connected and
added to the OVOC without needing to add them manually; when devices are connected to the
power supply in the enterprise network and/or are rebooted and initialized, they're automatically
detected by the OVOC and added by default to the AutoDetection region.
For this feature to function devices must be:
■ configured with the OVOC server's IP address
■ configured to send keep-alive messages
The OVOC then connects to the devices and automatically determines their firmware version and
subnet. They're then added to the appropriate tenant/region according to the best match for subnet
address.
■ When a default tenant exists, devices that cannot be successfully matched with a subnet are
added to an automatically created AutoDetection Region under the default tenant
■ When a default tenant does not exist and the device cannot be matched with a subnet, the
device isn't added to the OVOC
The Automatic Detection feature is used also for NAT traversal, and allows SNMP communication
with the devices when they are located behind a NAT and are managed over a remote WAN con-
nection.
- 92 -
● SNMPv2 or SNMPv3 credentials are configured in the device Web interface.

SNMP settings connect the devices and the OVOC. The following figures show the
Web interface pages in which these settings are configured. See also the device's
User's Manual for more information.
● If a device detects the OVOC but the OVOC does not detect the device, the device
sends an event to the OVOC; the OVOC takes the information from the event and
automatically connects the device.
Figure 4-9: Web interface: SNMP Community Strings
- 93 -
Figure 4-10: Web interface: SNMP Trap Destinations
When devices are deployed in a private network using Network Address Translation (NAT), they
can connect to the internet so long as their connection with the OVOC server is alive. You con-
sequently need to configure devices to send coldStart (after device reset) and keep-alive traps
(sent every 30 seconds by default) to the OVOC server. This allows the OVOC to perform SNMP
SET and GET commands at any time. When devices are added to the OVOC, the OVOC recog-
nizes them according to their field 'sysDesc' and their serial number, and according to the entries in
the OVOC database. A device's default name comprises the router's IP address and the port num-
ber. The NAT sometimes changes device IP address and port. The OVOC recognizes these
changes after devices are reset.
- 94 -
Figure 4-11: AudioCodes Devices Added to OVOC
The following figure illustrates SNMP connectivity between OVOC and AudioCodes devices:
■ UDP ports 162 and 1161 on the OVOC server are configured to listen for traps from
AudioCodes devices
■ UDP port 1161 on the OVOC server sends SNMP SET requests to AudioCodes devices
Figure 4-12: OVOC Server and Devices SNMP Connections
- 95 -
Adding AudioCodes Devices Manually

When manually adding an AudioCodes device - or multiple AudioCodes devices - to the network for
the first time, you can enable 'Initial Connection Provisioning' a.k.a. First Time Provisioning, for
devices to automatically be provisioned with their firmware and configuration files. The figure
following shows an example of manually adding multiple AudioCodes devices to OVOC.
Figure 4-13: Manually Adding Multiple AudioCodes Devices to OVOC
➢ To manually add the devices:

2. Click Add and select AC Device or Multiple AC Devices.
Figure 4-14: AC Device | Multiple AC Devices
- 96 -
The Device Details screen opens under the General tab:

Figure 4-15: Device Details – General
3. Define an intuitive device name to facilitate operator-friendly management later. Do not use
underscores in the name.
4. Provide a description of the device to facilitate operator-friendly management later.
5. From the 'Tenant' drop-down, select a tenant that you configured as shown in Adding a Tenant
on page 85.
6. Select the region under which the device is located.
7. Define the device by selecting one of these three options (refer to the figures above):
● Select and enter the device's IP address. If selected, the 'FQDN' and 'Serial Number'
fields will be disabled and the device will immediately be connected to the OVOC. If you're
adding Multiple AC Devices, you need to enter the IP Address range in the fields that will
be displayed.
● Select and enter the device's FQDN. If selected, the 'IP Address' and 'Serial Number'
fields will be read-only). This option allows performing SBC SSO in a way that the URL
includes only FQDN names (OVOC & SBC) rather than IP addresses.
- 97 -
● If a device is defined using FQDN and the OVOC cannot resolve the IP address,
the OVOC will not be able to manage the device until the IP address is resolved.
The same applies to the Add and Refresh processes.
● FQDN is not editable after a device is defined using the FQDN option. Same
applies to IP Address and Serial Number – they are not editable after defining the
device using them.
● The FQDN option is not supported when adding multiple devices.
● Devices behind a NAT and devices added as a result of a keep-alive trap (auto
detection) are managed using IP address + port (rather than FQDN).
● Alarm Forwarding is performed using IP address.
● [Optional] Select and enter the device's Serial Number. If selected, the 'FQDN' and 'IP
Address' fields will be read-only. You can get the SN from the device's Web interface's
Information page. The SN is only necessary for auto-detection. Generally, it is not
mandatory to enter the serial number when adding a device.
8. [Optional] In the 'Address' field, enter the first letters in the name of the city / country in which
9. You need to configure the device’s SNMP settings if you're connecting the device to the
OVOC.
● To configure SNMPv2, click the SNMPv2 tab:
Figure 4-16: Device Details – SNMP v2
- 98 -
Before connecting a device to the OVOC, an SNMP connection between the device
and the OVOC must be configured. SNMP is used to establish an initial connection with
the device for provisioning and in addition, for daily operations, including maintenance
actions and fault and performance management.
SNMPv3 provides more sophisticated security mechanisms than SNMPv2c. It imple-
ments a user-based security model (USM), allowing both authentication and encryption
of the requests sent between the OVOC and agents, as well as user-based access con-
trol.
The SNMP connection must be configured on both the OVOC and the device. SNMP
parameters include
● specifying the IP address of the OVOC server. All traps are sent from the device to
this address. For establishing the connection with the OVOC, this is the destination
address for the coldStart and Keep-alive traps.
● associating an SNMPv2 or SNMPv3 trap user with the OVOC server destination.
The Keep-alive trap indicates whether the device is configured for SNMPv2 or
SNMPv3. The configured SNMPv2 or SNMPv3 user credentials are verified with
the following default OVOC configuration:
◆ SNMPv2: SNMPReadCommunity string ‘public’ and
SNMPWriteCommunity string ‘private’ and Trap User 'trapuser'
◆ SNMPv3: User ‘OVOCUser’; Auth protocol ‘SHA’; Privacy protocol ‘AES-
128’; password ‘123456789’
Identical SNMP parameter values must be configured on the device and in the OVOC.
If different values are configured on the device, it's added to the OVOC as 'Unknown'
until updated in the OVOC. The defaults under the SNMP tab are taken from the SNMP
tenant profile.
◆ Enter the device's SNMP Read and Write Community strings.

● To configure SNMPv3, select the SNMP v3 option:
- 99 -
Figure 4-17: Device Details – SNMP v3
The OVOC can automatically add up to 255 devices at a time after SNMP credentials
and other device settings are configured and functioning correctly.
a. In the 'Security Name' field, enter the Security name of the SNMPv3 operator.
b. From the 'Authentication Protocol' drop-down, select an authentication protocol. The
corresponding security level is displayed in the 'Security Level' field.
c. In the 'Authentication Key' field, leave the default unchanged or enter an authentication
password.
d. From the 'Privacy Protocol' drop-down, leave the default unchanged or select a Privacy
Protocol.
e. In the 'Privacy Key' field, leave the default unchanged or enter a privacy password.
The defaults are taken from the SNMP tenant profile.
10. Click the now-activated OK button or click the HTTP tab.
- 100 -
Figure 4-18: AudioCodes Device Details – HTTP
The defaults are taken from the HTTP tenant profile.
11. [Optional] In the 'Device Admin User' field, enter the device's web server user name and in the
'Device Admin Password' field, enter the web server password.
Example: Admin, Admin.
12. To secure the connection with the device, select the Enable HTTPS Connection option.
Securing the connection between the OVOC server and the AudioCodes device over HTTPS
is used for files upload/download and for Web Client Single-Sign On.
● You can also configure HTTPS on the AudioCodes device (see the Server IOM for
more information).
● You can also secure the connection using the default AudioCodes self-signed
certificate or load custom certificates to the OVOC server (see the Server IOM for
more information).
● To operate in 'Mutual Authentication' mode:
✔ Set the HTTPS Authentication option 'Set Mutual Authentication' using the
OVOC Server Manager (see the Server IOM).
✔ Load certificates to the device (you must use the same root CA for signing the
device certificate as is used for signing the certificate installed on the OVOC
server) (see 'Custom X.509 Certificates - Supplementary Procedures' in the
Server IOM).
✔ Configure HTTPS on the device (see 'Custom X.509 Certificates -
Supplementary Procedures' in the Server IOM).
13. Click the now-activated OK button or click the SBA tab.
- 101 -
Figure 4-19: AudioCodes Device Details – SBA
14. Select the Enable SBA option. This is only relevant if the device contains an SBA module.
15. Enter the IP address of the SBA Management Interface –OR- select the 'FQDN Name' option
and in the field 'FQDN Name', enter the FQDN (Fully Qualified Domain Name) of the SBA.
Example: HOST/Branch01.SFB.interop
16. Enter an encrypted SNMP read community string.
17. Enter an encrypted SNMP write community string.
18. Enter a description to facilitate an operator-friendly management experience later.
19. Click the now-activated OK button or click the First Connection tab.
After adding a SmartTAP device to the OVOC, it's Unknown until the SmartTAP
Agents have been installed on the SmartTAP Server because the Keep- alive
mechanism is managed by these agents. See also the SmartTAP Installation Manual.
Enabling Initial Connection Provisioning

After acquiring a device - or multiple devices - from AudioCodes, you can add them to the OVOC.
You can opt to enable 'Initial Connection Provisioning' a.k.a. First Time Provisioning, for devices to
automatically be provisioned with their firmware and configuration files, rather than manually, after
they're connected to from the OVOC.
➢ To enable 'Initial Connection Provisioning' a.k.a. First Time Provisioning:

1. Click the First Connection tab and then select the option 'Enable Initial Connection
Provisioning'; this enables the device/s to automatically be provisioned with their firmware and
configuration files when they are connected to the OVOC server for the first time.
- 102 -
Figure 4-20: AudioCodes Device Details – First Connection
2. From the now-activated 'Configuration File' drop-down, select the applicable file.
3. From the now-activated 'Firmware File' drop-down, select the applicable file.
The configuration and firmware files must be prepared and located in the OVOC's Soft-
ware Manager. See Adding Configuration Files to the OVOC's Software Manager for
more information.
4. Click the now-activated OK button; the devices are added to the OVOC.
The AudioCodes Mediant 2000 Media Gateway device housing two TP-1610 blades
can be added to OVOC using a single IP address rather than using two IP addresses
(one for each blade) as was the case in OVOC versions earlier than Version 7.4.3000.
Existing customers must remove any Mediant 2000 device housing two TP blades that
was added to the OVOC using two IP addresses in OVOC versions earlier than Version
7.4.3000, and then add them again using a single IP address. After this action, the
Alarms History and QoE calls & statistics history is cleared.
In a related scenario, you can add OVOC to an existing deployment after acquiring the OVOC later.
- 103 -
Before Enabling the Feature

Before enabling Initial Connection Provisioning, you need to validate the ini file.
➢ To validate the ini file:

1. Access each device using its default IP address directly through the Web interface or CLI, and
then configure its network settings (e.g., OAMP IP address) so that it suits your network
environment. Network settings are configured in these tables:
● IP Interfaces
● Ethernet Device
● Ethernet Group
● Physical Ports
● Static Route
● QoS Settings
2. Make sure the IP Interfaces table's indexes, names and application types are identical for each
device so that the template configuration file will be applied to all devices in the network. In the
validation process, each index entry is validated with the equivalent entry in the template file
(see Interfaces Table Excerpted from the ini File below for a file example).
If any device's IP interface table does not meet these requirements, the Initial Con-
nection Provisioning will fail and an alarm will be sent to the OVOC (see Making Sure
First Time Provisioning was Successful on page 106).
Interfaces Table Excerpted from the ini File
The following example shows an example of a device's ini file's IP Interfaces table parameters.
Validated values are displayed in blue. Not validated values are displayed in red and are only read
from the device once the blue parameters are successfully validated.
[ \InterfaceTable ]
FORMAT InterfaceTable_Index = InterfaceTable_ApplicationTypes, InterfaceTable_

InterfaceMode, InterfaceTable_IPAddress, InterfaceTable_PrefixLength, InterfaceTable_
Gateway, InterfaceTable_InterfaceName, InterfaceTable_PrimaryDNSServerIPAddress,
InterfaceTable_SecondaryDNSServerIPAddress, InterfaceTable_UnderlyingDevice;
InterfaceTable 0 = 6, 10, 10.15.17.10, 16, 10.15.0.1, "Voice", 10.15.25.1, 0.0.0.0, "vlan 1";
InterfaceTable 1 = 5, 10, 195.189.192.156, 25, 195.189.192.129, "WANSP", 80.179.52.100,

80.179.55.100, "vlan 2";
Enabling the Feature

The Initial Connection Provisioning feature is implemented by the First Connection tab shown in
the following figure (on the left) - when adding a single AudioCodes device - and in the figure
following (on the right) when adding multiple AudioCodes devices.
- 104 -
Before adding a device or multiple devices, you must load the device ini and .cmp files
to the OVOC's Software Manager. See Adding Configuration Files to the OVOC's Soft-
ware Manager on page 72 for details.
Figure 4-21: First Connection: Add AudioCodes Device
- 105 -
Figure 4-22: First Connection: Add Multiple AudioCodes Devices
➢ To enable the feature:

■ Make sure the Enable Initial Connection Provisioning option shown in the figures above is
selected.
See also Adding AudioCodes Devices Automatically on page 92 for related information.
Making Sure First Time Provisioning was Successful

The Journal page helps you confirm that the configuration and firmware files were automatically
loaded to the device after the device is connected to the network.
➢ To make sure first time provisioning was successful:

1. Open the Journal page (Alarms > Journal).
Figure 4-23: Alarms Journal
- 106 -
2. Optionally filter the page by Time Range (see Filtering to Access Specific Information on
page 147), Topology (see Filtering by 'Topology' on page 150), Source Type (see Filtering by
'Severity' on page 158) or More Filters (see Filtering the Alarms Journal by 'More Filters' on
page 164).
3. Locate and select the First Time Provisioning / Initial Connection Provisioning alarm.
4. In the Journal Alarm Details pane on the right side of the page, click the Entity Info tab.
Figure 4-24: Alarms Journal – Entity Info
5. If Initial Connection Provisioning was unsuccessful, you'll view the following:

Figure 4-25: Critical Alarm – Initial Connection Provisioning Failed
If Initial Connection Provisioning was unsuccessful, download the configuration or firm-

ware file to the device as shown in Backing Up on page 212.
After an ini or cmp file is deployed on multiple devices, you may need to customize one device's
configuration to suite specific requirements.
➢ To change the .cmp or ini file after successfully automatically provisioning a device:
■ Remove the device from the OVOC and then add it again. When the device is removed, the
OVOC server IP address in the Trap Destination Rule is reset to 0.0.0.0, so when you add the
device again you need to reconfigure this IP address in the SNMP Trap Destinations table. See
the relevant SIP User's Manual for more information.
AudioCodes recommends that you consult with AudioCodes Customer Support or Pro-
fessional Services about special configuration issues.
- 107 -
Adding a Generic Device Manually

A generic (non-AudioCodes) device can manually be added to the OVOC.
➢ To manually add a generic device:

2. Click Add and select Generic Device.
Figure 4-26: Add Generic Device
The Generic Device Details screen opens:

Figure 4-27: Generic Device Details
3. Define an intuitive device name to facilitate operator-friendly management later. Do not use
underscores in the name.
4. Enter the device's IP address.
5. From the 'Tenant' drop-down, select the device's tenant.
6. From the 'Region' drop-down, select the device's region and then click the now-activated OK
button; the device is added and displayed in the OVOC.
- 108 -
Adding a Microsoft Skype for Business Device

Manually
The most commonly used Microsoft device is Microsoft Skype for Business server. The OVOC
can calculate, for example, call quality for the link defined between AudioCodes devices and
Microsoft Skype for Business server. See also Adding an Unprivileged User to MSSQL Server on
page 291.
➢ To add a Microsoft Skype for Business device:

2. Click Add and select Skype Device.
Figure 4-28: Add Skype Device
The Skype Details screen opens.
- 109 -
Figure 4-29: Skype Details
3. Define an intuitive name to facilitate operator-friendly management later. Don't use

underscores.
4. From the 'Region' drop-down, select a region you configured when Adding a Region on
page 91.
5. From the 'Device Type' drop-down, select:
● Microsoft Skype for Business FE (Front End) Server
◆ The main FE parameters are 'NAME' and 'FQDN'. Other SQL parameters are for the
SQL Skype for Business Database.
◆ FE Server points/reports to the SQL Database. It does not point/report to the Skype
for Business FE Services.
◆ The SEM server connects to the SQL Monitoring Server and pulls control and media
information from it for display.
● Microsoft Skype for Business Mediation Server
◆ Implements enterprise voice and dial-in conferencing
◆ Translates signaling and media (in some configurations) between your internal Skype
for Business Server infrastructure and a public switched telephone network (PSTN)
gateway, IP-PBX, or a Session Initiation Protocol (SIP) trunk
● Microsoft Skype for Business Edge Server
◆ Deployed in a DMZ
◆ Provides access to the Skype for Business system from the Internet
- 110 -
◆ Lets your users communicate with users outside the enterprise firewall
● Microsoft Skype for Business SBA (Survivable Branch Appliance)
◆ Ensures access to data and voice services in the event of a WAN outage
6. In the 'FQDN' field, enter the device's Fully Qualified Domain Name.
7. Under the SQL Server DB section, enter in the 'IP Address' field the IP address of the SQL
Server. Applies to the centralized Skype for Business database.
Microsoft Skype for Business Server for customers with multiple FrontEnd servers and
one SQL server.
● Up to two Microsoft Skype for Business solutions in one OVOC application.
● Microsoft Skype for Business Server limitation: When functioning with Skype for
Business server pools (FE, Edge and Mediation), the FE server defined in the
OVOC functions as the monitoring SQL database. After connecting, the OVOC
presents all Call Details from the Skype for Business network in the OVOC's Calls
List and Call Details views. When functioning with Skype for Business pools, FE,
Edge and Mediation servers cannot be defined in the OVOC, so the entire Skype
for Business network is presented in the OVOC only as a single object, namely, the
monitoring SQL database.
8. Select either the:

● 'SQL Port' option and in the now-activated field enter the port number of the SQL Server.
Applies to the centralized Skype for Business database.
● 'SQL Instance Name' option (by default selected)
9. [Optional] From the 'Connection Mode' drop-down, select:
● Windows Authentication to allow the connection between the MS-SQL Server
(Microsoft Front End) and the OVOC Server to be authenticated using a Windows user's
credentials (password and user)
● SQL Server Authentication (default) to allow the connection between the MS-SQL
Server (Microsoft Front End) and the OVOC Server to be authenticated using the SQL
Server user's credentials
10. In the 'User Name' field, enter the user of the SQL Server or Windows Server. Applies to the
centralized Skype for Business database.
11. In the 'Password' field, enter the Password of the SQL Server or Windows Server. Applies to
the centralized Skype for Business database.
12. In the 'Domain' field (relevant only when 'Connection Mode' is configured to Windows
Authentication), enter the Windows Server user's domain.
13. From the 'SSL' drop-down, secure the connection between the OVOC and the SQL server over
SSL by selecting either:
● Trusted: An SSL connection between the OVOC server and the SQL server is opened,
though it's not authenticated using a certificate.
● Using Certificate: An SSL connection between the OVOC and the SQL server is opened.
The OVOC authenticates the SSL connection using a certificate. Make sure you load the
SSL certificate file, required by the SQL server, to the Software Manager. See Adding
Configuration Files to the OVOC's Software Manager on page 72.
Default: Disabled. The SSL connection with the SQL server is by default non-secured.
14. [Optional] In the 'Address' field, enter the first letters in the name of the city / country in which
15. Click the now-activated OK button; the Skype for Business device is added.
- 111 -
Backing up a Device's Configuration using Backup

Manager
You can manually back up a device's configuration to the OVOC server using the Backup Manager.
For details on configuring automatic periodic device configuration backups, see Enabling Automatic
Device Backup Periodically on page 80.
Manually Backing up a Device's Configuration

The Backup Manager page lets you manually back up a device configuration on the server.
➢ To manually back up a device's configuration on the OVOC server:

1. In the OVOC, open the Backup Manager page (Network > Devices > Backup Manager).
Figure 4-30: Backup Manager
The Backup Manager page displays:

● Backup Summary pane: For all files that have been backed up to the OVOC for each
device.
● Backup Files pane: Full list of all the backup ini and CLI script (MSBR devices files) for
CPE devices files that have been saved to the Backup Manager for all devices.
Each entry in the summary displays:
● Device Name and Product Type
● The number of files backed up from the device to the OVOC
● The last backup status, e.g., Successful
● The date of the last backup file
● The tenant under which the device is located
You can filter displayed files for more effective access to the specific files you need:
● Click a column header; files are displayed accordingly.
Backed-up file names are in the format:
node id||timestamp _ Device IP Address _ Node ID _ Serial Number _ periodic/manual _ Product
type _ INI/CONF/CLI _ Date Formatted
Here's an example of a backed-up filename:
411515387481228_192.168.200.47_41_3968002_m_82_INI_TYPE_2258-Jan-07-2018.ini
Use the following table as reference to the example.
- 112 -
Table 4-7: Explanation of Backed Up File Name Format
File Name
Explanation
Format
411515387481228 Indicates the Node ID||Timestamp
192.168.200.47 Indicates the device's IP address
41 Indicates the Node ID
3968002 Indicates the Serial Number
m Indicates whether backup was periodic or manual. In the example, it was

manual.
82 Indicates the product type.
INI_TYPE Indicates the type of backed-up file: INI/CONF/CLI
2258-Jan-07-2018 Indicates the time and date, formatted as: HHmm-MMM-dd-yyyy
2. In the page's Backup Summary, select the device whose configuration (ini or cli script file) you
want to back up on the OVOC server.
3. From the Actions' drop-down, select the Backup option; you're prompted with a message 'Are
you sure you want to upload configuration from this device?'
Figure 4-31: Backup Manager – Backing up a Device's Configuration – Confirmation Prompt
4. Click Upload; the configuration is uploaded from the device to the OVOC server.
Saving the Last Backed-up Configuration to your PC

You can save the last backed-up device configuration to your PC.
➢ To save the last backed-up configuration to your PC:

1. In the Backup Manager page's Backup Summary, select the device whose last backed-up
configuration you want to save.
2. From the Actions' drop-down, select the option Save; the last backed-up device configuration
is saved on your PC.
Restoring the Last Backed-up Configuration to the Device

The last backed-up configuration can be restored to the device if necessary.
➢ To restore the last backed up configuration to the device:

1. In the page's Backup Summary pane, select the device whose last backup you want to
restore.
- 113 -
2. From the Actions' drop-down, select the option Restore Last Backup; you're prompted with a
message 'Are you sure you want to download configuration to this device?'.
Figure 4-32: Backup Manager – Restoring a Device's Last Backup – Confirmation Prompt
3. Click Download; the configuration is downloaded from the PC to the device.
Adding Links
Links are logical VoIP communication paths between devices that measure and display key
metrics on calls made on them. Links are defined according to IP Group (IP network entity such as
a server, e.g., IP PBX, or a group of users, e.g., LAN IP phones, with which the E- SBC
communicates), Trunk Group (logical group of physical trunks and channels), Phone Number or
SIP IP address.
The ‘source’ device on which key metrics monitoring is based must be an AudioCodes device or
Skype for Business device. The second device can be an AudioCodes device, Skype for Business
device or a non-AudioCodes device. You can define one or more links between devices. The links
are displayed in the Network Topology page. The voice quality status on each device/link is
indicated by the color green, yellow or red, i.e., good, fair or poor, based on QoE thresholds
described in Obtaining Quality Statistics on Calls on page 226.
You can add a link from the Topology page's Add Link drop-down or you can pull a line connector
from a device and connect it to another device on the page.
➢ To add a link:
1. After configuring devices, open the Links page (Network > Links).
Figure 4-33: Links
2. Click Add.
- 114 -
Figure 4-34: Link Details
3. Use the following table as reference.

Table 4-8: Adding a Link – Parameter Descriptions
Name Enter an intuitive name for the link to facilitate effective

management later.
Direction Defines the direction of the port link between source and
destination device. When the link is configured as Bi
Directional (for example), a bi-directional port will be used for
this connection.
Source Device From the drop-down list, select the source device fromwhich to
link to the destination device. You can alternatively search for
it.
Destination Device From the drop-down list, select the destination device to which
to link from the source device. You can alternatively search for
it.
The link counts and computes statistics on all calls that originate in the source device, based
on one of the following Category Types (selected from the 'Category Type' drop-down:
Category Type From the drop-down select one of the following Category
Types. Based on your selection, the link will count and
compute statistics on all calls originating in the source device.
- 115 -
IP Group - Defines the source device IP-Group index (a list of

options may be available).
Trunk Group - Lets you configure Trunk Groups, i.e., logical

groups of physical trunks and channels each of which can
include multiple trunks and ranges of channels. Trunk Groups
need to be configured and assigned with telephone numbers to
enable and activate the channels of the device. After
configuring Trunk Groups, you need to use them for routing
incoming IP calls to the Tel side, which is represented by a
specific Trunk Group (ID). You can also use Trunk Groups for
routing Tel calls to the IP side.
Phone Prefix - Defines the prefix text of a phone number or SIP

URI string. See the Note following for more information.
Control IP - Defines a valid IP-Address on which SIP control

messages are originated.
Media IP - Defines a valid IP-Address on which SIP media

messages (voice/fax) are originated. See the Note following for
more information.
Media Realm - Defines the source device Media Realm index

(a list of options may be available).
Remote Media Subnet - Defines the source device Media

Realm subnet index (a list of options may be available; Media
Realm must also be defined).
FQDN - Available only when the source device is a Skype for

Business device. The FQDN of the selected source and
destination devices.
4. The field below 'Category Type' (see the preceding parameter) is the category value field which
updates according to what you selected for 'Category Type'. If for 'Category Type' you
selected:
● IP Group (for example), then IP Group Value is displayed in this field. Enter the IP
Group's ID.
- 116 -
● Trunk Group (for example), then Trunk Group Value is displayed. Enter the Trunk
Group's ID.
● Control IP (for example), then Control IP Value is displayed. Enter the IP address (the
actual IP address, not the group ID).
● Media IP (for example), then Media IP Value is displayed. Enter the IP address (the
actual IP address, not the group ID).
Note that some categories for 'Category Type', like Remote Media Subnet and FQDN,
present two value fields, as shown in the following figure.
If you configured parameter 'Category Type' as Phone Prefix, Control IP or Media IP

(see the previous parameter), you can enter a regular expression instead of a string in
the field under 'Category Type' which updates according to 'Category Type'. If the
regular expression will be matched, the call will be sent over the link. Following are
examples of regular expressions:
.* = any value will be accepted, for example, abc, 123, abc123
a.* = any value beginning with the letter 'a' will be accepted, for example, abc, a,
abc123
.*a = any value ending with the letter 'a' will be accepted, for example, bca, a, bc123a
\\d = any value containing a single digit will be accepted, for example, 1, 2
\\d\\d\\d\\.\\d\\d\\.\\d\\d\\d\\.\\d\\d\\d = any value that contains (three digits - point -
two digits - point - three digits - point - three digits) will be accepted, for example, IP
address 172.17.118.165
To test complex regular expressions use either:
https://www.freeformatter.com/regex-tester.html
-OR-
https://regex101.com/
5. Click Apply; the link is added and displayed in the SEM.
- 117 -
● Statistics obtained from Links form a subset of those obtained from Devices
● Links statistics are obtained from streams. A stream is a single leg of an SBC call.
It's therefore possible for the total links streams statistics to be higher than the total
devices calls statistics. For example, when a call is sent from IP Group 1 to IP
Group 2 on same device, and there are two links configured to aggregate streams
from IP Group 1 and IP Group 2 respectively, the total Links statistics will present
it as twostreams but Devices statistics will present it as one call.
● Links are logical entities. Multiple links defined on the same device may therefore
aggregate statistics on the same streams, so the total number of links streams
statistics in the network may be higher than the total number of actual streams
statistics in the network.
It's therefore recommended to avoid overlapping links definitions.
Adding Sites
A site is a group of endpoints under which endpoints (phones) are located. You need to define a site
under a region. The region must be defined under a tenant.
➢ To add a site:
1. After configuring the region under which to locate the site, open the Sites page (Network >
Sites).
Figure 4-35: Sites
2. Click Add.
- 118 -
Figure 4-36: Site Details
3. From the 'Region' drop-down, select the region under which to locate the site.
4. Provide an intuitive name for the site to facilitate effective, intuitive management later.
5. Enter a description of the site to facilitate effective, intuitive management later.
6. Enter a Subnet Mask or multiple Subnet Masks. The format must be (for example)
255.255.0.0/1. Used for auto detection of endpoints. Must be contained in the same subnet
mask as the subnet mask of the region under which it is defined - if the region was configured
with a subnet mask.
7. [Optional] In the 'Location' field, enter the first letters in the name of the city / country in which
to locate the site, and then select the city / country from the list that pops up.
8. Click the now-enabled OK button; the site is added.
Managing Endpoints
The OVOC supports endpoints management through the directly accessible Device Manager
application.
Dynamic Allocation of Endpoint Licenses

The OVOC dynamically allocates endpoint licenses to tenants by default, so that distribution is
evenly and effectively performed. When a phone (endpoint) is connected to the network for the first
time, it reports to the OVOC with a keepalive message. The OVOC adds the phone to its database
and dynamically allocates licenses to its tenant.
Here’s an example to clarify the principle of dynamic allocation.
- 119 -
Figure 4-37: Example of Dynamic Allocation of Phone Licenses to Tenants
In the example (refer to the figure above):

■ Out of the total number of phone licenses which the enterprise purchased (100), indicated by
OVOC server parameter 'Managed Endpoints', the OVOC has already allocated 60.
● Tenant A was allocated 20
● Tenant B was allocated 20
● Tenant C was allocated 20
■ The OVOC is left with 40 free phone licenses which it can still allocate to tenants
(100 total – 60 allocated = 40 free)
■ A new phone is connected to the enterprise network
■ The OVOC detects the new phone added under Tenant A, adds the phone to the OVOC
database and dynamically allocates to the phone's tenant 5% of the number of phone licenses
that can still be allocated (5% of 40) or, if this results in less than 5 licenses, then 5 are
allocated. 5% of 40 is 2, so in the example, 5 licenses are allocated to Tenant A.
● Applies to all AudioCodes phones whose management is supported by Device

Manager, and to all phones which support SIP PUBLISH protocol and whose QoE
management is supported by the OVOC's Reports application.
● Before version 7.4.2000, if a tenant's allocation was full, the OVOC dropped the
phone and the user manually added it to another tenant in the OVOC GUI.
● An alarm endpointsFloatingLicenseEvent is sent when dynamic allocation occurs.
See the Alarms Guide for more information.
Configuring Endpoints
The OVOC lets you directly access the Device Manager application to configure endpoints
(phones).
➢ To access the Device Manager:

1. Select Configuration from the Endpoints drop-down under the Network menu.
- 120 -
Figure 4-38: Login to Device Manager
2. See the Device Manager Administrator's Manual for detailed information on how to configure
phones.
Monitoring Endpoints Status

The OVOC lets you monitor phones statuses.
➢ To monitor phones statuses:

1. Open the Endpoints page (Network > Endpoints drop-down > Status).
Figure 4-39: Endpoints - Status
2. See the Device Manager Administrator's Manual for detailed information on how to determine
phones statuses.
Removing Endpoints from QoE Support

Removing an endpoint from QoE monitoring removes the endpoint from QoE support, freeing the
used license. It does not remove the endpoint from display in the Endpoints page of the OVOC.
➢ To remove an endpoint from QoE support:

1. Open the Endpoints page as described previously and select the phone to remove from QoE
support.
2. Click the button Remove from QoE Monitoring; the relevant 'QoE Supported' column is
updated with X instead of ü.
- 121 -
CHAPTER 5 Managing SBC Licenses OVOC | User's Manual
5 Managing SBC Licenses

SBC licenses can be managed using one of following three optional methods:
■ Floating License monitoring method (see here)
● This method replaced the legacy method of using the OVOC Advanced Monitoring
package (SEM)
● The method requires the SBCs to be loaded with version 7.2.202 or later and an OVOC
version 7.2.3000 or later
■ Fixed License Pool (see Managing Device Licenses in the Fixed License Pool on page 134)
● Best when multiple SBCs are deployed and management wants to centrally manage the
licenses of all
● Allows a 'tenant' operator to update licenses from a central pool in a simple process
■ Locally by loading an ini file to the device using the Web interface, without requiring the
OVOC. See the device’s User Manual.
Configuring SBC Floating License Monitoring

Floating License monitoring can be configured on the AudioCodes SBCs and OVOC. For more
information, see also the Mediant SBC User’s Manual.
The Floating License monitoring method replaced the legacy method of using the OVOC Advanced
Monitoring package (SEM). The Floating License method requires that the SBCs are loaded with
version 7.2.202 or later and an OVOC version 7.2.3000 or later.
Figure 5-1: Floating License Monitoring Network
Here's how the Floating License method works:

■ SBCs report their usage statistics at short intervals (typically every 5 minutes) to the OVOC.
■ The OVOC accumulates these reports and sends them once a day to the AudioCodes Floating
License server. Since all communications occur over HTTPS, a special firewall setup is
unnecessary in most cases.
- 122 -
Important note before installation: To set up floating license monitoring for a new
customer, a floating license account must be created on the AudioCodes cloud license
manager (CLM) service. The CLM account is created by AudioCodes within a few days
of receiving a floating license order and signing of the floating license's Terms and
Conditions. After the account is set up and ready for use, a confirmation email is sent to
the email address used to receive the customer’s OVOC product key. Make sure the
confirmation email is received before attempting to connect OVOC to the CLM service.
If no confirmation email is received, contact your AudioCodes representative and
provide your OVOC product key to verify the CLM account was set up.
Managed as an AudioCodes cloud service, the Floating License feature is a network-wide license
intended for customer deployments featuring multiple SBCs sharing a dynamic pool of resources.
The feature simplifies network capacity planning and delivers cost benefits related to aggregated
call statistics, follow-the-sun scenarios and disaster recovery setups that involve two or more data
centers.
The feature allows customers to 'pay as they grow' by eliminating the need to manually purchase
additional SBC licenses when capacity requirements increase. Customers initially purchase
license capacity based on estimated requirements but may later experience business growth and
therefore require increased session capacity. In this case, customers are billed for the additional
sessions. SBCs deployed in the network are ‘open’ to maximum hardware capacity utilization
based on predefined profiles. SBCs can alternatively be configured by operators with customized
session capacity profiles.
Configuring the OVOC for Floating License Monitoring

Configuration should only be performed once for the OVOC of each customer.
➢ To configure the OVOC:

1. Add a new OVOC operator of type 'System' dedicated to the Floating License (i.e., 'Floating
License_User').
● They must have Admin or Operator security level
● Password expiration must be set to never expire
● SBCs use them to communicate with the OVOC for the floating license reports
2. Make sure the OVOC is configured with a Feature Key which enables Floating License.
● Open the License Configuration page (System > Administration > License >
Configuration).
● Make sure that 'Status' under the page section Floating License, is Enable.
Figure 5-2: Floating License Status - Enable
3. Open the Floating License page (System > Administration > License > Floating License).
- 123 -
Figure 5-3: Floating License
4. Configure the parameters like this:

● Floating License OVOC Operator: Use the new operator you configured here.
● Floating License Server Address: Set to: clm.audiocodes.com
● Change Floating License Key: Set to the OVOC Product Key. To find out the OVOC
Product Key, view the string in the License Configuration screen (System >
Administration > License > Configuration) under section 'General'.
Figure 5-4: Product Key
5. Open the Device Floating License page (Network > Devices > Floating License).
Figure 5-5: Device Floating License Page
● Make sure in the Device Floating License page that the OVOC successfully registered
with the Floating License. Make sure that 'Customer Status' in the device's Floating
License Summary pane displays Active.
- 124 -
Figure 5-6: Customer Status
Adding an SBC to the Floating License

Before adding an SBC to the Floating License, add an SBC to the OVOC using one of these
options:
■ Auto device detection. This is the Automatic Provisioning a.k.a. Zero Touch feature. See
Enabling Initial Connection Provisioning on page 102 for more information.
■ Manually from the AC Device page (Network > Add > AC Device).
■ Using the SBC's Web interface.
The Floating License method does not require configuring an open license on the SBC
(obtained via ordering of one of the device float CPNs i.e. SW/M500/FLOAT).
The SBC is authorized by the OVOC to operate in a mode with no resource restrictions.
➢ To add an SBC to the Floating License:

1. Open the Floating License page (Setup menu > Administration tab > Maintenance folder >
Floating License).
2. From the 'Floating License' drop-down list, select Enable.
Figure 5-7: Enable Floating License
- 125 -
3. Reset the device with a burn-to-flash for your settings to take effect. After the device resets, it
connects with OVOC and the following read-only fields display OVOC-related information:
● 'Connection with OVOC': Displays the device's connectivity status with OVOC:
◆ "Connected to OVOC": The device is connected to OVOC.
◆ "Disconnected from OVOC" The device is temporarily disconnected from OVOC due
to problems with the network (HTTPS TCP connection).
◆ "Not Connected to OVOC": The device is not connected to OVOC.
● 'OVOC IP Address': Displays the IP address of OVOC.
● 'OVOC Product Key': Displays the Product Key of the OVOC tool that is providing
the Floating License.
4. From the 'Allocation Profile' drop-down list, select an SBC license Allocation Profile. The
Allocation Profile determines the capacity of each SBC license type that you want allocated to
your device by OVOC. You can choose from factory default profiles, which may suit your
deployment requirements or you can configure your own customized profile. The optional
factory default profiles include:
● SIP Trunking: This profile is suited for SIP Trunking applications (i.e., where user
registration is typically not required)
● Registered Users: This profile is suited for applications where user registration is
required.
To configure your own profile, select Custom , and then configure the capacity for each SBC
license type in the corresponding 'Allocation' field. When you hover your mouse over each field, a
pop-up appears displaying the maximum capacity that can be supported by the device.
Figure 5-8: Maximum Capacity for Each SBC License Type
When configuring your own customized profile (i.e., using the Custom option), the
Transcoding Session capacity license cannot be changed in the 'Allocation' field, but
you can reduce the license using its corresponding 'Limit' field.
● Explanation of each profile:

◆ Far End Users (FEU) (# of concurrent users that can be registered on the device)
◆ SBC Sessions (# of concurrent SBC call sessions-media and signaling)
◆ SBC Signaling Sessions (# of concurrent SIP messages- only signaling)
◆ Transcoding Sessions (# of concurrent codec types)
5. Reset the device with a burn-to-flash for your settings to take effect.
6. Once you have configured the Allocation Profile, you can modify each SBC license capacity
without resetting the device. To do this, select the check box corresponding to the license type
you want to modify, and then in the corresponding 'Limit' field, enter a new value, and then click
Apply.
- 126 -
7. Open the OVOC's Device Floating License page (Network > Devices > Floating License)
and verify that the newly added SBC appears in the list and that the last report time is updated
(indicating that the SBC has successfully sent a report to the OVOC). As reports are sent
every 5 minutes, this may take up to 5 minutes to show.
Figure 5-9: Device Floating License Page – Newly Added SBC Appears in the List
8. Use the following table as reference to the page's columns.

Table 5-1: Floating License Page Column Descriptions
Column Description
Name Indicates the name of the managed device
Product Indicates the SBC device type.

Type
Address Indicates the IP address of the managed device.
HA Indicates the HA status of the device.
Managed Indicates whether the device is managed by the Floating License service server.
Last Indicates the date and time that the last usage report was sent from the OVOC to
Report the Floating License service server.
Floating Indicates the global device status reflecting the Device Status, Config Status and
License Report Status states.
Status
Green OK: Device Status, Config Status and Report Status are
green.
Red Error or Config Error: Indicates Device Status, Config Status

or Report Status errors (red).
Grey Unmanaged: Device is unmanaged by OVOC

Unmonitored: Device is unmonitored by OVOC
- 127 -
Column Description
Device Green Connected: Device is successfully connected to the Floating

Status License OVOC service.
Red Rejected: Device Floating License has been revoked by the

Cloud Floating License service and as a result the device’s
CAC is reset to 0.
Not Connected: Device is unable to establish a connection
with the Floating License OVOC service (CAC 0)
Temporarily Disconnected: Device is temporarily
disconnected from the Floating License OVOC service due to
problems with the HTTPS TCP connection.
Grey Unmanaged: The device is currently not managed by the

OVOC Floating License service.
Unmonitored: The device is currently unmonitored by the
OVOC Floating License service.
Not Applicable: The device was loaded with the Floating
License feature disabled. The operator must enable the feature
on the SBC device and reset it.
Config Green Success: Indicates that the device’s SNMP configuration is

Status successfully updated.
Red Failure: Indicates that the device’s SNMP configuration has

not been updated successfully. For example, the Floating
License REST operator’s user password or username has not
been updated correctly.
Grey Not applicable: Indicates that the device was added to the
OVOC but is not yet managed.
Unmonitored: Indicates that the device is currently
unmonitored by OVOC.
Report Green OK: Indicates that a report was successfully sent from the
Status device to the OVOC for the last reporting interval.
Red Fail: Indicates that there was a reporting failure for the last
reporting interval.
Grey Unmonitored: Indicates that the device is currently

unmonitored by OVOC.
Region Indicates the device’s region.
Tenant Indicates the device’s tenant.
9. Click the Actions button. See here for information about the actions that you can perform in the
Device Floating License page.
Performing Floating License Actions

Here’re the Actions you can perform in the Device Floating License page:
■ Unmanage (see here)
■ Update (see here)
- 128 -
■ Reset (see Reset below)

■ Register (see Register below)
Unmanage
This Action allows the device to be unmanaged by the Floating License method.
➢ To allow the device to be unmanaged by the Floating License method:

■ In the Device Floating License page, select the SBC to unmanage and then from the Actions
drop-down menu, select Unmanage.
Figure 5-10: Device Floating License Page – Unmanage Action
Update
Select this menu option for the action to update the HTTPS Rest connection between the device
and OVOC.
Reset
Select this menu option when:
■ The SBC is connected to the OVOC and Floating License is enabled.
■ One of the following SBC Web interface Floating License parameters is updated on the device:
● Allocation Profile
● Allocation Signaling Sessions
● Allocation Media Sessions
● Allocation Registered Users
■ A 'Limit' value is configured for one of the above SBC Web interface Floating License
parameters.
■ The SBC's ini file parameter 'SoftwareDSP' is updated (only applies to Mediant 9000, Mediant
SE and Mediant VE).
Register
Select this menu option for the action to perform random registration to the Floating License Cloud
service for the device.
Configuring OVOC-Floating License Service Communications

SBCs are connected to the OVOC over SNMP. Floating License service functions are managed
over TCP/HTTPS REST connections. For more information, see the OVOC IOM and the OVOC
Security Guidelines.
- 129 -
➢ To configure device Floating License parameters for OVOC-Floating License com-

munications:
1. Open the Floating License page (System > Administration > License > Floating License).
Figure 5-11: Floating License
2. Configure the parameters using the following table as reference.

Table 5-2: Device Floating License Configuration Parameter Descriptions
Floating Specifies the OVOC operator with REST authorization to receive and respond to
License REST requests from the SBC devices. This operator must be a 'System' type
OVOC operator with either 'Admin' or 'Operator' security permissions.
Operator
Floating Specifies the server address of the Floating License Service platform:
License CLM.audiocodes.com (default)
Server
Address
Change Enter the AudioCodes provided OVOC Product Key string used to authenticate
Floating the connection between the OVOC and the Floating License Service. You can
License view this string in the License Summary screen (System > Administration >
Key License > Summary).
Viewing Floating License Summaries

The OVOC's Device Floating License page displays summary panes on the right side of the page.
Panes you can view are:
■ Device Floating License Utilization pane (see here)
■ Floating License Info pane (see Viewing Floating License Info on page 132)
■ Device Info pane (see Viewing Device Info on page 132)
Device Floating License Utilization Pane

This pane is only displayed when no device is selected in the page.
➢ To view the pane if a device is selected:

1. Press the Ctrl key and then click the entry on the page that is selected.
- 130 -
Figure 5-12: Device Floating License Summary
2. Use the following table as reference to the pane.

Table 5-3: Device Floating License Utilization Pane Description
License
Description
Utilization
Total/Allocated Indicates the percentage of SBC devices in this OVOC installation that are
bar managed by the Floating license. For example, if the customer has
purchased licenses for 100 devices and 50 are currently managed, then this
bar displays 50 allocated devices and 50 free devices.
Address Indicates the IP address or FQDN of Floating License Service.
Registered Indicates whether OVOC is successfully registered to Floating License

Service.
Customer Indicates the state of the connection with the Floating License service.
Status OK - Indicates that a successful connection with the Floating License has
been established.
Blocked - Customer account has been blocked by the Floating License Ser-
vice.
Unknown - Status is undetermined by the OVOC
Last Indicates the time and date of the last successful usage report update that
Successful was sent from OVOC to the Floating License Cloud service.
Usage Report
Time
Last Sent Indicates whether the last attempt to send a usage report to the Floating
Successful/ License Cloud service was successful.
Failed
Number of Indicates the number of failed attempts to send usage reports to the Floating
Failed License Cloud service
- 131 -
Viewing Floating License Info

The OVOC's Device Floating License page displays the 'Floating License Info' summary pane only
when a device is selected in the page.
➢ To view the pane:

1. Select an entry on the page.
Figure 5-13: Device Floating License Summary – Floating License Info
2. Use the following table as reference to the pane's session capacities displayed.
Table 5-4: Device Floating License Summary - Floating License Info
Session Capacity Description
Current Indicates the currently utilized session capacity of the SBC device.
Maximum Indicates the customer configured session capacity on the SBC

Configuration device.
Maximum Actual Indicates the maximum physical session capacity of the SBC
device.
Viewing Device Info

The OVOC's Device Floating License page displays the 'Floating License Info' summary pane only
when a device is selected in the page.
➢ To view the pane:

1. Select an entry on the page if none is selected and then in the Device Floating License
Summary pane, click the Device Info tab.
Figure 5-14: Device Floating License Summary – Device Info
- 132 -
2. The pane summarizes the columns displayed in the main section of the Device Floating
License page.
Saving a Usage Data Report to your PC

Customers who do not want usage reports to be sent automatically to AudioCodes but would rather
export reports to a CSV file, download to a PC and then send manually to AudioCodes, can benefit
from this feature.
If you do not use this feature, the SBC automatically sends usage reports every five minutes to the
OVOC. Each report includes the currently configured license session values and the device's HA
state.
➢ To manually export a usage report to a CSV file:

1. Open the Device Floating License page (Network > Devices > Floating License) and click
Save Data Usage.
Figure 5-15: Save Usage Report Data
2. In the Save Usage Report Data screen shown above, define the period on which to produce the
usage report data and then click OK.
- 133 -
Managing Device Licenses in the Fixed License Pool
Only a 'tenant' operator can manage the Fixed License Pool. To configure a 'tenant'
operator, see License Pool Operator on page 86 for more information.
Customers who deploy multiple SBCs and want to centrally manage the licenses of all SBCs
deployed will benefit best from the Fixed License Pool feature. This feature allows updating a
device's license using the process shown here:
■ OVOC operator updates SBC license in OVOC's License Pool

■ OVOC notifies SBC that the License Pool has been updated
■ SBC requests updated license from OVOC
■ OVOC sends the updated license to SBC
■ SBC polls OVOC for license updates
● every 12 hours
● when the SBC is reset
● (HA) when switchover and synchronization by the new active device are performed
■ OVOC sends the license update to the SBC (if an update is discovered)
An SBC's license is valid for seven days but this is reset each time a successful con-
nection is established between it and the OVOC License Pool. If the SBC cannot con-
nect to the License Pool for seven days, its license expires and resets with its initial
'local' license. This feature prevents misuse of issued licenses.
The Fixed License Pool page in the OVOC allows you to:
■ centrally distribute session licenses to multiple devices according to capacity requirements
■ manage the licenses of multiple devices without changing their local License Key.
■ add/remove licenses to/from devices according to site requirements, independently of
AudioCodes.
■ apply different settings to each device without requiring a new License Key file per device from
AudioCodes each time.
■ manage licenses for multiple enterprise customers [ITSPs].
The Fixed License Pool supports the following license types:
■ SBC sessions (includes both media and signaling)
■ SBC Registrations (also referred to as Far-End Users)
■ SBC Signaling sessions (includes only signaling)
■ Transcoding sessions
The customer purchases a bulk number of licenses of these types and obtains a License Key to
install on the OVOC. The customer can then:
■ allocate licenses to any SBC managed by the OVOC
■ move licenses from any SBC back to the License Pool
■ move licenses from one SBC to another
■ purchase additional licenses for the pool at any time
- 134 -
When license capacity is fully utilized, the SBC rejects calls. If the SBC also has a 'local' license,
the two are cumulated to constitute a single license.
➢ To update a license using the Fixed License Pool:

1. Open the Fixed License Pool page (Network > Devices).
2. In the page, select a device and then click the Actions button.
Figure 5-16: Fixed License Pool - Refresh Device License
3. Use the table as reference to the icons in the column 'LP Status' in the preceding figure.
Table 5-5: LP Status
Icon Description
License Pool status is OK
License Pool status is WARNING
License Pool status is EXPIRED
License Pool status is CONFIGURATION ERROR
License Pool status is FAILED
License Pool status is OUT OF SYNC
License Pool status is UNMANAGED
License Pool status is APPLY NEEDED
License Pool status is APPLY IN PROGRESS
License Pool status is RESET NEEDED
4. From the Actions drop-down, select Fixed License > Refresh Device License.
- 135 -
Performing License Pool Actions

The License Pool page allows operators to perform a range of actions.
Applying a License to a Device from the Pool

You can apply a license to a device.
Applies only to HA devices. A switchover is performed to apply the license parameter

on both devices.
➢ To apply a license to a device:

1. In the Fixed License Pool page, from the Actions menu select License > Apply.
Figure 5-17: Apply License
2. In the confirmation prompt, click Apply.
Saving Fixed License Pool Data to CSV File

Information displayed in the Fixed License Pool page can be exported to a CSV file. The feature is
used internally when (for example) AudioCodes requires the information from a customer who has
reported an issue.
➢ To export Fixed License Pool data to a CSV file:

1. Open the Fixed License Pool page (Network > Devices > Fixed License Pool).
- 136 -
Figure 5-18: Fixed License Pool
2. Select the device select and click Save As.
3. Click OK; locate the saved CSV file whose icon is displayed in the systray and send it to
AudioCodes.
4. To open the CSV file, click its icon or right-click and select Open.
5. View the file opened in a CSV file editor like Microsoft's Excel.
For each license (SBC column / CB column) listed in the Fixed License Pool page, four
parameters are displayed in the CSV file according to the License Info
‘Pool/Local/Actual/Active’. For example, the parameters that are displayed in the CSV
file for the Fixed License Pool page column 'SBC Session' are:
● sbcSession_pool
● sbcSession_local
● sbcSession_actual
● sbcSession_active
- 137 -
Before Performing 'Manage Device' / 'Update Device'

Make sure of the following before performing 'Manage Device' or 'Update Device':
■ Make sure sufficient licenses are allocated on the device’s tenant (System > Administration
> License > Tenants Allocations).
Figure 5-19: Make Sure Sufficient Licenses are Allocated on the Device’s Tenant
■ Make sure the device’s tenant’s 'License Pool Operator' is valid; make sure their password has
not expired (Network > Devices > Manage > select the device > Edit).
Figure 5-20: Make Sure License Pool Operator is Valid
■ Make sure the device is connected to the OVOC (Network > Devices > Manage > select the
device > Show).
- 138 -
Figure 5-21: Make Sure the Device is Connected to the OVOC
License Pool Alarms

Devices can issue the following License Pool alarms:
■ acLicensePoolInfraAlarm
■ acLicensePoolApplicationAlarm
■ acLicensePoolOverAllocationAlarm
■ acLicenseKeyHitlessUpgradeAlarm
For more information about alarms related to the License Pool, see the OVOC Alarms Guide.
- 139 -
CHAPTER 6 Assessing Network Health OVOC | User's Manual
6 Assessing Network Health

The OVOC enables you to determine the health of your IP telephony network. The OVOC provides
real-time monitoring as well as historical monitoring of network traffic, giving operators a health
monitoring functionality that includes alarms and diagnostics capability.
Assessing Health from the Network Summary

The Network Topology page displays a Network Summary pane which you can reference to quickly
assess the overall health of the network.
Figure 6-1: Network Summary
■ The four upper Network Summary panes display:
- 140 -
● The count of Devices, Links, Sites and Endpoints on which alarms are currently active.
● The color-coded number of Devices, Links, Sites and Endpoints whose status is currently
Error / Warning. If you click the # of
◆ Devices then the Device Management page opens displaying all devices whose
status is Error / Warning
◆ Links then the Links page opens displaying all links whose status is Error / Warning
◆ Sites then the Sites page opens displaying all sites whose status is Error / Warning
◆ Endpoints then the Endpoints page opens displaying all endpoints whose status is
Error / Warning
Figure 6-2: Example: 12 Endpoint Warnings
■ The Active Alarms pane displays:

● The total number of Critical, Major, Minor and Indeterminate active alarms (color-coded)
currently active in the network.
● Click any severity level's total to display only alarms of that severity level in the Alarms
page. Example: Under Critical in the Active Alarms pane above, click 1:
Figure 6-3: Alarms Filtered by Severity Level
You can select an alarm in the page to view detailed information about it in the All Alarm Details
pane on the right side of the page.
■ In the Network Summary window, the (default) Links tab displays:
● The total # of streams over links in the network.
● The maximum # of concurrent streams over links in the network.
- 141 -
● The average MOS measured over links in the network.

● The average Jitter measured over links in the network.
● The average Delay measured over links in the network.
● The average Packet Loss measured over links in the network.
Quality Distribution pie chart
● Point your cursor over a green, yellow or red segment; a pop-up indicates the # and % of
streams over links in the network whose quality was measured to be good, fair or poor
respectively. For example:
● Click any color-coded voice quality segment to open the Calls List filtered by that voice
quality score (Good, Fair or Poor).
Successful/Failed Streams pie chart
● Point your cursor over a green or red segment; a pop-up indicates the # and % of streams
over links in the network whose performance was measured to be successful or failed
respectively. For example:
● Click any color-coded segment to open the Calls List filtered by that call performance
evaluation (Successful or Failed).
■ Click the Devices tab to display:
● The total # of calls over devices in the network.
● The maximum # of concurrent calls over devices in the network.
- 142 -
● The average MOS measured over devices in the network.

● The average Jitter measured over devices in the network.
● The average Delay measured over devices in the network.
● The average Packet Loss measured over devices in the network.
calls over devices in the network whose quality was measured to be good, fair or poor
respectively.
Successful/Failed Streams pie chart
● Point your cursor over a green or red segment; a pop-up indicates the # and % of calls over
devices in the network whose performance was measured to be successful or failed
respectively.
■ Click the Endpoints tab to display:
● The total # of calls over endpoints in the network.
● The maximum # of concurrent calls over endpoints in the network.
● The average MOS measured over endpoints in the network.
● The average Jitter measured over endpoints in the network.
● The average Delay measured over endpoints in the network.
● The average Packet Loss measured over endpoints in the network.
calls over endpoints in the network whose quality was measured to be good, fair or poor
respectively.
Successful/Failed Endpoints pie chart
● Point your cursor over a green or red segment; a pop-up indicates the # and % of calls over
endpoints in the network whose performance was measured to be successful or failed
respectively.
- 143 -
Assessing Health from the Network Topology Page

The Network Topology page lets you assess overall network health at a glance. The 'tree' in the left
window of the page displays an aggregation of statuses in the network, up to the level of region.
This is the first-level navigation window:
A red-coded tenant icon indicates that there is an alarm in the tenant, or that an OVOC threshold for
voice quality has been exceeded in the tenant. This is the first-level navigation level.
In the middle window, a red-coded icon indicates that there is an alarm on a device, or that an
OVOC threshold for voice quality has been exceeded on a device. This is the second- level
navigation window:
The window lets you quickly drill down from a region to the core of an issue in a device. Very fast
access to very specific information facilitates efficient network management and network
optimization. For this reason, OVOC is an 'expert system'. A dynamic tab added to the menu bar
provides easy future access to that specific information, facilitating troubleshooting:
Figure 6-4: Dynamic Tab for Quick Future Access to Device Information
Use the following table as reference to the page section 'Device Information' shown in the
preceding figure.
Table 6-1: Device Information
Info About Status Type Description Values
Management Device Alarm Indicates the severity status ■ Critical

Status of the device's alarm, ■ Major
reported by the device;
■ Minor
usually this is the maximum
severity of the device’s ■ Warning
active alarm. ■ Indeterminate
■ Clear
- 144 -
Administration Indicates the status of the ■ Locked

Status device’s administration ■ Unlocked
Connection Indicates the status of the ■ Connected

Status device’s SNMP ■ Not Connected
connectivity
Voice Quality Control Status Indicates the status of the ■ Unmonitored

calls control as defined in ■ Clear
the QoE Status and Alarm
■ Major
rule for this device
■ Critical
Media Status Indicates the status of the ■ Unmonitored

calls media as defined in the ■ Clear
QoE Status and Alarm rule
■ Major
for this device
■ Critical
Connection Indicates the status of the ■ Not Defined – the

Status QoE connection device never
connected for calls
sending
■ Connected – device is
currently connected
and sending calls
■ Not Connected –
device was
disconnected; possible
reasons: time
synchronization
between device and
OVOC server, device
was connected but for
some reason closed
the connection
(disabled QoE
reporting)
License Management Indicates the status of the ■ Not Defined

Status license management ■ Managed - device
license contains
management license
■ Unmanaged - device
license does not
contain management
license
Voice Quality Indicates the status of the ■ Not Requested –

Status voice quality device does not require
a Voice Quality
License
- 145 -
■ Managed – device
requires and receives a
Voice Quality License
from the OVOC server
■ Unmanaged – device
requires a Voice
Quality license but the
OVOC server can’t
assign a license for
this device
OVOC License Indicates the status of the ■ Unmanaged

Status OVOC license ■ If License Pool is
configured (same
status as the status in
the Fixed License Pool
table)
■ If Floating License is
configured (same
status as the status in
the Floating License
table)
■ For information about the page section 'Device Calls', see Accessing the Calls List on
page 226. The page section 'Device Calls' mirrors the Calls List page. In the page section
'Device Calls', you can select a call made over this device and then click the Show button to
display that call's details.
■ For information about the page section 'Statistics Summary', see Viewing Statistics on Calls
over Devices on page 184 and specifically Statistics Summary on page 187. The page section
'Statistics Summary' mirrors the Statistics Summary pane in the Devices Statistics page.
■ For information about the page section 'Active Alarms | Journal Events', see Monitoring Active
Alarms to Determine Network Health on page 155 and Viewing Journal Alarms to Determine
Operator Responsibility on page 163. The page section 'Active Alarms | Journal Events'
mirrors the Active Alarms page and the Journal Alarms page.
- 146 -
Filtering to Access Specific Information

You can filter OVOC pages to quickly access specific information. Filters let you exclude unwanted
information so that only the specific information you need is displayed. An example of a filter is
Time Range, available in the Network Topology, Alarms, Calls List and Users Experience pages.
Figure 6-5: Real Time | Time Range
■ Real Time. Pages by default display real time network information. Pages continuously
refresh, presenting up-to-date network information – statistics|calls|history alarms - collected
over the last 3 hours (default).
■ Add Filter > Time Range. The page displays network information collected over a time range
you specify, e.g., 10:17 - 1:17. The page is fixed. It does not keep updating and is not
refreshable. See also the 'Pin all selected' feature described in the table in Filtering by 'Time
Range' on the next page.
- 147 -
Filtering by 'Time Range'

You can filter the Network Topology page and other pages by 'Time Range'. The 'Time Range' filter
allows you to display time range specific information on the page.
Figure 6-6: Time Range Filter
Use the following table as reference.

Table 6-2: Time Range Filter
Filter
Description
Feature
Pin all Select this option (default) to 'preserve' the filter; the filter will remain displayed in
selected every page whose tab you click. If you clear the option, the filter will only apply
locally - to the page in which you apply the filter. The feature facilitates
troubleshooting.
Back to The link is enabled when you select a filter. Clicking the link removes the filter; the
real time OVOC returns to real time.
Last 3 | Select one of these 'quick' filters in order to present only network data collected
6 | 12 | over the last 3 | 6 | 12 | 24 hours, to the exclusion of all other times.
24 hours
Custom You can customize dates and times by which to filter. Select Custom and then
click the drop-down field below it.
- 148 -
Filter
Description
Feature
In the calendar on the left, select from when to filter: Choose a month and a day and
optionally enter a time – the hour and the minutes past the hour. In the calendar on
the right, select until when to filter: Choose a month and day and optionally enter
the time – the hour and the minutes past the hour. Click Apply.
Apply Click to implement the filter. To remove the filter if necessary, click the Back to
real time link – see above.
● There is no limitation on the time you can define.

● If you define a time range of up to (and including) six hours, the OVOC will calculate
and display in the page a summation of all statistics calculated for all five-minute
intervals in the range. The interval that is in process when you define the filter will
not be included in the calculation. Only complete five-minute intervals will be
included in the calculation.
● If you define a time range of between six and 48 hours, the OVOC will calculate and
display in the page a summation of all statistics calculated for all one-hour intervals
in the range. The interval that is in process when you define the filter will not be
included in the calculation. Only complete one-hour intervals will be included in the
calculation.
● If you define a time range of more than 48 hours, the OVOC will calculate and
display in the page a summation of all statistics calculated for all one-day intervals
in the range. The interval that is in process when you define the filter will not be
included in the calculation. Only complete one-day intervals will be included in the
calculation.
- 149 -
Filtering by 'Topology'
Filtering can be performed according to 'Topology'.
Figure 6-7: Topology
Table 6-3: Topology Filter
Filter
Description
Feature
Pin all Select this option (default) in order to 'preserve' the filter; the filter will remain
selected displayed in every screen whose tab you click. If you clear the option, the filter will
only apply to the screen in which you apply the filter. The feature facilitates
troubleshooting. After the filter is applied, the OVOC becomes non real time.
Search ■ Enter a search string; all information is filtered out except for the information
related specifically to the string you entered.
■ In every page in which there is a Topology filter, you can search according to IP
address or serial number.
● Enter the IP address of the entity to search for; the entity whose IP address
you entered is displayed. Use the figure here as reference. Click the arrow
adjacent to the entity to view in a pop-up window information about the
entity and to decide if this entity is the one you are looking for. In the pop-up
window, you can also choose to perform management actions from the row
of action icons displayed lowermost.
- 150 -
Filter
Description
Feature
■ Enter the Serial Number of the entity to search for; the entity whose SN you
entered is displayed. Click the arrow adjacent to the entity to view information
about the entity in a pop-up window and to decide if this entity is the one you are
looking for. In the pop-up window, you can also choose to perform management
actions from the row of action icons displayed lowermost.
Note that the option to search per IP address and Serial Number is available in
all pages / windows in which there is a Topology tree. In the Alarms Forwarding
Rules Details screen, for example, the Open Topology Tree button opens a
window whose search field can be searched per IP address and SN.
'Tenant' Filters the page according to the tenant. At least one tenant is always defined – see
Network Architecture on page 2 for an explanation of multi-tenancy architecture.
Allows you to filter further, according to entities defined under the tenant.
- 151 -
Filtering by 'Status'
The 'Status' filter enables you to filter a page. The filter applies to the pages under the Network
menu: Topology, Devices – Manage, Links and Endpoints – Status pages.
Figure 6-8: Alarm 'Status' Filter
- 152 -

Table 6-4: Status Filter
Filter Description
OK Select to display entities whose status is clear (OK), color coded green,
for example, indicates a tenant whose status is 'OK' and indicates a
region whose status is 'OK'.
WARNING Select to display entities whose status is warning, color coded orange, for
example, indicates a tenant whose status is 'Warning' and
indicates a region whose status is 'Warning'.
ERROR Select to display entities whose status is error, color coded red, for
example, indicates a tenant whose status is Error and indicates a
region whose status is Error.
UNMONITORED Select to display entities whose status is unmonitored, color coded black,
for example, indicates a tenant whose status is 'Unmonitored' and
indicates a region whose status is 'Unmonitored'.
- 153 -
Filtering by 'More Filters'

You can filter a page by 'More Filters'.
Figure 6-9: More Filters – Network Topology Page

Table 6-5: More Filters - Network Topology Page
Filter Description
Managed by From the drop-down list, select either Both, Managed or Not managed.
license pool
Device family From the drop-down list, select the device's family type to display on the
type page: AudioCodes Devices, SmartTAP Devices, UMP Devices,
CloudBond Devices, Skype Devices, Generic Devices, or Unknown
Devices. Alternatively, enter a search string.
Device type From the drop-down list, select the device type to display on the page, for
example, Mediant 2000.
Link type From the drop-down list, select IPGroup, Trunk Group, Phone Prefix,
Control IP, Media IP, Media Realm or Remote Media Subnet to display
on the page.
- 154 -
Determining Network Health from Alarms

The Active Alarms page facilitates management of all alarms currently active in the IP telephony
network. Management includes performing actions such as deleting, acknowledging and saving
alarms to file, as well as monitoring active alarms in the network to determine network health.
Configuring Alarm Settings

For information on how to configure the way alarms and events are displayed in the Alarms pages,
see Configuring Alarms Settings on page 69.
Monitoring Active Alarms to Determine Network Health

The Active Alarms page's Active Alarm Summary pane lets you effectively monitor all the active
alarms of all severities in the IP telephony network.
➢ To monitor the active alarms:

1. Open the Active Alarms page (Alarms > Active) and locate the Active Alarms Summary pane
on the right side of the page.
Figure 6-10: Active Alarms Summary
Performing Management Actions on Active Alarms

The Active Alarms page lets you perform management actions on all alarms currently active in the
network, including deleting, acknowledging, and saving alarms to file.
➢ To perform management actions on active alarms:

1. Open the Active Alarms page (Alarms > Active).
- 155 -
Figure 6-11: Alarms - Active
2. Optionally filter the page by Topology (see Filtering by 'Topology' on page 150), Severity (see
Filtering by 'Status' on page 152), Source Type (see Filtering by 'Severity' on page 158), or
More Filters (see Filtering by 'More Filters' on page 161), and then select an alarm or multiple
alarms and click Actions.
Figure 6-12: Alarms - Actions
3. Select Acknowledge to acknowledge an alarm.

Figure 6-13: Acknowledge Alarm Confirmation
4. Select Save Alarms to File to save alarms to file for future reference.
➢ To delete an alarm or multiple alarms:

■ In the Active Alarms page, select the alarm or multiple alarms to delete, and click the Delete
button.
- 156 -
Figure 6-14: Delete Alarms Confirmation
➢ To refresh the page:

■ In the Active Alarms page, select Refresh.
➢ To enable audial alert on incoming alarms:

■ From the Actions drop-down, select Enable Alarms Sound.
➢ To disable audial alerts:

■ From the Actions drop-down, select Disable Alarms Sound.
➢ To stop automatic refresh:

■ From the Actions drop-down, select Stop Automatic Refresh.
- 157 -
Filtering by 'Severity'
The 'Severity' filter applies to the pages under the Alarms menu: Active, Journal and History
pages.
Figure 6-15: Alarm 'Severity' Filter
The 'Severity' filter lets you select

■ one severity level
■ more than one severity levels
■ all severity levels (All)
■ no severity levels (None)
The 'Severity' filter also lets you invert a selection (Invert). If you select Invert after filtering (for
example) for
■ All, then all severity levels previously selected will be cleared.
■ None, then all severity levels previously cleared will be selected.
■ Critical, then the 'Critical' severity level previously selected will be cleared and all other levels
will be selected.
- 158 -

Table 6-6: Severity Filter
Filter Description
Critical Select to display entities whose alarm severity level is critical, color coded
red.
Major Select to display entities whose alarm severity level is major, color coded
orange.
Minor Select to display entities whose alarm severity level is minor, color coded
yellow.
Warning Select to display entities whose alarm severity level is warning, color coded
blue.
Indeterminate Select to display entities whose alarm severity level is indeterminate, color
coded black.
Clear Select to display entities whose alarm severity level is clear, color coded
green.
- 159 -
Filtering by 'Source Type'

You can filter a page using the 'Source Type' filter. The filter applies to the Calls List page under the
Calls menu and the Alarms pages. The filter lets you display calls according to the entity from
which the calls reported to the OVOC.
Figure 6-16: 'Source Type' Filter

Table 6-7: 'Source Type' Filter
Filter Description
Show Devices Displays only calls whose report was sent to the OVOC from devices.
Show Sites Displays only calls whose SIP Publish report was sent by endpoints to
the OVOC from sites.
Show Links Displays only calls transmitted through links.
Show Endpoints Displays only calls whose SIP Publish report was sent to the OVOC
from endpoints.
- 160 -

Figure 6-17: More Filters – Alarms Active Page

Table 6-8: More Filters – Alarms Active Page
Filter Description
Sources Enter the name of the entity from which the alarm originated.
Alarm Select the 'Events' option for the page to display only alarms that are of type
Type events.
- 161 -
Filtering by 'Type'
The 'Type' filter augments existing filtering capability in the Alarms – Active page; you can filter the
page for 'Only Alarms' or 'Only Events'.
➢ To filter for 'Type':

1. In the Active Alarms page, click Add Filter, choose More Filters and then from the 'Type'
drop-down, select All, Only Alarms or Only Events.
Figure 6-18: Type Filter
2. View in the Active Alarms page, in the 'Name' column:

● Bell icons, if you filtered for 'Only Alarms'
● Flag icons, if you filtered for 'Only Events'
Figure 6-19: Type - Only Alarms - Bells in 'Name' Column
- 162 -
Filtering by 'Alarm Names'

The 'Alarm Names' filter augments already existing filtering capability in the Active Alarms page;
you can filter the page by alarm name.
➢ To filter by 'Alarm Names':

■ In the Active Alarms page, click Add Filter, choose More Filters and then from the 'Alarm
Names' drop-down, select the filter.
■ In the Alarms Forwarding Rule screen (Alarms > Forwarding > Add), click the tab Rule
Conditions and then from the 'Alarm Names' drop-down, select the alarm.
Viewing Journal Alarms to Determine Operator Responsibility

The Journal Alarms page lets you view actions of operators performed historically in the OVOC up
to the present. The page can help you determine if operator activity may have been responsible for
an active alarm. You can then reference the History page to verify correlation (see Viewing History
Alarms on page 165).
Figure 6-20: Journal Alarms
- 163 -
The Journal Alarms page reflects all actions performed by network administrators in
AudioCodes' Device Manager. Records of network administrator actions are sent from
the Device Manager to the OVOC server to be displayed in the OVOC Journal Alarms
page. See also AudioCodes' Device Manager Administrator's Manual.
Filtering the Alarms Journal by 'More Filters'

You can filter the Alarms Journal page by 'More Filters'.
Figure 6-21: More Filters – Alarms Journal Page

Table 6-9: More Filters – Alarms Journal Page
Filter Description
Sources Enter the name of the entity from which the alarm
originated.
Operator Enter the name of the operator according to whom to filter.
- 164 -
Viewing History Alarms

The History page displays historical alarms. The page can help you verify that an operator's action
was responsible for an active alarm.
➢ To determine if an operator's action was responsible for an active alarm:

1. Open the History page (Alarms > History).
Figure 6-22: Alarms - History
2. Click Add Filter to filter the page according to Topology, Time Range, Severity or More
Filters. For a full description of these filters, see Filtering to Access Specific Information on
page 147.
Figure 6-23: Alarms Page Filters
- 165 -
Filtering by 'Type'
The 'Type' filter augments existing filtering capability in the History Alarms page; you can filter the
page for 'Only Alarms' or 'Only Events'.
➢ To filter for 'Type':

1. In the Active Alarms page, click Add Filter, choose More Filters and then from the 'Type'
drop-down, select All, Only Alarms or Only Events.
Figure 6-24: Type Filter
2. In the 'Name' column in the Alarms History page, you can view:
● Bell icons, if you filtered for 'Only Alarms'
● Flag icons, if you filtered for 'Only Events'
Figure 6-25: History Alarms - Type Filter
- 166 -
Filtering by 'Alarm Names'

The 'Alarm Names' filter augments already existing filtering capability in the History Alarms page;
you can filter the page by alarm name.
➢ To filter by 'Alarm Names':

1. In the Alarms History page, click Add Filter, choose More Filters and then from the 'Alarm
Names' drop-down, select the filter.
Figure 6-26: 'Alarm Names' Filter
2. In the Alarms Forwarding Rule screen (Alarms > Forwarding > Add), click the tab Rule
Conditions and then from the 'Alarm Names' drop-down, select the alarm.
Forwarding Alarms
The Forwarding page lets you add an alarm forwarding rule. The OVOC can forward alarms to
multiple destinations in these formats:
■ SNMP Notifications (SNMP 1 / SNMP 2) - see Forwarding Alarms whose Destination Type is
'SNMP' on page 173
■ External Mail / Internal Mail - see Forwarding Alarms whose Destination Type is 'Mail' on
page 176
■ Syslog - see Forwarding Alarms whose Destination Type is 'Syslog' on page 179
■ Notification - see Forwarding Alarms whose Destination Type is 'Notification' on page 181
➢ To configure alarm forwarding:

1. Open the Alarms Forwarding page (Alarms > Forwarding).
- 167 -
Figure 6-27: Alarms Forwarding Page
2. Click Add.
Figure 6-28: Alarms Forwarding Rule Details – Topology Conditions
3. Configure the Topology Conditions using the following table as reference:
- 168 -
Table 6-10: Alarms Forwarding – Topology Conditions
Rule Name Define an intuitive name, to be displayed in the alarm summary screen.
Forward Allows or prevents forwarding alarms depending on the destination you

matching select. If you select Prevent forwarding matching alarms/events and
alarms/events then select Minor Alarms from the 'Severities' drop-down under the Rule
-or- Conditions tab, then minor alarms are not forwarded.
Prevent See related parameters 'Internal Mail Server From Address' and 'Internal
forwarding Mail Server Real Name' in Configuring Alarm Settings on page 155
matching
alarms/events
Enable/Disable Enables or disables the rule if the parameters and conditions configured
Rule under this tab as well as under Rule Conditions and Destinations are met.
See related parameters 'Internal Mail Server From Address' and 'Internal
Mail Server Real Name' in Configuring Alarm Settings on page 155
Rule Owner From the drop-down, select System – all tenants; the rule will then apply to
all tenants and to all regions/links/devices/sites under all tenants.
Here's what you'll then view next to 'Attachments':
all Tenant/s, all Region/s, all Device/s, all Link/s, all Site/s
If you select a specific tenant from the drop-down, the rule will apply by
default to all entities under that specified tenant.
Click Open Topology Tree and then click > to view the entities under that
tenant and if you want, to change the default.
Only the operator assigned to that tenant can view and change it. The
All/None filters next to 'Attachments' allow you to quickly specify to which
entities rule forwarding will apply, if not to all.
4. Click the Rule Conditions tab.
- 169 -
Figure 6-29: Alarms – Forwarding – Rule Conditions
- 170 -
5. Configure the screen using the following table as reference.

Table 6-11: Forwarding Alarms – Rule Conditions - Parameter Descriptions
Forward matching Allows or prevents forwarding alarms depending on the destination

alarms/events -or- you select. If you select Prevent forwarding matching
Prevent forwarding alarms/events and then select Minor Alarms from the 'Severities'
matching drop-down under the Rule Conditions tab, then minor alarms are not
alarms/events forwarded.
See also related parameters 'Internal Mail Server From Address' and
'Internal Mail Server Real Name' in Configuring Alarm Settings on
page 155
Enable/Disable Rule Enables or disables the rule if the parameters and conditions
configured under this tab as well as under Rule Conditions and
Destinations are met.
'Internal Mail Server Real Name' in Configuring Alarm Settings on
page 155
Alarm Origin Select the origin from which alarms will be forwarded:
■ Management
■ QoE
■ Devices
■ Endpoints
Event Origin Select the origin from which events will be forwarded:
■ Management
■ QoE
■ Devices
■ Endpoints
Severities From the 'Severities' drop-down, select the severity level of the alarms
you want to receive:
■ Warning
■ Minor
■ Major
■ Critical
■ Indeterminate
Default: All Selected.
Alarm Names Allows forwarding alarms according to specific alarm names. For
example, if you select Power Supply Failure then only this alarm will
be forwarded. Default: All Selected. The search field lets you find an
alarm according to name or origin.
- 171 -
Alarm Types Allows forwarding alarms according to specific alarm types. For
example, if you select communicationsAlarm then only this alarm
type will be forwarded. Default: All Selected. The search field lets you
find an alarm according to type.
Source Free text box that allows you to filter according to alarms' 'Source' field
(identical to the 'Source' column displayed in the Alarms History page).
6. Click the Destination tab.
- 172 -
Forwarding Alarms whose Destination Type is 'SNMP'

The SNMP forwarding option is typically used for integration of the OVOC with a Network
Management System (NMS). For more information about forwarding SNMP notifications, see the
OAM Integration Guide. After selecting the Destination tab, the screen whose destination type is
SNMP v2 or SNMP v3 opens by default.
Figure 6-30: Alarms – Forwarding – Destination Type - SNMP v2
- 173 -
Figure 6-31: Alarms – Forwarding – Destination Type - SNMP v3
Use the following table as reference for the 'Destination Type' parameter.
Table 6-12: Forwarding Alarms – Destination

Prevent See also related parameters 'Internal Mail Server From Address' and
forwarding 'Internal Mail Server Real Name' in Configuring Alarms Settings on page 69
matching
alarms/events
- 174 -
'Internal Mail Server Real Name' in Configuring Alarms Settings on page 69
Destination Determines the format in which the alarm or event will be forwarded.
Type From the drop-down, select
■ SNMP (default)
✔ SNMP v2
✔ SNMP v3
■ MAIL
■ SYSLOG
- 175 -
Forwarding Alarms whose Destination Type is 'Mail'
➢ To forward alarms whose destination is 'Mail':

1. In the Alarms Forwarding Rule Details screen, select MAIL from the 'Destination Type' drop-
down.
Figure 6-32: Alarms Forwarding Rule Details – Destination – Mail
2. Select the Use Internal Mail Server option.
- 176 -
Figure 6-33: Alarms Forwarding Rule Details – Destination – Mail – Use Internal Mail Server
- 177 -

Table 6-13: Forwarding Alarms - Destination – Mail
Use If this option is selected, all the fields in this table following will be deactivated,
Internal except the 'To' field. If selected, it'll only be necessary to configure the internal
Mail mail server as the destination to which to forward alarms; it'll be unnecessary to
Server configure a mail host. If the option is cleared, all the fields in the table following
will be activated.
See also related parameters 'Internal Mail Server From Address' and 'Internal
Mail Server Real Name' in Configuring Alarms Settings on page 69
Mail Host Enter the Mail Host IP address or FQDN (e.g., smtp.office365.com).
Mail Host Enter the mail host username.

Username
Mail Host Enter the mail host password.

Password
From Enter the e-mail address the recipient will see when the mail arrives.
To Enter the list of email addresses (coma separated) to which to send mail. If the
option 'Use Internal Mail Server' is selected, 'To' will be the only parameter
activated; all others will be deactivated. In this case, configure the internal mail
server as the destination to which to forward alarms.
4. Click OK; alarms are forwarded to specified email destinations in the following email format:
Title: New <Alarm/Event> <Alarm Name>, received from <Node Name> with Severity
<Severity>
Message body: will include all the fields we have today in Alarm Item
- 178 -
Forwarding Alarms whose Destination Type is 'Syslog'

Alarms can be forwarded to the Syslog destination type.
➢ To forward alarms whose Destination Type is 'Syslog':

1. In the Alarms Forwarding Rule Details screen, select SYSLOG from the 'Destination Type'
drop-down.
Figure 6-34: Destination Type 'Syslog'
- 179 -
Table 6-14: Forwarding Alarms - Destination – Syslog

matching
alarms/events
Syslog Host IP Enter the IP address of the Syslog host.

Address
Syslog Host Enter the port of the Syslog host.

Port
3. Click OK; alarms are forwarded to Syslog.

Syslog features a well-defined message format structure detailed in RFC 3164. The OVOC'S
severity levels are adjusted to the severity levels of the Syslog protocol. The following table maps
the two:
Critical Alert
Major Critical
Minor Error
Warning Warning
Indeterminate Informational
Clear Notice
The message part of the Syslog protocol contain this structure:
Title: <Alarm/Event> <Alarm Name>, received from <Node Name, Node IP> with Severity
<Severity>.
Description: <Source>, <Description>
If the alarm is forwarded from the source global IP address in an HA configuration, the device IP is
the global IP address.
- 180 -
Forwarding Alarms whose Destination Type is 'Notification'

Alarms can be forwarded to the 'Notification' destination type. After configuring this destination
type, notifications will automatically pop up in the OVOC GUI when alarms are received.
➢ To forward alarms whose Destination Type is 'Notification':

1. In the Alarms Forwarding Rule Details screen under the DESTINATION tab, select
NOTIFICATION from the 'Destination Type' drop-down.
Figure 6-35: Destination Type 'Notification'
2. Configure the parameters using the table as reference.
- 181 -
Table 6-15: Forwarding Alarms - Destination – Destination

matching
alarms/events
Assigned Under 'Destination Details', configure the operator (or operators) to whom
Operators you want the alarm notifications to be forwarded.
Note:
■ Operators whose security level is 'Admin' can assign notifications to any
operator / all operators.
■ Operators whose security level is 'Operator' can assign notifications only
to themselves.
3. Click OK; notifications will automatically pop up in the uppermost right corner in the GUIs of all
assigned operators, when alarms are received.
Figure 6-36: Notifications Pop-up
- 182 -
To configure the timeout of notification pop- ups, see Configuring Operator

Authentication Locally, in the OVOC on page 34 and refer to the parameter
'Notifications display time (sec)'. The default is 3 seconds. Configuring the parameter to
0 disables the feature.
➢ To view the notifications history:

1. Click the bell icon in the uppermost right corner of the OVOC GUI; the icon indicates the
number of notifications that have not yet been viewed; its color indicates highest alarm severity
level.
2. View the alarm notifications history.
3. In the list, you can delete a notification, clear all notifications or click a notification to open the
Alarms History page displaying that alarm.
4. Scroll down to view earlier notifications. Most recent notifications are listed first. Every
notification indicates how long ago it was listed, e.g., 4 minutes ago.
- 183 -
Viewing the New Rules in the Alarms Forwarding Page

■ The new rules are displayed in the Alarms Forwarding page (Alarms > Forwarding):
Figure 6-37: New Rules in the Alarms Forwarding Page
Assessing Network Health in the Statistics Pages

The OVOC graphically and textually displays network-wide statistics on call performance (% and #
of calls evaluated as successful or failed), voice quality (% and # of calls whose voice quality
scored good, fair or poor), etc. Statistics on calls over devices, links, sites and endpoints are
displayed. The pages help operators assess and optimize network health.
Viewing Statistics on Calls over Devices

The Devices tab under the Statistics menu allows you to make a quick assessment of the health of
the network from the perspective of calls over devices.
➢ To view statistics on calls over devices:

■ Open the Devices Statistics page (Statistics > Devices).
Figure 6-38: Devices Statistics
You can optionally filter the page by Time Range (see Filtering to Access Specific Information on
page 147) and Topology (see Filtering by 'Topology' on page 150).
The page displays (from L-R):
■ Metrics (see Metrics Bar Charts on the next page)
■ Bar Charts (see Metrics Bar Charts on the next page)
■ Statistics Summary (see Statistics Summary on page 187)
- 184 -
Metrics Bar Charts

Three metrics / bar charts are displayed by default:
■ Successful / Failed Calls chart shows the % and # of calls whose performance was evaluated
as successful or failed, distributed over time (see Filtering to Access Specific Information on
page 147 for information about the time range filter). The chart lets you assess calls
performance at a glance. The chart shows when successful calls peaked compared to when
failed calls peaked. You can compare this to other charts to identify correlations.
■ Max Concurrent Calls chart shows the maximum concurrent calls distributed over time. The
chart shows when the maximum concurrent calls peaked compared to when they dipped. You
can compare this to other charts to identify correlation. Max Concurrent Calls is the maximum
number of calls opened at the same time in the server. Note that if you click a bar to open the
Calls List page, the number of calls shown in the Calls List page might be different to the
number shown in the graph; only calls that end within the time range are displayed in the Calls
List page; if a call exceeds the time range, it won't be displayed in the Calls List page.
■ Calls Quality chart shows the distribution of voice quality (% and # of calls whose voice quality
scored Good Fair or Poor) over time. Gray indicates 'Unknown' voice quality. Point the
cursor over a color-coded bar segment in any time period to view this pop-up. The date and
time indicates when the period ended.
Figure 6-39: Calls Quality Bar Chart
Compare charts. If, for example, you identify a correlation over time between 'Poor' voice quality
and Jitter, then Jitter is the reason for the poor voice quality.
Other metrics / bar charts that you can select and display:
■ Utilization Distribution chart shows distribution of the media packets network utilization over
time. A glance shows when a high rate (in Kbps) was received or transmitted (Rx/Tx rate in
Kbps). The chart shows when a network is congested or uncongested, i.e., when voice quality
scores may be lower. To view information on a time period, position the cursor over the bar
representing the time period; the pop-up shows the date and time on which the period ended
and the Rx / Tx rate in Kbps and the kilobits consumed per second during the time period:
- 185 -
Figure 6-40: Utilization Distribution Bar Chart
■ Average Call Duration (ACD) chart shows distribution of ACD in the network over time. Point
your mouse over a bar to determine average call duration in that time interval.
■ MOS chart. Point your mouse over a bar to determine the average MOS scored in that time
interval.
■ Packet Loss chart. Point your mouse over the time axis to determine the average packet loss,
as a percentage of the total number of packets sent, measured at that time.
■ Jitter chart. Point your mouse over the time axis to determine the average jitter measured at
that time, in milliseconds.
■ Delay chart. Point your mouse over a bar to determine the average delay measured in that time
interval, in milliseconds.
■ Echo chart. Point your mouse over the time axis to determine the precise average echo
measured at that time, in DB.
Values displayed in the charts are reported by devices for representation in the OVOC.
Sometimes when reported values are higher than expected, for example, packet loss
might be higher than 100%, please contact AudioCodes Support for clarification.
- 186 -
Statistics Summary
On the right side of the Devices Statistics page, you can view the Statistics Summary pane.
Figure 6-41: Statistics Summary
The pane displays

■ the total # of calls made over devices in the time period
■ the maximum concurrent calls measured over devices in the time period
■ the values of MOS, Jitter, Delay and Packet Loss quality metrics measured over devices in the
time period
The pane also displays two metrics as pie charts:
■ Successful/Failed Calls pie chart. Point your mouse over a segment of the color-coded pie
chart to determine the # and % of calls that were evaluated as Successful or Failed in that
time interval.
■ Quality Distribution pie chart. Point your mouse over a segment of the color-coded pie chart to
determine the # and % of calls whose voice quality scored Good Fair or Poor in that time
interval.
Viewing Statistics on Streams over Links

The Links tab under the Statistics menu allows you to make a quick assessment of the health of
the network from the perspective of streams over links. Information in the page is presented
identically to information in the Devices Statistics page, described in Viewing Statistics on Calls
over Devices on page 184). You can optionally filter the page by Time Range (see Filtering to
Access Specific Information on page 147) and Topology (see Filtering by 'Topology' on page 150).
- 187 -
Viewing Statistics on Calls over Sites

The Sites tab under the Statistics menu allows you to make a quick assessment of the health of the
network from the perspective of calls over sites. Information in the page is presented identically to
information in the Devices Statistics page, described in Viewing Statistics on Calls over Devices
on page 184. You can optionally filter the page to display only the information that you require. You
can filter by Time Range (see Filtering to Access Specific Information on page 147) and Topology
(see Filtering by 'Topology' on page 150).
Viewing Statistics on Calls over Endpoints

The Endpoints tab under the Statistics menu allows you to make a quick assessment of the health
of the network from the perspective of calls over endpoints. Information in the page is presented
identically to information in the Devices Statistics page, described in Viewing Statistics on Calls
over Devices on page 184). You can optionally filter the page to display only the information that
you require. You can filter by Time Range (see Filtering to Access Specific Information on
page 147) and Topology (see Filtering by 'Topology' on page 150).
Monitoring Performance
As your network's central management application, the OVOC features Performance Monitoring
(PM) capability to help operators make sure the Quality of Service (QoS) purchased by the ITSP |
enterprise is delivered to users after it's provisioned. PM metrics are collected from VoIP network
devices. The feature allows operators to monitor historical data. Historical data allows for long-term
network analysis and planning.
● For a comprehensive list of PM parameters supported on each device, see the

Performance Monitoring Guide.
● Two OVOC pages (Perf Monitoring | PM Profiles) facilitate efficient and flexible PM
setup - see flows below this note.
✔ For information on how to use the Perf Monitoring page, see Adding a PM
Template on the next page.
✔ For information on how to use the PM Profiles page, see Adding a PM Profile
on page 193.
➢ To set up PM using the default PM template:

1. Open the Perf Monitoring page (System > Configuration > Templates > Perf Monitoring)
and make sure it displays a default Performance Monitoring (PM) template provided by
AudioCodes.
2. Add a new tenant, open the PM Profiles page (Statistics > PM Profiles) and make sure the
default PM template provided by AudioCodes is duplicated and displayed as a PM profile. This
profile is automatically attached to every newly added tenant. If other profiles are added, all
profiles listed in the page will automatically be attached to every newly added tenant.
➢ To set up PM using a configured PM template:

1. Open the Perf Monitoring page (System > Configuration > Templates > Perf Monitoring),
add a PM template and configure it as default. Optionally, delete the previous default (the
AudioCodes-provided default PM template will be the first default you'll have). The default PM
template, be it the AudioCodes-provided default or a newly configured default, cannot be
deleted.
- 188 -
2. Add a new tenant, open the PM Profiles page (Statistics > PM Profiles) and make sure the
newly configured default template is duplicated and displayed as a PM profile; this profile will
automatically be attached to every newly added tenant.
➢ To set up PM per specific device:

■ Open the PM Profiles page (Statistics > PM Profiles), add a new PM profile and in its
configuration manually attach it to a specific device.
Adding a PM Template
The OVOC includes an AudioCodes-provided default Performance Monitoring (PM) template. Para-
meters (metrics) selected in the default are those most frequently requested by AudioCodes enter-
prise and ITSP customers. The OVOC displays the default PM template in the Perf Monitoring
page (System > Configuration > Templates > Perf Monitoring).
Figure 6-42: Perf Monitoring
● The default PM template cannot be deleted. The Delete button is disabled when the
default is selected. When selected, the template's details are displayed in the right
pane; approximately 40 parameters (metrics) are included in the default.
● If you add a PM template and configure the newly added template to be the default,
the previous will lose its default configuration and you will be able to delete it. Rule:
There will always be one default PM template in the Perf Monitoring page, be it the
AudioCodes-provided default or a newly added PM template configured as the
default.
● The default PM template is duplicated as a PM profile in the PM Profiles page
(Statistics > PM Profiles) shown in the figure following. Every time you add a new
tenant, the default PM template together with all other templates (if you configured
other templates) are automatically duplicated as profiles in the PM Profiles page,
and allocated to that tenant.
Figure 6-43: PM Profiles
➢ To add a PM template:
1. Open the Perf Monitoring page (System > Configuration > Templates > Perf Monitoring)
and click Add.
- 189 -
Figure 6-44: Add PM Template
2. Configure the PM template using the table below as reference.

Table 6-16: PM Template Parameter Descriptions
Name Enter a name for the template. Choose an intuitive name to facilitate
an operator-friendly network management experience later.
Description Enter a free-text description of the template to help facilitate an

operator-friendly network management experience. Example: "This
template is for all tenants of Meteor Bank". This can help orient
operators when managing complex networks.
Default The PM Templates page always displays one default PM template. If

you select this 'Default' option, the earlier default PM template will
lose its default configuration and you'll be able to delete it from the
Perf Monitoring page. There will always be a default PM template in
the page, be it the AudioCodes-provided default PM template or a
newly added operator-configured default PM template. The PM tem-
plate configured as the default cannot be deleted. Every time you add
a tenant, all PM templates listed in the Perf Monitoring page are duplic-
ated as PM profiles in the PM Profiles page (Statistics > PM Mon-
itoring) and all PM profiles listed in the PM Profiles page are
automatically allocated to that newly added tenant.
- 190 -
Create Data File OVOC's server polls device parameters every 15 minutes and saves
the resulting PM metrics in the server's database. Select this option
to save the PM metrics (data) as a file in operator-friendly JSON
format. All PM information resulting from the poll is conveniently
located in this file. An event is sent when the file is created (see the
next parameter).
Send Event per Select this option for an event to be sent every 15 minutes, indicating
Interval that all parameters per device were successfully polled. If 10 devices
were selected for polling, the event is sent indicating that all
parameters on all 10 devices were successfully polled.
Parameters (0) Indicates how many PM metrics (check boxes) you selected to be
polled. (0) indicates that none have been selected (yet). When you
select parameters (metrics), the indication changes accordingly. The
following tabs are displayed under 'Parameters':
■ System (0) - Click the tab to select or clear the check box DSP
Utilization gauge.
■ SBC (0) - Click the tab to select or clear check boxes under 'Call
Stats', e.g., the counter Tel to IP Call Attempts and the gauge
Tel to IP Call Duration, and / or the check boxes under 'Other
Stats', e.g., Media Legs.
■ Gateway (0) - Click the tab to select or clear check boxes under
'Call Stats', e.g., the G711 Active Calls gauge and the
Attempted Calls counter, and / or the check boxes under 'Other
■ Network (0) - Click the tab to select or clear check boxes under
'Global', for example, the gauge Net Util KBytes Tx and the
counter Incoming Discarded Pkts.
■ IP Group (0) - Click the tab to select or clear the check boxes
under 'Call Stats', e.g., the gauge Invite Dialogs and / or the
check boxes under 'Other Stats', e.g., the counter Subscribe
Dialogs.
■ Trunk Group (0) - Click the tab to select or clear the check box
under 'Call Stats', i.e., the gauge Call Duration, the check box
under 'Call Failures', i.e., the counter No Resources Calls, and /
or the check boxes under 'Trunk Stats', e.g., the counter All
Trunks Busy Time.
■ SRD (0) - Click the tab to select or clear the check boxes under
'Call Stats', e.g., the gauge ASR.
See the SNMP Reference Guide for detailed information about each
PM parameter.
For SBC devices, you can also configure Performance

Monitoring parameters for counting the number of call
failures for specific SIP responses. These are configured
in the SBC device's Web interface's User Defined Failure
PM table. For more information, see the SBC device's
User's Manual.
- 191 -
Metric Name Select this option to select all check boxes (PM metrics) under all
tabs in the Call Stats pane. To include most but not all PM metrics in
your template, select 'Name' (all check boxes will be selected) and
then clear those to exclude.
Min Max Avg Value In the Call Stats pane shown in the next figure, parameters 'Tel-IP
[Minimum value, Call Attempts' and 'IP-Tel Call Attempts' are counters.
Maximum value and A single value (Val) is displayed after they're measured, i.e., # of coun-
Average value (Avg)], ted call attempts.
In the figure, parameters 'Tel-IP Call Duration' and 'IP-Tel Call Dur-
ation' are gauges. If all three adjacent check boxes are selected, the
# of calls of minimum duration, the # of calls of maximum duration and
the # of average-length calls will be monitored.
Thresholds are configured at the SBC level in the device's Web interface, in the Open
Device page. See the device's User's Manual for more information. Thresholds can
alternatively be configured in an ini file and loaded to the device in the OVOC's Software
Manager. When a PM parameter value in the device crosses the configured threshold,
the device generates an event that is sent to the OVOC.
3. Click OK (or Close to exit without saving the template).
In the PM Profiles page, operators can manually attach a PM profile to a specific device
within a tenant. For more information, see Adding a PM Profile on the next page
➢ To view PM templates:
■ Open the PM Templates page (System > Configuration > Templates > Perf Monitoring).
Figure 6-45: Performance Monitoring Templates
➢ To view the details of a specific PM template:

■ Select the row of the template whose details you want to view, as shown in the preceding
figure; the details are displayed in the right pane.
- 192 -
➢ To edit a PM template:
1. In the Perf Monitoring page (System > Configuration > Templates > Perf Monitoring),
select the template to edit and click Edit.
2. In the PM Template page that opens (identical to the page displayed when adding a template),
edit the template using the preceding table as reference.
➢ To delete a PM template:
■ In the Perf Monitoring page (System > Configuration > Templates > Perf Monitoring),
select the template to delete and click Delete.
Adding a PM Profile
PM templates are duplicated as PM profiles in the PM Profiles page (Statistics > PM Profiles).
Every time you add a new tenant, the default PM template together with all other templates (if you
configured other templates) are automatically duplicated as profiles in the PM Profiles page and
allocated to that newly added tenant.
You can manually add a PM profile in the PM Profiles page and optionally configure it to
be the default. If you configure it as the default, the previous default will lose its default
configuration and you'll be able to delete it from the page, so there will always be one
default PM profile in the PM Profiles page.
➢ To add a PM profile:
1. Open the PM Profiles page (Statistics > PM Profiles).
2. Click Add.
Figure 6-46: PM Profile
- 193 -
3. Configure a profile using the following table as reference.

Table 6-17: PM Profile Parameter Descriptions
Name Enter a name for the profile. Choose an intuitive name to facilitate an
operator-friendly network management experience in the future.
Description Enter a free-text description for the profile to help facilitate an

operator-friendly network management experience. Example: This
profile is for all tenants in England. The description can help orient
operators in complex networks.
Default The PM Profiles page always displays one default PM profile. If you
select this 'Default' option, the previously configured default PM pro-
file - be it the AudioCodes-provided default or a new operator-con-
figured default - will lose its default configuration and you'll be able to
delete it from the page. Every time you add a new tenant, the default
profile together with all other profiles (if you configured other profiles)
are automatically allocated to that tenant.
Create Data File OVOC's server polls device parameters every 15 minutes and saves
the resulting PM metrics in the server's database. Select the option
to save the PM metrics (data) as a file in operator-friendly JSON
format. All PM information resulting from the poll is conveniently
located in this file. An event is sent when the file is created (see the
next parameter).
Send Event per Select this option for an event to be sent every 15 minutes, indicating
Interval that all parameters per device were successfully polled. If 10 devices
were selected for polling, the event is sent indicating that all
parameters on all 10 devices were successfully polled.
Tenant Select from the drop-down list the tenant to allocate this PM profile
to. In the preceding figure, MeteorBank is selected.
Attachments The Devices link gives operators the option to manually select a
specific device to which to attach this PM profile. In the preceding
figure, SBC 4 is selected.
Parameters (0) Indicates how many PM metrics (check boxes) you selected to be
polled. (0) indicates that none have been selected (yet). When you
select parameters (metrics), the indication changes accordingly. The
following tabs are displayed under 'Parameters':
■ System (0) - Click the tab to select or clear the check box DSP
Utilization gauge.
■ SBC (0) - Click the tab to select or clear check boxes under 'Call
Stats', e.g., the counter Tel to IP Call Attempts and the gauge
Tel to IP Call Duration, and / or the check boxes under 'Other
■ Gateway (0) - Click the tab to select or clear check boxes under
'Call Stats', e.g., the G711 Active Calls gauge and the
Attempted Calls counter, and / or the check boxes under 'Other
- 194 -
■ Network (0) - Click the tab to select or clear check boxes under
'Global', for example, the gauge Net Util KBytes Tx and the
counter Incoming Discarded Pkts.
■ IP Group (0) - Click the tab to select or clear the check boxes
under 'Call Stats', e.g., the gauge Invite Dialogs and / or the
check boxes under 'Other Stats', e.g., the counter Subscribe
Dialogs.
■ Trunk Group (0) - Click the tab to select or clear the check box
under 'Call Stats', i.e., the gauge Call Duration, the check box
under 'Call Failures', i.e., the counter No Resources Calls, and /
or the check boxes under 'Trunk Stats', e.g., the counter All
Trunks Busy Time.
■ SRD (0) - Click the tab to select or clear the check boxes under
'Call Stats', e.g., the gauge ASR.
Metric Name Select this option to select all check boxes (PM metrics) under all
tabs in the Call Stats pane. To include most but not all PM metrics in
your profile, select 'Name' (all check boxes will be selected) and then
clear those to exclude.
Min Max Av Value In the Call Stats pane shown in the figure below, parameters 'Tel-IP
Call Attempts' and 'IP-Tel Call Attempts' are counters.
A single value (Val) is displayed after they're measured, i.e., the # of
counted call attempts.
In the figure, parameters 'Tel-IP Call Duration' and 'IP-Tel Call Dur-
ation' are gauges. If all three adjacent check boxes are selected, the
# of calls of minimum duration, the # of calls of maximum duration and
the # of average-length calls will be monitored.
Filter Only applies to tabs 'IP Group', 'Trunk Group' and 'SRD'. Enables
filtering for specific entities per index or per name. 'Trunk Group' can
be filtered only by index.
- 195 -
For example, after selecting tab 'IP Group' and then selecting By
Name, enter a regular expression in the 'Rule' field that is displayed,
e.g., ^B; all IP groups whose names begin with B will be polled. The
By Index filter enables you to filter specific indexes in the group to be
polled; if you enter 9 (for example) in the 'Rule' field, only row 9 in the
IP groups table will be polled (out of a maximum of 5000 indexes
supported). This feature allows operators more flexibility when polling
for PM.
Thresholds are configured at the SBC level in the device's Web interface, in the Open
Device page. See the device's User's Manual for more information. Thresholds can
alternatively be configured in an ini file and loaded to the device in the OVOC's Software
Manager. When a PM parameter value in the device crosses the configured threshold,
the device generates an event that is sent to the OVOC.
4. Click OK (or Close to exit without saving the profile).
➢ To view PM profiles:
1. Open the PM Profiles page (Statistics > PM Profiles).
Figure 6-47: PM Profiles
2. View the new profile displayed. In the figure, you can see that the new profile 'MeteorBank'
was configured as the default profile, replacing the provided default profile 'Factory PM Profile'.
➢ To edit a PM profile:
1. In the PM Profiles page (Statistics > PM Profiles) select the profile to edit and click Edit.
2. Use the preceding table as reference when editing.
Starting and Stopping PM Polling

The OVOC allows operators to start or stop polling a device (or multiple devices) for Performance
Monitoring metrics, in order to decrease the impact PM may have on device resources and to optim-
ize bandwidth consumption.
➢ To start | stop PM:

1. Open the Network Topology page (Network > Topology) or the Device Management page
(Network > Devices > Manage).
2. Select an entity or multiple entities to poll and then from the 'Actions' drop-down menu, select
the Start Polling action under the Performance Monitor sub-menu.
- 196 -
Figure 6-48: Start Polling
If a device does not support PM, the Performance Monitor sub-menu in the 'Actions'
drop-down menu will not be displayed. It will only be displayed if the selected device or
devices support PM.
3. After at least 15 minutes (the default polling interval), stop the polling.
Figure 6-49: Stop Polling
4. View the results of the poll.

● See Viewing PM Data Resulting from Polling below
Viewing PM Data Resulting from Polling

After polling a device (see Starting and Stopping PM Polling on the previous page), operators can
view PM data resulting from polling in:
■ the OVOC, in a device's dynamic tab (see below)
■ a data file that's created when 'Create Data File' is selected in the PM Profile (see below)
■ the OVOC, under Statistics > Devices (see below)
➢ To view PM data in a device's dynamic tab:

1. Open the Device Management page (Network > Devices > Manage), select the device whose
PM data you want to view, and then click the Show button.
2. In the device's dynamic tab's Summary page, click the Statistics tab.
- 197 -
Figure 6-50: Device Dynamic tab - Statistics
[Refer to the figure]

■ Device Name (HQ SBC) [left side of page]
■ ADD FILTER
● displays the Time Range; click to select a different one; the default is the last 24 hours,
00:00 to 23:59
● displays the metrics (parameters); click to select fewer, more or different metrics; defaults
are taken from this device's PM profile
■ Daily Summary - METRIC NAME [middle of page]:
● the search field 'Filter by parameter' can be used to display (for example) only 'Tel to IP'
metrics; all other metrics will be excluded from the list of metric values displayed:
Figure 6-51: Filter by parameter
● a summary of metric values measured over the Time Range; the default is 24 hours, from
00:00 to 23:59; the list is structured per entity
Multiple metrics can be selected using the Ctrl key on the keyboard. Operators can
select multiple metrics for tabular and graphical comparisons of the metrics.
■ Details [right side of page]:
- 198 -
● after a metric is selected in the Daily Summary list, a table and a bar chart display the
distribution details of that metric's values over each 15 minute interval in the Time Range
(the default Time Range is 24 hours, from 00:00 to 23:59)
● pointing the cursor over a bar in the chart opens a tool tip summarizing that bar; the tool tip
in the figure indicates that the maximum incoming calls per second (CAPS) was measured
on IP Group#1 (Lync) in the interval beginning 10:00 on March 20, 2019 to be 2
■ Status bar (lowermost in page):

● displays the name of the PM profile assigned to the device, the Status of the last polling
interval (Successful), the date and time at which the device was last polled, and the
number of metrics (parameters) polled in the last interval
➢ To view PM data in a data file:

■ Make sure the 'Create Data File' option in the PM Profile is selected. The OVOC's server polls
device parameters every 15 minutes and saves the resulting PM metrics in the server's
database. If this option is selected, the PM metrics (data) are saved as a file in operator-
friendly XML format. All PM information resulting from the poll will conveniently be located in
this file. An event is sent when the file is created.
➢ To access the data file:

1. In your browser, enter URL http://172.17.140.84/nbif and in the prompt, enter user name nbif
and password pass_1234.
- 199 -
Figure 6-52: NBIF Index
2. In the NBIF index, click the entry pmFiles.

Figure 6-53: NBIF Index - pmFiles
● File-naming convention:
◆ File Name Format: DeviceName_NodeId_TimeInterval.xml
◆ Time Interval Format: yyyy-MM-dd_TimeZone_HHmm
- 200 -
◆ Example: M4K1_123456_2018-04-16_IST_1200.xml
3. Open the file of the period whose PM metrics you want to view.
Figure 6-54: Data File Displayed in XML Editor
● XML file format:
- 201 -
First-Level Info Second-Level Info Third-Level Info Fourth-Level Info
Basic Device Info Tenant Name Region Name -
Device Name
Device IP Address
Serial Number (x2 if

HA)
Product Type
Software Version
Time Period From Time - -
To Time
Profile Data Profile ID - -
Profile Name
Dictionary ID
Polled Data: Structured Topics Parameter Index:Name:Value

Polled Data Name
➢ To view aggregated PM metrics from the OVOC's Statistics page:
● Explanation of aggregated PM metrics: After selecting an aggregated PM

metric, the OVOC aggregates it over all devices and device objects. For example,
after selecting aggregated PM metric X of type 'MIN' measured per IP group over
three devices, one graph is displayed; for each timestamp, the OVOC calculates
the metric's minimum value over all IP groups over the three selected devices. The
metric types are:
✔ MIN – the minimum value measured
✔ MAX – the maximum value measured
✔ AVG – the average value measured
✔ VALUE – summation of values measured
● Explanation of standalone PM metrics: Each standalone PM metric is
measured and displayed per specific entity per specific device. No function is
applied.
1. Open the Statistics page and from the Devices drop-down, select Aggregated PMs.
- 202 -
Figure 6-55: Selecting 'Aggregated PMs'
2. In the Aggregated PMs page that opens, you're prompted 'Missing Topology and Metrics
Filter'. Click Add Filter.
a. Change the 'Time Range' or leave it unchanged at the default (the preceding 24 hours, i.e.,
00:00 to 23:59).
b. Click Topology and either select a tenant or multiple tenants, and then click Apply.
c. Click Metrics and select the metrics (parameters) you want to poll. They're displayed like
in the PM Profile. Use the information in Adding a PM Profile on page 193 as reference.
3. View the aggregated PMs then displayed.
Figure 6-56: Aggregated PMs

■ Add Filter (left side of page):
● displays the Time Range; click to select a different time range if necessary
● displays the Topology; click to add, remove or change tenants
● displays the metrics (parameters); click to select fewer, more or different metrics
■ Bar charts (middle of page):
● each chart displays a metric (parameter); scroll down to view all
● aggregated results are displayed in bars
● if there are no aggregated results found or if the topmost metric value is 0, no bars are
displayed
● pointing the cursor over a bar displays a tool tip showing the time interval and the metric
value
◆ the tool tip in the preceding figure indicates that on this SBC, the maximum
aggregated incoming calls per second (CAPS) measured between March 1, 2019 at
00:00 and March 30, 2019 at 23:59, was 6
■ Statistics Summary (right side of page)
- 203 -
● 'Entities Summary' displays the entity type | types polled and how many of each type was
polled
● Top Most Metric Values indicates the interval in which the highest value was measured for
a metric, for example, on 06-Mar-2019 the metric 'IN CAPS (Max)', i.e., the maximum
aggregated incoming calls per second (CAPS), was measured to be 6
➢ To view standalone PMs from the OVOC's Statistics page:
● Explanation of standalone PM metrics: Each standalone PM metric is

measured and displayed per specific entity per specific device. No function is
applied.
● Explanation of aggregated PM metrics: After selecting an aggregated PM
metric, the OVOC aggregates it over all devices and device objects. For example,
after selecting aggregated PM metric X of type 'MIN' measured per IP group over
three devices, one graph is displayed; for each timestamp, the OVOC calculates
the metric's minimum value over all IP groups over the three selected devices. The
metric types are:
✔ MIN – the minimum value measured
✔ MAX – the maximum value measured
✔ AVG – the average value measured
✔ VALUE – summation of values measured
1. Open the Statistics page and from the Devices drop-down, select Standalone PMs.
Figure 6-57: Selecting 'Standalone PMs'
2. In the Standalone PMs page that opens, you're prompted 'Missing Topology and Metrics Filter'.
Click Add Filter.
a. Change the 'Time Range' or leave it unchanged at the default (the preceding 24 hours, i.e.,
00:00 to 23:59). Click Apply.
b. Click Topology and select a tenant or multiple tenants and / or a device under a tenant or
multiple devices, and then click Apply.
c. Click Metrics and select the standalone PM metrics (parameters) you want to poll. They're
displayed in a similar way to the way they're displayed in the PM Profile but for example
with the standalone PM metric 'Invite Dialogs' shown in the next figure, Min, Max or Av
can be selected; you cannot select all three or two, as you can with aggregated PM
metrics.
d. In the 'Entitles' drop-down, select if necessary (and if available) the specific IP Group (for
example) to poll. In this case, select its index. You can then select another. Optionally,
select All.
- 204 -
3. View the standalone PMs metrics then displayed.

Figure 6-58: Standalone PMs

■ Add Filter (left side of page):
● displays the Time Range; click to select a different time range if necessary
● displays the Topology; click to add, remove or change tenants
● displays the metrics (parameters); click to select fewer, more or different metrics
■ Bar charts (middle of page):
● each chart displays a metric (parameter); scroll down to view all
● results are displayed in bars; if there are no results found or if the topmost metric value is
0, no bars are displayed
● pointing the cursor over a bar displays a tool tip showing the time interval and the
standalone PM metric's value
■ Statistics Summary (right side of page)
● 'Entities Summary' displays the entity type | types polled and how many of each type was
polled
● Top Most Metric Values indicates the interval in which the highest value was measured for
a metric
- 205 -
CHAPTER 7 Managing your Network OVOC | User's Manual
7 Managing your Network

The OVOC enables ITSPs and enterprises to independently manage their telephony networks.
Performing Management Actions

The OVOC lets operators perform multiple network management actions in the network.
➢ To perform a management action:

1. Open the Network page under the Devices tab for example.
2. Select a device or a link on which to perform an action; the Actions button, Edit button, Show
button and Delete button are activated.
Figure 7-1: Actions | Edit | Show | Delete
3. Click the Actions button and select an action from the drop-down sub-menus.
The sub-menus and the items under them are dynamic. They change according to the
device selected and its status.
● Maintenance
◆ Update Firmware (see Updating Firmware on the next page)
◆ Update Firmware on Multiple Devices (see Updating Firmware on Multiple Devices on
page 209)
◆ Reset (see Resetting a Device on page 209)
◆ Lock or Unlock (see Locking or Unlocking a Device on page 209)
◆ Populate Links (see Populating Links on page 211)
◆ Move (see Moving a Device on page 211)
● Configuration
◆ Backup (see Backing Up on page 212)
◆ Restore Last Backup (restore a device's configuration) (see Restoring the Last
Backup on page 213)
◆ Restore Default Configuration (see Setting Configuration Factory Defaults on
page 215)
◆ Save Configuration to Flash (see Saving a Device's Configuration File to Flash
Memory on page 215)
- 206 -
◆ Save Current Configuration to File (see Saving a Device's Configuration File to the
PC on page 215)
● Performance Monitor
◆ Start Polling (see Starting Polling)
◆ Change Profile (see Changing Profile on page 217)
● High Availability
◆ Reset Redundant (see Resetting Redundant on page 216)
◆ Switchover (see Performing Switchover on page 217)
4. Use also the following dedicated buttons to perform management actions:
● Show device information (see Showing Device Information on page 219)
● Show link information (see Showing Link Information on page 220)
● Show user information (see Showing User Information on page 221)
● Edit a device (see Editing a Device on page 223)
● Delete a device (see Deleting a Device on page 223)
Updating Firmware
The OVOC lets you update a device's .cmp firmware version file. After loading the .cmp file to the
device, you can also load an ini file and Auxiliary files (e.g., CPT file).
➢ To update a device's firmware:

1. In the Network Topology page, position your cursor over the device.
2. Click More Actions and then the Update Firmware icon.
- 207 -
Figure 7-2: Update Firmware
3. Select the firmware file you require and click OK.
- 208 -
Updating Firmware on Multiple Devices

The OVOC lets you upgrade the .cmp firmware version file on multiple devices. After loading the
.cmp file to the devices, you can also load an ini file and Auxiliary files (e.g., CPT file).
➢ To update firmware on multiple devices:

■ In the Network Topology page, select the devices whose firmware you want to upgrade (Ctrl +
click devices) and then from the 'Actions' drop-down select Update Firmware. Alternatively,
in the Device Management page, select the devices whose software you want to upgrade (Ctrl
+ click devices) and then from the 'Actions' drop-down under the 'Maintenance' sub-menu,
select Update Software.
Resetting a Device
For certain settings to take effect a device reset is required. Resetting a device may also be
necessary for maintenance purposes.
➢ To reset a device:
1. Open the Device Management page (Network > Devices > Manage).
2. Click Actions and from the drop-down select Reset under the 'Maintenance' menu.
Figure 7-3: Resetting the Device
3. [Optional] Select the Save configuration to flash memory option.

● If you select the option, the current configuration will be saved (burned) to flash memory
prior to reset.
● If you do not select the option, the device resets without saving the current configuration to
flash and all configuration performed after the last configuration save will be discarded
(lost) after reset.
4. Click Reset.
Locking or Unlocking a Device

Locking a device suspends call functionality and places the device in maintenance state, for
troubleshooting, for example. Unlock returns it to service.
➢ To lock a device:
1. In the Network Topology page, position your cursor over the device; the Actions menu pops up.
2. Click More Actions and then click the Lock icon.
- 209 -
Figure 7-4: Lock Device
3. Select either:
● Immediate Lock. The device is locked regardless of traffic. Any existing traffic is
terminated immediately.
● Graceful Lock. Existing calls first complete and only then is the device locked. No new
traffic is accepted.
● Graceful Lock (time in seconds). The device is locked only after the time configured in
the adjacent field. During this time, no new traffic is accepted. If no traffic exists and the
time has not yet expired, the device locks immediately.
These options are available only if the current status of the device is in "UNLOCKED"
state
4. Click OK.
Figure 7-5: Lock Confirmation
If you selected Immediate Lock, the lock process begins immediately. The device does not
process any calls.
If you selected Graceful Lock, a lock icon is displayed and a window appears displaying the
number of remaining (unfinished) calls and time.
➢ To unlock the device:

■ In the Network Topology page, position your cursor over the device and from the Actions menu
shown above, click the More Actions link. Click the now-displayed Unlock icon; the device
unlocks immediately and accepts new incoming calls.
- 210 -
Populating Links
[See also Adding Links on page 114 ] The device action Populate Links allows links to be
automatically generated and updated between SBCs/gateways and their connected entities. Three
different SBC configuration tables are managed by the OVOC:
■ IP group
■ Trunk group
■ Media realm (typically, one for internal (LAN) traffic, another for external (WAN) traffic)
Populate Links checks each row in each table and then generates links between AudioCodes
devices and generic devices for each row in each table for which a link does not already exist. A
new generic device is created for each link.
Example:
If two IP Groups, Skype for Business Server 2015 and SIP Trunk ABC, and two Media Realms are
configured on an SBC, LAN and WAN, then when Sync Link is performed, four links are generated
(two IP Groups and two Media Realms).
➢ To populate links:
1. In the Network Topology page, position your cursor over the device.
2. Click the Populate Links icon.
Figure 7-6: Populate Links
3. If necessary, clear an SNMP table option and then click OK; links are generated between
AudioCodes devices and generic devices for each row in each table where a link does not
already exist, and a new generic device is created for each link.
Moving a Device
The device action Move lets you move a device across tenants and/or regions. A device cannot be
moved if it has a Zero Touch configuration which has not been applied yet.
➢ To move a device:
1. In the Network Topology page, position your cursor over the device; the Actions menu pops up.
2. Click the Move icon.
- 211 -
Figure 7-7: Move Device
3. From the 'Tenant' drop-down, select from the list of tenants the tenant to move the device to
(see Adding a Tenant on page 85 for information on how to add a tenant).
4. From the 'Region' drop-down, select from the list of regions the region to move the device to
(see Adding a Region on page 91 for information on how to add a region).
5. If the device is an HA device, configure 'Reset redundant'.
6. Click OK.
Backing Up
You can back up a device's configuration file to the server.
➢ To back up a device's configuration file to the server:

1. Open the Device Management page (Network > Devices > Manage) and select the device
from which to upload the software configuration file to the server.
2. Click Actions and from the drop-down choose the 'Configuration' sub-menu.
3. Select the Backup option.
4. In the Backup Configuration File prompt, click Backup.
- 212 -
5. Click OK; the latest file is uploaded to the server from the device.
● If the device selected is an MSBR, the latest cli file is uploaded.

● If the device selected is an MP-202 or MP-204, the latest conf file is uploaded.
● If the device selected is any other AudioCodes device (except CloudBond and
UMP), the latest ini file is uploaded.
Restoring the Last Backup

You can restore or download the latest software configuration file, backed up on the server, to the
device.
➢ To download the latest backup software configuration file to the device:

1. Open the Device Management page (Network > Devices > Manage) and select the device to
which to restore the latest backed-up software configuration file.
2. Click Actions and from the drop-down choose the 'Configuration' sub-menu.
3. Select the Restore Last Backup option.
4. In the prompt, click Restore.

5. In the confirmation prompt, click OK; the latest file is downloaded to the device from the
server.
- 213 -
● If the device selected is an MSBR, the latest cli file is downloaded.

● If the device selected is an MP-202 or MP-204, the latest conf file is downloaded.
● If the device selected is any other AudioCodes device (except CloudBond and
UMP), the latest ini file is downloaded.
- 214 -
Setting Configuration Factory Defaults

You can set a device's configuration to its factory defaults.
The only settings that are not restored to default are the management (OAMP) LAN IP
address and the OVOC's login username and password.
Saving a Device's Configuration File to Flash Memory

You should save (burn) the current configuration of a device to the device's flash memory (non-
volatile) before performing a Reset action (see Resetting a Device on page 209) or before powering
down, in order to ensure configuration changes you made are retained.
➢ To save (burn) a device's software configuration to the device's flash memory:

1. Open the Devices page (Network > Devices) and select the device to which to save (burn) the
software configuration.
2. Click Actions and select the Configuration sub-menu.
Figure 7-8: Saving Configuration to Flash
3. From the sub-menu, select Save Configuration to Flash.
Saving configuration to flash may disrupt current traffic on the device. To avoid this, dis-
able all new traffic before saving, by performing a graceful lock (see Locking or Unlock-
ing a Device on page 209).
Saving a Device's Configuration File to the PC

You can save the current configuration of a device to your PC.
➢ To save a device's configuration to the PC:

1. Select the device whose configuration you want to save to the PC and click Actions.
- 215 -
2. From the Actions menu, select Save Config File.
3. Save the configuration file to the PC's download folder or Save As to the location of your
choice.
● If the device is an MSBR, a cli file is saved.

● If the device is an MP-202/MP-204, a conf file is saved.
● If the device is another AudioCodes device (except CloudBond and UMP), an ini
file is saved.
Resetting Redundant
You can reset a device's redundant chassis.
Resetting a device's redundant chassis only applies to HA devices. For detailed inform-
ation about HA devices, see the relevant device's User's Manual.
➢ To reset a device's redundant chassis:

1. In the Network page under either the Topology or Devices tab, select the device to reset and
then click the now-activated Actions button.
Figure 7-9: Actions – Reset Redundant
- 216 -
2. From the Actions drop-down, select the Reset Redundant option. If the menu option is
disabled, the device selected does not support HA.
3. Resetting a device's redundant chassis is identical to resetting an active device. See
Resetting a Device on page 209 for more information.
Performing Switchover
This only applies to HA devices. For detailed information about HA devices, see the relevant
device's User's Manual.
If a failure occurs in a device's currently active chassis, a switchover to the redundant chassis
occurs. The active chassis becomes redundant and the redundant chassis becomes active.
Current calls are maintained and handled by the active chassis (previously the redundant chassis).
You can switch from the active chassis (i.e., the previously redundant chassis) to the redundant
chassis (i.e., the previously active chassis) to return the device to its original HA state.
➢ To perform a switchover:
1. In the Network page under either the Topology or Devices tab, select the device on which to
perform the switchover, and then click the now-activated Actions button.
Figure 7-10: Actions – Switchover
2. From the Actions drop-down, select the Switchover option. If the menu option is disabled, the
device selected does not support HA.
Changing Profile
Operators can poll a device for Performance Monitoring metrics according to a PM profile. For
information about defining a PM profile, see Adding a PM Profile on page 193. A profile determines
how the OVOC monitors network | device performance. A profile determines:
■ What's monitored [which network | device parameters]
■ How frequently [how often they're polled]
■ When an alarm is issued [at what parameter threshold]
■ Alarm severity [if a parameter threshold is exceeded]
➢ To change profile:
1. In the Device Management page (Network > Devices), select the Change Profile action
under the Performance Monitor sub-menu in the 'Actions' drop-down menu.
- 217 -
Figure 7-11: Select PM Profile
2. From the drop-down list, choose the profile (template) according to which to poll the device for
PM metrics, and then click Select.
- 218 -
Showing Device Information

The Show button lets operators quickly retrieve and assess information related to any device in the
network.
➢ To show device information:

1. In the Network page under the Topology tab or Devices > Manage tab, select the device and
click the activated Show button.
Figure 7-12: Show Device Information
2. The page displays information related to active alarms on the device, journal events, statistics
summary and calls made over the device.
3. The page is dynamically automatically tabbed on the menu bar. Operators can delete the tab at
any time. The tab facilitates quick future access to the page from other OVOC pages, for
troubleshooting.
4. Under the 'Statistics Summary' section of the page, the Successful / Failed Calls pie chart and
the Quality Distribution pie chart function as filters. Click a color to open the Calls List filtered
by these criteria: Device, Time, Successful / Failed or Quality Color.
5. Under 'Device Calls' you can select a call made over the device and click the Show button to
display that call's details; the Call Details page opens (see Showing Call Details on page 232
for more information).
- 219 -
Showing Link Information

The OVOC lets operators quickly retrieve and assess information related to any link in the network.
➢ To show link information:

1. In the Network page under the Topology or Links tab, select the link and click the Show
button. Alternatively, under the Topology tab, hover your mouse device over the link label and
from the pop-up menu select the icon .
Figure 7-13: Show Link Information
The link's Summary page opens.
- 220 -
Figure 7-14: Link's Summary Page
2. The page displays information about active alarms on the link, journal events, statistics
summary and calls made over the link.
3. The page is dynamically automatically tabbed on the menu bar: Link from FE in the figure
above. Operators can delete the tab at any time. The tab facilitates quick future access to the
page from other OVOC pages, for troubleshooting.
4. Under the 'Statistics Summary' section of the page, the Successful / Failed Streams pie chart
and the Quality Distribution pie chart function as filters. Click a color to open the Calls List
filtered by these criteria: Stream, Time, Successful / Failed or Quality Color.
5. Under 'Link Calls' select any call made over the link and click Show to display that call's
details; the Call Details page opens (see Showing Call Details on page 232 for more
information).
Showing User Information

The OVOC lets operators quickly retrieve and assess telephony information related to any user.
➢ To show telephony information about a user:

1. In the Users page under the Users Experience or User Details tab, select a user and click
Show.
Figure 7-15: Showing Information about a User
2. The page displays contact details, Skype for Business details if any, user statistics and recent
calls.
- 221 -
The page is dynamically automatically tabbed on the menu bar with the user's name. Operators
can delete it at any time. The tab facilitates quick access to the page from other OVOC pages,
for future reference.
3. Under the 'User Statistics' section of the page, the Successful / Failed Calls pie chart and the
Quality Distribution pie chart function as filters. Click a color to open the Calls List filtered by
these criteria: User, Time, Successful / Failed or Quality Color.
4. Under 'Recent Calls' you can select any call made by this user and then click the Show button
to display that call's details. The Call Details page opens (see Showing Call Details on
page 232 for more information).
- 222 -
Editing a Device
The Edit button lets you edit a device's configuration.
➢ To edit a device's configuration:

1. Select the device to edit and then click the Edit button.
Figure 7-16: Device Details
2. Edit the device's details. For more information, see Adding AudioCodes Devices Automatically
on page 92.
3. Click OK.
Deleting a Device
The Delete button lets you delete a device from the OVOC.
➢ To delete a device:
■ Select the device to delete and then click the Delete button.
- 223 -
Resetting a Device
You can reset a device.
➢ To reset a device:
1. In the Device Management page, from the Actions > Maintenance menu, select Reset.
Figure 7-17: Reset Device – Confirmation
2. Select the Burn configuration into the flash memory in order to make sure changes are
retained. They're burned (saved) to the device's non-volatile memory, i.e., flash memory. See
Saving a Device's Configuration File to Flash Memory on page 215 for more information about
burning a device's configuration to flash memory.
Without burning, changes are saved to the device's volatile memory (RAM). The
changes revert to their previous settings if the device subsequently resets (hardware or
software) or powers down.
3. Click Reset.
- 224 -
Refreshing a Device's Pool License

You can refresh a device's Pool License.
Only relevant to HA devices. A switchover is performed in order to apply the license

parameter on both devices.
➢ To refresh a device's Pool License:

■ From the Actions menu, select Refresh License.
Monitoring Device-Level Backup and Performing

Rollback
The Backup Manager page (Network > Devices drop-down > Backup Manager) allows you to
monitor device-level backup and perform rollback. For detailed information, see Backing up a
Device's Configuration using Backup Manager on page 112.
- 225 -
CHAPTER 8 Obtaining Quality Statistics on Calls OVOC | User's Manual
8 Obtaining Quality Statistics on Calls

You can get quality statistics a.k.a. Key Quality Indicators (KQIs) on calls made by end users in
your telephony network.
Accessing the Calls List

The Calls List page (Calls > Calls List) lists and shows quality information on calls made in the
network over the past three hours (default).
Figure 8-1: Calls List
Calls on AudioCodes High Availability devices during switchover are not supported.
The OVOC QoE application does not display and count a call that starts on unit A and is
transferred to unit B after device switchover.
The page features filtering capabilities to help obtain precise information on calls quickly and
efficiently. Optionally, filter the page by Time Range (see Filtering to Access Specific Information
on page 147), Topology (see Filtering by 'Topology' on page 150), Source Type (see Filtering by
'Severity' on page 158), Quality (see Filtering by 'Quality' on page 228) or More Filters (see Filtering
by 'More Filters' on page 230).
Use the following table as reference to the columns in the Calls List.
Table 8-1: Calls List Columns
Column Description
Source indicates the call is from Microsoft Skype for Business

indicates the call is from an AudioCodes device.
indicates the call is from an AudioCodes IP phone.
Status Indicates call control status: Successful or Failed
Quality Indicates the call quality:

Green = Good, Yellow = Fair, Red = Poor, Gray = Unknown
- 226 -
Column Description
Quality Delay Delay (or latency) - the time it takes for information to travel from
Cause (msec) source to destination (round-trip time). Sources of delay include
voice encoding / decoding, link bandwidth and jitter buffer depth.
Two Delay values are shown, one value for the caller side and one
value for the callee side.
Echo The level difference (measured in dB) between the signal

transmitted to the listener and the residual echo of this signal.
Jitter Jitter can result from uneven delays between received voice
(msec) packets. To space packets evenly, the jitter buffer adds delay. The
higher the measurement, the greater the impact of the jitter buffer’s
delay on audio quality. Two Jitter values are shown, one value for
the caller side and one value for the callee side.
MOS MOS - Mean Opinion Score (specified by ITU-T recommendation

P.800) - the average grade on quality scales of Good to Failed,
given by the SEM to voice calls made over a VoIP network at the
conclusion of the testing.
Packet Lost packets - RTP packets that aren’t received by the voice
Loss (%) endpoint for processing, resulting in distorted voice transmission.
Two Packet Loss % values are shown, one value for the caller side
and one value for the callee side. Packet Loss can be more than
100%.
None Indeterminate cause
Caller The phone number or address of the person who initiated the call.
Callee The phone number or address of the person who answered the call.
Start Time The precise time (hour, minutes and seconds) and date (month, day and year)
when the call was started.
End Time The precise time (hour, minutes and seconds) and date (month, day and year)
when the call was terminated.
Duration The duration of the call, in seconds. See the note following.
(sec)
Call Type Indicates the call type.
Device Indicates the device/s over which the call passed.
Link Indicates the link/s over which the call passed.
Termination Indicates the reason why the call was terminated.

Reason
An SBC call (exclusively) whose duration is longer than three hours (e.g., the session of
a participant in a Skype for Business conference call over an SBC) or an SBC call that
is incompletely reported to the OVOC server won't be displayed in the Calls List.
- 227 -
The Save button allows operators to save up to one million calls to a zip file comprising 10
separate csv files, each including up to 100,000 calls.
A README file is also included in the save, with details of the Calls List filter settings, the number
of exported entities, the time range and the tenant operator credentials.
The foot of the page features a pager.
The pager lets you (from left to right):

■ Click the |◄ Go to the first page to return to the first page from any page.
■ Click the Go to the previous page arrow to return to the page before the presently displayed
page.
■ Click … [More pages] to the left of the page number or … [More pages] to the right of the
page number to page backwards or forwards respectively.
■ Click the Go to the next page arrow to browse to the page after the presently displayed page.
■ From the ‘Items per page’ drop-down, select the number of calls to display per page:
20, 30 or 50.
Filtering by 'Quality'
You can filter a page using the 'Quality' filter. The filter applies to the Calls List page under the Calls
menu. The filter lets you display calls according to quality.
- 228 -
Figure 8-2: Quality Filter

Table 8-2: 'Quality' Filter
Filter Description
Failed | Filters calls according to their status. If you clear Success and select Failed,
Success only calls whose status was Failed are displayed in the page.
Poor, Fair, Filters calls according to their quality. If you clear all except Poor, only calls
Good or whose quality was Poor will be displayed.
Unknown
None, MOS, Filters calls according to the cause of the quality. If - after displaying only calls
Jitter, whose quality was poor/fair - you clear all except Delay, the page will display
Delay, P. only calls whose quality was poor/fair because there was a delay on the line.
Loss or
Echo
- 229 -

The Calls List page can be filtered using the 'More Filters' filter. This filter lets you display calls
according to caller, callee, media type, etc.
Figure 8-3: More Filters – Calls List Page

Table 8-3: More Filters – Calls List
Filter Description
Caller Enter the name of a caller (or the names of callers) whose calls you want to
display in the page. The filter is case sensitive.
Callee Enter the name of a called party (or the names of called parties) whose calls you
want to display in the page. The filter is case sensitive.
- 230 -
Filter Description
Media Type From the drop-down list, select the media type to display on the page (or enter a
search string). Select either MSRP (Message Session Relay Protocol), Voice,
Image, Application Sharing (a Skype for Business media type), Video, Data,
Audio Video, Chat, Audio V150 (currently unsupported), Text, Unknown or All
(and then optionally remove unwanted media types). By default, all media types
are selected.
Call Type From the drop-down list, select the call type to display on the page, or enter a
search string. Select either GW (Gateway), SBC, Skype Conference, Endpoint,
Test SBC, HTTP, IP2IP or Skype.
Skype Conference can be of media type 'Audio Video' or 'Chat'. The conference
participant's name is shown in the ‘Caller’ column. To retrieve conference calls
information, the OVOC uses the Microsoft Skype for Business
ConferenceSessionDetailsView Monitoring Server report. For example, from
the 'Media Type' drop-down choose Chat; the Media Type column then displays
only MS Skype for Business conferences whose Media Type is Chat.
Termination Enter the reason why the call was terminated. See the device's User's Manual
Reason for more information about Termination Reason.
Some AudioCodes termination reasons are:
■ Reason Not Relevant
■ Unassigned Number
■ Invalid Information Element Content
■ The remote equipment received an unexpected message that does not
correspond to the current state of the connection.
■ Recovery on Timer Expiry
■ Protocol Error Unspecified
■ Unknown Error
■ Q931 Last Reason
Some MS Skype for Business Termination Reasons are:
■ OK. Indicates the request was successful.
■ Accepted. Indicates that the request has been accepted for processing, but
the processing has not been completed.
■ No Notification
■ Multiple Choices
■ Moved Permanently
■ Moved Temporarily
■ Use Proxy
■ Alternative Service
- 231 -
Showing Call Details

After filtering the calls listed in the Calls List page by either Time Range (see Filtering to Access
Specific Information on page 147), Topology (see Filtering by 'Topology' on page 150), Source Type
(see Filtering by 'Severity' on page 158), Quality (see Filtering by 'Quality' on page 228) and / or
More Filters (see Filtering by 'More Filters' on page 230), select the call whose details you want to
view and then click the activated Show button. The Call Details page that opens displays detailed
information about that call.
Figure 8-4: Call Details – Details of a Call Made over a Device Belonging to AudioCodes
Details of a Call Made over an AudioCodes SBC

The figure above shows the details of a call made over the AudioCodes SBC. You can also display
the details of calls made/received over other entities. The page is automatically dynamically tabbed
on the menu bar for quick and easy future access and troubleshooting. Operators can delete the tab
at any time. The page displays detailed diagnostic information, in graphic and textual format,
facilitating effective management, precise diagnosis and targeted remedial action to prevent
recurrence of unsuccessful call performance or poor call quality. Use the following table as
reference.
Table 8-4: Call Details Page
Page Sub-
Description
division
(Uppermost) Displays parameters and values identical to those displayed in the Calls
Call summary List page.
(Middle) Graphic Displays a graphical illustration of voice quality on each leg of the call, on
illustration both the caller and callee side. Each leg is:
■ Connected via the VoIP cloud to the device
■ Color-coded to indicate quality (green = good, yellow = fair, red = poor,
grey = unknown)
■ Tagged by C and M
C = Control summary (point cursor to view tooltip)
M = Media IP address and Port (point cursor to view tooltip)
- 232 -
Page Sub-
Description
division
(Lowermost) Each opens a page displaying detailed information:

Three tabs ■ Media (see Media below‎) (includes Quality)
■ Signaling (see Signaling on page 236)
■ Trend (see Trends on page 237‎) (Only displayed if there is a trend; if
there is not a trend, the tab is not displayed‎)
■ SIP Ladder (see SIP Call Flow on page 238)
Media
The Media tab displays a call's media parameter settings that operators can refer to for diagnostics,
troubleshooting and session experience management issues.
Figure 8-5: Media
Use the following table as reference to the parameters displayed under the Media tab.
Table 8-5: Media Parameters
Media IP ■ The IP address of the device source in the operations, administration,

Address maintenance, and provisioning (OAMP) network.
■ The IP address of the destination host / media network.
Media Port ■ The device's source port in the operations, administration,

maintenance, and provisioning (OAMP) network.
■ Port of the destination host / media network.
Signal Level The ratio of the voice signal level to a 0 dBm0 reference.
Signal level = 10 Log10 (RMS talk spurt power (mW)).
A value of 127 indicates that this parameter is unavailable.
Noise Level The ratio of the level of silent-period background noise level to a 0 dBm0
reference. Noise level = 10 Log10 (Power Level (RMS), in mW, during
periods of silence). A value of 127 indicates that this parameter is
unavailable.
- 233 -
SNR The ratio of the signal level to the noise level (Signal-Noise Ratio).
SNR = Signal level – Noise level.
Burst Duration The mean duration (in milliseconds), of the burst periods that have occurred
since the initial call reception.
Rx Rate Shows the call's reception rate, in Kbps.
Quality Voice quality: Good (green), Fair (yellow) OR Red (poor).
MOS Mean Opinion Score (specified by ITU-T recommendation P.800).

Defines the average grade, on a quality scale of Good to Poor, determined
after testing calls made over a VoIP network. Comprises:
MOS-LQ = listening quality, i.e., the quality of audio for listening purposes.
Doesn't account for bi-directional effects such as delay and echo. Two
values are shown: (1) for the device side on the caller leg (2) for the device
side on the callee leg.
MOS-CQ = conversational quality; it takes listening quality in both
directions into account, as well as the bi-directional effects. Two values are
shown: (1) for the device side on the caller leg (2) for the device side on the
callee leg.
Jitter Jitter can result from uneven delays between received voice packets. To
space evenly, the jitter buffer adds delay. The higher the measurement, the
greater the impact of the jitter buffer’s delay on audio quality. Two Jitter
values are shown, one value for the caller side and one value for the callee
side.
Packet Loss Lost packets are RTP packets that aren’t received by the voice endpoint for
processing, resulting in distorted voice transmission. Two Packet Loss %
values are shown, for the caller and for the callee side. Packet Loss can be
more than 100%.
Delay The round trip delay is the estimated time (in milliseconds) that it takes to
transmit a packet between two RTP stations. Sources of delay include
voice encoding / decoding, link bandwidth and jitter buffer depth. Two
values are shown, one caller side and another for the callee side.
Echo The residual echo return loss is the level difference (measured in dB)
between the signal transmitted to the listener and the residual echo of that
signal.
Media IF Shows the name and index of the Media Realm interface reported by the
device. Example: SIMcmxLAN (n), where n following the displayed name
is the number indicating the Media Interface's index used to facilitate
network configuration.
Network IF Network Interface Name.
Coder Up to 10 coders (per group) are supported. See the device manual for a list
of supported coders.
SCE Method for conserving bandwidth on VoIP calls by not sending packets
when silence is detected. True = Enabled (On), False = Disabled (Off).
- 234 -
RTP Direction RTP Directional Control. Controlled internally by the device according to
the selected coder.
RTCP Direction RTCP Directional Control. Controlled internally by the device according to
the selected coder.
PTime (msec) Packetization time, i.e., how many coder payloads are combined into a
single RTP packet.
The following figure shows the Media tab in the Call Details page.
Figure 8-6: Call Details page - Media tab
Use the preceding figure as reference to the following explanation of the QoE indicators.
1. Local QoE values of MOS, Jitter, Packet loss, Delay and MOS are calculated by the SBC
based on RTP packets it receives from the 'remote peer'
2. The SBC reports this information to the OVOC using an XML-based, proprietary protocol
3. The OVOC displays the information it receives (indicated by 1 in the preceding figure)
4. Remote QoE values can be calculated by the 'remote peer' and reported back to the SBC using
RTCP packets, except 'Delay' (and RTPC-XR, if supported, for MOS)
5. The SBC forwards QoE information (if received) from the 'remote peer' to the OVOC, as
described in point 2 above
6. The OVOC displays the information it receives (indicated by 2 in the preceding figure) (from
'SBC' to 'remote peer')
7. Quality (Good, Fair, Poor), indicated by 3 in the preceding figure, is based on the following
criteria:
● If MOS is received from AudioCodes equipment (SBC) configured with a QOE profile, the
'Quality' displayed matches the profile’s thresholds:
◆ Poor = major threshold reached
◆ Fair = minor threshold reached
◆ Good = minor threshold not reached
● If MOS is received from non-AudioCodes equipment, local settings on the OVOC are used
(System > Configuration > Templates > QoE threshold)
● If no MOS information is received, the 'Quality' displayed corresponds to the worst of the 3
QoE values received (Jitter, Packet Loss, Delay)
● As before, the 'Quality' displayed matches the QoE profile (from the SBC or locally on the
OVOC)
- 235 -
MOS gets priority because it's based on algorithms that emulate the human perception
of voice quality during a call.
Signaling
The Signaling tab displays a call’s signaling parameters that operators can refer to for diagnostics,
Figure 8-7: Signaling
Use the following table as reference to the parameters displayed under the Signaling tab.
Table 8-6: Signaling Parameters
SIP IP The call's caller/callee (source/destination) IP address.
SIP Port The port number used for the SIP call.
URI The URI (Uniform Resource Identifier) of the caller/callee

(source/destination). The SIP URI is the user’s SIP phone number (after
manipulation, if any). The SIP URI resembles an e-mail address and is
written in the following format: sip:x@y:Port, where x=Username and
y=host (domain or IP).
Output URI The SIP URI address of the caller/callee before manipulation (if any) was
Before Map done on the URI.
Endpoint Type Indicates the type of endpoint. For example, 'SBC'.
SRD The unique name and index configured for the signaling routing domain
(SRD). Example: someSRD (n), where n following the displayed name is
the number indicating the SRD's index used to facilitate network
configuration.
IP Group The ID of the IP Group with which the call is associated.
SIP IF The ID of the SIP Interface with which the call is associated.
- 236 -
Proxy Set The Proxy Set to which the call is associated. This is a group of Proxy
servers. Typically, for IP-to-IP call routing, at least two are defined for call
destination – one for each leg (IP Group) of the call (i.e., both directions).
For example, one Proxy Set for the Internet Telephony Service provider
(ITSP) interfacing with one 'leg' of the device and another Proxy Set for the
second SIP entity (e.g., ITSP) interfacing with the other 'leg' of the device.
IP Profile The IP Profile assigned to this IP destination call. The IP Profile assigns
numerous configuration attributes (e.g., voice codes) per routing rule.
Transport Type Two options: UDP or TCP
Signaling diff The value for Premium Control CoS content (Call Control applications).
server
Trends
The Trends tab shows a call's voice quality trend that operators can refer to for diagnostic,
troubleshooting and session management experience issues.
Figure 8-8: Trends
Voice quality applies to the call's:

■ Caller leg
● caller side (of cloud)
● device side (of cloud)
■ Callee leg
● callee side (of cloud)
● device side (of cloud)
➢ To assess voice quality:

■ Select a quality metric graph option (MOS, Jitter, Packet Loss, Delay and/or Echo) and then
select a leg; the graph displayed indicates:
● the voice quality of the call for the selected quality metric across the selected leg
● how long the leg lasted
● the time the leg started and ended
- 237 -
Legs over PSTN are not measured for quality, only legs over IP.
➢ To compare one voice quality metric with another across different legs:
1. Select multiple voice quality metric graphs, for example, MOS and Packet Loss, as shown in
the figure above.
2. Select a leg option and compare the displayed graphs of quality metrics with one another
across this leg.
3. Select another leg and compare the same metrics graphs with one another across this leg.
SIP Call Flow

The SIP Call Flow tab is displayed in the Call Details page when a SIP ladder is available or
partially available and found for a specific call over SBC.
Figure 8-9: SIP Call Flow – Example
■ Click the textual indication of a SIP message to display MESSAGE INFO in the right pane:
● The text indication changes color to bold pink
● The call flow leg line is made bold
● See 404 Not Found as an example in the figure above
The number of participants indicated in the Call Details and in the Call Flow tabs can be
different. The Call Flow tab can include more participants than the Call Details tab,
which always includes caller and callee.
- 238 -
The following table shows error response color codes.

The table following it shows SIP message color codes.
Table 8-7: Error Response Color Codes
Color Error Response
Red Error response message with response code 6xx, 5xx, 4xx, excluding
486 (busy) which is colored green
Green Error response message with response code 486 (busy) and all other
responses
Black Error response message with response codes 401 and 407
Table 8-8: SIP Message Color Codes
Color SIP Message
Dark Green ACK
Dark Blue INVITE
Brown CANCEL
Purple BYE
Black (unbolded) All other SIP messages and codes
- 239 -
Details of a Test Call Made over an SBC

After filtering calls listed in the Calls List page by clicking Add Filter > More Filters > Call Type >
Test SBC (see Filtering by 'More Filters' on page 230), select the test call whose details you want
to view and then click the activated Show button. The Call Details page that opens displays
detailed information about that test call. The following figure shows the details of a test call made
over an SBC. The page displays detailed diagnostic information on the call, in textual format,
facilitating effective management, precise diagnosis and targeted remedial action to prevent
recurrence of unsuccessful call performance or poor call quality.
Figure 8-10: Call Details – Test Call Over an SBC
Use the following table as reference to the preceding figure.

Table 8-9: Call Details - Test Call Made over an SBC
Page Section Description
Call Summary Indicates the caller's full name and email address and callee's full name
(Uppermost) and email address.
Call Status Successful or Failed
Call Quality Good | Fair | Poor voice quality
Call Type Test SBC
Start Time The precise time (hour, minutes and seconds) and date (month, day and
year) when the caller began dialing the number to call.
End Time The precise time (hour, minutes and seconds) and date (month, day and
year) when the call was terminated.
Connect Time The precise time (hour, minutes and seconds) and date (month, day and
year) the connection was established.
Duration The duration of the call, in seconds.
Termination The network entity from which the call was terminated.
Initiator
- 240 -
Termination The reason why the call was terminated. See the device's User's
Reason Manual for more information about Termination Reason.
SIP PSTN Reason The reason why the call was terminated. See the device's User's
Manual for more information about the SIP/PSTN Reason.
Media Type Voice
[Quality] Cause Delay Delay (or latency) - the time it takes for information to
travel from source to destination (round-trip time).
Sources of delay include voice encoding / decoding,
link bandwidth and jitter buffer depth. Two Delay
values are shown, one value for the caller side and one
Echo The level difference (measured in dB) between the

signal transmitted to the listener and the residual echo
of this signal.
Jitter Jitter can result from uneven delays between received

voice packets. To space packets evenly, the jitter
buffer adds delay. The higher the measurement, the
greater the impact of the jitter buffer’s delay on audio
quality. Two Jitter values are shown, one value for the
caller side and one value for the callee side.
MOS MOS - Mean Opinion Score (specified by ITU-T

recommendation P.800) - the average grade on quality
scales of Good to Failed, given by the SEM to voice
calls made over a VoIP network at the conclusion of
the testing.
Packet Loss Lost packets - RTP packets that aren’t received by the
voice endpoint for processing, resulting in distorted
voice transmission. Two Packet Loss % values are
shown, one value for the caller side and one value for
the callee side. Packet Loss can be more than 100%.
No value No value will be displayed for 'Cause' if the quality of

the test call is Good. The field will display a value only
when call quality is Fair or Poor.
(Middle) Graphic ■ Indicates the time the call started and ended
illustration ■ Visualizes a caller in a call with a callee, including full names and
email addresses
■ Displays each leg of the call, on both caller and callee side.
■ Each leg is:
✔ Connected to a device
✔ Color-coded to indicate voice quality (green = good, yellow =
fair, red = poor, grey = unknown)
- 241 -
✔ Tagged by C and M
(Lowermost) Two Each opens a page displaying detailed information:

tabs ■ Media (see Media on page 250)
Call Details Page – Debug File Button

To facilitate troubleshooting if for example there's a discrepancy between the Call Details that the
OVOC reports and the call details that you report, you can click a Debug File button in the Call
Details page to save (download) a debug file in json format and then send it to AudioCodes FAEs
for analysis.
Details of a Call Made over Microsoft Skype for Business

The following figure shows the details of a call made over Microsoft Skype for Business. The
Details page displays detailed diagnostic information on the call, in textual format, facilitating
effective management, precise diagnosis and targeted remedial action to prevent recurrence of
unsuccessful call performance or poor call quality.
Figure 8-11: Call Details - Microsoft Skype for Business
If there's an issue of poor quality with a call over Microsoft Skype for Business, one of the two legs
of the call in the Call Details screen will indicate that there's an issue. The leg that indicates that
there's an issue is the leg that scores the worse score of the two legs, i.e., the score indicated in
red, as shown in the figure above. Use this table as reference:
Table 8-10: Call Details - Microsoft Skype for Business
Call Summary Indicates the caller's full name and email address and callee's full
(Uppermost) name and email address.
- 242 -
Call Type Microsoft Skype for Business
Start Time The precise time (hour, minutes and seconds) and date (month, day
and year) when the caller began dialing the number to call.
End Time The precise time (hour, minutes and seconds) and date (month, day
and year) when the call was terminated.
Connect Time The precise time (hour, minutes and seconds) and date (month, day
and year) the connection was established.
Termination Initiator The network entity from which the call was terminated.
Termination Reason The reason why the call was terminated. See the device's User's
Manual for more information about Termination Reason.
Some Skype for Business Termination Reasons are:
■ OK. Indicates the request was successful.
■ Accepted. Indicates that the request has been accepted for
processing, but the processing has not been completed.
■ No Notification
■ Multiple Choices
■ Moved Permanently
■ Moved Temporarily
■ Use Proxy
■ Alternative Service
Manual for more information about Termination Reason.
Media Type Voice
- 243 -
[Quality] Cause Delay Delay (or latency) - the time it takes for information
to travel from source to destination (round-trip
time). Sources of delay include voice encoding /
decoding, link bandwidth and jitter buffer depth.
Two Delay values are shown, one value for the

signal transmitted to the listener and the residual
echo of this signal.
Jitter Jitter can result from uneven delays between

received voice packets. To space packets evenly,
the jitter buffer adds delay. The higher the
measurement, the greater the impact of the jitter
buffer’s delay on audio quality. Two Jitter values
are shown, one value for the caller side and one

recommendation P.800) - the average grade on
quality scales of Good to Failed, given by the SEM
to voice calls made over a VoIP network at the
conclusion of the testing.
Packet Loss Lost packets - RTP packets that aren’t received by

the voice endpoint for processing, resulting in
distorted voice transmission. Two Packet Loss %
values are shown, one value for the caller side and
one value for the callee side. Packet Loss can be
more than 100%.
illustration ■ Visualizes a caller in a call with a callee, including full names
and email addresses
■ Each leg is:
✔ Color-coded to indicate voice quality (green = good, yellow
= fair, red = poor, grey = unknown)
(Lowermost) Two tabs Each opens a page displaying detailed information:

■ Media (see Media on the next page)
- 244 -
Media
The Media tab displays a call’s media parameter settings that operators can refer to for diagnostics,
Figure 8-12: Media
Use the following table as reference to the parameters displayed under the Media tab.
Quality Indicates the call's voice quality: Good | Fair | Poor

Media Port ■ The device's source port in the operations, administration, maintenance, and
provisioning (OAMP) network.
Media Two options: UDP or TCP

Transport
Coder Up to 10 coders (per group) are supported. See the device manual for a list of
supported coders.

Defines the average grade, on a quality scale of Good to Poor, determined after
testing calls made over a VoIP network. Comprises:
Doesn't account for bi-directional effects such as delay and echo. Two values
are shown: (1) for the device side on the caller leg (2) for the device side on the
callee leg.
MOS-CQ = conversational quality; it takes listening quality in both directions into
account, as well as the bi-directional effects. Two values are shown: (1) for the
device side on the caller leg (2) for the device side on the callee leg.
- 245 -
Jitter Jitter can result from uneven delays between received voice packets. To space
evenly, the jitter buffer adds delay. The higher the measurement, the greater the
impact of the jitter buffer’s delay on audio quality. Two Jitter values are shown,
one value for the caller side and one value for the callee side.
Packet Lost packets are RTP packets that aren’t received by the voice endpoint for
Loss processing, resulting in distorted voice transmission. Two Packet Loss % values
are shown, for the caller and for the callee side. Packet Loss can be more than
100%.
Delay The round trip delay is the estimated time (in milliseconds) that it takes to
transmit a packet between two RTP stations. Sources of delay include voice
encoding / decoding, link bandwidth and jitter buffer depth. Two values are
shown, one caller side and another for the callee side.
Echo The residual echo return loss is the level difference (measured in dB) between the
signal transmitted to the listener and the residual echo of that signal.
Signal The ratio of the voice signal level to a 0 dBm0 reference.

Level Signal level = 10 Log10 (RMS talk spurt power (mW)).
Noise The ratio of the level of silent-period background noise level to a 0 dBm0
Level reference. Noise level = 10 Log10 (Power Level (RMS), in mW, during periods of
silence). A value of 127 indicates that this parameter is unavailable.
Burst The mean duration (in milliseconds), of the burst periods that have occurred since
Duration the initial call reception.
BW The estimated bandwidth consumed.

Estimation
Signaling
The Signaling tab displays a call’s signaling parameters that operators can refer to for diagnostics,
Figure 8-13: Signaling
Use the following table as reference to the parameters displayed under the Signaling tab.
- 246 -
Table 8-12: Signaling Parameters
Edge FQDN of the Edge server used by the user who started (caller) / joined (callee)
Server the session.
Gateway Gateway of the user who started (caller) / joined (callee) the session.
Mediation Mediation Server of the user who started (caller) / joined (callee) the session.
Server
URI URI of the user who started (caller) / joined (callee) the session.
Phone Phone URI of the user who started (caller) / joined (callee) the session.
Number
Is Internal Indicates whether the user who started (caller) / joined (callee) the session
logged on from the internal network.
Front End FQDN of the Front End server that captured the data for the session.
Pool FQDN of the pool that captured the data for the session.
Call Call priority of the session.

Priority
Details of a Call Made over an Endpoint Using SIP Publish

The following figure shows the details of a call made over an endpoint using SIP Publish. The
Details page displays detailed diagnostic information on the call, in textual format, facilitating
effective management, precise diagnosis and targeted remedial action to prevent recurrence of
unsuccessful call performance or poor call quality.
Figure 8-14: Call Details – Over an Endpoint Using SIP Publish
- 247 -
Table 8-13: Call Details - Over an Endpoint Using SIP Publish
Call Summary Indicates the caller's full name and email address and callee's full name
(Uppermost) and email address.
Call Type Endpoint
Start Time The precise time (hour, minutes and seconds) and date (month, day and
year) when the caller began dialing the number to call.
End Time The precise time (hour, minutes and seconds) and date (month, day and
year) when the call was terminated.
Connect Time The precise time (hour, minutes and seconds) and date (month, day and
year) the connection was established.
Termination The network entity from which the call was terminated.
Initiator
Termination The reason why the call was terminated. See the device's User's
Reason Manual for more information about Termination Reason.
Manual for more information about the SIP/PSTN Reason.
Media Type Voice
- 248 -
[Quality] Cause Delay Delay (or latency) - the time it takes for information to
travel from source to destination (round-trip time).
Sources of delay include voice encoding / decoding,
link bandwidth and jitter buffer depth. Two Delay
values are shown, one value for the caller side and one

signal transmitted to the listener and the residual echo
of this signal.
Jitter Jitter can result from uneven delays between received

voice packets. To space packets evenly, the jitter
buffer adds delay. The higher the measurement, the
greater the impact of the jitter buffer’s delay on audio
quality. Two Jitter values are shown, one value for the

recommendation P.800) - the average grade on quality
scales of Good to Failed, given by the SEM to voice
calls made over a VoIP network at the conclusion of
the testing.
Packet Loss Lost packets - RTP packets that aren’t received by the
voice endpoint for processing, resulting in distorted
voice transmission. Two Packet Loss % values are
shown, one value for the caller side and one value for
the callee side. Packet Loss can be more than 100%.
illustration ■ Visualizes a caller in a call with a callee, including full names and
email addresses
■ Each leg is:
✔ Color-coded to indicate voice quality (green = good, yellow =
fair, red = poor, grey = unknown)
(Lowermost) Two Each opens a page displaying detailed information:

tabs ■ Media (see Media on the next page)
- 249 -
Media
The Media tab displays a call’s media parameter settings that operators can refer to for diagnostics,
Figure 8-15: Media


Media ■ The device's source port in the operations, administration, maintenance, and
Port provisioning (OAMP) network.
Signal The ratio of the voice signal level to a 0 dBm0 reference.

Level Signal level = 10 Log10 (RMS talk spurt power (mW)).
Noise The ratio of the level of silent-period background noise level to a 0 dBm0
Level reference. Noise level = 10 Log10 (Power Level (RMS), in mW, during periods of
silence). A value of 127 indicates that this parameter is unavailable.
Rx Rate Shows the call's reception rate, in Kbps.
Quality Voice quality: Good (green), Fair (yellow) OR Red (poor).

Defines the average grade, on a quality scale of Good to Poor, determined after
testing calls made over a VoIP network. Comprises:
- 250 -
Doesn't account for bi-directional effects such as delay and echo. Two values are
shown: (1) for the device side on the caller leg (2) for the device side on the callee
leg.
MOS-CQ = conversational quality; it takes listening quality in both directions into
account, as well as the bi-directional effects. Two values are shown: (1) for the
device side on the caller leg (2) for the device side on the callee leg.
Jitter Jitter (in msec) can result from uneven delays between received voice packets.
To space packets evenly, the jitter buffer adds delay. The higher the
measurement, the greater the impact of the jitter buffer’s delay on audio quality.
Packet Lost packets, as a percentage - RTP packets that aren’t received by the voice
Loss endpoint for processing, resulting in distorted voice transmission. Packet Loss
can be more than 100%.
Delay Delay (or latency) (in msec) - the time it takes for information to travel from source
to destination (round-trip time). Sources of delay include voice encoding /
decoding, link bandwidth and jitter buffer depth.
Echo The residual echo return loss is the level difference (measured in dB) between the
signal transmitted to the listener and the residual echo of that signal.
Coder Up to 10 coders (per group) are supported. See the device manual for a list of
supported coders.
SCE Method for conserving bandwidth on VoIP calls by not sending packets when
silence is detected. True = Enabled (On), False = Disabled (Off).
RTP RTP Directional Control. Controlled internally by the device according to the
Direction selected coder.
RTCP RTCP Directional Control. Controlled internally by the device according to the
Direction selected coder.
PTime Packetization time, i.e., how many coder payloads are combined into a single
(msec) RTP packet.
- 251 -
Managing QoE Thresholds Profiles per Tenant

The QoE Thresholds page lets you adding a profile of Quality of Experience threshold values, per
tenant.
For information about adding a global (system) QoE Thresholds template, see QoE Thresholds on
page 65.
➢ To view QoE thresholds profiles:

■ Open the QoE Thresholds page (Calls > QoE Thresholds).
Figure 8-16: QoE Thresholds Profiles
In the page you can:

■ view QoE thresholds profiles and their metrics thresholds
■ add a profile (see Adding a QoE Thresholds Profile per Tenant on page 254)
■ edit or delete an existing profile (see Editing a QoE Thresholds Profile per Tenant on page 257
and Deleting a QoE Thresholds Profile per Tenant on page 257)
Understanding the 3 Sensitivity-Level Profiles

The following table shows the monitored parameters MOS, Delay, Packet Loss and Jitter, each
associated with each of the 3 sensitivity-level profiles: Low, Default and High. Each parameter's
Green-Yellow Threshold and Yellow-Red Threshold differ in association with the configured Profile.
For each monitored parameter, administrators can use the thresholds in the predefined profile, or
define their own thresholds.
Table 8-15: Quality Profile Parameters
Good-Fair Fair-Poor
Parameter Sensitivity
(Green-Yellow) (Yellow-Red)
(units) Level
Threshold Threshold
MOS Low 3.4 2.7
Medium 3.5 2.8
High 3.6 2.9
Delay (msec) Low 200 1200
Medium 160 500
High 140 400
- 252 -
Good-Fair Fair-Poor
Parameter Sensitivity
(Green-Yellow) (Yellow-Red)
(units) Level
Threshold Threshold
Packet Loss (%) Low 2.7 6.6
Medium 2 5
High 1.5 4.3
Jitter (msec) Low 45 90
Medium 40 80
High 35 70
Echo (dB) Low 23 9
Medium 25 10
High 27 11
Understanding How Call Color is Determined

It may be useful for you to understand how Skype for Business call color is determined. As shown
previously, a default profile is assigned to each Front End server, which you can change. (No profile
is attached to the Mediation Server or Edge Server).
A default profile is also assigned to each Link, which you can change and apply to each Link as
shown previously.
Link Profile as Determinant

Each call comprises one or more legs. Each leg is assigned a color, determined by its associated
Link profile. If a call leg passes over few Links and each has a different profile, each Link has its
own color (displayed in the Summary Panes) corresponding to its profile. However, the call leg's
color is set as the worst color received from all the Links profile; the Call Details screen shows
what profile caused the leg color. If a call leg does not match any of the Links, its color is defined
based on the FE profile. The color representing worst quality among all the legs will be the call
color. (If a call comprises only from one leg, the color of the leg will be the call color).
MOS Metric as Determinant

Each profile can be configured with a set of quality metrics (MOS / Packet Loss / Jitter / Delay /
Echo). Each call leg's color is determined at the end of the call using its reported metrics. If MOS is
reported, the leg will be determined by the MOS' color; if not, the color representing worst quality
will be the leg's color. If any of the call leg's reported metrics are excluded from the profile, color
calculations will ignore this metric.
- 253 -
Adding a QoE Thresholds Profile per Tenant

You can add a QoE Thresholds profile.
➢ To add a QoE thresholds profile:

1. Open the QoE Thresholds page (Calls > QoE Thresholds).
2. Click Add.
Figure 8-17: QoE Thresholds Details
3. Provide an intuitive name for the profile. Use the names of the three predefined QoE profiles,
displayed in the QoE Threshold Details screen following, as a reference.
4. In the 'Description' pane, provide an intuitive, friendly description to facilitate future operator
management.
5. From the 'Tenant' drop-down, select the tenant for whom you're customizing this profile.
6. Next to 'Attachments', click the View button.
- 254 -
Figure 8-18: Attachments
7. Expand the tenant to navigate to and select the entities to which to attach this QoE thresholds
profile (devices, links or endpoints).
8. Next to 'Defaults', select:
● Devices in order to set this QoE thresholds profile as the default for all devices. If
selected, then every new device that is added to the tenant is automatically set with this
QoE thresholds profile and all previous devices' default QoE thresholds profile is set with
this new default profile.
● Links in order to set this QoE thresholds profile as the default for all links. If selected, then
every new link that is added to the tenant is automatically set with this QoE thresholds
profile and all previous links' default QoE thresholds profile is set with this new default
profile.
● Endpoints in order to set this QoE thresholds profile as the default for all endpoints. If
selected, then every new endpoint that is added to the tenant is automatically set with this
QoE thresholds profile and all previous endpoints' default QoE thresholds profile is set with
this new default profile.
9. Specify which voice quality metrics to include in or exclude from the profile. You can exclude,
for example, the metrics of 'MOS', 'Delay' and 'Echo', but include 'Packet Loss' and 'Jitter'. To
exclude a voice quality metric, clear its check box. By default, all voice quality metrics are
included in the profile.
- 255 -
10. Enter the MOS metric's thresholds (for example). Enter the other metrics' thresholds. The
following figure shows the profile 'Medium Sensitivity Threshold' as an example.
Figure 8-19: QoE Thresholds Settings - Medium Sensitivity Threshold
11. Click OK; the profile is displayed in the QoE Thresholds page.
12. In the page, select the profile; the QoE Threshold Details are displayed.
- 256 -
Figure 8-20: QoE Threshold Details
The QoE Threshold Details window displays under Attached Items the number of devices / links /
endpoints to which the selected profile is attached.
In the QoE Threshold Details window:
x indicates the lower threshold of the quality metric:
● Up until the threshold value of x is reached = green = good voice quality
● If the threshold value of x is exceeded = yellow = fair voice quality
y indicates the upper threshold of the quality metric:
● Up until the threshold value of y is reached = yellow = fair voice quality
● If the threshold value of y is exceeded = red = poor voice quality
Editing a QoE Thresholds Profile per Tenant

You can edit an existing QoE Thresholds profile per Tenant.
➢ To edit a QoE Thresholds profile:

■ In the QoE Thresholds page (Calls > QoE Thresholds), select the profile to edit and click
Edit; the screen shown under Adding a QoE Thresholds Profile per Tenant on page 254 opens.
Refer to the instructions under the figure.
Deleting a QoE Thresholds Profile per Tenant

You can delete a QoE Thresholds profile per Tenant.
➢ To delete a QoE Thresholds profile per Tenant:

■ In the QoE Thresholds page (Calls > QoE Thresholds), select the profile to delete and click
Delete. Note that default profiles cannot be deleted.
- 257 -
Managing QoE Status and Alarms per Tenant

The QoE Status & Alarms page lets you manage QoE statuses and alarms per tenant.
For information about managing global (system-wide) QoE statuses and alarms, see QoE Status
and Alarms on page 67.
➢ To view QoE statuses and alarms per tenant:

■ From under the Calls menu, open the QoE Status & Alarms page (Calls > QoE Status &
Alarms).
Figure 8-21: QoE Status & Alarms
The information displayed in the page above - QoE Status & Alarms per tenant – is identical to the
information displayed in the global (system-wide) QoE Status & Alarms page. See QoE Status and
Alarms on page 67 for a detailed description.
Adding a QoE Alarm Rule per Tenant

You can add a new rule for a QoE alarm per tenant.
➢ To add a new QoE alarm rule per tenant:

1. From the QoE Status & Alarms page, open the QoE Status & Alarms Settings screen (Calls >
QoE Status & Alarms and then click Add).
- 258 -
Figure 8-22: QoE Status & Alarms Settings

Table 8-16: QoE Status & Alarms Settings
Name Enter an operator-friendly alarm rule name to facilitate intuitive effective

management later.
Description Describe the alarm rule to facilitate effective management later.
Attachments Click View and then navigate to and select the entities to which to
attach this QoE Alarm Rule: devices, links, sites and/or endpoints.
Defaults Select the Device, Link, Site and/or Endpoint monitoring filter.
■ If you select Link, the links selection pop-up opens; select the links
to monitor (the default is All Selected).
■ If you select Device, the device selection pop-up opens; select the
devices to monitor (the default is All Selected).
- 259 -
Monitoring Determines how frequently the OVOC automatically performs data

Frequency (min) analysis. Defines every 15 (default), 30 or 60 minutes.
Minimum Calls to Defines the number of calls to analyze. Default = 50 calls. Up to 1000
Analyze calls can be defined.
If the number of calls made doesn't exceed the defined # of calls to
analyze, the OVOC won't perform data analysis.
Failed Calls Alarm Select the Generate Alarm option to active the alarm. Clear the option
to deactivate the alarm.
Critical Threshold: 5% of calls (default); if this threshold is exceeded,
the alarm is triggered.
Major Threshold: 3% of calls (default); if this threshold is exceeded, the
alarm is triggered.
Poor Quality Calls Select the Poor Quality Calls Alarm option to active the alarm. Clear
Alarm the option to deactivate the alarm.
Critical Threshold: 10% of calls (default); if this threshold is exceeded,
the alarm is triggered.
Major Threshold: 8% of calls (default); if this threshold is exceeded, the
alarm is triggered.
Avg Call Duration Select the Avg Call Duration Alarm option to active the alarm. Clear
Alarm the option to deactivate the alarm.
Critical Threshold: 5 seconds (default), up to 100 seconds; if the
average duration of calls is below this, the alarm is triggered.
Major Threshold: 10 seconds (default), up to 100 seconds; if the
average duration of calls is below this, the alarm is triggered.
Bandwidth Alarm Select the Bandwidth Alarm option to active the alarm. Clear the
option to deactivate the alarm.
Major Threshold: if the bandwidth falls below or exceeds the value you
configure (minimum of 0 Kbps and a maximum of 1000000 Kbps), an
alarm of Major severity is triggered.
Critical Threshold: if the bandwidth falls below or exceeds the value you
configure (minimum of 0 Kbps and a maximum of 1000000 Kbps), an
alarm of Critical severity is triggered.
■ You must configure a higher value for the Critical Threshold than for
the Major Threshold.
■ You can configure a minimum of 0 Kbps and a maximum of 1000000
Kbps for either the Critical or the Major Threshold, so long as the
value you configure for the Critical Threshold is higher than the value
you configure for the Major Threshold.
Max Concurrent Select the Max Concurrent Calls Alarm option to active the alarm.
Calls Alarm Clear the option to deactivate the alarm.
Major Threshold: if the the number of concurrent calls falls below, or
exceeds, the value you configure (minimum of 0 and a maximum of
100000), an alarm of Major severity is triggered.
Critical Threshold: if the number of concurrent calls falls below, or
exceeds, the value you configure (minimum of 0 and a maximum of
100000), an alarm of Critical severity is triggered.
- 260 -
■ You must configure a higher value for the Critical Threshold than for
the Major Threshold.
■ You can configure a minimum of 0 and a maximum of 1000000 for
either the Critical or the Major Threshold, so long as the value you
configure for the Critical Threshold is higher than the value you
configure for the Major Threshold.
3. Click OK; the QoE alarm rule is now listed in the QoE Status & Alarms page.
Editing a QoE Alarm Rule per Tenant

You can edit a QoE alarm rule per tenant.
➢ To edit a QoE alarm rule per tenant:

■ In the QoE Status & Alarms page (Calls > QoE Status & Alarms), select the QoE alarm rule
to edit and then click Edit; the Alarm Rule Details screen opens displaying parameters
identical to those displayed when adding a rule. Use the table above as reference.
Deleting a QoE Alarm Rule

You can delete a QoE alarm rule if necessary.
➢ To delete a QoE alarm rule:

■ In the QoE Status & Alarms page (Calls > QoE Status & Alarms), select the QoE alarm rule
to delete and then click Delete. Note that default QoE alarm rules cannot be deleted.
- 261 -
CHAPTER 9 Getting Information on Users Experience OVOC | User's Manual
9 Getting Information on Users Experience

The OVOC enables you to get information on how end users experience IP network telephony.
'End users' refers to an enterprise's employees. By contrast, 'operators' refers to admin-

istrators managing the enterprise's network using the OVOC.
Adding an Active Directory to the OVOC below shows how to add an Active Directory in the Active
Directories page.
Assessing Overall End Users Experience on page 266 and Assessing a Specific End User's
Experience on page 268 show how to get user experience info in the Users Experience page.
Adding an Active Directory to the OVOC below shows how to manage end users in the User
Details page.
Figure 9-1: Getting Information on Users
Adding an Active Directory to the OVOC

You can add an Active Directory to the OVOC.
➢ To add an Active Directory to the OVOC:

1. Open the Active Directory page (Users > Active Directories).
Figure 9-2: Active Directories
2. Click Add.
- 262 -
Figure 9-3: Active Directory Settings
3. Configure the General AD settings using the following table as reference.

Table 9-1: Active Directory Settings - General
Setting Description
Name Enter an intuitive name for the AD to facilitate operator management

later.
Tenant From the drop-down, select the tenant configured as shown in Adding a
Tenant on page 85.
Host Consult with the IT manager responsible for the AD in your enterprise.
Port The default is typically 389 but consult with the IT manager responsible
for the Active Directory in your enterprise.
Base object Enterprise employees are listed under branches/departments in a tree

structure. Enter in the field the branch/department whose employees
the AD manages. The AD will then access only to that (relevant)
branch/department's employees. For more information, consult with
the IT manager responsible for the Active Directory in your enterprise.
Bind DN For the 'DN' (Domain Name) field, consult with the IT manager
responsible for the Active Directory in your enterprise.
- 263 -
Setting Description
Password Consult with the IT manager responsible for the AD in your enterprise.
Enable SSL Select the option to secure the connection with the AD server over
SSL; an HTTPS connection between the OVOC and the LDAP server
is opened. Clear (default) the option for the connection with the LDAP
server to be non-secured.
Certificate file This option is only activated if the 'Enable SSL' option described before
was selected. From the drop-down, select the certificate file that you
want to use to secure the SSL connection with the LDAP server. The
OVOC authenticates the SSL connection using the certificate. Make
sure you load the SSL certificate file, required by the LDAP Active
Directory platform, to the Software Manager, as described in Adding
Configuration Files to the OVOC's Software Manager on page 72.
Test connectivity Click to test synchronization of the OVOC and the Active Directory
(NA) databases. You can alternatively click Sync Now in the Active
Directories page.
Verify Certificate This option is only activated if the 'Enable SSL' option described
Subject Name previously was selected and a 'Certificate file' was selected from the
drop-down list.
Select this option to enable authentication of the hostname (FQDN)
sent in the Certificate file by the LDAP server. The option provides an
additional means of securing the SSL connection between the OVOC
server and the LDAP server.
4. Click the Synchronization tab.
5. Configure the AD settings - Synchronization tab settings using the following table as reference.
Table 9-2: Active Directory Settings - Synchronization
Setting Description
Check for updates Lets you schedule how frequently synchronization of the OVOC and
every….hours the Active Directory databases takes place. After synchronization is
performed, the OVOC's User Details page is updated to reflect the
Active Directory.
Perform full update Lets you schedule how frequently a full synchronization is performed.
every….days Select from a range of 1-7, i.e., once a day (most frequent) to once a
week (most infrequent). After synchronization is performed, the
OVOC's User Details page is updated to reflect the Active Directory.
- 264 -
Setting Description
At 0:0 Lets you schedule the time at which the full synchronization is
performed. After it's performed, the OVOC's User Details page is
updated to reflect the Active Directory.
6. Click OK.
Editing an Active Directory

You can edit an Active Directory after adding one.
➢ To edit an Active Directory:

2. Select the Active Directory to edit and click now-enabled Edit button.
Figure 9-4: Active Directory Settings
3. Edit the parameters using the table Adding an Active Directory to the OVOC on page 262 as
reference, and then click OK.
- 265 -
Deleting an Active Directory

You can delete an Active Directory if necessary.
➢ To delete an Active Directory:

2. Select the Active Directory to delete and click now-enabled Delete button.
Synchronizing an AD with the AD Server

You can manually synchronize an AD with the AD server.
➢ To synchronize an AD with the AD server:

1. Open the Active Directories page (Users > Active Directories).
Figure 9-5: Active Directories
2. Select the AD to synchronize and click Sync Now.
3. In the confirmation prompt, click OK.
Assessing Overall End Users Experience

The OVOC enables operators to assess at a glance the overall experience of end users and to
tweak the enterprise's telephony network to enhance their experience. Users experience includes
statistics related to voice quality (good, fair and poor quality voice) and statistics related to call
performance (rate and number of successful versus failed calls).
➢ To assess end users experience:

1. Open the Users Experience page (Users > Users Experience).
- 266 -
Figure 9-6: Users Experience
2. [Optional] Filter the page to present only information you require. You can filter by Time Range
(see Filtering to Access Specific Information on page 147) or by Users (see Filtering the User
Details Page on page 270).
3. Use the following table as reference to the page.
Table 9-3: Users Experience
Column Description
Full Name The first name and the family name of the end user (the employee) in the
enterprise.
User Name The employee's user name, defined by the enterprise's network
administrator.
Calls Count The total number of calls made by the end user (employee).
Total Duration The total length of time the end user (enterprise employee) spent on the
phone.
Success/Failed Color-coded bar lets you determine at glance the call success/failure rate
(percentage) was for end users. Point your cursor over a specific end user's
bar to see the rate of successful versus unsuccessful calls.
Call Quality Lets you determine at glance end users calls whose voice quality was
measured as Good (green), Fair (yellow) or Poor (red).
Point your cursor over a specific end user's bar to see that specific end
user's % of calls whose voice quality was measured as Good (green), Fair
(yellow) or Poor (red).
MOS MOS - Mean Opinion Score (specified by ITU-T recommendation P.800) -

the average grade on quality scales of Good to Failed, given by the SEM to
voice calls made over a VoIP network at the conclusion of the testing.
- 267 -
Column Description
Jitter Jitter (in msec) can result from uneven delays between received voice
packets. To space packets evenly, the jitter buffer adds delay. The higher
the measurement, the greater the impact of the jitter buffer’s delay on audio
quality.
Delay Delay (or latency) (in msec) - the time it takes for information to travel from
source to destination (round-trip time). Sources of delay include voice
encoding / decoding, link bandwidth and jitter buffer depth.
Packet Loss Lost packets, as a percentage - RTP packets that aren’t received by the
voice endpoint for processing, resulting in distorted voice transmission.
Packet Loss can be more than 100%.
Description The end user's professional position in the enterprise.
4. [Optional] Select an end user's row and then click Show; details about that specific user's
experience are displayed.
5. [Optional] Click Refresh to manually synchronize the page with the Active Directory.
Assessing a Specific End User's Experience

The OVOC lets operators quickly assess a specific end user's experience, helping operators to
tweak the enterprise's telephony network to enhance that experience.
➢ To assess a specific end user's experience:

1. Open the Users Experience page (Users > Users Experience).
2. Select the row of the end user whose experience you want to assess and then click Show;
details about this specific end user's experience are displayed.
Figure 9-7: Specific End User's Experience
3. Note that the page displaying specific information related to this end user's experience is
automatically dynamically tabbed on the menu bar as a pin (labeled Remco Westerman… in
the page shown above, facilitating quick and easy future access and troubleshooting
management. Operators can delete the pin from the menu bar at any time.
- 268 -
Managing End Users
Only OVOC operators with 'Administrator' security level can perform local management
of end users.
Usernames and passwords of end users are by default locally stored in the OVOC application's
database. The User Details page allows operators to locally manage end users. The page mirrors
the Active Directory. Any change to the AD is reflected in the User Details page immediately after
synchronization is performed.
➢ To manage end users:

1. Open the User Details page (Users > User Details).
Figure 9-8: User Details
2. Optionally, use filters for quick access to specific users.

3. Obtain contact information about end users from under the columns in the table: Full Name,
User Name, Description, Department, Office, Mobile, Home, MS Skype for Business Line
URI, Email, Server, Country.
- 269 -
Filtering the User Details Page

You can filter the Users Details page using the 'User's filter (click the Add Filter button).
Figure 9-9: Users Filter

Table 9-4: 'Users' Filter
Filter Description
Tenants From the drop-down, select a configured tenant. Only calls made by and
received from users assigned to that tenant will be displayed in the page.
Active directories From the drop-down, select an Active Directory. Only calls made by and
received from users associated with that AD will be displayed in the
page.
Name Enter the name of a user. Only calls made by and received from that user
will be displayed in the page.
Country Enter the name of a country. Only calls made and received by users in
that country will be displayed in the page.
Department Enter the name of a department in the enterprise. Only calls made and
received by users in that department will be displayed in the page.
- 270 -
CHAPTER 10 Producing Reports OVOC | User's Manual
10 Producing Reports
The OVOC features essential reports-generation capability that operators can utilize to distribute
session experience data and comparative analyses quickly and effectively to responsible persons
within the enterprise and to external authorities associated with the enterprise's IP telephony
network, for accurate diagnosis and correction of degraded sessions and for general network
optimization.
➢ To open the Reports page:

■ Under the Statistics menu, click the Reports tab.
Figure 10-1: Login
Log in with the same name and password you used to log in to the OVOC.
The default name and password are:
acladmin
pass_1234
The Session Experience Manager (SEM) Reports module opens.

Figure 10-2: SEM Reports
Log in with the same name and password you used to log in to the OVOC.
Three categories of reports help users to quickly and thoroughly analyze different aspects of calls
made over the VoIP network:
■ Network Status Reports
■ Trend Reports
■ Top Users Reports
- 271 -
Categories 1 and 2 are identical in terms of the information displayed (columns); however the
calculation differs.
Category 1 is calculated as a summary of calls made over the entire period for specified entities
(devices / links). The x axis represents the specified entities.
Category 2 is calculated per time interval specified, summarizing the same entity in the specified
interval. The x axis represents the time interval (hour / day / week / month).
The following table shows the categories and the reports options in each.
Table 10-1: Reports Categories
Report Category Explanation
Network Status Reports Displays a summary of key call metrics during a

■ Call Statistics by Device specified time period with a separate row entry for each
device/link.
■ Call Statistics by Link
Purpose: To compare performance, quality and utilization
■ Call Quality by Device across devices/links. For example, the 'Call Statistics by
■ Call Quality by Link Device' report summarizes the % of successful and
■ Call Utilization by Device failed calls and the # of calls that scored in each quality,
■ Call Utilization by Link across specified devices/links. By contrast, a ‘Call
Quality by Device’ report summarizes key metrics
affecting voice quality (jitter, delay, packet loss).
Trend Reports Displays a summary of key call metrics over specified

■ Call Statistics by Device time intervals of a specified device/link.
■ Call Statistics by Link For example, the ‘Calls Trend by Device’ report displays
‘Number of Calls’, ‘ASR’ and ‘Total Duration’ in hourly
■ Call Quality by Device
intervals.
■ Call Quality by Link
■ Call Utilization by Device
■ Call Utilization by Link
Top Users Reports Displays users graded according to number of calls

■ Calls Count made, calls duration, and calls whose quality scored
'Poor' based on specified metrics.
■ Calls Duration
■ Poor Calls Quality
■ Poor Quality by MOS
■ Poor Quality by Jitter
■ Poor Quality by Delay
■ Poor Quality by Packet Loss
■ Poor Quality by Echo
■ Poor Fax Quality
■ Utilization
Using Reports Features

The following features apply to all reports pages across all three reports categories unless stated
otherwise:
- 272 -
Table 10-2: Reports Features
Feature Description
Lets you save a report as a Comma-Separated Value

Save as CSV
(CSV) file which represents charts, data bars,
sparklines, gauges, indicators, etc., in a standardized,
plain-text format easily readable and exchangeable with
many applications. You can open the file in a
spreadsheet such as Microsoft Excel or use it as an
import format for other programs.
Lets you generate a PDF file of the report reflecting

Export to PDF
selected filters, columns, graphs, etc.
Filters Let you specify:

■ The Time Range for the report to cover (in the
Network Status Reports page)
■ The Time Range and the Interval for the report to
cover (in the Trend Report page; Hourly, Daily,
Weekly or Monthly)
■ Devices / Links on which to produce the report
■ Top 10/20/30 Users on which to produce the report
(in the Top Users Report page)
SEM Reports Click the button at any time to return to the Reports
page displaying the three reports categories and the
report options available under each. Click an option to
produce a report.
Scheduled Reports Click the button to schedule a report.
Displayed after selecting a report to produce in the

reports menu. First filter (see above) and then click it;
the report is produced and displayed.
Charts view / Table view Two views are displayed in every report produced:
Charts (uppermost) and table (lowermost). Click to
expand charts view; table view is eclipsed. Click to
revert to both views.
Switch to horizontal / Charts are by default displayed vertically, one below

Switch to vertical the other, in this order: Calls #, Calls %, ASR, Total
Duration, AVG Duration and Calls Quality. Use the
scrollbar to scroll down from one to the next.
They can optionally be displayed horizontally to suit
user preference. To display horizontally, click the link.
Click next or previous to navigate from chart to chart.
[Only applies to Network Status Reports] By default,

Bar / Linear
charts are displayed as bar charts. Click the drop-down
to choose linear charts if required.
Click the icon; optional table view columns are

displayed.
Add / Remove Columns
- 273 -
Feature Description
To add, if required, select an optional column and click

or select all and click . To remove a column,
select it in the Columns List pane and click or select
all and click .
Default metrics columns (left pane) and optional
metrics columns (right pane) in the Summary/Trend
category (except 'Call Quality by Device / Link') are as
follows:

metrics columns (right pane) in a 'Call Quality by
Device / Link' report in the Summary/Trend category
are:

metrics columns (right pane) in the Top Users reports
category are:
- 274 -
Feature Description
See in Producing Top Users Reports on page 280 for

variations across reports in the Top Users Reports
category.
Table column headers display this icon. Click one to

display the metric as a chart. If the chart is already
Show Column Graphical open, you're notified. After report generation, the table's
Representation Display column as ASR metric column is the only one displayed as a chart
chart in Charts view.
Table Bottom Line (Total) The table's bottom line shows column's total. For
example:
■ Calls # column's bottom line shows the total sum of
all counts of all calls on all devices / links
■ ASR column's bottom line shows the average
success rate of the average success rates of all
devices / links.
‘Total’ is calculated according to the measured
parameter.
It can be SUM, AVG, MIN or MAX.
Search Users can use the ‘Search’ option to search for and find
precise information related to a query. When
information related to the search query is found, the
report exclusively displays only that information.
Producing a Network Status Report

Network Status Reports show the sum totals, over the entire period, of calls performance scores,
quality scores, #s, %s, total duration and average duration (default metrics). Reports in this
category are identical in terms of metrics measured. Metrics columns can optionally be added /
removed (see 'Add / Remove Columns' in the table in Using Reports Features on page 272).
➢ To produce a Network Status Report:

1. Click an option in the 'Network Status Reports' category, for example, click the first option,
i.e., Call Statistics by Device.
Figure 10-3: Create Report
2. Filter for 'Time Range' and 'Devices'.

3. Click the Create Report button:
- 275 -
Figure 10-4: Network Status Report – Call Statistics by Device
Following report generation, the Success/Fail Rate column is the only one displayed in charts view.
➢ To display a metric as a chart:
■ In the table, click in the metric's column header. For example, click in the
Success/Fail Rate column header; the Success/Fail Rate chart is displayed:
Figure 10-5: Displaying the Success/Fail Rate Chart
In a Network Status Report you can:

■ Click the Switch to horizontal link to switch from vertical view (default) to horizontal view.
■ Click to expand the charts pane. Click it again to contract it.
■ Click to switch from bar charts (default) to linear charts. Select from the drop-down
(see 'Charts view / Table view' in the table in Using Reports Features on page 272).
■ Click to add/remove a column to/from the table (see 'Add / Remove Columns' in the table
in Using Reports Features on page 272).
■ See in the chart which entities registered the highest failed / successful calls rate.
- 276 -
■ See in the table on which entities most calls were made, what % of calls were made on each,
on which entities most failed / successful calls were made, on which entities most call time
was recorded, on which entities the average call duration was longest / shortest and on which
entity voice quality scored highest (green = good, yellow = fair, red = poor, grey = unknown).
■ See in the chart an entity's success / fail rate (%). Point your cursor over a color in a bar (green
= successful, red = failed):
■ See in the table an entity's success / fail rate (%). Point your cursor over the entity's row (green
= successful, red = failed):
■ See in the table quality scores by pointing your cursor over a color in the entity's Calls Quality
row (green = good, yellow = fair, red = poor, grey = unknown):
- 277 -
Default and optional table columns in Network Status Reports are:

Table 10-3: Table Columns in Network Status Reports
Network Status
Default Columns Optional Columns
Report Type
Call Statistics by Name, Calls #, Calls %, Success/Fail Report ID

Device Rate, Total Duration, AVG Duration, Successful/Failed Calls
Established Calls, Calls Quality, Max %
Concurrent Calls Successful/Failed Calls #
Good/Fair/Poor/Unknown
%
#
Voice Calls #
Fax Calls #
Total Duration
AVG Duration
Call Quality by Name, Voice Calls #, Calls %, Calls Report ID

Device Quality, MOS, Jitter, Delay, Packet Loss, AVG/Max/Min
Echo MOS/Jitter/Delay/Packet
Loss/Echo
AVG SNR
%
#
MOS/Jitter/Delay/Packet
Loss/Echo
%
MOS Calls #
Jitter Calls #
Delay Calls #
- 278 -
Network Status
Report Type
Packet Loss Calls #

Echo Calls #
SNR Calls #
Call Utilization by Name Report ID

Device AVG Total Kbps Calls #
AVG Rx Kbps Packet Loss Calls #
AVG Tx Kbps
AVG Packet Loss
The table above shows call statistics, quality and utilization by device. The same
default and optional columns apply to call statistics, quality and utilization bylinks, but
in terms of streams rather than calls.
■ You can re-filter and re-run the report (see 'Filters' in the table in Using Reports Features on
page 272).
■ You can generate another report. Click the SEM Reports button.
■ You can schedule a report. Click the Scheduled Reports button (for details see Scheduling a
Report on page 282).
Producing Trend Reports

Trend reports show general tendencies over intervals of calls performance, quality, #s, %s, total
duration and average duration (default metrics measured).
Reports in this category are identical in terms of metrics columns displayed. Columns can
optionally be added / removed (see 'Add / Remove Columns' in the table in Using Reports Features
on page 272).
➢ To produce a trend report:

1. Click an option in the 'Trend Reports' category, e.g., the first; the 'Run now' page opens
2. Filter for 'Time Range' and 'Devices'. For the 'Interval' filter select Hourly, Daily, Weekly or
Monthly.
3. Click Create Report.
- 279 -
Figure 10-6: Trend Reports – Call Statistics by Device
In a Trend Report you can:

■ See when most/least calls were made, how many, % of total, each period's success/fail rate
and each period's quality scores.
■ Click the Switch to horizontal link to switch from vertically viewed charts (default) to
horizontally viewed charts (see the table in Using Reports Features on page 272).
■ Click to switch from bar (default) to linear charts. Select from the drop-down (see
'Charts view / Table view' in the table in Using Reports Features on page 272).
■ Click in a column header in the table to display that column as a chart (see 'Show Column
Graphical Representation' in the table in Using Reports Features on page 272)
■ Click to add a column to table view or remove a column from table view (see 'Add /
Remove Columns' in the table in Using Reports Features on page 272). Default columns and
optional columns are identical to the 'Call Statistics by Device/Link' and 'Call Quality by
Device/Link' reports in the Network Status Reports category.
■ Use the pager to navigate to a page if there are multiple pages.
■ Re-filter and re-run the report (see 'Filters' in the table in Using Reports Features on page 272)
■ Export the report to PDF. Click (see 'Export…' in the table in Using Reports Features on
page 272)
■ Save the report as a CSV file. Click (see 'Save…' in the table in Using Reports Features on
page 272)
■ Choose to produce another report by clicking the SEM Reports button.
Producing Top Users Reports

Top Users reports display the top 10, 20 or 30 users in terms of # of calls made, total duration,
average duration, outgoing calls and incoming calls (default metrics measured).
Reports in this report category are identical in terms of metrics columns displayed. Metrics
columns can optionally be added / removed (see 'Add / Remove Columns' in the table in Using
Reports Features on page 272).
- 280 -
➢ To produce a top users report:

1. Click an option in the 'Top Users Reports' category, for example, click the first report option,
i.e., Calls Count; the 'Run now' page opens.
2. Filter for 'Time Range' and 'Devices'. For the 'Top Users' filter, select 10, 20 or 30.
3. Click Create Report.
Figure 10-7: Top Users Report – Calls Count
In a Top Users Report you can:
■ Save the report as a CSV file. Click (see 'Save…' in the table in Using Reports Features on
page 272)
■ Export the report to PDF. Click (see 'Export…' in the table in Using Reports Features on
page 272)
■ Click the Switch to horizontal link to switch from vertically viewed charts (default) to
horizontally viewed charts (see the table in Using Reports Features on page 272)
■ Click in a column header in the table to display that column as a chart (see 'Show Column
Graphical Representation' in the table in Using Reports Features on page 272)
■ Click to add a column to table view or remove a column from table view (see 'Add /
Remove Columns' in the table in Using Reports Features on page 272).
Default and optional table columns in Top Users reports are:
Table 10-4: Table Columns in Top Users Reports
Top Users Report

Type
Calls Count User Name, Calls #, Total Report ID, Voice Calls #/Fax
Duration, Average Duration, Calls #, Total Duration (sec),
Outgoing Calls, Incoming Calls AVG Duration (sec)
Calls Duration User Name, Total Duration, Calls Report ID, Total Duration
#, Average Duration, Outgoing (sec), AVG Duration (sec)
Calls, Incoming Calls
Poor Calls Quality User Name, Poor Quality Calls, Report ID

Calls #, Calls Quality
- 281 -
Top Users Report

Type
Unknown / Good / Fair / Poor

%
Fair #
Poor #
Poor Quality by MOS / User Name, AVG MOS / Jitter / Report ID

Jitter / Delay / Packet Delay / Packet Loss / Echo, Calls MOS / Jitter / Delay / Packet
Loss / Echo #, Total Duration Loss / Echo Calls #
Total Duration (sec)
Poor Fax Quality User Name, Poor Quality Faxes, Report ID

Poor Quality Pages, Total Faxes,
Total Pages
Utilization User Name, Total, RX, TX Report ID
■ Use the pager to navigate if there are multiple report pages.

■ Re-filter and re-run the report (see 'Filters' in the table in Using Reports Features on page 272)
■ Choose to produce another report by clicking the SEM Reports button.
Scheduling a Report
You can schedule the SEM to automatically produce a report periodically.
➢ To schedule a report:
1. Click the Reports icon; the SEM Reports page opens (see the table in Using Reports Features
on page 272).
2. Click the Scheduled Reports button.
Figure 10-8: Scheduled Reports
3. Click to add a schedule.
- 282 -
Figure 10-9: Scheduler
4. Under 'Report Name', select a report to schedule from the 'Report' drop-down list. All reports
under all three report types are listed.
5. In the 'Scheduler Name' field define a name to help you easily identify the schedule.
6. In the 'Description' field, provide a description to help you distinguish this schedule from
others.
7. Under 'Report Filter' you can filter the devices on which the report which you're scheduling will
be produced. By default, all devices will be included. Click All Selected to change the default.
For detailed information on how to filter devices, see Filtering by 'Status' on page 152.
8. Under 'Report Frequency', select either Hourly, Daily (default), Weekly or Monthly. If the
frequency you select is Daily, set the 'Time'.
9. Under 'Run Times', select Unlimited or Limit to limit the schedule to a limited number of report
run times (you can limit to up to 100 run times).
10. Under 'Forward Report', select the Mail option for the report to be automatically forwarded to
your email address.
11. In the 'Mail Addresses' field, define the email address / addresses to which to automatically
forward the report.
12. Click OK; the report is scheduled; you can expect the first to arrive in your mail according to
schedule.
- 283 -
Viewing a Scheduler Generated Report

You can view a report generated by the scheduler.
➢ To view a report generated by the scheduler:

1. In the Scheduled Reports page under the Reports column, click the Generated hyperlink in the
row of the report generated by the scheduler; the Report Generated by Scheduler opens.
Figure 10-10: Report Generated by Scheduler
2. Click Show; the report is generated according to the scheduler.
Saving the File of a Scheduler Generated Report

You can save the file of a report generated by the scheduler.
➢ To save the file:
1. In the Report Generated by Scheduler, click Save Report File.

2. Select the location on your pc in which to save the file and click Save.
Deleting the File of a Scheduler Generated Report

You can delete the file of a report generated by the scheduler.
➢ To delete the file:
1. In the Report Generated by Scheduler page, click Delete File; you're prompted 'Delete
Generated Report File?'
2. Click Yes; the file is deleted.
Editing a Schedule
You can edit a report schedule.
➢ To edit a schedule:
1. In the Scheduled Reports page, click Update Scheduler; the Scheduler opens.
2. Edit the reports schedule and then click OK; you're prompted Previous attachments will be
deleted. Are you sure you want to continue?
3. Click Yes; the edited schedule is displayed in the Scheduled Reports page.
Deleting a Schedule
You can delete a report schedule.
➢ To delete a schedule:
1. In the Scheduled Reports page, click Delete Scheduler; you're prompted 'Are you sure?'.
2. Click Yes; the report schedule is deleted.
- 284 -
Manually Running or Pausing a Schedule

You can manually run or pause a report schedule.
➢ To manually run a schedule:
■ In the Scheduled Reports page, click Run Scheduler; the icon changes to and the
report scheduler is run.
➢ To manually pause a schedule:
■ Click Pause Scheduler; the icon reverts to and the scheduler is paused.
- 285 -
CHAPTER 11 AudioCodes IP Network Telephony Equipment OVOC | User's Manual
11 AudioCodes IP Network Telephony

Equipment
The following table shows the supported AudioCodes IP network telephony equipment.
Table 11-1: Supported AudioCodes IP Network Telephony Equipment
Supported IP
Network Telephony Description
Equipment
MP-1xx: Analog VoIP devices featuring up to 24 analog ports

connected directly to an enterprise PBX (FXO), to phones, or to fax
(FXS). Support up to 24 simultaneous calls.
MP-20x: VoIP Gateway. An all-in-one unit featuring (depending on
model) a VoIP adapter, FXS lines, FXO interfaces, Ethernet LAN
interfaces (with an internal Layer-2 switch), and Ethernet WAN
interface.
MediaPack
(See product documentation for detailed information)
Members of the AudioCodes family of Enterprise Session Border

Controllers. Enable connectivity and security between small medium
Mediant 500 E-SBC businesses (SMBs) and service providers' VoIP networks. Provide
VoIP SBC functionality. Offer enhanced dialing plans and voice routing
capabilities along with SIP-to-SIP mediation, allowing enterprises to
implement SIP Trunking services (IP-to-IP call routing) and IP-based
Mediant 500L E-SBC Unified Communications.
These Multi-Service Business Routers are networking devices that

combine multiple service functions such as a Media Gateway, Session
Border Controller (SBC), Data Router and Firewall, LAN switch, WAN
access, Stand Alone Survivability (SAS) and an integrated general-
purpose server.
Mediant 500 MSBR
Stand Alone Survivability (SAS) functionality offers service continuity
to enterprises served by a centralized SIP-based IP-Centrex server or
branch offices of distributed enterprises. SAS enables internal office
Mediant 500L MSBR communication between SIP clients, along with PSTN fallback in the
case of disconnection from the centralized SIP IP-Centrex server or
IP-PBX.
Mediant 800 MSBR The devices also provide an integrated Open Solution Network (OSN)
Server module. The OSN can host a variety of third-party applications
such as IP-PBX, Call Center, and Conferencing.
Mediant 1000 MSBR (See the specific product documentation for detailed information)
Member of the AudioCodes family of E-SBCs. Enables connectivity

and security between small medium businesses (SMBs) and service
Mediant 500 providers' VoIP networks. Provides VoIP SBC functionality. Offers
Enterprise Session enhanced dialing plans and voice routing capabilities along with SIP-to-
Border Controller SIP mediation, allowing enterprises to implement SIP Trunking
(E-SBC) services (IP-to-IP call routing) and IP-based Unified Communications.
- 286 -
Supported IP
Equipment

Mediant 2600 E-SBC providers' VoIP networks. The device is a fully featured enterprise-
class SBC that provides a secured voice network deployment based
on a Back-to-Back User Agent (B2BUA) implementation. The SBC
functionality provides perimeter defense for protecting the enterprise
from malicious VoIP attacks; mediation for allowing the connection of
any IP PBX to any service provider; and service assurance for service
quality and manageability.
Mediant Software E-SBCs are pure-software products, enabling

connectivity and security between enterprises' and service providers’
VoIP networks. Includes the following product variants:
Mediant Server Edition SBC: x86 server-based platform, which must
be installed on a server that complies to the specified hardware
requirements.
Mediant Virtual Edition SBC: Installed and hosted in a virtual
machine environment that complies to specified requirements.
AudioCodes Mediant
Software Enterprise
Session Border
Controllers
Mediant Cloud The OVOC supports the AudioCodes Mediant Cloud Edition. The
Edition feature is offered by the Mediant VE SBC in AWS-based
environments. It provides similar functionality to the Media
Transcoding Cluster feature but is in the cloud, and its Media
Components handle transcoding as well as all media directly, without
traversing the Mediant VE SBC.
Cost-effective best-of-breed, high density analog media VoIP gateway.

Provides superior voice technology for connecting legacy telephones,
fax machines and modems with IP-based telephony networks, as well
as for integration with IP PBX systems. Designed and tested to be fully
interoperable with leading soft switches, unified communications (UC)
MP-1288
servers and SIP proxies.
Designed for carrier environments including 1+1 power supplies and
1+1 Ethernet redundancy, maintaining high voice quality to deliver
reliable enterprise VoIP communications. Advanced call routing
mechanisms, network voice quality monitoring and survivability
capabilities (including PSTN fallback) result in minimum
communications downtime.
Medium-sized member of the family of market-ready, standards-

compliant Media Gateway systems.
Mediant 3000 Media

Gateway
- 287 -
Supported IP
Equipment
Main features: Redundant common equipment (Power, Controller,

Ethernet Switch); Optional N+1 protection of DSP Cards; Designed for
NEBS Level 3; Optimal, cost-effective channel density; Field-proven,
high voice quality; SS7/SIGTRAN Interworking (SS7/PRI); Open,
scalable architecture; Flexible deployment options; Packet telephony
standards-compliant; IETF and ETSI standards-compliant
Applications: VoP Trunking devices, IP-Centrex devices, VoP Access
devices
Selected specifications: Up to 2,880 independent VoIP to PSTN voice
calls; Voice Coders: include G.711, G.723.1, G.726, G.728, G.729A;
G.165 and G.168 compliant echo cancellation; T.38 compliant relay or
fallback to G.711 analog fax and modem support; call progress tones,
VAD, CNG, dynamic programmable jitter buffer, modem detection,
DTMF detection and generation. Signaling: PSTN: ISDN PRI, CAS,
MFC-R2, MF-R1, SS7/M2UA/SIGTRAN Interworking, IP Transport:
IETF RFC 1889, RFC 1890 RTP/IP Transport, TCP, UDP
(See product documentation for detailed information)

Mediant 4000 E-SBC providers' VoIP networks. The device is a fully featured enterprise-
class SBC provides a secured voice network deployment based on a
Back-to-Back User Agent (B2BUA) implementation. SBC functionality
provides perimeter defense for protecting the enterprise from malicious
VoIP attacks; mediation for allowing the connection of any IP PBX to
any service provider; and service assurance for service quality and
manageability.
Highly scalable Session Border Controller designed for deployment in

large enterprise and contact center locations and as an access SBC for
service provider environments. High-capacity SBC supporting
thousands of concurrent sessions and extensive SIP connectivity with
Mediant 9000 SBC
wide-ranging interoperability, enhanced perimeter defense against
cyber-attacks, and advanced voice quality monitoring.
Also supports active/standby (1+1) redundancy (High Availability) by
employing two devices in the network. Offers branch survivability
during WAN failure, ensuring call service continuity.
Survivable Branch Designed for Microsoft Skype for Business Server, the Survivable
Appliance (SBA) Branch Appliance (SBA) allows remote branch resiliency in a Microsoft
Skype for Business Server network. The AudioCodes SBA resides on
the OSN server platform of the Mediant 800B and the Mediant 1000B
running on a Microsoft Windows 2008 Telco R2 operating system.
Displayed in the OVOC as a module of the Mediant 800B and the
Mediant 1000B devices. When you add either of these platforms to the
OVOC, there is an option to enable the SBA module. The SBA module
has a separate IP address and FQDN Name.
- 288 -
Supported IP
Equipment
405HD, 420HD, 430HD, 440HD (shown here), 445HD, 450HD and

C450HD IP phones, based on AudioCodes High Definition voice
technology, providing clarity and a rich audio experience in VoIP calls.
All models include a large monochrome multi-language graphic LCD
display. The phones provide voice communication over an IP network,
allowing you to place and receive phone calls, put calls on hold,
transfer calls, make conference calls, etc. Phone models support
Microsoft Skype for Business environments as well as non-Microsoft
environments.
■ CloudBond 365 is a modular, adaptable solution for the data center,

customer premises or the branch.
A versatile all-in-one Skype for Business appliance designed for
hybrid environments, it combines the best of the Skype for
Business server, the Cloud-PBX and the service provider’s voice
services.
■ User Management Pack (UMP) 365 is a software application for
managing Skype for Business users on premises or in Cloud PBX
environment and is also part of the AudioCodes CloudBond 365
solution and applies to all CloudBond 365 editions - Standard,
Standard+, Pro, Enterprise and Virtualized Edition.
SmartTAP The AudioCodes SmartTAP 360° Recording for Microsoft Skype for
Business is an intelligent, fully certified and secured enterprise
interactions recording solution of voice, video and IMs. With
SmartTAP, enterprises can capture and index any customer or
organizational interaction across external and internal communication
channels seamlessly.
The AudioCodes Mediant Server CCE Appliance bundles AudioCodes

field-proven SBCs and gateways with the Skype for Business Cloud
Connector Edition into an elegantly packaged 1U chassis that is easy
to deploy and manage.
Based on a powerful HP server, the Mediant Server CCE Appliance
delivers the Cloud Connector integrated with the AudioCodes SBC for
organizations or enterprise branches with up to 2500 users and
supports up to 500 concurrent sessions.
The AudioCodes Mediant 800 CCE Appliance bundles AudioCodes

field-proven SBCs and gateways with the Skype for Business Cloud
Connector Edition into an elegantly packaged 1U chassis that is easy
to deploy and manage.
For organizations or enterprise branches with up to 1000 users, the
AudioCodes Mediant 800 with the integrated OSN server module can
host the Cloud Connector on the same self-contained appliance
supporting up to 185 concurrent sessions.
- 289 -
Supported IP
Equipment
The AudioCodes Voice.AI Gateway brings an intuitive form of human

communications to an enterprise's chatbot service. Supporting phone
and WebRTC voice calls, the service eliminates waiting time,
increases caller satisfaction and can save up to 30% in support
expenditure by automating simple and repetitive tasks.
- 290 -
CHAPTER 12 Adding an Unprivileged User to MSSQL Server OVOC | User's Manual
12 Adding an Unprivileged User to MSSQL

Server
An unprivileged user can be added to the MSSQL server with SQL Server Management Studio.
➢ To add an unprivileged user to the MSSQL server:

1. In the 'Security' folder, right-click Logins and select New Login.
Figure 12-1: New Login
2. Under 'General', enter the Login name, select the SQL server authentication option, enter
and confirm the password, from the 'Default database' drop-down select the default database
to log in with, and then click OK.
- 291 -
Figure 12-2: SQL Server Authentication
3. Under 'Server Roles' shown in the following figure, select public.

Figure 12-3: Login Properties – Servers Role - public
4. Under 'User Mapping' shown in the following figure, in the 'Users mapped to this login' pane,
select LcsCDR and in the 'Database role membership for LcsCDR' pane, select db_
datareader and public.
- 292 -
Figure 12-4: Login Properties – User Mapping – db_datareader | public
5. Under 'User Mapping' shown in the following figure, in the 'Users mapped to this login' pane,
select QoEMetrics and then in the 'Database role membership for QoEMetrics' pane, select
db_datareader and public.
Figure 12-5: User Mapping – QoEMetrics - db_datareader | public
The SQL server side is now ready.

6. In the OVOC, under 'Network', click Add and then select Skype Device.
- 293 -
Figure 12-6: Skype Details
7. From the 'Device Type' drop-down, select Front End Server.

8. Enter the SQL Server IP address.
9. Select the SQL Port option and leave the default unchanged.
10. Click the 'Address' field, enter the first letter of the location, and from the list displayed, select
it.
11. Enter the other details about your Microsoft SQL server - use the user credential defined
previously in the SQL server.
- 294 -
This page is intentionally left blank.
- 295 -
International Headquarters
1 Hayarden Street,
Airport City
Lod 7019900, Israel
Tel: +972-3-976-4000
Fax: +972-3-976-4040
AudioCodes Inc.
200 Cottontail Lane
Suite A101E
Somerset NJ 08873
Tel: +1-732-469-0880
Fax: +1-732-469-2298
Contact us: https://www.audiocodes.com/corporate/offices-worldwide

Website: https://www.audiocodes.com/
©2019 AudioCodes Ltd. All rights reserved. AudioCodes, AC, HD VoIP, HD VoIP Sounds Better,
IPmedia, Mediant, MediaPack, What’s Inside Matters, OSN, SmartTAP, User Management Pack,
VMAS, VoIPerfect, VoIPerfectHD, Your Gateway To VoIP, 3GX, VocaNom, AudioCodes One
Voice and CloudBond are trademarks or registered trademarks of AudioCodes Limited. All other
products or trademarks are property of their respective owners. Product specifications are sub-
ject to change without notice.
Document #: LTRT-91046

One Voice Operations Center Users Manual Ver 76

Uploaded by

Copyright:

Available Formats

One Voice Operations Center Users Manual Ver 76

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

One Voice Operations Center Users Manual Ver 76

Uploaded by

Copyright:

Available Formats

What is the purpose of this document?

What is the purpose of this document?

What products does AudioCodes provide technical documentation for?

What products does AudioCodes provide technical documentation for?

User's Manual

AudioCodes One Voice Operations Center (OVOC)

One Voice Operations

Stay in the Loop with AudioCodes

Mediant 500 MSBR User's Manual

Mediant 500L MSBR User's Manual

Mediant 500L Gateway and E-SBC User's Manual

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 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

One Voice Operations Center Product Description

One Voice Operations Center Integration with Northbound Interfaces Guide

Device Manager Pro Administrator's Manual

Device Manager Express Administrator's Manual

ARM User's Manual

One Voice Operations Center Security Guidelines

One Voice Operations Center Alarms Guide

Document Revision Record

91036 Initial document release for Version 7.4.

91037 Version 7.4 GA

91046 User Defined Failure PM table

3 Configuring Global (System) Settings 50

Restoring the Last Backed-up Configuration to the Device 113

Filtering by 'Alarm Names' 163

Refreshing a Device's Pool License 225

Producing Top Users Reports 280

OVOC enables administrators to adopt a holistic approach to network lifecycle management by

About the One Voice Operations Center

ITSP Multi-Tenancy Architecture

Enterprise Multi-Tenancy Architecture

Non Multi-Tenancy Architecture

Figure 1-4: Non Multi-Tenancy Architecture - Enterprise

Elements in Multi-Tenancy Architecture

System An ITSP managing multiple enterprises using a cloud-based or hosted 'global'

Entity Any element which can be managed or used as a whole:

Resource Any element that can be partly managed/assigned:

ITSP Customer Multi-Tenant Architecture

➢ To log in to the OVOC:

2. Enter your Username and Password:

It's recommended to change the password after initial login.

Getting Acquainted with the Dashboard

Figure 2-2: Dashboard

Use the following table as reference:

Cluster Icon Description

[Devices] Indicates the number of AudioCodes SBC / MSBR / Gateway

[Endpoints] Indicates the number of endpoints currently managed by the

[UMP] Indicates the number of User Management Packs (UMPs) 365

[SmartTAP] Quickly accesses the OVOC's Device Management page filtered

Cluster Icon Description