Quality Of Experience; Reporting Voice Quality Of Experience To Ovoc; Configuring The Ovoc Server - AudioCodes Mediant 4000 SBC User Manual

User's Manual
16

Quality of Experience

This chapter describes how to configure the Quality of Experience feature.
16.1

Reporting Voice Quality of Experience to OVOC

The device can be configured to report voice (media) Quality of Experience (QoE) to
AudioCodes' One Voice Operations Center (OVOC) server, a plug-in for AudioCodes
OVOC. The reports include real-time metrics of the quality of the actual call experience,
which are then processed by the OVOC.
OVOC is a VoIP-quality monitoring and analysis tool. OVOC provides comprehensive
details on voice traffic quality, allowing system administrators to quickly identify, fix and
prevent issues that could affect the voice calling experience in enterprise and service
provider VoIP networks. IT managers and administrators can employ OVOC in their VoIP
networks to guarantee effective utilization, smooth performance, reliable QoS levels, and
SLA fulfillment.
Note:

16.1.1 Configuring the OVOC Server

The device can report QoE voice metrics to a single OVOC server or to two OVOC servers
deployed in a Geographic Redundancy, High-Availability (HA) mode. Geographic
Redundancy is when each OVOC server is located in a different network subnet and has
its own IP address. For the device to report QoE to both servers, you need to configure the
IP address of each server. For normal HA mode, when both OVOC servers are located in
the same subnet, a single OVOC server (global, virtual) IP address is used for all network
components (OVOC clients and managed devices). Thus, in such a setup, you need to
configure only this IP address.
You can also configure the device to use a TLS connection with the OVOC server. Before
you can do this, configure a TLS Context (certificates) in the TLS Contexts table (see
''Configuring TLS Certificate Contexts'' on page 103). If no TLS Context is specified, the
device uses the default TLS Context (ID 0).
You can also configure at what stage of the call the device must send the report to the
OVOC server. The report can be sent during the call or only at the end of the call.
Reporting at the end of the call may be beneficial when network congestion occurs, as this
reduces bandwidth usage over time.
Note:
•
If a QoE traffic overflow is experienced between OVOC and the device, the device
sends the QoE data only at the end of the call, regardless of your settings.
•
The 'Call Flow Report Mode' parameter is for enabling the device to send SIP
messages to OVOC for displaying SIP call dialog sessions as call flow diagrams.
For more information, see Enabling SIP Call Flow Diagrams in OVOC on page
777.
For a detailed description of the OVOC parameters, see ''Quality of Experience
Parameters'' on page 848.
Version 7.2
For information on the OVOC server, refer to the OVOC User's Manual.
309
16. Quality of Experience
Mediant 4000 SBC