Failure List Report in Lync Server 2013

Artikkeli
07/23/2014

Topic Last Modified: 2012-07-02

The Failure List report provides information about the individual participants who took part in a failed peer-to-peer or conferencing session. This information includes the URI of the user who experienced the problem, as well as the SIP Response code and Diagnostic ID associated with the failure.

Accessing the Failure List Report

The Failure List Report is accessed by clicking any of the following metrics on the Failure Distribution Report in Lync Server 2013:

Top diagnostic reasons (sessions)
Top modalities (sessions)
Top pools (sessions)
Top sources (sessions)
Top components (sessions)
Top from users (sessions)
Top to users (sessions)
Top from user agents (sessions)

From the Failure List Report you can access the Peer-to-Peer Session Detail Report in Lync Server 2013 by clicking the Session detail metric for a peer-to-peer session. You can also access the Conference Detail Report by clicking the Conference metric for a conference.

Making the Best Use of the Failure List Report

In the Failure List Report, you can view a description for each Response code or each Diagnostic ID simply by holding your mouse over that value. For example, if you hold your mouse over Diagnostic ID 7025 you'll see the following displayed in a tooltip:

Internal server error creating media for user.

It's important to note that the Failure List Report does not provide a straightforward way to directly retrieve a list of all the users who participated in at least one failed session, nor does it provide a way to determine which users were most-often involved in a failed session. (For one thing, the Failure List Report has no filtering capabilities.) However, if you export the data and then convert it to a comma-separated values file, you can use Windows PowerShell to find the answers to questions like those. For example, suppose you save the data to a .CSV file named C:\Data\Failure_List.csv. Based on the data saved in that file, this command lists all the users who were involved in at least one failed session:

$failures = Import-Csv -Path " C:\Data\Failure_List.csv"
$failure |Sort-Object "From user" | Select-Object "From user" -Unique

That command will return a list similar to this:

From user
----
Pilar.Ackerman@litwareinc.com
Henrik.Jensen@litwareinc.com
Gilead.Amosnino@litwareinc.com
David.Ahs@litwareinc.com
Ken.Myer@litwareinc.com

These two commands report back the total number of failed sessions that each user was involved in:

$failures = Import-Csv -Path "C:\Data\Failure_List.csv"
$failures | Group-Object "From user" | Select-Object Count, Name | Sort-Object -Property Count -Descending

That will return data similar to this:

Count    Name
 -----    ----
    20    Pilar.Ackerman@litwareinc.com
    20    David.Ahs@litwareinc.com
    16    Gilead.Amosnino@litwareinc.com
    16    Ken.Myero@litwareinc.com
    14    Henrik.Jensen@litwareinc.com

Filters

None. You cannot filter the Failure List Report.

Metrics

The following table lists the information provided in the Failure List Report for each failed call.

Failure List Report Metrics

Name	Can you sort on this item?	Description
Reported time	No	Date and time the report was recorded.
Request	No	SIP request type that failed. For example, INVITE or BYE.
Response code	No	SIP response code sent when the conference failed.
Diagnostic ID	No	Unique identifier (in the form of an ms-diagnostics header) attached to a SIP message that often provides information useful in troubleshooting errors.
Join cost time (ms)	No	Amount of time (in milliseconds) required for the user to join the conference.
From user	No	SIP address of the user who initiated the call.
From user agent	No	Software used by the endpoint of the user who initiated the call.
To user	No	SIP address of the user who was being called.

Jaa