How to File a Bug Report

Short guide on what you should include in an OpenSIPS bug report on the mailing lists or 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

• relevant OpenSIPS logs. The higher logging level, the better (ideally log_level = 4, which is the DEBUG level).
• a network capture (e.g. .txt, .pcap, .pcapng) of your problematic SIP signaling.
• a way of replicating the issue (if possible)
• your opensips.cfg[*], or sections of it which are relevant to the bug in question. Plenty of bugs are caused by unorthodox usage of the scripting language.
• if it's a crash, please try to extract a full gdb backtrace. If you cannot generate a corefile, go here. Otherwise:
  • open the corefile with gdb opensips path/to/corefile
  • bt full

[*] If privacy is a concern, you may email any sensible details to bogdan@opensips.org, razvan@opensips.org or liviu@opensips.org.