Module10

Monitoring

MVA Jump Start

Module Overview

• Voice Quality Concepts

• Exploring Lync Monitoring Server Components
• Exploring Lync Monitoring Server Reports
• RTP and RTCP Collected Information
Lesson 1: Voice Quality Concepts

• What Defines Voice Quality?

• What Constitutes “Good” Voice Quality?
• Common Audio Problems
• Voice Processing Sender to Receiver (1 of 2)
• Voice Processing Sender to Receiver (2 of 2)
What Defines Voice Quality?

• Call reliability:
– Calls get established as expected
– Calls do not drop midway through

• Audio quality:
– Meeting user needs for how audio sounds within a call

• Who matters:
– User quality of experience (QoE):
• Can I make voice calls successfully?
– Administrator quality of life:
• Can I discover, diagnose, and resolve voice quality issues effectively?
What Constitutes “Good” Voice Quality?

• Starting point for most user expectations is the desktop PBX phone:
– High dial-tone availability
– Narrow-band audio

• “Good” voice quality is highly subjective and context-sensitive:

– Up to a point, users will accept lower voice quality given other advantages:
• For example, cellular phones trade mobility for lower call reliability
– Internet Voice over Internet Protocol (VoIP) users trade price for audio quality

• Bottom line: Users not noticing voice-quality issues is what defines success
Common Audio Problems
Acronym

 AEC = Acoustic Echo Cancellation

 AGC = Automatic Gain Control

 VAD = Voice Activity Detection

Voice Processing Sender to Receiver (1 of 2)

Echo
AEC component deals with
echo. AEC requires linearity
for both timestamp and
wave form of the media. If
there are too many glitches
it could reset AEC.
Fidelity
Fidelity of audio depends on
clarity of the audio quality.
Noise Suppression (NS)
helps in this area. Also, the
Microphone Array
component enhances the
audio capture quality which
in turn enhances the fidelity.
Voice Processing Sender to Receiver (2 of 2)

Network
Network related issue has to do with bandwidth.
Bandwidth issues are addressed by VAD. Also
codecs and ptime can impact the bandwidth
available for Audio.
Glitch and Latency
Latency can be due to many things for example,
OS, the network, AEC, codec, jitter buffer, all of this
can contribute to latency
Lesson 2: Exploring Lync Monitoring Server Components

• Monitoring Server Components (1 of 2)

• Monitoring Server Components (2 of 2)
• Enabling Monitoring Server
• Lync Server 2013 Monitoring Management Pack for SCOM
• Lync Server 2013 SCOM
• SCOM Monitoring Scenarios
Monitoring Server Components (1 of 2)

• Lync Server 2013 Monitoring Server role:

– Role has been deprecated
– Instead, monitoring services are now collocated on each Front End server

• Monitoring Server databases:

– Built on Microsoft SQL Server database software
– Microsoft SQL Server 2008 R2 Enterprise Edition (64-bit)
– Microsoft SQL Server 2008 R2 Standard Edition (64-bit)
– Microsoft SQL Server 2012 Enterprise Edition (64-bit)
– Microsoft SQL Server 2012 Standard Edition (64-bit)

• SQL Server Reporting Services

– Required in order to deploy Monitoring Server reports
Monitoring Server Components (2 of 2)

• Data collection agents

– Unified Data Collection Agent running on each Front-End Server
– The agent will capture all data required by the different modalities
– The raw data will persist in the local LYSS* Queue
– The data will be processed by appropriate data adapters for migration to the
respective final destination data store
• Monitoring Server Reports (optional)

* Lync Storage Service: buffers communication between

Lync Server and back-end storage (SQL Server and Exchange)
Enabling Monitoring Server

• Unified data collection agents are automatically installed and

activated on each Front-End Server
• You do not need to configure a server to act as the Monitoring
Server.
• Each Front-End Server already functions as a Monitoring Server.
• You need to install and configure a database to act as the backend
data store for monitoring data
Lync Server 2013 Monitoring Management Pack for SCOM

