Export (0) Print
Expand All

Failure Distribution Report

 

Topic Last Modified: 2011-02-01

The Failure Distribution report provides an analysis of failed sessions.

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 Failed Distribution Report enables you to filter on such things as the activity type (peer-to-peer session or conferencing session) or by the diagnostic ID that accompanied each failed session.

The following table lists the filters that you can use with the Failure Distribution Report.

Failure Distribution 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.

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.

Activity type

Type of activity to filter on. Select one of the following:

  • [All]
  • Peer-to-peer
  • Conference

Session category

Indicates whether the activity in question succeeded or failed. Select one of the following:

  • [All]
  • Success
  • Expected failure
  • Unexpected failure

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.

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.

The following table lists the information provided in the Failure Distribution Report based on the most frequently reported diagnostic ID.

Metrics for Top Diagnostic Reasons

Name Can you sort on this item? Description

Rank

No

Relative ranking of failed sessions based on diagnostic IDs. The diagnostic ID is a unique identifier (in the form of an ms-diagnostics header) attached to a SIP message that often provides information useful in troubleshooting errors.

Top diagnostic reasons

No

Diagnostic ID generated in a session.

Sessions

No

Total number of failed sessions where the specified diagnostic ID was generated.

The following table lists the information provided in the Failure Distribution Report based on the session modalities that experienced the most failures.

Metrics for Top Modalities

Name Can you sort on this item? Description

Rank

No

Relative ranking based of failed session based on session type (for example, audio/video conference or peer-to-peer file transfer).

Top modalities

No

Session type.

Sessions

No

Total number of failed sessions involving the specified modality.

The following table lists the information provided in the Failure Distribution Report based on the pools that experienced the most failures.

Metrics for Top Pools

Name Can you sort on this item? Description

Rank

No

Relative ranking of failed sessions based on the Registrar pool or Edge Server where the session was conducted.

Top pools

No

Name of the Registrar pool or Edge Server.

Sessions

No

Total number of failed sessions per Registrar pool or Edge Server.

The following table lists the information provided in the Failure Distribution Report based on the computers that experienced the most failures.

Metrics for Top Sources

Name Can you sort on this item? Description

Rank

No

Relative ranking failed sessions per computer.

Top sources

No

Name of the computer involved in the failed session.

Sessions

No

Total number of failed sessions per computer.

The following table lists the information provided in the Failure Distribution Report based on the Microsoft Lync Server 2010 components that experienced the most failures.

Metrics for Top Components

Name Can you sort on this item? Description

Rank

No

Relative ranking of failed sessions based on Lync Server 2010 component (for example, ExumRouting, GroupChat, MediationServer,).

Top components

No

Name of the component involved in the failed session.

Sessions

No

Total number of failed sessions per component.

The following table lists the information provided in the Failure Distribution Report based on users who experienced the most failures when they tried to call someone else (known as "From" users).

Metrics for Top From Users

Name Can you sort on this item? Description

Rank

No

Relative ranking of failed sessions based on the user who was invited to join the session.

Top from users

No

SIP address of the user invited to join the session.

Sessions

No

Total number of failed sessions per user.

The following table lists the information provided in the Failure Distribution Report based on the users who experienced the most failures when another user tried to call them (known as "To" users).

 

Name Can you sort on this item? Description

Rank

No

Relative ranking of failed sessions based on the user who initiated the session.

Top to users

No

SIP address of the user who initiated the session.

Sessions

No

Total number of failed sessions per user.

The following table lists the information provided in the Failure Distribution Report based on the endpoint software that experienced the most failures.

Metrics for Top User Agents

Name Can you sort on this item? Description

Rank

No

Relative ranking of failed sessions based on the user agent (software) involved in the session. For example: RTCC/4.0.0.0 Inbound Routing/4.0.0.0.

Top user agents

No

Name of the user agent involved in the failed session.

Sessions

No

Total number of failed sessions per user agent.

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft