Diagnostic Report in Lync Server 2013
Topic Last Modified: 2014-02-07
The Diagnostic Report provides diagnostic and troubleshooting information for a failed session. This information includes both the Diagnostic ID and the Diagnostic header that were reported when the session failed. The Diagnostic ID is a unique identifier (in the form of an ms-diagnostics header) that gets attached to a SIP message, while the Diagnostic header provides an accompanying description for the Diagnostic ID. The report might also contain valuable troubleshooting details that are known by the reporting component. For example:
The cause code provided by the PSTN gateway that generated the failure. When an outgoing call fails on the PSTN network, an ISDN User Part (ISUP) cause code is automatically generated. For example, a PSTN gateway might send cause code 34 to indicate that no circuit or channel was available for completing the call.
Peer FQDN, port, and Winsock errors for connectivity failures.
Names being looked up for DNS resolution failures. DNS resolution takes place any time a client contacts a name server and requests the IP address that corresponds to specified device name.
Accessing the Diagnostic Report
The Diagnostic Report can be accessed by clicking the Diagnostic Report (Detail) metric on either the Peer-to-Peer Session Detail Report in Lync Server 2013 or the Conference Detail Report.
Filters
None. You cannot filter the Diagnostic Report.
Metrics
The following table lists the information provided in the Diagnostic Report for each session.
Diagnostic Report Metrics
| Name | Can you sort on this item? | Description |
|---|---|---|
Report time |
No |
Date and time that the report was recorded. |
Response code |
No |
SIP response code sent when the session failed. |
Request type |
No |
SIP request type that failed. For example, INVITE, BYE, or SERVICE. |
Source |
No |
Source of the error. |
From user URI |
No |
SIP address of the user who initiated the session. |
From user agent |
No |
Software used by the endpoint of the user who initiated the session. |
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. |
Content type |
No |
Type of media content that failed. For example, a common content type is Application/sdp. Session Description Protocol (SDP) is a standard Internet protocol used for session announcements, session invitations, and other forms of multimedia session initiation. |
Application |
No |
Application involved in the error. |
To user URI |
No |
SIP address of the user who was invited to the session. |
Conference join times (ms) |
No |
Amount of time (in milliseconds) it took for the user to join the conference. |
Diagnostic header |
No |
Diagnostic ID description. |
A list of diagnostic errors can be found on the Ms-Diagnostics Header page.