Tuesday, January 11, 2011

Troubleshooting steps: No audio, video, or desktop sharing with Lync Server topology

We recently stood up our Lync 2010 Edge server and found a problem with audio/video functionality. The issue appeared to be related to firewall ports but we had recently swapped out our OCS 2007 R2 Edge for the Lync 2010 Edge server and none of the firewall port requirements have changed.

We ended up doing a trace using the Lync Server 2010 Logging Tool. Here are the step-by-step instructions for troubleshooting it:

  1. Install the Lync Server 2010 Resource Kit if you haven't already (http://www.microsoft.com/downloads/en/details.aspx?FamilyID=80cc5ce7-970d-4fd2-8731-d5d7d0829266)
  2. From the Lync Server 2010 Edge, open the Logging Tool.
  3. Enable S4, set the Level to "All", and turn on "All Flags" for the Flags section.
  4. Enable SIPStack and set the Level and Flags to the same as above.
  5. Get ready to place a call and be sure you have one test subject inside your network (behind the Edge server) and another person outside the organization (in front of the Edge server).
  6. Click the Start Logging button.
  7. Place the phone call or start a sharing session.
  8. Wait for it to fail and then click the Stop Logging button
  9. Click the Analyze Log Files button
  10. Click the Analyze button
You should now have a capture of the SIP messages which will tell you how the call was trying to be established. 

  1. In the search window at the top, type in "INVITE" and hit Enter.
  2. Click on the INVITE sip:
    in the trace and scroll down the window on the right.
  3. Locate the area in blue where it states "a=candidate". You should see a 'candidate' entry for each IP bound to your local PC along with the Edge server's audio/video conferencing IP. 

The Lync client will attempt to 'nail up the audio' between the path of least resistance. For example, if someone was on the same subnet (172.16.130.x) then a direct connection would be made between the two of us for audio/video and desktop sharing. If not, the next IP is tried. If you have your Edge server configured properly you should see the public IP. In my case I did not. My issue stemmed from a topology configuration which was incorrect. 

When building the topology for your Lync Edge server, you'll be asked if your public IP is using NAT. In the section where this is discussed, other options are available which lead a person to believe the public IP they're talking about has to do with the Access Edge role and not A/V Edge. 

My SIP trace showed the INVITE with a candidate IP of my Access Edge role which lead me to realize the issue and change it. Specifically I had to open Topology Builder, expand the Edge Pool section, click on the Edge server, then click Edit Properties. The top section has a checkbox for "NAT enabled public IP address used". This is very poorly worded and should be changed for future builds. The text should read "Use NAT for your Audio/Video Edge public IP" or "Enter the public IP for your Audio/Video Edge role if you're using NAT".

Thinking about it more and more I understand why there is only one entry for a public IP and not one for Access Edge or Web Conferencing Edge. It's just not very clear.

Anyway, I hope this helps a few of you out there with Lync Server 2010 Edge implementations.

Cheers.




1 comment:

  1. Hi,

    I think I meet the same problem.
    IM works fine to federated users.
    But if I try to make an audio/video session, I can see (through wireshark) that my PC is trying to connect to a private IP (I'm a remote user)...
    So I activated the NAT Checkbox but it does not change anything afeter publishing the topology.

    Do I have to restart edge server or Fe server for this modification to take effect ?

    Thanx,
    Bastien.

    ReplyDelete