The failure alert contains the Failure Details section, which provides specific details of the actual failure. The Failure Details section displays information based on the scenario failing, for example the table below details the failure details for an Audio Conference Scenario failure.
|
Failure Details Section Fields |
Description of Field |
|
Failed Step |
Provides a sequence of the user’s behaviors associated with the relevant Scenario. For each behavior the failed step outlines whether the step was successful, in addition to which step failed. This information is important, as it not only provides an understanding of the true end user impact, but it also assists in the identification of components that may be involved with the issue.
Example: If the failed step states ‘Attempt to connect and logon to the Lync or Skype for Business Server’, then the Lync or Skype for Business Access Proxies or Lync or Skype for Business Pool are the most likely causes of the failure. However, if the step that failed is associated with media flow, then the failure is potentially an associated gateway. |
|
Message |
Provides the SIP error code and text received with the SIP response that resulted in the failure. |
|
Conference Web URL |
Provides the URL that failed in the audio conference scenario. |
|
HTTP Response |
The response received from the web server providing meeting join capabilities. |
|
Conference URI |
The unique conference meeting URI. |
An example of a failure Alert is detailed below.