Interpreting Lync Monitoring and Reporting
•Download as PPTX, PDF•
1 like•973 views
Working with an interpreting Lync Monitoring and Reporting with Examplse
Recommended
More Related Content
Viewers also liked
Viewers also liked (17)
Similar to Interpreting Lync Monitoring and Reporting
Similar to Interpreting Lync Monitoring and Reporting (20)
Recently uploaded
Recently uploaded (20)
Interpreting Lync Monitoring and Reporting
- 4. • Call Detail Records (LCSCDR) • Information Lync collects about whom, what, where… and stores them in the CDR database • Who made the call? • Who received the call? • Who initiated a conference? • What was the duration of the call? • Who’s using the system? How many unique users? • Quality of Experience (QOEMetrics) • Lync collects standard metrics for calls and stores it in the QOE database. This information pertains to the metrics such as • Packet loss • Jitter • Round trip times
- 6. Just a small taste of what’s reported on
- 8. Avg. listening MOS Calculation based on an algorithm to classify the overall quality of a call. 1 – poor (unusable) 2 – bad 3 - fair 4 - good 5 - excellent Avg. Jitter Measures the average variability of packet reception times. Packets should arrive in expected intervals to have the best call quality. < 20 ms is good >30 ms but < than 45 ms is ok >45 ms is bad Avg. Round Trip Average time for a packet to be sent to the server and an acknowledgement to be sent back. < 200 ms is good > 200 ms is poor > 500 ms is bad
- 9. Avg. packet loss rate When you are on a VoIP call, the conversation is encoded in a series of packets that must all arrive in order at the other side for the conversation to continue to make sense. Packet loss occurs when packets are either don’t arrive at their destination or they are dropped because they potentially arrived too late to be played. <=3% - Good >5%< 7% - Will impact audio >7%<10% - Threshold >10% - bad >50% - no chance Avg. network MOS degradation Average network MOS degradation is an integer represents the amount of the MOS value lost to network affects. > 1 is not good > 0.5 and < 1 is threshold < 0.5 represents acceptable degradation. Avg. concealed samples ratio Concealing audio samples is a technique used to deal with dropped network packets. Average concealed samples Ratio (%) is the % of packets that were concealed. < 2% is good > 3% is not good > 7% is bad
- 15. Using this report, we can easily pinpoint commonalities of where poor calls are coming from/going. Just by looking quickly at this Location Report, can someone tell me where there might be an issue here? Bonus Question – Why might this be an issue?
Editor's Notes
- Report Category Description Dashboard Report The Monitoring Dashboard report delivers a snapshot of all of the other reports. This report gives you a quick statistic driven breakdown of your Lync system performance. The report is broken down into the past week starting from Sunday to present, and the Trend of the past 6 weeks displayed in a line graph to give you a visual representation of trends, the report can also be displayed System Usage Reports Number of unique users that registered to the Lync system. This report gives you a good idea of system load. The first categories in each section (Totals) are clickable and allow you to have a deeper look into the week’s reports. Call Diagnostic Reports (per-user) Breaks down how the system is used. How many IM sessions, conferences. Allows you to see exactly how Lync is used within the organization. Call Diagnostic Reports Failure and poor quality rates on sessions. Gives you a window into where failures and problems might exist. Searchable by user. Media Quality Diagnostic reports Poor quality rates for calls and conferences, top servers for poor quality.
- There are a number of metrics that Lync uses to determine a call’s quality. Each of these metrics can and will adversely affect a call. If one of the metrics cross a threshold, it is marked as red on the call and the call is marked as a poor quality call. Please note this is a strictly a numerical grading of the call, the participant perception of the call might be that they call was just fine. This occurs because in some instances Lync is able to correct for the network issue.
- MOS (Mean Opinion Score)- interestingly enough this measure was once calculated by people listening to calls and offering their perception of the quality of the call.
- MOS (Mean Opinion Score)- interestingly enough this measure was once calculated by people listening to calls and offering their perception of the quality of the call.
- Other recommendations Try to restrict using Lync over wireless, or at least see if QOS can be setup on wireless networks/ Try not to use Lync over VPN connections. Depending on the speed of decryption and how busy the VPN server is, issues could arise because Lync packets are already encrypted and are real time packets, sometimes when decrypting over the VPN packets get lost or times get extended and call issues start to occur. Microsoft recommends using split tunnels where instead over the VPN Lync traffic is blocked from the VPN (DNS lookups as well) and sent over the internet via the Edge server instead. This is called split tunnel.