You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

  1. 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"

  2. If stack trace doesn't have symbols then use https://etwiki.sys.comcast.net/pages/viewpage.action?spaceKey=CPE&title=Producing+stack+traces+from+google+breakpad+minidump procedure to get manual stack trace.
    - 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. If the crash has been reported more than 3 ago, please check JIRA for similar issues.
    3. 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 XRE connection is disconnected.
    1. Check why receiver is sending the tune request.
    2. Request receiver 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.
    2. http-proxy configuration only valid for Comcast VOD and CDVR content.
  • No labels

DISCLAIMER: Please note that the use of the RDK Wiki is subject to its Privacy Policy & Terms of Use. In addition, this Wiki may be accessed by all RDK licensees and their contractors.