Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  1. Sign up for an account
    Account signup for community services (including JIRA, Confluence and FishEye/Crucible) can be found at
  2. Create a new issue in the tracker
    Select the Create Issue button in the top right hand corner of the page. This will prompt you for the project and issue type. Pick the ASTERISK project, and choose an appropriate issue type. The following are the supported issue types:

    • Bug

    • New feature

    • Improvement


      Please do not select the Information request issue type. This type is not currently used, and your issue is likely to be closed or redefined.

  3. Fill out the issue form
    For a bug you must include the following information:

    • Concise and descriptive summary

      • Accurate and descriptive, not prescriptive. Provide the facts of what is happening and leave out assumptions as to what the issue might be.

      • Good example: "Crash occurs when exactly twelve SIP channels hang up at the same time inside of a queue"

      • Bad Examples: "asterisk crashes" , "problem with queue", "asterisk doesn't work", "channel hangups cause crash"

    • Operating System detail (Linux distribution, kernel version, architecture etc)

    • Asterisk version (exact branch and point release, such as

    • Information on any third party software involved in the scenario (database software, libraries, etc)

    • Frequency and timing of the issue (does this occur constantly, is there a trigger? Every 5 minutes? seemingly random?)

    • Symptoms described in specific detail ("No audio in one direction on only inbound calls", "choppy noise on calls where trans-coding takes place")

    • Steps required to reproduce the issue (tell the developer exactly how to reproduce the issue, just imagine you are making steps for a manual)

    • Workarounds in detail with specific steps (if you found a workaround for a serious issue, please include it for others who may be affected)

    • Debugging output - You'll almost always want to include extensions.conf, and config files for any involved component of Asterisk. Depending on the issue you may also need the following:

      • For crashes, provide a backtrace generated from an Asterisk core dump. See Getting a Backtrace for more information.

      • For apparent deadlocks, you may need to enable the compile time option DEBUG_THREADS. A backtrace may also be necessary. See Getting a Backtrace for more information.
      • For memory leaks or memory corruptions, Valgrind may be necessary. Valgrind can detect memory leaks and memory corruptions, although it does result in a substantial performance impact.
      • For debugging most problems, a properly generated debug log file will be needed. See CLI commands useful for debugging and Collecting Debug Information for more information. Note that for issues involving SIP, IAX2, or other channel drivers, you should enable that driver's enhanced debug mode through the CLI before collecting information. A pcap demonstrating the problem may also be needed.


        Be courteous. Do not paste debug output in the description or a comment, instead please attach any debugging output as text files and reference them by file name.

  4. Submit the Issue
    Once you have created the issue, you can now attach debug as files. You are ready to wait for a response from a bug marshal or post additional information as comments. If you are responding to a request for feedback, be sure to use the workflow actions to "send back" the status to the developers.

  5. Update the issue
    If you plan to work the issue yourself, please "Acknowledge" the issue to open it and assign it to yourself.

How you can speed up bug resolution