How to Trace a Malicious Call Using Lync Server 2010 - NextHop - Site Home

Microsoft Lync Server 2010 provides a new Enterprise Voice functionality called Malicious Call Tracing. In this blog post and accompanying video, I’ll show you how to enable this feature, report a malicious call, and locate evidence of a malicious call.

Author: Sasa Juratovic

Publication date: May 2011

Product version: Lync Server 2010

During a recent customer event in UK, I was talking about the new Enterprise Voice features in Lync Server 2010. One of the topics was Malicious Call Tracing. While preparing for the event, I was looking for details about this feature to create an end-to-end scenario. I set up my lab for video and created a screencast. I had fun creating this video and may create additional videos for future blog posts. Let me know if you like this approach and what improvements you would like to see.

My lab environment is relatively simple. I deployed Microsoft Lync Server 2010 Enterprise Edition pool (Standard Edition server will also work), Monitoring Server, and Monitoring Server reports. I also have a few Lync 2010 clients to simulate malicious call reporting.

Here is the scenario.

Jane is a Lync administrator at Contoso. She updates one of the existing voice policies to allow malicious calls reporting
Bob is a help desk representative at Contoso. He has Lync enabled, and the voice policy for malicious call reporting is enabled.
Bob uses his Lync client to receive calls at the help desk.
Bob receives a call that turns out to be very unpleasant. Bob decides to use the Lync client Report a Call feature to report the event as a malicious call.
The malicious call report is sent to Monitoring Server where it is recorded in the Call Details Record database.
Jane then uses Monitoring Server reports to discover details about the reported call. To filter the reported malicious call, Jane uses Diagnostic ID 51017.

Now that we understand how malicious call tracing works at the scenario level, let’s take a look at the video for some “real action.”

Summary

Malicious call tracing might not be the most exciting product feature in Lync, but it is useful if you need it. I hope this post gives you a good overview of how to enable this feature, report a malicious call, and find a malicious call in Monitoring Server reports.

Additional Information

To learn more, check out the following articles:

Voice Policies, http://technet.microsoft.com/en-us/library/gg412891.aspx
Voice Policy Cmdlets, http://technet.microsoft.com/en-us/library/gg415663.aspx
Planning for Monitoring, http://technet.microsoft.com/en-us/library/gg412952.aspx
Using Monitoring Server Reports, http://technet.microsoft.com/en-us/library/gg558662.aspx

Lync Server Resources

We Want to Hear from You

Keywords: Lync Server 2010, malicious call tracing