Module: kamailio Branch: master Commit: 9f7bd4e18d04ea96fb956b697d232676c2d4705e URL: https://github.com/kamailio/kamailio/commit/9f7bd4e18d04ea96fb956b697d232676...
Author: Henning Westerholt henningw@users.noreply.github.com Committer: Henning Westerholt henningw@users.noreply.github.com Date: 2018-09-27T15:06:48+02:00
Update issue templates
---
Added: .github/ISSUE_TEMPLATE/custom.md
---
Diff: https://github.com/kamailio/kamailio/commit/9f7bd4e18d04ea96fb956b697d232676... Patch: https://github.com/kamailio/kamailio/commit/9f7bd4e18d04ea96fb956b697d232676...
---
diff --git a/.github/ISSUE_TEMPLATE/custom.md b/.github/ISSUE_TEMPLATE/custom.md new file mode 100644 index 0000000000..83993d3a80 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/custom.md @@ -0,0 +1,109 @@ +--- +name: Custom issue template +about: Kamailio issue template + +--- + +<!-- +Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. + +If you have questions about using Kamailio or related to its configuration file, +ask on sr-users mailing list: + + * http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users + +If you have questions about developing extensions to Kamailio or its existing +C code, ask on sr-dev mailing list + + * http://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev + +Please try to fill this template as much as possible for any issue. It helps the +developers to troubleshoot the issue. + +If you submit a feature request (or enhancement), you can delete the text of +the template and only add the description of what you would like to be added. + +If there is no content to be filled in a section, the entire section can be removed. + +You can delete the comments from the template sections when filling. + +You can delete next line and everything above before submitting (it is a comment). +--> + +### Description + +<!-- +Explain what you did, what you expected to happen, and what actually happened. +--> + +### Troubleshooting + +#### Reproduction + +<!-- +If the issue can be reproduced, describe how it can be done. +--> + +#### Debugging Data + +<!-- +If you got a core dump, use gdb to extract troubleshooting data - full backtrace, +local variables and the list of the code at the issue location. + + gdb /path/to/kamailio /path/to/corefile + bt full + info locals + list + +If you are familiar with gdb, feel free to attach more of what you consider to +be relevant. +--> + +``` +(paste your debugging data here) +``` + +#### Log Messages + +<!-- +Check the syslog file and if there are relevant log messages printed by Kamailio, add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site). +--> + +``` +(paste your log messages here) +``` + +#### SIP Traffic + +<!-- +If the issue is exposed by processing specific SIP messages, grab them with ngrep or save in a pcap file, then add them next, or attach to issue, or provide a link to download them (e.g., to a pastebin site). +--> + +``` +(paste your sip traffic here) +``` + +### Possible Solutions + +<!-- +If you found a solution or workaround for the issue, describe it. Ideally, provide a pull request with a fix. +--> + +### Additional Information + + * **Kamailio Version** - output of `kamailio -v` + +``` +(paste your output here) +``` + +* **Operating System**: + +<!-- +Details about the operating system, the type: Linux (e.g.,: Debian 8.4, Ubuntu 16.04, CentOS 7.1, ...), MacOS, xBSD, Solaris, ...; +Kernel details (output of `uname -a`) +--> + +``` +(paste your output here) +```