: the Lync 2010 client, runs the binary communicator.exe which harkens back to the days of Microsoft Live Communication Server 2005. The Lync 2010 client creates logs in the Communicator-uccapi-0.uccapilog format, while Lync 2013 creates logs in the Lync-UccApi-0.UccApilog format. Userprofile%\appdata\Local\Microsoft\Office\15.0\Lync\Tracing. The Lync 2013 client tracing logs located at: % The Lync 2010 client tracing logs are located at: : To ensure you capture the correct call and QoE data in the UCCAPI log, remove all client UCCAPI logs from the path before starting Lync and replicating the issue. In the upper right corner of the Lync main window, click To enable client logging in your Lync 2010 or Lync 2013 client: Microsoft Lync Server 2010 Resource Kit Tool Here are the tools you’ll need to do the job:
Parse that XML data with a free tool called Lync Server 2010 Resource Kit Tool: SnooperĬopy the call quality data into a XML file. To capture, analyze, and diagnose poor quality audio, do the following:Īfter the call is complete, open the client log using Assuming you don’t have access, you need to wait for Michelle to initiate her next call with the CIO and gather her client log when the call is completed. I could argue that you should, but that’s a different discussion.
Why is she having an issue with this particular call and can you fix the problem?Īs the branch office administrator, you don’t have full access to the Lync Server Monitoring reports. She uses her Lync client for all other calls and the call quality is excellent. 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.
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