• Article

UC-to-UC Summary/Trend Report

Topic Last Modified: 2009-03-06

The UC-to-UC Summary/Trend report shows a snapshot of the higher-level media-quality trends in unified communications-to-unified communications (UC-to-UC) calls in the network. It includes the following metrics:

  • Packet Loss
  • Jitter
  • Round Trip Time
  • Network MOS
  • Network MOS Degradation
  • Conversational MOS
  • Sending MOS
  • Listening MOS

At the top of the report, each of these metrics is shown in a summary table. Below the table are graphs for each metric, plotted according to the granularity specified in the report. Each plot point in the graphs is labeled with the number of samples reported during that time period, as well as the average value of those samples. You can click each plot point in the graph to see a call list for the period represented by that plot point.

In the table at the top of the main report, you can click the Network MOS, Network MOS Degradation, Conversational MOS, Sending MOS, or Listening MOS to see a graph that shows the distribution of scores for that metric.

Note

In general, a sample size of less than 30 has too large a margin of error to provide a useful mean opinion score (MOS).

Dd572852.2f491e92-c2df-4760-a02f-22fe9b5238ea(en-us,office.13).jpg

Filters

You can view the report with a granularity of hourly, daily, weekly, or monthly. Daily and hourly trends can be useful to see how the network performs during peak daily usage, while weekly and monthly rates can help you see longer-term trends, especially as new users are added or network hardware is updated.

The number of points to be plotted must be between 2 and 24. If you choose a granularity, and start and end times, that would cause there to be more than 24 points to be plotted, the report will truncate the end time to make it fit within the plot point limit.

Additionally, you can filter the data in this report based on the following:

  • Exclude External Calls. Select this to exclude calls where either the sender or receiver are located outside of the enterprise network. Note that this is True by default; select False to include external calls in the report.
  • Media Connectivity. Use this to choose only calls that are directly connected (that is, by users within the enterprise), or calls that use the A/V Edge service or the HTTP Proxy to be connected (that is, calls that involve external users).
  • Client Type. Use this filter to view the quality of calls on specific client types, such as Office Communicator, Office Communicator Phone Edition, or Office Communications Server 2007 R2 Attendant.
  • Capture Device. Use this filter to view the quality of calls on specific devices and versions. The items in this list are generated by parsing the Quality of Experience (QoE) reports stored in the Monitoring Server database.
  • Location Scope. You can include all locations in the report, or filter it down to one or two locations (that is, selected in Location 1 and Location 2), or even to specific callers within those locations (that is, selected in Caller/Callee). If you filter to specific locations, the data about all calls to or from either of those locations are shown.

Scenario

  • Your deployment is rolling out new IP phones, in addition to its current Office Communicator use, and you want to track the media quality of the new phones. Examine this report twice, once with the Client Type filter set to Communicator and then with it set to IP phone, to see the relative quality of internal calls with the new phones.
  • You have been receiving complaints about audio quality on calls. Most complaints are about calls in the afternoons. You use the Summary/Trend report to see the hourly trends, and see that packet loss peaks in the afternoon, which is the peak call time. This indicates the routers are likely losing packets due to network congestion, and an improvement in network capacity can likely solve the audio quality problem.