#### Pre-Submission Checklist
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [x] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
Created GitHub action script to allow building Alpine docker image.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/3420
-- Commit Summary --
* .github/workflows: added GitHub action script to build Alpine based docker image
-- File Changes --
A .github/workflows/alpine.yml (47)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/3420.patchhttps://github.com/kamailio/kamailio/pull/3420.diff
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3420
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/pull/3420(a)github.com>
<!--
Kamailio Project uses GitHub Issues only for bugs in the code or feature requests. Please use this template only for bug reports.
If you have questions about using Kamailio or related to its configuration file, ask on sr-users mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-users.lists.kamailio…
If you have questions about developing extensions to Kamailio or its existing C code, ask on sr-dev mailing list:
* https://lists.kamailio.org/mailman3/postorius/lists/sr-dev.lists.kamailio.o…
Please try to fill this template as much as possible for any issue. It helps the developers to troubleshoot the issue.
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
We would use **www_challenge** method of **auth** module on our kemi lua script.
Function is not mapped on [auth kemi](https://kamailio.org/docs/tutorials/5.3.x/kamailio-kemi-framework/mod…
so we tried to use [modf](https://kamailio.org/docs/tutorials/5.3.x/kamailio-kemi-framework/kem… but we have every time this log
```
app_lua [app_lua_api.c:1725]: sr_kemi_lua_modf(): function 'www_challenge' has fixup - cannot be used
```
We tried this call to the method on lua script
```
KSR.x.modf("www_challenge", realm, 1);
```
The question is:
are we calling method on a bad way or is not possible to call www_challenge method by kemi lua ?
<!--
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 `lsb_release -a` and `uname -a`)
-->
```
(paste your output here)
```
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3423
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3423(a)github.com>
Hi!
Using the “syft” tool from Anchore I created an SBOM for a server with Kamailio installed from Debian.
The result is quite interesting. Some notes:
- For each component (debian package) a list of licenses are made.
- The CPEs - filters for matching with NVD - are based on the debian package names, which is incorrect
I will try with a newer system, like Debian Bullseye.
My question is if we can fix this somehow by modifying meta data in our packages.
Will have to check what syft is using, but this SBOM is not
very useful….
Cheers,
/O
Examples:
"cpe": "cpe:2.3:a:kamailio-extra-modules:kamailio-extra-modules:5.3.9\\+bpo10:*:*:*:*:*:*:*",
"licenses": [
{
"license": {
"id": "Apache-1.0"
}
},
{
"license": {
"id": "BSD-2-Clause"
}
},
{
"license": {
"id": "BSD-3-Clause"
}
},
{
"license": {
"name": "Expat"
}
},
{
"license": {
"id": "GPL-2.0-only"
}
},
{
"license": {
"id": "GPL-2.0-or-later"
}
},
{
"license": {
"id": "GPL-2.0-or-later"
}
},
{
"license": {
"id": "ISC"
}
},
{
"license": {
"id": "MIT"
}
},
Hello,
it is time to make the roadmap to the next major release series v5.7.x.
In my opinion, I would try to freeze the development during the first
part of April 2023, tentatively proposing April 14 as freezing date,
being like 4 weeks from now. Then testing phase and first release
(v5.7.0) sometime during May 2023. Alternative timelines can be
proposed, of course.
If anyone wants to add new features/modules, they have to be published
till freezing date, either pushed in the git repository or proposed as
pull request.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com
Kamailio Advanced Training - Online - March 27-30, 2023 - www.asipto.com
Hi,
Currently studying SIPREC call recording, I just want to ask if Kamailio supports SIPREC or does it have modules that supports it similar to OpenSips?
https://opensips.org/docs/modules/3.4.x/siprec.html
Thank you!
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3416
You are receiving this because you are subscribed to this thread.
Message ID: <kamailio/kamailio/issues/3416(a)github.com>