Topic Last Modified: 2011-02-03
The Top Failures report provides a list of the most frequent failures and their trends over time.
Filters
Filters provide a way for you to return a more finely-targeted set of data or to view the returned data in different ways. For example, the Top Failures Report enables you to filter the returned data based on such things as the activity type (peer-to-peer session or conferencing session) or by the SIP response code that accompanied the failed session. You can also choose how data should be grouped. In this case, usages are grouped by hour, day, week, or month.
The following table lists the filters that you can use with the Top Failures Report.
Top Failures Report Filters
| Name | Description |
|---|---|
|
From |
Start date/time for the time range. To view data by hours, enter both the start date and time as follows: 1/1/2011 1:00 PM If you do not enter a start time, the report automatically begins at 12:00 AM on the specified day. To view data by day, enter just the date: 1/1/2011 To view by week or by month, enter a date that falls anywhere within the week or month that you want to view (you do not have to enter the first day of the week or month): 1/3/2011 Weeks always run from Sunday through Saturday. |
|
To |
End date/time for the time range. To view data by hours, enter both the end date and time as follows: 1/1/2011 1:00 PM If you do not enter an end time, the report automatically ends at 12:00 AM on the specified day. To view data by day, enter just the date: 1/1/2011 To view by week or by month, enter a date that falls anywhere within the week or month that you want to view (you do not have to enter the first day of the week or month): 1/3/2011 Weeks always run from Sunday through Saturday. |
|
Activity type |
Type of activity. Select one of the following:
|
|
Modality |
At this time the only option available is [All]. |
|
Pool |
Fully qualified domain name (FQDN) of the Registrar pool or Edge Server. You can either select an individual pool or click [All] to view data for all the pools. This drop-down list is automatically populated for you based on the records in the database. |
|
Category |
Type of failure experienced. Select one of the following:
An "expected failure" is a failure that is expected to happen. For example, if a user has set his or her status to Do Not Disturb you would expect any call to that user to fail. An "unexpected failure" is a failure that occurs in what would appear to be an otherwise healthy system. For example, a call should not be terminated if the caller is placed on hold. If that occurs, that would be flagged as an unexpected failure. |
|
Response code |
SIP response code sent when the conference failed. Enter the entire response code For example: 400 |
|
Diagnostic ID |
Unique identifier (in the form of an ms-diagnostics header) attached to a SIP message that often provides information useful in troubleshooting errors. Diagnostics headers are optional (it is possible to have SIP sessions that do not include these headers), and diagnostic IDs are reported only for sessions that experienced problems of some kind. |
Metrics
The following table lists the information provided in the Top Failures Report.
Top Failures Report Metrics
| Name | Can you sort on this item? | Description |
|---|---|---|
|
Rank |
Yes |
Relative rank based on the number of reported sessions. |
|
Reported sessions |
Yes |
Total number of failed sessions based on diagnostic ID and SIP response code. |
|
Users impacted |
Yes |
Total number of users affected by the failed session. |
|
Failure information |
No |
Detailed information about the failure, including diagnostic ID, SIP response code, and description of why the session failed. |
|
Trend in the past |
No |
Graphs failed sessions over time. |