none
Lync QOE Details RRS feed

  • Question

  • Is there a reference that explains how QOE data is measured, bundled and delivered for use in Call Quality Reports?

    We have an issue where some calls show EXTREMELY high Round Trip Time (some averaging in the 5,000ms range, or 5 seconds).  When we talk to the people on the call they indicate that the call was fine, the only issue was the Lync client reporting poor call quality despite both parties agreeing that the call was good.

    We are QOSing audio traffic (via static port ranges) and are not seeing any issue with actual bandwith for audio.  We are hoping to learn how Lync calculates and transports this data in hopes that it will help us understand why the reports are (sometimes) misrepresenting call quality.  These report anomalies make it very tough for our team to spot actual issues.

    I am hoping to find an answer without calling PSS, it seems every time we call for complex issues such as these we blow through many very expensive and limited (to us) support hours for mediocre at best service.

    Friday, January 17, 2014 3:31 AM

All replies

  • High round-trip values can be caused by international call routing, a routing misconfiguration, or an overloaded media server. High round-trip times result in difficulties with two-way, real-time audio conversations.

    What is the type of call that have high round-trip time?

    Were they coming from external users?

    Please check if you can find any error or warning on Mediation Server.


    Lisa Zheng
    TechNet Community Support

    Monday, January 20, 2014 5:57 AM
    Moderator
  • These are audio calls, the round trip time reported from teh Monitoring Server Reports is above 5000ms average or 5 seconds; clearly peopl eon a call with a 5 second latency would notice.  The issue is that despite the calls reporting terrible performance the people on the calls have a great experience (other than the quality indicaor telling them the call is poor).

    Basically the reports are not aligning with reality making it hard for us to use the reports to see when issues are actually occuring.  If I could gain understanding on how QOE data is captured and delivered I might be able to determine why this is occuring.

    Monday, January 20, 2014 3:15 PM
  • The article below may be helpful:

    http://technet.microsoft.com/en-us/library/gg412952(v=ocs.14).aspx

    The data is collected from SIP message.


    Lisa Zheng
    TechNet Community Support

    Friday, January 24, 2014 8:24 AM
    Moderator
  • Hello JB,

    The RTT values in QoE come from the RTP/RTCP reports in the actual call.  RTT is measured and reported every 5 seconds and the value in QoE is averaged over the entire duration of the call.  For short calls, there will be fewer samples and the errors could be higher.  For longer calls, the average RTT should be fairly accurate.  If the problem repros easily and the call is at least 2 mins long, please report back to this thread. 

    The shipped QOE reports in the Monitoring Server offer initial views of the call quality data. For more advanced monitoring and troubleshooting of poor calls, take a look at the "Lync Network Guide" released last year:

    http://www.microsoft.com/en-us/download/details.aspx?id=39084

    Wednesday, January 29, 2014 6:02 PM