Triage Guidelines
Created on June 21, 2022
- Before embarking on issue, Check is there any similar ticket which is working in team
- – Search with a keywords(like signature, trickplay…) in Jira to know if any similar issue.
- – Search Few keywords in logs to confirm it’s not AAMP issue
grep -inr “OCDM could not be instantiated|AAMP_BUILD_INFO|aamp_tune|TELEMETRY_GATEWAY_PACKET_LOSS:100”
- If stack trace doesn’t have symbols then use Google Breakpad to get manual stack trace.
- – Try to search for the latest occurrence of the crash trace from crash portal.
- For crash issues:
- Always check for the latest occurrence from the crash portal.
-
Always check WPE framework log around the crash time and see if there is any abnormality with ocdm plugin around the time.
- For any playback related issues always ensure the following.
- Whether Manifest download is successful.
- Submanifest (HLS) download is successful.
- Fragment download is successful.
- Ensure License is acquired from the licensing server.
- Ensure the pipeline is constructed successfully.
- Ensure the pipeline received the first video segment from the callback.
- TDK related issues
- Instead of bringing up TDK setup, we can run directly with aampcli binary to reproduce issue.
- For any config mismatch or not reflected issues from fog or aamp.
- Compare the automation logs and box logs to find any mismatch.
- Check the latest codebase if the variables are present.
- For any playback tune failures during STB standby mode or when UI connection is disconnected.
- Check why main UI application is sending the tune request.
- Request main UI application team to have a look, as tune during standby or disconnected state is an invalid scenario.
- HTTP proxy feature is targeted for third party application vendors who don’t support IPv6 addressing right now. To tackle v6 addressing issue, vendors will be using a 6to4 proxy to route their traffic.
- Don’t use RFC/aamp.cfg to configure http-proxy for IP_Linear playback.
Go To Top