Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Triage Guidelines

Created on June 21, 2022
  1. Before embarking on issue, Check is there any similar ticket which is working in team
    1. – Search with a keywords(like signature, trickplay…) in Jira to know if any similar issue.
    2. – 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”
  2. If stack trace doesn’t have symbols then use Google Breakpad to get manual stack trace.
    1. – Try to search for the latest occurrence of the crash trace from crash portal.
  3. For crash issues:
    1. Always check for the latest occurrence from the crash portal.
    2. Always check WPE framework log around the crash time and see if there is any abnormality with ocdm plugin around the time. 

  4. For any playback related issues always ensure the following.
    1. Whether Manifest download is successful.
    2. Submanifest (HLS) download is successful.
    3. Fragment download is successful.
    4. Ensure License is acquired from the licensing server.
    5. Ensure the pipeline is constructed successfully.
    6. Ensure the pipeline received the first video segment from the callback. 
  5. TDK related issues
    1. Instead of bringing up TDK setup, we can run directly with aampcli binary to reproduce issue.
  6. For any config mismatch or not reflected issues from fog or aamp.
    1. Compare the automation logs and box logs to find any mismatch.
    2. Check the latest codebase if the variables are present.
  7. For any playback tune failures during STB standby mode or when UI connection is disconnected.
    1. Check why main UI application is sending the tune request.
    2. Request main UI application team to have a look, as tune during standby or disconnected state is an invalid scenario.
  8. 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.   
    1. Don’t use RFC/aamp.cfg to configure http-proxy for IP_Linear playback.