• A comprehensive end-to-end monitoring management pack for

System Center Operations Manager (SCOM):
– SCOM 2007 R2
– SCOM 2012

• Provides extensive component event and performance monitoring:

– Full support for Synthetic Transactions against a Lync Server 2013 deployment

• Uses Monitoring Server CDR and QoE data to generate alerts

showing deployment health
Lync Server 2013 SCOM

What’s New?

–Scenario availability from any location

–Synthetic transaction logs
–Increased call reliability coverage
–Dependency monitoring
–Enhanced reporting
SCOM Monitoring Scenarios

• Synthetic transactions
• Call reliability alerts
• Media quality alerts
• Component health alerts
• Dependency health monitoring
Lesson 3: Exploring Lync Monitoring Server Reports

• Peer-to-Peer Activity Summary Report

• User Registration Report
• Call Diagnostic Summary Report
• Media Quality Summary Report
• Monitoring Database Performance
• Configuring Monitoring Server Settings
• Collecting Monitoring Data
Peer-to-Peer Activity Summary Report
User Registration Report
Call Diagnostic Summary Report
Media Quality Summary Report
Monitoring Database Performance

An important consideration is the placement of data and log files

• Recommended disk configuration:
– RAID 10 using 6 spindles

• Placing all database and log files that are used by the Front End Pool
onto the RAID drive set.
• Using the Lync Server Deployment Wizard will result in a
configuration that has been tested for good performance
• All Lync 2013 Pool databases will follow this SQL design

http://technet.microsoft.com/en-us/library/gg398479.aspx
Configuring Monitoring Server Settings

• Lync Server Control Panel, Monitoring and Archiving:

– Call Detail Reporting tab
• Enable or disable Call Detail Reporting
• Configure the Call Detail Reporting purging settings
– QoE Data tab
• QoE purging settings
– Server Application tab
• Enable or disable QoE

• Lync Server Management Shell:

– Set-CsCdrConfiguration
– Set-CsServerApplicationSetting
– Set-CsQoEConfiguration
Collecting Monitoring Data

• If monitoring has been enabled for a pool

• You can disable / enable Call Detail Recording
• You can disable / enable Quality of Experience data collection

Set-CsCdrConfiguration –Identity “Global” –EnableCDR $False

Set-CsQoEConfiguration –Identity “Global” –EnableQoE $False

Monitoring Report Types

• Media Quality Summary Report

• User Activity Report
• Quality of Experience Report
• Call Detail Record Report
• Location Report
• Server Performance Report
• Device Report

http://blog.insidelync.com/2012/06/a-primer-on-lync-audio-quality-metrics/
Lesson 4: RTP and RTCP Collected Information

• What Data Does the Media Quality Summary Report Collect?

• Media Quality Summary Report — Poor Call Percentage
• Media Quality Summary Report — Poor Call Percentage Detail
What Data Does the Media Quality Summary Report Collect?

• JitterInterArrival: Average network jitter from Real Time Control Protocol

(RTCP) statistics. Jitter is the variation in the time between packets arriving,
caused by network congestion, timing drift, or route changes.

• RoundTrip: Round trip time from RTCP statistics. For acceptable quality
this should be less than 100ms.

• PacketLossRate: Average packet (RTP) loss rate during the call

• OverallAvgNetworkMOS: Average wideband network MOS for the call.

This metric depends on the packet loss, jitter, and codec used. The range
is [1.0 to 5.0].

http://blog.insidelync.com/2012/06/a-primer-on-lync-audio-quality-metrics/
Media Quality Summary Report — Poor Call Percentage
Media Quality Summary Report — Poor Call Percentage Detail
Lync Client Debugging

• Enable client logging

• Request log file from user

– %homepath%\AppData\local\Microsoft\Lync\Tracing

• Download Lync Server 2013 Debugging Tools

• Inspect log file using Snooper
©2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics and other product names are or may be
registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the
current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be
interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this
presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.