In the 8D Troubleshooting Methodology, which two steps does Discipline 3, Contain Interim Actions, involve? (Choose two.)
In the 8D Troubleshooting Methodology, which two steps does Discipline 3, Contain Interim Actions, involve? (Choose two.)
In the 8D Troubleshooting Methodology, Discipline 3 focuses on isolating the problem and preventing it from escalating. Developing immediate controlled actions to isolate the problem ensures that the issue is contained while working on a permanent solution. Additionally, trying actions that bypass the issue, such as creating a temporary workaround, is also a part of containing interim actions to restore service temporarily. These two steps are aimed at managing and controlling the issue in the short term.
Avaya currently uses the online tool called Avaya Diagnostic Methodology (ADM) for partners to raise trouble tickets and receive assistance, and expects customers/partners to have performed the following tasks before raising a trouble ticket.
1. Clearly stated the problem.
2. Detailed the findings.
3. Clarified the problem.
When they receive the trouble ticket, what is the next step in ADM that Avaya Tier 3 support will perform?
After receiving the trouble ticket, the next logical step for Avaya Tier 3 support in the ADM process is to implement a solution. This involves diagnosing the issue based on the stated problem and findings, and then taking actionable steps to resolve the issue. Installing a patch, praising individuals, or updating the Knowledge Management database are not primary actions that directly address the immediate need for problem resolution.
Incoming SIP Trunking calls from Service Provider to Session Manager are failing because Avaya Session Border Controller for Enterprise (SBCE) is not sending a domain name in the TO, FROM and REQUEST headers.
What needs to be changed in SBCE to make this happen?
To ensure that Avaya Session Border Controller for Enterprise (SBCE) sends a domain name in the TO, FROM, and REQUEST headers for incoming SIP Trunking calls, navigate to the SBCE GUI. Go to Global Profiles, then Topology Hiding. Edit the SessionManager_TH profile to change the action for the To, From, and Request Headers to 'Overwrite with domain name.' This will ensure that the required domain name is included in these headers.
A customer reports that remote worker users cannot see their feature buttons. Their Avaya Session Border Controller for Enterprise (SBCE) was recently damaged and replaced due to a lightning strike. After doing some troubleshooting, support was able to see that PPM was misconfigured in the SBCE.
Which tool was used, and which symptoms were visible that pointed to this issue?
When troubleshooting issues with Avaya Session Border Controller for Enterprise (SBCE) where PPM is misconfigured, using traceSBC with PPM debugging enabled is effective. This tool would show that PPM requests are being directed incorrectly, such as going to the Utility Server instead of the Session Manager. This misrouting aligns with the reported symptoms and allows for precise identification of the misconfiguration.
Which tool has an option to debug the TLS handshake between the server and the client?
traceSM is the tool that provides an option to debug the TLS handshake between the server and the client. It is specifically designed for tracing and debugging SIP and related protocols, and it includes capabilities for monitoring TLS handshakes, which occur at the transport layer to establish secure connections.