She can’t use Lync for these calls, because the call always sounds bad-it cuts in and out, and is choppy. Michelle Martin comes to you and says that she has a scheduled call with the CIO every Tuesday. Let’s assume you are the administrator of a branch office. To be clear, we’re not talking about tracing failed calls.
#MICROSOFT LYNC 2013 CLIENT DOWNLOAD 64 BIT HOW TO#
This article explains how to gather the automatically generated Quality of Experience data found in client logs, and analyze that data to determine the source of the call quality problems. Monitoring Server Reports is the best place to get diagnostic information and troubleshoot call quality issues.įor one-offs, it’s possible to gather the data locally and use Lync troubleshooting tools to diagnose call quality issues. The first course of action was to install
Recently, I was helping a colleague troubleshoot a client’s audio quality issues and discovered that we didn’t have access to the Lync Server Monitoring reports.
Have you ever wanted to figure out why a user experienced poor call quality, but didn’t have access to the Lync Sever Monitoring Server reports to dig into the data? This article shows you how to use UCCAPI logging, Snooper, and XML Notepad to log, review, and analyze call data, when Lync Server 2010 or Lync Server 2013 monitoring reports aren’t available. First published on TECHNET on Dec 07, 2012
0 kommentar(er)
