How to File a Bug Report

Short guide on what you should include in an OpenSIPS bug report on GitHub

Minimally required troubleshooting info

• output of opensips -V. We constantly push fixes to all supported branches - knowing the version helps us isolate the problem faster.

Any of the following will help us understand the problem better

• a full gdb backtrace. If you cannot generate a corefile, (go here)[https://www.opensips.org/Documentation/TroubleShooting-Crash]. Otherwise:
  • open the corefile with gdb opensips path/to/corefile
  • bt full
• relevant OpenSIPS logs. The higher logging level, the better (ideally log_level = 4, which is the DEBUG level)
• your specific way of using the OpenSIPS scripting language, or relevant parts of it. A good portion of bugs come from unorthodox script codes. If privacy is a concern, you may email these details to [email protected], [email protected] or [email protected].
• a way of replicating the issue (if possible)