One Voice Operations Center Users Manual Ver 74
One Voice Operations Center Users Manual Ver 74
One Voice Operations Center Users Manual Ver 74
Version 7.4
User's Manual Contents
Table of Contents
1 Introduction ....................................................................................................... 15
1.1 About the One Voice Operations Center................................................................ 15
1.2 Benefits .................................................................................................................. 15
1.3 Intended Audience ................................................................................................. 15
1.4 Network Architecture .............................................................................................. 15
1.4.1 ITSP Multi-Tenancy Architecture .............................................................................16
1.4.2 Enterprise Multi-Tenancy Architecture ....................................................................16
1.4.3 Non Multi-Tenancy Architecture ..............................................................................17
1.4.4 OC Elements in Multi-Tenancy Architecture............................................................17
2 Getting Started .................................................................................................. 19
2.1 Logging in............................................................................................................... 19
2.2 Getting Acquainted with the Network Page Topology ............................................ 19
2.2.1 Returning to 'Home' Page by Clicking AudioCodes' Logo .......................................27
2.2.1.1 Hovering Over a Cluster to Display Information .......................................27
2.2.1.2 Hovering Over a Device to Display Information .......................................28
2.2.1.3 Hovering over a Link to Display Information ............................................29
2.3 Getting Acquainted with the Network Map Page .................................................... 30
2.4 Configuring Operator Authentication ...................................................................... 33
2.4.1 Configuring Operator Authentication Centrally using an LDAP Server ...................33
2.4.2 Configuring Operator Authentication Centrally with a RADIUS Server ...................35
2.4.3 Viewing Operator Authentication in the Application Information Window ...............36
2.4.4 Testing Connectivity with the LDAP / RADIUS Server ............................................37
2.4.5 Configuring Operator Authentication Locally, in the OVOC ....................................38
2.5 Adding an Operator ................................................................................................ 40
2.5.1 How Multi Tenancy Impacts Operator Capabilities .................................................40
2.5.2 Adding a 'System' Operator .....................................................................................41
2.5.2.1 Editing a 'System' Operator ......................................................................44
2.5.2.2 Deleting a 'System' Operator ...................................................................44
2.5.2.3 Deleting Multiple Operators ......................................................................44
2.5.2.4 Suspending a 'System' Operator ..............................................................44
2.5.2.5 Releasing a Suspended 'System' Operator .............................................44
2.5.2.6 Forcing a Password Change ....................................................................45
2.5.3 Adding a 'Tenant' Operator ......................................................................................46
2.5.3.1 Editing a 'Tenant' Operator.......................................................................49
2.5.3.2 Deleting a 'Tenant' Operator ....................................................................49
2.5.3.3 Deleting Multiple Operators ......................................................................49
2.5.3.4 Suspending a 'Tenant' Operator ..............................................................49
2.5.3.5 Releasing a Suspended 'Tenant' Operator ..............................................49
2.5.3.6 Forcing a Password Change ....................................................................50
3 Managing SBC Licenses................................................................................... 51
3.1 Using the Floating License ..................................................................................... 51
3.1.1 Performing Floating License Actions .......................................................................54
3.1.1.1 Unmanage ................................................................................................54
3.1.1.2 Update ......................................................................................................54
3.1.1.3 Reset ........................................................................................................55
3.1.1.4 Register ....................................................................................................55
3.1.2 Configuring OVOC-Floating License Service Communications ..............................55
3.1.3 Viewing Floating License Summaries......................................................................56
3.1.3.1 Device Floating License Utilization Pane .................................................56
3.1.3.2 Viewing Floating License Info ..................................................................57
3.1.3.3 Viewing Device Info ..................................................................................58
List of Figures
Figure 1-1: ITSP Multi-Tenancy Architecture .........................................................................................16
Figure 1-2: Enterprise Multi-Tenancy Architecture .................................................................................16
Figure 1-3: Non Multi-Tenancy Architecture - Enterprise .......................................................................17
Figure 2-1: Login ....................................................................................................................................19
Figure 2-2: OVOC GUI – Network Page – Topology .............................................................................19
Figure 2-3: Dynamic Tab for Fast Access to Specific Information .........................................................24
Figure 2-4: Menu Bar..............................................................................................................................24
Figure 2-5: Network Map Page ..............................................................................................................30
Figure 2-6: Example: Endpoints - 12 Warnings......................................................................................31
Figure 2-7: Alarms Filtered by Severity Level ........................................................................................32
Figure 2-8: OVOC Operator Authentication Options ..............................................................................33
Figure 2-9: Authentication - LDAP ..........................................................................................................34
Figure 2-10: Authentication - RADIUS ...................................................................................................35
Figure 2-11: Test Connectivity ...............................................................................................................37
Figure 2-12: Authentication – OVOC......................................................................................................38
Figure 2-13: 'System' Operator Settings - Basic Info .............................................................................41
Figure 2-14: 'System' Operator Settings – Advanced Info .....................................................................42
Figure 2-15: 'Tenant' Operator Settings – Basic Info .............................................................................46
Figure 2-16: 'Tenant' Operator Settings – Advanced Info ......................................................................47
Figure 2-17: 'Tenant' Operator Settings – Tenants ................................................................................48
Figure 2-18: 'Tenant' Operator Settings – Tenant Assigned ..................................................................48
Figure 3-1: Floating License ...................................................................................................................52
Figure 3-2: Device Floating License Page .............................................................................................52
Figure 3-3: Device Floating License Page Actions ................................................................................54
Figure 3-4: Device Floating License Page – Unmanage Action ............................................................54
Figure 3-5: Device Floating License - Administration Page ...................................................................55
Figure 3-6: Device Floating License Summary ......................................................................................56
Figure 3-7: Device Floating License Summary – Floating License Info .................................................57
Figure 3-8: Device Floating License Summary – Device Info ................................................................58
Figure 3-9: Save Usage Report Data .....................................................................................................59
Figure 4-1: License Summary ................................................................................................................62
Figure 4-2: Tenants Allocations ..............................................................................................................63
Figure 4-3: Tenant Allocations Settings .................................................................................................63
Figure 4-4: SNMP Connectivity Template ..............................................................................................65
Figure 4-5: HTTP Connectivity Template ...............................................................................................66
Figure 4-6: QoE Thresholds Templates .................................................................................................67
Figure 4-7: QoE Thresholds Settings .....................................................................................................68
Figure 4-8: QoE Status and Alarms .......................................................................................................68
Figure 4-9: Alarms Settings ....................................................................................................................70
Figure 4-10: Software Manager ..............................................................................................................72
Figure 4-11: Add Auxiliary File – ini File .................................................................................................73
Figure 4-12: Add Software File ...............................................................................................................73
Figure 4-13: Add Auxiliary File ...............................................................................................................74
Figure 4-14: External Applications - ARM ..............................................................................................75
Figure 4-15: Link for Single Sign On to the ARM ...................................................................................76
Figure 4-16: Device Backup ...................................................................................................................76
Figure 4-17: Task - Add Multiple AudioCodes Devices..........................................................................77
Figure 4-18: Prompt to go to Tasks Page to Assess Status ..................................................................77
Figure 4-19: Tasks Page Showing Task Status - Adding Multiple AudioCodes Devices ......................78
Figure 5-1: Add Tenant...........................................................................................................................79
Figure 5-2: Tenant Details - General ......................................................................................................79
Figure 5-3: Tenant Details – SNMP v2...................................................................................................80
Figure 5-4: Tenant Details – SNMP v3...................................................................................................81
Figure 5-5: Tenant Details - HTTP .........................................................................................................82
Figure 5-6: Tenant Details – Operators ..................................................................................................83
Figure 5-7: Tenant Details - License ......................................................................................................83
Figure 5-8: Add Region ..........................................................................................................................85
List of Tables
Table 1-1: OVOC Application Elements Defined in Multi-Tenancy Architecture....................................17
Table 2-1: Network Topology – Network Entities and Statuses .............................................................20
Table 1-2: Menu Bar ...............................................................................................................................24
Table 2-3: Cluster Icons in the Network Map Page ................................................................................30
Table 2-4: OVOC Operator Authentication Parameters .........................................................................39
Table 2-5: Capabilities Allowed for Each Operator Type / Security Level .............................................40
Table 2-6: 'System' Operator Settings - Basic Info ................................................................................41
Table 2-7: 'System' Operator Settings – Advanced Info ........................................................................43
Table 2-8: 'Tenant' Operator Settings – Advanced Info .........................................................................47
Table 3-1: Floating License Page Column Descriptions ........................................................................52
Table 3-2: Device Floating License Configuration Parameter Descriptions...........................................55
Table 3-3: Device Floating License Utilization Pane Description ...........................................................56
Table 3-4: Device Floating License Summary - Floating License Info ...................................................57
Table 4-1: System Menu ........................................................................................................................61
Table 4-2: SNMP Connectivity Template ...............................................................................................65
Table 4-3: HTTP Connectivity Template ................................................................................................66
Table 4-4: QoE Thresholds Templates ..................................................................................................67
Table 4-5: QoE Status and Alarms.........................................................................................................69
Table 4-6: Alarms Settings .....................................................................................................................70
Table 4-7: OVOC Software File Management per Operator Type .........................................................72
Table 5-1: Tenant Details - General .......................................................................................................80
Table 5-2: Tenant Details – SNMP v2 ....................................................................................................80
Table 5-3: Tenant Details – SNMP v3 ....................................................................................................81
Table 5-4: Tenant Details - HTTP ..........................................................................................................82
Table 5-5: Tenant Details - Operators ....................................................................................................83
Table 5-6: Tenant Details – License.......................................................................................................84
Table 5-7: LP Column Indicating License Statuses ...............................................................................98
Table 5-8: Explanation of Backed Up File Name Format .....................................................................102
Table 5-9: Adding a Link – Parameter Descriptions .............................................................................105
Table 6-1: Time Range Filter ................................................................................................................118
Table 6-2: Topology Filter.....................................................................................................................119
Table 6-3: Status Filter .........................................................................................................................120
Table 6-4: More Filters - Network Topology Page ...............................................................................120
Table 6-5: Severity Filter ......................................................................................................................127
Table 6-6: 'Source Type' Filter .............................................................................................................128
Table 6-7: More Filters – Alarms Active Page ......................................................................................129
Table 6-8: Alarms Forwarding – Topology Conditions .........................................................................135
Table 6-9: Forwarding Alarms – Rule Conditions - Parameter Descriptions .......................................137
Table 6-10: Forwarding Alarms – Destination ......................................................................................137
Table 6-11: OVOC-Syslog Severity Levels Mapping ...........................................................................139
Table 6-12: Forwarding Alarms - Destination – Mail ............................................................................140
Table 8-1: Calls List Columns ..............................................................................................................159
Table 8-2: 'Quality' Filter .......................................................................................................................161
Table 8-3: More Filters – Calls List.......................................................................................................162
Table 8-4: Call Details Page .................................................................................................................164
Table 8-5: Media Parameters ...............................................................................................................165
Table 8-6: Signaling Parameters ..........................................................................................................167
Table 8-7: Error Response Color Codes ..............................................................................................170
Table 8-8: SIP Message Color Codes ..................................................................................................170
Table 8-9: Call Details - Microsoft Skype for Business ........................................................................171
Table 8-10: Media Parameters .............................................................................................................173
Table 8-11: Signaling Parameters ........................................................................................................175
Table 8-12: Call Details - Over an Endpoint Using SIP Publish ...........................................................176
Table 8-13: Media Parameters .............................................................................................................178
Table 8-14: Quality Profile Parameters ................................................................................................181
Table 8-15: QoE Alarm Rule ................................................................................................................186
Table 9-1: Active Directory Settings .....................................................................................................190
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 cannot
guarantee accuracy of printed material after the Date Published nor can it accept responsibility
for errors or omissions. Updates to this document can be downloaded from
https://www.audiocodes.com/library/technical-documents.
This document is subject to change without notice.
Date Published: May-23-2018
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 Web site at
https://www.audiocodes.com/services-support/maintenance-and-support.
Related Documentation
Document Name
Document Name
LTRT Description
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 Web site at http://online.audiocodes.com/documentation-feedback.
1 Introduction
1.1 About the One Voice Operations Center
AudioCodes' One Voice Operations Center (referred to as ‘OVOC’ for short in this document)
is a life-cycle management application for large-scale cloud or premises-based Unified
Communications (UC) deployments.
The OVOC provides full coverage of the entire set of actions required to manage a voice
network in a UC environment. The application provides a powerful voice Network Operation
Center (NOC), complete end-to-end voice network control, service assurance capabilities
and comprehensive optimization and planning tools.
The OVOC uniformly manages, monitors and operates the entire AudioCodes One Voice
portfolio, including Media Gateways, Session Border Controllers, Microsoft SBAs and IP
Phones.
1.2 Benefits
Easy and secure transition to VoIP deployments including UC, hosted business
services and contact centers
OpEx and TCO reduction by using centralized tools to remotely operate the VoIP
network components
Efficiency and simplified device operation, administration and fault management
Intuitive real time network view, capturing entire network status in real time
Reduce MTTR with integrative detection and correction tools
Powerful analytic reports for effective planning of future network expansion and
optimization
Note: The enterprise administrator whose network does not feature multi-tenancy
architecture can skip documentation related to multi-tenancy.
'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.
'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.
Element Description
2 Getting Started
This section shows how to get started with the One Voice Operations Center.
2.1 Logging in
This section covers how to log in to the OVOC.
The Network Topology page (see Figure 2-2) 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. Table 2-5 below 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-1: Network Topology – Network Entities and Statuses
Network
Icon Explanation
Entity
Network
Icon Explanation
Entity
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
= 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 AudioCodes SBC communicating with the OVOC.
= 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
Network
Icon Explanation
Entity
Note:
If no voice quality license exists, status will be Unmonitored.
Link status does not impact device / region
If >> or << is displayed, one-directionality is signified, i.e., the link
only aggregates incoming or outgoing calls.
If no arrows are displayed, bi-directionality is signified, i.e., the
link aggregates both incoming and outgoing calls.
Device Indicate aggregated clusters of devices (AudioCodes devices as well as
clusters 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
Network
Icon Explanation
Entity
Link Square icons indicate aggregated clusters of links. The link indication
clusters 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
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
The Show Grid button allows operators to display gridlines; the background of the
Network Topology page is by default white.
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.
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:
For more information about the dynamic tab that is created for call details, see Section 8.2.
For more information about the dynamic tab that is created for user details, see Section 9.3.
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.
Figure 2-4 below shows the OVOC's menu bar.
Figure 2-4: Menu Bar
Sites Displays the Sites 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 sites to display (per Topology or Time Range)
Quick access to specific information lets operators quickly and
effectively maximize users' QoE.
Endpoints Displays the Endpoints 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 endpoints to display (per Topology or Time Range)
Quick access to specific information lets operators quickly and
effectively maximize users' QoE.
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 Calls Count, Total Duration, Success / Failed, Call Quality, MOS,
Experience 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 Lync
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 Lets you add an AD. Displays existing ADs. Allows you to edit and
Directories to synchronize with the AD server.
The popup displays a summary of devices, links and sites. The popup also indicates the
number of errors and warnings on each.
The popup displays a summary of device information and statuses. The lowermost section
of the popup displays the actions that can be performed on the device. More actions can be
accessed and performed by clicking the More button. The content displayed in the popup
depends on the type of device over which you hover.
The popup displays a summary of link information and statuses. The lowermost section of
the popup displays the actions that can be performed on the link. The content displayed in
the popup depends on the type of device over which you hover.
With the exception of cluster icons, entity icons in the Network Map page are identical to
those in the Network Topography page described in Table 2-5. 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-3: 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. In the
Network Map page you can:
Click the +- icon to zoom in or out of the map.
Click the Save Map Locations button to save the map locations.
Click the Center Map button to center the map in the page - useful if the previous
operator dragged it off center.
In the pane on the right side of the Network Map page, the Network Summary lets you:
Determine how many Devices, Links, Sites and Endpoints on which alarms are
currently 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 Devices Manage 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
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 Critical in the Active Alarms pane above, click 1:
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 shown below allows
you to point your cursor over a green, yellow or red segment; a popup 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:
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 shown below
allows you to point your cursor over a green or red segment; a popup 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).
Note: If an operator tries to log in to the LDAP server and it's unavailable, a local login to
the OVOC is attempted and 'Authentication Type' is automatically switched to OVOC
(local authentication). When the connection is re-established, the operator must manually
switch back authentication mode.
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. Click Submit.
Note: If an operator tries to log in to RADIUS and it's inaccessible, a local login to the
OVOC is attempted and 'Authentication Type' is automatically switched to OVOC (local
authentication). When the connection is re-established, the operator must manually
switch back authentication mode.
The application information window always displays operator security level irrespective of
how authentication is performed.
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.
Parameter Description
Suspend after number of login Lets you configure the number of login attempts attempted by the
attempts operator before the OVOC application suspends 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.
Minimal password length Default: 8 characters. Maximum supported: 30 characters.
Non repetitive characters # from Default: 0. Maximum supported: 10 characters.
previous password
Dictionary check for password Select this option for the OVOC server to perform a password
cracking simplicity weakness check on the OVOC operator's password.
Default: Disabled (unselected).
Enable Password Expiration Select the option to extend the password expiration; the following
Extension two parameters are activated.
Number of Additional Logins Defines the number of logins the operator 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 perform
(days) the number of additional logins defined with the previous
parameter. Range: 1-60.
Monitoring No No No No No Yes
Note: Only a 'system' operator with a security level of 'Admin' can perform tenant
management operations (Add/Remove/Update).
3. Configure the new operator's basic information using the table below as reference. The
screen displays basic operator information and security settings.
Table 2-6: 'System' Operator Settings - Basic Info
Parameter Description
Parameter Description
5. Configure the new 'system' operator's advanced information using Table 2-7 below as
reference. The screen displays advanced account and password settings.
Parameter Description
Note: The operator is automatically prompted to change their password the next time
they log in.
Note: Only a 'system' operator with a security level of 'Admin' can perform 'tenant'
management operations (Add/Remove/Update/Clone/Suspend).
3. Configure the 'tenant' operator's basic info using Table 2-6 as reference.
4. Click Advanced Info.
5. Configure the 'tenant' operator's advanced information using the table below as
reference. The screen displays advanced account and password settings.
Table 2-8: 'Tenant' Operator Settings – Advanced Info
Parameter Description
Parameter Description
Password Warning Max Period Specify the number of days. The operator will receive a warning
(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).
6. Click Tenants.
Figure 2-17: 'Tenant' Operator Settings – Tenants
7. [The screen is only available for the 'tenant' operator]. From the 'Assigned Tenant'
dropdown, select a tenant for this operator from the list of tenants defined in the server.
Multiple tenants can be selected.
Figure 2-18: 'Tenant' Operator Settings – Tenant Assigned
Note: The operator is automatically prompted to change their password the next time
they log in.
Note:
• The Floating License feature must first be enabled on the SBC, in the device's Web
interface: Setup tab > Maintenance folder > Floating License. When the feature
is disabled in the Web interface, the SBC is not displayed in the OVOC.
• If the Floating License is enabled, the 'local' license option will not be available.
• The Floating License cannot exceed the maximum capabilities of the SBC product
for concurrent calls/sessions, due to hardware / CPU limitations.
When an SBC is configured to operate with Floating License and a connection is successfully
established with the OVOC, it is connected to the OVOC’s Floating License application mode.
SBCs report to the OVOC every five minutes their capacity consumption for the above call
functionalities. The OVOC then sends the information in usage reports to the service for all
SBCs managed by OVOC for this feature. The service determines if customers exceed their
purchased license limit based on this information. If a customer hasn't met the terms of
payment, their license may be revoked and this action is reported to the OVOC which blocks
the calling service for all managed SBCs.
If a disconnection of service occurs between the SBC and the OVOC or between the OVOC
and the service, a one-month period of grace is given without affecting SBC call service.
1. View the SBC licenses in the Floating License page that opens.
Figure 3-2: Device Floating License Page
Column Description
Column Description
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
Device Status Green Connected: Device is successfully connected to the Floating 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 Status Green Success: Indicates that the device’s SNMP configuration is 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 Status Green OK: Indicates that a report was successfully sent from the 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.
3. Click the Actions button.
3.1.1.1 Unmanage
This Action allows the device to be unmanaged by the Floating License method.
3.1.1.2 Update
Select this menu option for the action to update the HTTPS Rest connection between the
device and OVOC.
3.1.1.3 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).
3.1.1.4 Register
Select this menu option for the action to perform random registration to the Floating License
Cloud service for the device.
Parameter Description
Floating License OVOC Specifies the OVOC operator with REST authorization to receive and
Operator respond to REST requests from the SBC devices. This operator must
Parameter Description
Total/Allocated bar Indicates the percentage of SBC devices in this OVOC installation that
are 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.
2. Use the table below as reference to the pane's session capacities displayed.
Table 3-4: Device Floating License Summary - Floating License Info
2. The pane summarizes the columns displayed in the main section of the Device Floating
License page, described in Table 2-4.
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.
Three tabs are displayed under the System menu: Administration, Configuration and
Tasks. The table below and the sections following describe the tabs, folders and items under
the System menu.
Table 4-1: System Menu
Under the Administration tab's Security folder you can define authentication and add
operators. See Section 4.1.2 for more information.
Note: The License Summary 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.
2. Select the tenant to whom to allocate licenses and then click Edit.
Figure 4-3: Tenant Allocations Settings
Note: 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
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.
2. Use the table below as a reference to the parameters in the figure above.
Table 4-2: SNMP Connectivity Template
Parameter Description
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 dropdown, select either:
• Authentication and Privacy (default)
• No Security
• Authentication
Parameter Description
2. Use the table below as a reference to the parameters in the figure above.
Table 4-3: HTTP Connectivity Template
Parameter Description
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 dropdown, select either:
• HTTP (default)
• HTTPS
3. Click Submit.
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 table below as reference to the figure above.
Table 4-4: QoE Thresholds Templates
Template Description
Low Sensitivity Threshold Threshold values representing recommended data for the 'Low'
sensitivity level.
Medium Sensitivity Threshold Threshold values representing recommended data for the 'Medium'
sensitivity level.
High Sensitivity Threshold Threshold values representing recommended data for the 'High'
sensitivity level.
3. Provide an intuitive name for the profile. As a reference, use the names of the three QoE
Threshold Templates displayed in Figure 4-6.
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.
Last Runtime Indicates the last time the alarm rule was activated.
Minimum Calls per Entity Indicates the minimum number of calls to analyze, per entity. Default: 50
to Analyze
Failed Calls (%) x y indicates that green changes to orange ('Major' severity)
when the x 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 Section 8.4.1).
Poor Quality Calls (%) x y indicates that green changes to orange ('Major' severity)
when the x percentage of poor quality calls is exceeded and orange
changes to red ('Critical' severity) when the y percentage of of poor
quality calls is exceeded.
indicates alarm issued – displayed if the Generate Alarm option is
selected in the Alarm Rule Details screen (see Section 8.4.1).
Average Call Duration x y indicates that green changes to orange ('Major' severity)
(seconds) when x seconds call duration is exceeded and orange changes to red
('Critical' severity) when y seconds call duration is exceeded.
indicates alarm issued – displayed if the Generate Alarm option is
selected in the Alarm Rule Details screen (see Section 8.4.1).
Bandwidth Rule (Kbps) x y indicates that green changes to orange ('Major' severity)
when x bandwidth is exceeded and orange changes to red ('Critical'
severity) when y bandwidth is exceeded.
indicates alarm issued – displayed if the Generate Alarm option is
selected in the Alarm Rule Details screen (see Section 8.4.1).
Setting Description
Alarms Automatic Clearing Select this option to clear all devices listed in the Alarms page of
all 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 Clearing [Only relevant if the 'Alarms Automatic Clearing' option is selected]
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 Clearing Select this option for device events (events originating from the
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 Clearing Events are by default cleared every three days. You can change
Period (days) the default to suit your requirements.
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
Setting Description
this point, these alarms are not added to the database and are not
forwarded to configured destinations.
Alarms Suppression Counter [Only applicable if 'Alarms Suppression' is selected] Lets you
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 Interval During the time the suppression alarm is active, the OVOC server
(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 interval [Only applicable if 'OVOC Keep-Alive' is selected] Determines how
(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.
System (except operators with • Add any global file that will not be assigned to any specific
'Monitoring' security level) tenant. These files will be visible to both 'tenant' and 'system'
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 with • Add any file. This file will be assigned only to the tenant. These
'Monitoring' security level) files will be visible to both 'tenant' and 'system' operator types.
• Download any file visible by the tenant to the devices in the
tenant.
• Remove any file added by a 'tenant' operator type.
Note:
• 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.
2. Click Add and select Add Auxiliary File from the menu dropdown.
3. From the 'Tenant' dropdown, select the tenant under which the ini file will be added.
4. From the 'File Type' dropdown, select INI (default) if it isn't selected already.
5. Next to the 'File Name' field, click … 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.
3. From the 'Tenant' dropdown, 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' dropdown, select the device version (Default: 6.6).
8. From the 'Select Product' dropdown list, select the relevant product corresponding to the
cmp or rmt/rms file.
9. From the 'Select Protocol' dropdown, select the protocol. Default: SIP. MGCP and
MEGACO are also available.
10. Click OK; the cmp file is added to the Software Manager.
Note:
• 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 Center Security Guidelines.
5. Enter a description of the file in the 'File Description' pane for intuitive future file
management.
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.
4.2.4.1 ARM
The External Applications page enables connecting directly to the ARM (AudioCodes Routing
Manager) in order to manage calls routing over the network. In this page, operators (Admin
and Operator types) configure this connection, a.k.a. Single Sign On (SSO), to the ARM. An
ARM link is then displayed on all OVOC pages, visible to all operator types.
2. In the field 'ARM Server IP', enter the IP address of the ARM server to connect to.
3. [Optionally] Enter the 'ARM User Name' and 'ARM Password' and click Submit.
4. In any OVOC screen, click the ARM button now displayed in the upper right corner as
shown in the figure above; the ARM main screen opens in a new browser tab. Note that
this Single Sign On feature applies only to ARM versions that support it.
Note: If the operator is not a 'system' operator, only tasks performed by that operator are
displayed in the Tasks page.
[Optional] In the 'Location' field, enter the first letters in 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, the operator is prompted to go to the Tasks page to assess task status:
Figure 4-18: Prompt to go to Tasks Page to Assess Status
Figure 4-19: Tasks Page Showing Task Status - Adding Multiple AudioCodes Devices
The page helps this operator determine if all ten AudioCodes devices where added
successfully, or, if the task isn't complete yet, what percentage is complete and what
percentage remains to be completed.
Note: Before you can connect a device to the OVOC you need to:
• Note the server machine's ID and then download the license activation form from
AudioCodes' website's 'Services and Support' page:
http://www.audiocodes.com/services-and-support .
• Obtain your OVOC license, save it on your PC, and then load it to the server. For
detailed information on loading the license to the server, see the One Voice
Operations Center IOM Manual. You can view the license details in the EMS
Server Manager License screen.
• Enable the device's Feature Key.
Note: See Section 1.4 for details on multi-tenancy vs. non multi-tenancy architecture.
To add a tenant:
1. In the Network page, click Add.
Figure 5-1: Add Tenant
2. Select Tenant.
Figure 5-2: Tenant Details - General
3. Use the table below as reference when configuring the tenant's General parameters.
Table 5-1: Tenant Details - General
Parameter Description
5. Use the table below as reference when configuring the SNMP v2 parameters.
Table 5-2: Tenant Details – SNMP v2
Parameter Description
SNMP Read Community Enter an encrypted SNMP read community string. The default
value for the SNMP read community string is taken from the
SNMP main template.
SNMP Write Community Enter an encrypted SNMP write community string. The default
value for the SNMP write community string is taken from the
SNMP main template.
SNMP Trap Community Enter the Trap Community string to be received as part of the
Notification message. The default value for the SNMP trap
community string is taken from the SNMP main template.
7. Use the table below as reference when configuring the SNMP v3 parameters.
Table 5-3: Tenant Details – SNMP v3
Parameter Description
Security Name Enter a name for SNMP v3. Example: OVOC User.
Security Level From the dropdown, select either:
• Authentication and Privacy (default)
• No Security
• Authentication
Authentication Key Enter an Authentication Key. The default is taken from main
SNMP template.
Privacy Protocol From the dropdown, select either:
• AES 128 (default)
• None
• DES
• DES 3
• AES 192
• AES 256
The default is taken from main SNMP template.
Privacy Key Enter a Privacy Key. The default is taken from main SNMP
template.
8. Click OK and then click HTTP.
9. Use Table 5-4 below as reference when configuring the HTTP parameters.
Table 5-4: Tenant Details - HTTP
Parameter Description
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 dropdown, select either:
• HTTP (default)
• HTTPS
The default is taken from main SNMP template.
10. Click OK and then click Operators.
11. Use the table below as reference when configuring the Operators parameters.
Table 5-5: Tenant Details - Operators
Parameter Description
Assigned Operators Select an operator from the list of operators. Only operators
configured as 'tenant' operators are displayed. The list will be
empty if no such operator has been configured, in which case you
can click the Add new operator button described below. The
parameter lets you assign the operator – or operators – to the
tenant. See under Section 2.5.3 for more information about
configuring 'tenant' operators.
Add new operator Click to button; the 'Operator Settings' screen opens for 'tenant'
type operators. For detailed information, see under Section 2.5.3.
12. Click OK and then click License.
Figure 5-7: Tenant Details - License
13. Use the table below as reference when configuring the License parameters.
Table 5-6: Tenant Details – License
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 Devices Support pending. Currently unsupported.
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 Accounts Support pending. Currently unsupported.
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 tenant.
Endpoints Management
Endpoints Enter the number of endpoints the IP Phone Manager Pro
application supports for this tenant.
To add a region:
15. Open the Network Topology page (Network > Topology).
16. Click Add and select Region.
Figure 5-8: Add Region
17. From the 'Tenant' dropdown, select a tenant that you configured - shown in the previous
section.
18. Define the region's name and type in a description to facilitate operator-friendly
management later.
19. [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.
20. Click the now-activated OK button; the region is added to the OVOC.
• 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.
Note:
• 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 'Location' field, enter the first letters in the name of the city / country in
which to locate the device, and then select the city / country from the list that pops up.
9. You need to configure the device’s SNMP settings if you're connecting the device to the
OVOC.
• To configure SNMPv2, click the SNMP v2 tab:
Figure 5-12: Device Details – SNMP v2
Note: The defaults are taken from the SNMP tenant profile.
a. In the 'Security Name' field, enter the Security name of the SNMPv3
operator.
b. From the 'Authentication Protocol' dropdown, 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' dropdown, leave the default unchanged or select
a Privacy Protocol.
e. In the 'Privacy Key' field, leave the default unchanged or enter a privacy
password.
Note: The defaults are taken from the SNMP tenant profile.
Note: 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.
Note:
• 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).
14. Select the Enable SBA option. This is only relevant if the device contains an SBA
module.
Figure 5-16: AudioCodes Device Details – Enable SBA
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. Click the now-activated OK button or click the First Connection tab.
19. Select the Enable Initial Connection Provisioning option. This is the Automatic
Provisioning a.k.a. Zero Touch feature. See Appendix B for more information. When
adding an AudioCodes device or when adding multiple AudioCodes devices, you can
implement this feature to enable 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.
20. From the now-activated 'Configuration File' dropdown, select the applicable file.
21. From the now-activated 'Firmware File' dropdown, select the applicable file.
22. Click the now-activated OK button; the device is added to the OVOC.
Note: 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.
6. In the 'FQDN' field, enter the Microsoft Lync device's Fully Qualified Domain Name.
7. In the 'SQL Server IP' field, enter the IP address of the SQL Server. Applies to the
centralized Lync 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 Lync database.
• 'SQL Instance Name' option (by default selected)
9. In the 'SQL Server User' field, enter the user of the SQL Server. Applies to the
centralized Lync database.
10. In the 'SQL Server Password' field, enter the Password of the SQL Server. Applies to
the centralized Lync database.
11. From the 'SSL' dropdown, 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 Section 4.2.3.
Default: Disabled. The SSL connection with the SQL server is by default non-secured.
12. [Optional] In the 'Location' field, enter the first letters in the name of the city / country in
which to locate the device, and then select the city / country from the list that pops up.
13. Click the now-activated OK button; the Lync device is added.
Note: Only a 'tenant' operator can manage the Fixed License Pool. To configure a 'tenant'
operator, see License Pool Operator 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:
SBC periodically polls
Operator updates OVOC notifies SBC SBC requests OVOC sends the If an updated license for
OVOC for license
SBC license in that LP has been updated license updated license to the SBC is discovered,
updates (License
OVOC LP updated from OVOC the SBC OVOC sends it
Status request)
Note: An SBC's license is valid for seven days but this is reset each time a successful
connection is established between it and the OVOC License Pool. If the SBC cannot
connect 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
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.
2. Select the Manage Device option to allow the License Pool to allocate capacities to the
device if the capacities allowed by the locally installed License Key are exceeded.
Note:
• The device periodically checks with the pool for SBC capacity licenses. If the pool
has one for the device, it sends it.
• A standalone device must be reset for an allocated license to take effect. This
impacts service. If communication with the pool is lost for a long period, the device
discards the allocated license (i.e., expires) and resets with its initial license
according to the License Key (preventing misuse of licenses allocated by the pool).
• When a device operates in High-Availability (HA) mode, the active and redundant
devices are installed with a new SBC license from the pool without impacting traffic
through a hitless license upgrade mechanism whereby the pool first downloads the
license to the redundant device, resets it, and then triggers the devices to perform an
HA switchover. It then downloads the same license to the previously active device
(now the redundant), resets it, and then triggers another HA switchover. Currently
active calls are therefore maintained throughout the process. With HA devices, you
need to perform an Apply License action (rather than a Reset Device action). If you
decrease the pool, traffic in HA mode may be impacted. You can optionally perform
a Refresh License action to check current open sessions.
• For HA systems, the pool automatically allocates an equal number of SBC licenses
(sessions) to both the active and redundant devices. For example, if the pool
allocates 200 sessions to the active device, it also allocates 200 to the redundant.
It's therefore important to take this into consideration when ordering a license pool.
• If the device is restored to factory defaults, the SBC licenses allocated by the pool
are removed and those from the locally installed License Key are applied.
• If the pool allocates a device an SBC license that exceeds the maximum number of
sessions the device supports, the device sets the number to its maximum supported.
3. Select SBC Sessions and enter the number of media sessions (voice calls) the License
Pool will allocate to the SBC.
4. Select SBC Registrations and enter the number of registration sessions (the number
of users that can be registered with the device) the License Pool will allocate to the SBC.
5. Select SBC Transcoding and enter the number of transcoding sessions the License
Pool will allocate to the SBC.
6. Select SBC Signaling and enter the number of SIP signaling sessions the License Pool
will allocate to the SBC.
Note:
• The number of licenses required for an HA device is twice the number of licenses
per device (active device + redundant device). If the License Pool server allocates
200 sessions to the active, it will allocate 200 sessions to the redundant.
• According to AudioCodes licensing policies, HA devices require an equivalent
number of licenses for both the active and redundant devices. For more
information, contact your AudioCodes representative.
To apply a license:
The icon alerts you to apply a hitless new license to an HA-supported device
because the number of active sessions/users on the device is higher than that
allocated to the device (see the table below). From the Actions dropdown, select
Apply License; When the action is performed, the device performs a hitless upgrade
using the HA switchover mechanism. Refresh License (see the next action below) is
also needed until you see that all active license values are displayed with the new
reduced values otherwise some of the users/sessions will be disconnected when
choosing Apply License.
Note: When applying a hitless license update (Apply License) to an HA device whose
maximum number of sessions exceeds that available in the License Pool, service is
affected.
To refresh a license:
1. From the Actions dropdown, select Refresh License; the configured license session
values are refreshed according to the current active sessions/users on the device.
Icon Status
Note:
• If a device's capacity is exceeded, the value displayed in the License Pool is red.
• If a devices license expires, the Last Request Time displayed is red.
• Running a hitless license downgrade on an HA device when the current number of
active SBC sessions/users on the device is higher than that allocated to the device
can lead to service disruption. To avoid this, run the Refresh License action or wait
until the number of current SBC sessions/users is aligned to the configured value.
• If you downgrade the transcoding session license so that the number of active
transcoding sessions/users is higher than what was allocated to the device, service
is not affected, i.e., there is no forceful closure of excess call sessions. No new call
sessions can be established, however, until the number of current transcoding
sessions is less than / equal to the limit defined in the new session license.
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-25: Make Sure License Pool Operator is Valid
Make sure the device is connected to the OVOC (Network > Devices > Manage >
select the device > Show).
Figure 5-26: Make Sure the Device is Connected to the OVOC
4. Click Upload; the configuration is uploaded from the device to the OVOC server.
To add a link:
1. After configuring devices, open the Links page (System > Network > Links).
Figure 5-30: Links
2. Click Add.
Figure 5-31: Link Details
Parameter Description
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 dropdown list, select the source device from which to link to
the destination device. You can alternatively search for it.
Destination Device From the dropdown 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' dropdown:
Category From the dropdown select one of the Category Types below. Based on your selection,
Type the link will count and compute statistics on all calls originating in the source device.
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 below 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 below for more information.
Media Realm Defines the source device Media Realm index (a list of options may
be available).
Remote Media Defines the source device Media Realm subnet index (a list of options
Subnet may be available; Media Realm must also be defined).
FQDN Available only when the source device is a Lync 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.
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 figure below.
Note:
• 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 two
streams 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.
To add a site:
1. After configuring the region under which to locate the site, open the Sites page (Network
> Sites).
Figure 5-32: Sites
2. Click Add.
Figure 5-33: Site Details
3. From the 'Region' dropdown, 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.
Note:
• Applies to all AudioCodes phones whose management is supported by IP Phone
Manager Pro, and to all phones which support SIP PUBLISH protocol and whose
QoE management is supported by the OVOC's Session Experience Management.
• 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.
2. See the IP Phone Manager Pro Administrator's Manual for detailed information on how
to configure phones.
2. See the IP Phone Manager Pro Administrator's Manual for detailed information on how
to determine phones statuses.
Warning
♦ Endpoints then the Endpoints page opens displaying all endpoints whose
status is Error / Warning
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.
• 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 popup 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 popup 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.
• 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.
• Quality Distribution pie chart
♦ Point your cursor over a green, yellow or red segment; a popup indicates the
# and % of 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 popup 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.
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
Under 'Device Calls', select a call made over that device and then click the Show button
to display that call's details.
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 Table 6-1.
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'.
Filter Description
Managed by license pool From the dropdown list, select either Both, Managed or Not
managed.
Product type From the dropdown list, select the product type to display on the
page, or enter a search string.
Link type From the dropdown list, select IPGroup, Trunk Group, Phone
Prefix, Control IP, Media IP or Media Realm to display on the
page.
You can optionally filter the page by Time Range (see Section 6.2.1) and Topology (see
Section 6.2.1.2).
The page displays (from L-R):
Metrics (see Section 6.3.1.1)
Bar Charts (see Section 6.3.1.1)
Statistics Summary (see Section 6.3.1.2)
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
popup. The date and time indicates when the period ended.
Figure 6-11: 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 popup 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:
Figure 6-12: 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. Packet Loss can be more than 100%.
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.
For more information about these voice quality metrics, see under Table 8-5.
2. Optionally filter the page by Topology (see Section 6.2.1.2), Severity (see Section
6.2.1.3), Source Type (see Section 6.4.3.1), or More Filters (see Section 6.4.3.3), and
then select an alarm alarm or multiple alarms and click Actions.
4. Select Save Alarms to File to save alarms to file for future reference.
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.
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.
Filter Description
Sources Enter the name of the entity from which the alarm originated.
Alarm Type Select the 'Events' option for the page to display only alarms that
are of type events.
2. In the 'Name' column in the Active Alarms page, you can view:
• Bell icons, if you filtered for 'Only Alarms'
• Flag icons, if you filtered for 'Only Events'
Figure 6-23: Active Alarms - Type Filter
In the Alarms Forwarding Rule screen (Alarms > Forwarding > Add), click the tab
Rule Conditions and then from the 'Alarm Names' dropdown, select the alarm.
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 under Section 6.2.1.
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-28: History Alarms - Type Filter
2. In the Alarms Forwarding Rule screen (Alarms > Forwarding > Add), click the tab Rule
Conditions and then from the 'Alarm Names' dropdown, select the alarm.
To forward alarms:
1. Open the Alarms Forwarding page (Alarms > Forwarding).
Parameter Description
Rule Name Define an intuitive name, to be displayed in the alarm summary screen.
Forward matching Allows or prevents forwarding alarms depending on the destination you
alarms/events -or- select. If you select Prevent forwarding matching alarms/events and then
Prevent forwarding select Minor Alarms from the 'Severities' dropdown under the Rule
matching Conditions tab, then minor alarms are not forwarded.
alarms/events
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.
Parameter Description
Rule Owner From the dropdown, 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 dropdown, 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.
3. Click the Rule Conditions tab.
Parameter Description
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' dropdown, 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.
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).
5. Click the Destination tab.
Parameter Description
Destination Type Determines the format in which the alarm or event will be forwarded.
From the dropdown, select
• SNMP (default)
SNMP v2
SNMP v3
• MAIL
• SYSLOG
Figure 6-34: Alarms – Forwarding – Destination – Mail – Use Internal Mail Server
Parameter Description
Use Internal Mail If this option is selected, all the fields in this table below will be deactivated,
Server except the 'To' field. If selected, it'll only be necessary to configure the internal
mail server as the destination to which to forward alarms; it'll be unnecessary
to configure a mail host. If the option is cleared, all the fields in this table
below will be activated.
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 Password Enter the mail host 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.
3. 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
To upgrade a device:
1. In the Network Topology page, position your cursor over the device; the Actions menu
pops up, as shown above.
2. Click the More Actions link and then click the now-displayed Software Upgrade icon;
the Software Upgrade dialog opens.
Figure 7-2: Software Upgrade
To reset a device:
1. In the Network Topology page, position your cursor over the device; the Actions menu
pops up, as shown above.
2. Click the More Actions link and then click the now-displayed Reset icon.
3. [Optional] Select the Burn configuration into the 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.
5. Click OK; the latest file is downloaded to the device from the server.
Note:
• If the device selected is an AudioCodes MSBR, the latest cli file is downloaded.
• If the device selected is an AudioCodes MP-202 or MP-204, the latest conf file is
downloaded.
• If the device selected is any other AudioCodes device (except CloudBond), the
latest ini file is downloaded.
To upload a device's software configuration file from the device to the server:
1. Open the Devices page (Network > Devices) and select the device from which to
upload the software configuration file to the server.
2. Click Actions.
5. Click OK; the latest file is uploaded to the server from the device.
Note:
• If the device selected is an AudioCodes MSBR, the latest cli file is uploaded.
• If the device selected is an AudioCodes MP-202 or MP-204, the latest conf file is
uploaded.
• If the device selected is any other AudioCodes device (except CloudBond), the
latest ini file is uploaded.
To lock a device:
1. In the Network Topology page, position your cursor over the device; the Actions menu
pops up, as shown in Figure 7-1.
2. Click More Actions and then click the Lock icon.
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.
Note: 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 synchronize links:
1. In the Network Topology page, position your cursor over the device; the Actions menu
pops up, as shown in Figure 7-1.
2. Click the Sync Links icon.
Figure 7-6: Sync 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.
To move a device:
1. In the Network Topology page, position your cursor over the device; the Actions menu
pops up, as shown in Figure 7-1.
2. Click the Move icon.
Figure 7-7: Move Device
3. From the 'Tenant' dropdown, select from the list of tenants the tenant to move the device
to (see Section 5.1 for information on how to add a tenant).
4. From the 'Region' dropdown, select from the list of regions the region to move the device
to (see Section 5.2 for information on how to add a region).
5. If the device is an HA device, configure 'Reset redundant'.
6. Click OK.
3. Save the configuration file to the PC's download folder or Save As to the location of your
choice.
Note:
• If the device is an AudioCodes MSBR, an cli file is saved.
• If the device is an AudioCodes MP-202/MP-204, a conf file is saved.
• If the device is another AudioCodes device (except CloudBond), an ini file is saved.
Note: Saving configuration to flash may disrupt current traffic on the device. To avoid
this, disable all new traffic before saving, by performing a graceful lock (see Section
7.1.6).
Note: The only settings that are not restored to default are the management (OAMP)
LAN IP address and the OVOC's login username and password.
Note: Resetting a device's redundant chassis only applies to HA devices. For detailed
information about HA devices, see the relevant device's User's Manual.
2. From the Actions dropdown, select the Reset Redundant option. If the menu option is
disabled, the device selected does not support HA.
Resetting a device's redundant chassis is identical to resetting an active device. See
Section 7.1.3 for more information.
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.
2. From the Actions dropdown, select the Switchover option. If the menu option is
disabled, the device selected does not support HA.
The page displays information related to active alarms on the device, journal events,
statistics summary and calls made over the device.
The page is dynamically automatically tabbed on the menu bar: IL S48 EF 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.
Under the 'Statistics Summary' section, 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, Successfull / Failed or Quality Color.
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 under Section 8.2
for more information).
The page displays information about active alarms on the link, journal events,
statistics summary and calls made over the link.
The page is dynamically automatically tabbed on the menu bar: Bezeq SIPT 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.
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, Successfull / Failed or Quality Color.
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 under Section 8.2 for more information).
The page displays contact details, Lync details if any, user statistics and recent calls.
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.
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, Successfull / Failed or Quality Color.
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 under Section 8.2
for more information).
2. Edit the device's details. For more information, see Section 5.3.
3. Click OK.
To delete a device:
Select the device to delete and then click the Delete button.
To reset a device:
1. From the Actions menu, select Reset Device.
Figure 7-15: 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 Section 7.1.10 for more information about burning a device's configuration
to flash memory.
Note: 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.
Note: Only relevant to HA devices. A switchover is performed in order to apply the license
parameter on both devices.
2. Click OK.
Note: Only relevant to HA devices. A switchover is performed in order to apply the license
parameter on both devices.
Note: 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 Section 6.2.1), Topology (see
Section 6.2.1.2), Source Type (see Section 6.4.3.1), Quality (see Section 8.1.1 below) or
More Filters (see Section 8.1.2 below).
Use the table below as reference to the columns in the Calls List.
Table 8-1: Calls List Columns
Column Description
Column Description
Note: 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.
The Save As button lets you download calls information (numbers and text) in a coma-
separated calls.csv file format that can later be easily opened and read in any text editor, as
well as sent as an attachment in an email to others.
At the foot of the page, the pager shown above 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
Filter Description
Failed | Success Filters calls according to their status. If you clear Success and
select Failed, only calls whose status was Failed are displayed in
the page.
Poor, Fair, Good or Unknown Filters calls according to their quality. If you clear all except Poor,
only calls whose quality was Poor will be displayed.
None, MOS, Jitter, Delay, P. Filters calls according to the cause of the quality. If - after
Loss or Echo displaying only calls whose quality was poor/fair - you clear all
except Delay, the page will display only calls whose quality was
poor/fair because there was a delay on the line.
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.
Media Type From the dropdown list, select the media type to display on the
page, or enter a search string. Select either Voice, Video, Audio
Video, Image, Data, Unknown, Application Sharing or Chat. By
default, all media types are selected.
Call Type From the dropdown list, select the call type to display on the
page, or enter a search string. Select either Gateway, SBC,
IP2IP, MS Lync, MS Lync Conference or Endpoint.
Microsoft Lync 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
Microsoft Lync's ConferenceSessionDetailsView Monitoring
Server report. For example, from the 'Media Type' dropdown
choose Chat; the Media Type column then displays only MS
Lync conferences whose Media Type is Chat.
Filter Description
Termination Reason Enter the reason why the call was terminated. See the device's
User's Manual 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 Lync 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
8.2.1.1 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 table below as reference to the parameters displayed under the Media tab.
Table 8-5: Media Parameters
Parameter Description
Media IP Address The IP address of the device source in the operations, administration,
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.
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.
Parameter Description
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).
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.
8.2.1.2 Signaling
The Signaling tab displays a call’s signaling parameters that operators can refer to for
diagnostics, troubleshooting and session experience management issues.
Figure 8-6: Signaling
Use the table below as reference to the parameters displayed under the Signaling tab.
Table 8-6: Signaling Parameters
Parameter Description
8.2.1.3 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-7: Trends
Note: 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.
Select a SIP message to display its MESSAGE INFO in the right pane
Note: 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.
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
8.2.3 Details of a Call Made over Microsoft Skype for Business (Lync)
The figure below shows the details of a call made over Microsoft Skype for Business (Lync).
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-10: Call Details - Microsoft Skype for Business
If there's an issue of poor quality with a call over Microsoft Skype for Business (Lync), 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-9: Call Details - Microsoft Skype for Business
Call Summary (Uppermost) Indicates the caller's full name and email address and callee's full
name and email address.
Call Status Successful or Failed
Call Quality Good | Fair | Poor voice quality
Call Type Microsoft Lync (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.
Duration The duration of the call, in seconds.
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 MS Lync 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.
8.2.3.1 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-11: Media
Use the table below as reference to the parameters displayed under the Media tab.
Table 8-10: Media Parameters
Parameter Description
Parameter Description
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.
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.
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.
BW Estimation The estimated bandwidth consumed.
8.2.3.2 Signaling
The Signaling tab displays a call’s signaling parameters that operators can refer to for
diagnostics, troubleshooting and session experience management issues.
Figure 8-12: Signaling
Use the table below as reference to the parameters displayed under the Signaling tab.
Table 8-11: Signaling Parameters
Parameter Description
Edge Server FQDN of the Edge server used by the user who started (caller) / joined
(callee) the session.
Gateway Gateway of the user who started (caller) / joined (callee) the session.
Mediation Server Mediation Server of the user who started (caller) / joined (callee) the session.
URI URI of the user who started (caller) / joined (callee) the session.
Phone Number Phone URI of the user who started (caller) / joined (callee) the session.
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 Priority Call priority of the session.
Call Summary (Uppermost) Indicates the caller's full name and email address and callee's full
name and email address.
Call Status Successful or Failed
Call Quality Good | Fair | Poor voice quality
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.
Duration The duration of the call, in seconds.
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.
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 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 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
Loss 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%.
None Indeterminate cause
(Middle) Graphic illustration Indicates the time the call started and ended
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)
Tagged by C and M
C = Control summary (point cursor to view tooltip)
M = Media IP address and Port (point cursor to view tooltip)
(Lowermost) Two tabs Each opens a page displaying detailed information:
Media (see Section 8.2.4.1)
Signaling (see Section 8.2.1.2)
8.2.4.1 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-14: Media
Parameter Description
Media IP Address The IP address of the device source in the operations, administration,
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.
SNR The ratio of the signal level to the noise level (Signal-Noise Ratio).
SNR = Signal level – Noise level.
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.
Parameter Description
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 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%.
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 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.
Good-Fair Fair-Poor
Parameter (units) Sensitivity Level (Green-Yellow) (Yellow-Red)
Threshold Threshold
3. Provide an intuitive name for the profile. Use the names of the three predefined QoE
profiles, displayed in Figure 8-15, as a reference.
4. In the 'Description' pane, provide an intuitive, friendly description to facilitate future
operator management.
5. From the 'Tenant' dropdown, select the tenant for whom you're customizing this profile.
6. Next to 'Attachments', click the View button.
Figure 8-17: 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.
10. To configure the MOS metric's thresholds (for example), click the bar or drag the
markers. Each bar unit increments or decreases the threshold by 0.1 (MOS, Packet
Loss) or 1 (Delay, Jitter, Echo). Configure the other metrics' thresholds in the same way.
Figure 8-18 below shows the 'Medium Sensitivity Threshold' profile as an example.
Figure 8-18: Medium Sensitivity QoE Thresholds Profile
11. Click OK; the profile is displayed in the QoE Thresholds page shown in Figure 8-15.
12. In the page, select the profile; the QoE Threshold Details are displayed.
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
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
Section 4.2.1.4 for a detailed description.
Parameter Description
Parameter Description
Avg Call Duration Alarm Select the Avg Call Duration Alarm option to active the alarm.
Clear 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 Calls Alarm Select the Max Concurrent Calls Alarm option to active the 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.
• 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.
Section 9.1 shows how to add an Active Directory in the Active Directories page.
Section 9.2 and 9.3 show how to get user experience info in the Users Experience page.
Section 9.1 shows how to manage end users in the User Details page.
2. Click Add.
Figure 9-2: Active Directory Settings
Setting Description
Tenant From the dropdown, select the tenant configured as shown under Section 5.1.
Name Enter an intuitive name for the AD to facilitate operator management later.
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.
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 From the dropdown, 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 under Section 4.2.3.
Test connectivity Click to test synchronization of the OVOC and the Active Directory databases.
(NA) You can alternatively click Sync Now in the Active Directories page.
Check for updates Lets you schedule how frequently synchronization of the OVOC and the
every….hours 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. Select
every….days 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.
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.
4. Click OK.
2. [Optional] Filter the page to present only information you require. You can filter by Time
Range (see Section 6.2.1) or by Users (see Section 9.4.1).
3. Use Table 9-2 as reference to the page.
Table 9-2: 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).
Column Description
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.
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 (see the next section).
5. [Optional] Click Refresh to manually synchronize the page with the Active Directory.
3. Note that the page shown in Figure 9-6, displaying specific information related to this
end user's experience, is automatically dynamically tabbed on the menu bar as a pin
(labeled Walter van… in the page shown in Figure 9-6), facilitating quick and easy future
access and troubleshooting management. Operators can delete the pin from the menu
bar at any time.
Note: 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.
2. Optionally, use filters for quick access to specific users (see the section below).
3. Obtain contact information about end users from under the columns in the table: Full
Name, User Name, Description, Department, Office, Mobile, Home, MS Lync Line URI,
Email, Server, Country.
Filter Description
Tenants From the dropdown, 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 dropdown, 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.
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. Requirements for the Session Experience
Manager (SEM) Reports module are:
Microsoft Lync Server for customers with one Front End server and one SQL server.
• Up to two Microsoft Lync solutions in one SEM application.
• Microsoft Lync Server limitation: When functioning with Lync server pools (FE,
Edge and Mediation), the FE server defined in the SEM functions as the
monitoring SQL database. After connecting, the SEM presents all Call Details
from the Lync network in the SEM's Calls List and Call Details views. When
functioning with Lync pools, FE, Edge and Mediation servers cannot be defined in
the SEM, so the entire Lync network is presented in the SEM only as a single
object, namely, the monitoring SQL database.
Note: 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
Note: 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
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).
Table 10-1 shows the categories and the reports options in each.
Table 10-1: Reports Categories
Network Status Reports Displays a summary of key call metrics during a specified time
Call Statistics by Device period with a separate row entry for each device/link.
Call Statistics by Link
Purpose: To compare performance, quality and utilization across
devices/links. For example, the 'Call Statistics by Device' report
Call Quality by Device
summarizes the % of successful and failed calls and the # of
Call Quality by Link calls that scored in each quality, across specified devices/links.
Call Utilization by Device By contrast, a ‘Call Quality by Device’ report summarizes key
Call Utilization by Link metrics affecting voice quality (jitter, delay, packet loss).
Trend Reports Displays a summary of key call metrics over specified time
Call Statistics by Device intervals of a specified device/link.
Call Statistics by Link For example, the ‘Calls Trend by Device’ report displays
Call Quality by Device ‘Number of Calls’, ‘ASR’ and ‘Total Duration’ in hourly intervals.
Call Quality by Link
Call Utilization by Device
Call Utilization by Link
Top Users Reports Displays users graded according to number of calls made, calls
Calls Count duration, and calls whose quality scored 'Poor' based on
Calls Duration
specified metrics.
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
Feature Description
Feature Description
Default metrics columns (left pane) and optional metrics columns (right
pane) in a 'Call Quality by Device / Link' report in the Summary/Trend
category are:
Default metrics columns (left pane) and optional metrics columns (right
pane) in the Top Users reports category are:
See under Section 10.1.3 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 open, you're notified. After report
Show Column Graphical generation, the table's ASR metric column is the only one displayed as a
Representation Display chart in Charts view.
column as chart
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.
Following report generation, the Success/Fail Rate column is the only one displayed in charts
view.
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
Click to switch from bar charts (default) to linear charts. Select from the drop-
down (see 'Charts view / Table view' in Table 10-2).
Click to add/remove a column to/from the table (see 'Add / Remove Columns' in
Table 10-2).
See in the chart which entities registered the highest failed / successful calls rate.
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):
Note: The table above shows call statistics, quality and utilization by device. The same
default and optional columns apply to call statistics, quality and utilization by links, but in
terms of streams rather than calls.
You can re-filter and re-run the report (see 'Filters' in Table 10-2).
You can generate another report. Click the SEM Reports button.
You can schedule a report. Click the Scheduled Reports button (for details see Section
10.2).
Click to switch from bar (default) to linear charts. Select from the drop-down
(see 'Charts view / Table view' in Table 10-2).
Click in a column header in the table to display that column as a chart (see 'Show
Column Graphical Representation' in Table 10-2)
Click to add a column to table view or remove a column from table view (see 'Add
/ Remove Columns' in Table 10-2). 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 Table 10-2)
Save the report as a CSV file. Click (see 'Save…' in Table 10-2)
Choose to produce another report by clicking the SEM Reports button.
Save the report as a CSV file. Click (see 'Save…' in Table 10-2)
Click in a column header in the table to display that column as a chart (see 'Show
Column Graphical Representation' in Table 10-2)
Click to add a column to table view or remove a column from table view (see 'Add
/ Remove Columns' in Table 10-2).
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, Report ID, Total Duration (sec),
Calls #, Average Duration, AVG Duration (sec)
Outgoing Calls, Incoming Calls
Poor Calls Quality User Name, Poor Quality Calls, Report ID
Calls #, Calls Quality Unknown / Good / Fair / Poor %
Fair #
Poor #
Poor Quality by MOS / Jitter / User Name, AVG MOS / Jitter / Report ID
Delay / Packet Loss / Echo Delay / Packet Loss / Echo, MOS / Jitter / Delay / Packet
Calls #, Total Duration Loss / Echo Calls #
Total Duration (sec)
Poor Fax Quality User Name, Poor Quality Report ID
Faxes, Poor Quality Pages,
Total Faxes, Total Pages
Utilization User Name, Total, RX, TX Report ID
To schedule a report:
1. Click the Reports icon; the SEM Reports page opens (see Figure 10-2)
2. Click the Scheduled Reports button.
Figure 10-8: Scheduled Reports
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 Section
6.2.1.3.
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.
1. In the Report Generated by Scheduler (see Figure 10-10), click Save Report File.
2. Select the location on your pc in which to save the file and click Save.
1. In the Report Generated by Scheduler page (see Figure 10-10), click Delete File;
you're prompted 'Delete Generated Report File?'
2. Click Yes; the file is deleted.
To edit a schedule:
1. In the Scheduled Reports page (see Figure 10-8), click Update Scheduler; the
Scheduler opens (see Figure 10-9).
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.
To delete a schedule:
1. In the Scheduled Reports page (see Figure 10-8), click Delete Scheduler; you're
prompted 'Are you sure?'.
2. Click Yes; the report schedule is deleted.
In the Scheduled Reports page (see Figure 10-8), click Run Scheduler; the icon
changes to and the report scheduler is run.
Click Pause Scheduler; the icon reverts to and the scheduler is paused.
Note: If any device's IP interface table does not meet these requirements, the Initial
Connection Provisioning will fail and an alarm will be sent to the OVOC (see Section B.3).
[ \InterfaceTable ]
Note: Before adding an AudioCodes device or multiple devices, you must load the
device ini and .cmp files to the OVOC's Software Manager. See Section 4.2.3 for
details.
Figure B-1: First Connection: Add AudioCodes Device | Add Multiple AudioCodes Devices
2. Optionally filter the page by Time Range (see Section 6.2.1), Topology (see Section
6.2.1.2), Source Type (see Section 6.4.3.1) or More Filters (see Appendix B.4 below).
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.
After an ini or cmp file is deployed on multiple devices, you may need to customize one
device's configuration to suite specific requirements.
Note: AudioCodes recommends that you consult with AudioCodes Customer Support or
Professional Services about special configuration issues.
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.
2. Under 'General', enter the Login name, select the SQL server authentication option,
enter and confirm the password, from the 'Default database' dropdown select the default
database to log in with, and then click OK.
Figure C-2: SQL Server Authentication
4. Under 'User Mapping' shown in the figure below, in the 'Users mapped to this login'
pane, select LcsCDR and in the 'Database role membership for LcsCDR' pane, select
db_datawriter and public.
Figure C-4: Login Properties – User Mapping – db_datareader | public
5. Under 'User Mapping' shown in the figure below, 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.
AudioCodes Inc.
27 World’s Fair Drive,
Somerset, NJ 08873
Tel: +1-732-469-0880
Fax: +1-732-469-2298
©2018 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 subject to change without notice.
Document #: LTRT-91043