This is part four of a four-part series that outlines how to use Snooper to troubleshoot Lync Server 2010. In this video, Jigar Dani, a Senior Support Escalation Engineer at Microsoft, uses Snooper to troubleshoot an outbound call failure to a PSTN number. He explains how to analyze log files to determine the root cause of the failure.

Author: Jigar Dani

Publication date: May 7, 2012

Products: Lync Server 2010, Lync 2010

Snooper is a multipurpose debugging tool for Microsoft Lync Server 2010 communications software. Snooper parses server and client trace log files and makes protocol (for example, SIP and HTTP) messages and traces easier to read. It can also read call details and stored procedure execution reports for errors. In addition, Snooper can display reports about users, conferences, and conferencing servers (also known as multipoint control units or MCUs). You can download this tool and other Microsoft Lync Server 2010 Resource Kit tools from the Download Center.

Scenario

Attempt is to make a call from the PSTN to Joe Healy (+1 (704) 256-2011).

The call path is:  PSTN phone –> PSTN Gateway –> Lync Mediation Server –> Lync Front End Server –> Lync Client.

The figure below illustrates the network layout. NAPool consists of two Front End Servers with co-located Mediation Servers.

 

Troubleshooting

I used the Lync Server Logging Tool to troubleshoot the call connectivity issue. Below is the data that may help you to troubleshoot your issues.

Lync Server Logging Tool on the Mediation Server for the following components with all levels and all flags:

  • Mediation Server
  • S4

Lync Server Logging Tool on the Front End Server for the following components with all levels and all flags:

  • S4
  • SipStack
  • InboundRouting
  • TranslationApplication
  • UserServices

Network Monitor network captures from the internal and external network adapters of the Lync Server 2010 Mediation Server

Additional Resources

 Lync Server Resources

We Want to Hear from You